Differences between revisions 8 and 9
Revision 8 as of 2006-02-13 12:21:02
Size: 4195
Editor: ZugSchlus
Comment: add drec question
Revision 9 as of 2006-03-06 13:44:31
Size: 4480
Editor: ZugSchlus
Comment:
Deletions are marked like this. Additions are marked like this.
Line 83: Line 83:
=== My does my exim HELO as localhost.localdomains with TLS connections === === Why does my exim HELO as localhost.localdomain ===
Line 92: Line 92:

----------

=== How do I configure a catch-all? ===

Answer not yet fleshed out.

  * {{{*: target}}} in {{{/etc/aliases}}}
  * break the loop by aliasing the target account to itself
  * other aliases take precedence, alias exceptions to themselves
  * catch-all is a real bad idea these days

1. Debian Exim4 User FAQ

This is work in progress, so it is probably not yet very helpful.

?TableOfContents


1.1. Questions not categorized yet

1.1.1. How do I re-execute the debconf-driven configuration?

  • dpkg-reconfigure exim4-config
  • $EDITOR /etc/exim4/update-exim4.conf.conf
  • Further reading: man update-exim4.conf


1.1.2. When I try to deliver a message via SMTP to my Exim, I get "550 relay not permitted"

Answer not yet fleshed out.

  • dc_relay_nets
  • If client host is on dynamic IP, SMTP AUTH
  • ISP blocking tcp/25


1.1.3. I cannot connect to my Exim from my home connection. From internet hosts, it works

Answer not yet fleshed out.

  • ISP blocking tcp/25
  • Use ISP Smarthost
  • Use tcp/587
  • ISP blocking incoming tcp/25 => no chance to have an MX there


1.1.4. I am trying to have exim forward mail to some internal hosts, but all I am getting is "all relevant MX records point to non-existent hosts"

A probeble cause for this might be that all MX records for the offending domain point to site local or link local IP addresses, which are ignored by the dnslookup router to protect from misconfigured external domains. The default configuration has relaxed checking for domains that the local system is configured to allow relaying to, so adding the offending domain to dc_relay_domains will most probably help.

Please note that no domain on the public Internet should have MX records pointing to site local or link local IP addresses, so you might check your externally visible MX records.

If this doesn't help, try analyzing the output of exim -d -bt some.local.part@the.offending.domain.example

[http://www.exim.org/eximwiki/FAQ/Routing_to_remote_hosts/Q0302 Upstream Exim FAQ Q0302] might help as well.


1.1.5. What do "lowest numbered MX record points to local host" or "remote host address is the local host" mean?

This is covered in [http://www.exim.org/eximwiki/FAQ/Routing_to_remote_hosts/Q0301 Upstream Exim FAQ Q0301.] The Debian default configuration has the hubbed_hosts router mentioned there already defined. Its configuration file is /etc/exim4/hubbed_hosts, and some documentation can be found in /etc/exim4/conf.d/router/150_exim4-config_hubbed_hosts.


1.1.6. What do the "DEBCONFfooDEBCONF" macros in the Debian configuration do?

When the Exim daemon is started, the dpkg-conffiles in /etc/exim4 are post-processed to the result /var/lib/exim4/config.autogenerated, which is the configuration file that Exim reads. In this post-processing step, done by update-exim4.conf, the DEBCONFfooDEBCONF strings are replaced with values pulled from /etc/exim4/update-exim4.conf.conf and system configuration.

Please note that the string DEBCONF is kind of a misnomer since the strings are _not_ directly pulled from the Debconf database, but from user-editable conffiles instead. This is a common misunderstanding.

For more information, read the update-exim4.conf man page.


1.1.7. I am experiencing timeout issues with TLS connections

Answer not yet fleshed out.

  • GnuTLS Entropy issue
  • Kernel not generating enough entropy
    • network removed
  • /proc/sys/kernel/random/entropy_avail
  • hardware RNG
  • audio in RNG
  • Rebuild exim 4.60-3+ with OpenSSL


1.1.8. Why does my exim HELO as localhost.localdomain

Answer not yet fleshed out.

  • The name used in EHLO/HELO is pulled from configuration option primary_hostname

  • Debian's exim4 default configuration does not set primary_hostname

  • exim then defaults to uname() to find the host name. If that call only returns one component, gethostbyname() or getipnodebyname() is used to obtain the fully qualified host name.

  • Most frequent cause for localhost.localdomain is the default /etc/hostname created by Debian installation.

  • The recommended way is to fix the system instead of forcing exim to the intended host name.


1.1.9. How do I configure a catch-all?

Answer not yet fleshed out.

  • *: target in /etc/aliases

  • break the loop by aliasing the target account to itself
  • other aliases take precedence, alias exceptions to themselves
  • catch-all is a real bad idea these days