diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 1997-05-13 15:36:42 +0000 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 1997-05-13 15:36:42 +0000 |
| commit | 2cbdef3efbe733325aea934ed3ffab9e9ba6175e (patch) | |
| tree | fb7137822136ee6753ae693fc486525de39e96db | |
| parent | 01cd94b5228ce4f13383212f1e83a758a1c2e9ff (diff) | |
| download | fetchmail-2cbdef3efbe733325aea934ed3ffab9e9ba6175e.tar.gz fetchmail-2cbdef3efbe733325aea934ed3ffab9e9ba6175e.tar.bz2 fetchmail-2cbdef3efbe733325aea934ed3ffab9e9ba6175e.zip | |
Better exim caveats.
svn path=/trunk/; revision=991
| -rw-r--r-- | fetchmail-FAQ.html | 41 |
1 files changed, 32 insertions, 9 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index 6923ad05..bc61da64 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -9,8 +9,8 @@ <BODY> <H1>Frequently Asked Questions About Fetchmail</H1> -The current version of fetchmail is 3.9.3. New in the FAQ: <a -href="#T3">T3</a> on using fetchmail with smail.<p> +The current version of fetchmail is 3.9.3. New in the FAQ: improved +version of <a href="#T2">T2</a> on using fetchmail with exim.<p> Before reporting any bug, please read <a href="#G3">G3</a> for advice on how to include diagnostic information that will get your bug fixed @@ -650,15 +650,38 @@ in the alias directory (normally /var/qmail/alias) with the contents:<p> Note this <em>does</em> require a modern /bin/sh.<p> <hr> -<h2><a name="T2">T2. How can I use fetchmail with exim?</a></h2> +<h2><a name="T2">T2. How can I use fetchmail with exim?</a></h2><p> -There is a switch somewhere in exim's configuration files that allows -it to accept domainless MAIL FROM addresses; you may have to flip that -if you're running a fetchmail version prior to 3.9.3. Otherwise -you're all set.<p> +By default, the exim listener enforces the the RFC1123 requirement +that MAIL FROM addresses you pass to it have to be canonical +(e.g. with a fully qualified hostname part). <p> + +This is a potential problem if the MTAs upstream from your fetchmail +don't necessarily pass canonicalized From and Return-Path addresses, +and fetchmail's <TT>rewrite</TT> option is off. The specific case +where this has come up involves bounce messages generated by sendmail +on your mailer host, which have the (un-canonicalized) origin address +MAILER-DAEMON.<p> + +The right way to fix this is to enable the <TT>rewrite</TT> option and +have fetchmail canonicalize From and Return-Path addresses with the +mailserver hostname before exim sees them.<p> + +If you must run with <TT>rewrite</TT> off, there is a switch in exim's +configuration files that allows it to accept domainless MAIL FROM +addresses; you will have to flip it by putting the line <p> + +<pre> + sender_unqualified_hosts = localhost +</pre> + +in the main section of the exim configuration file. Note that this +will result in such messages having an incorrect domain name attached +to their return address (your SMTP listener's hostname rather than +that of the remote mail server). <p> <hr> -<h2><a name="T3">T3. How can I use fetchmail with smail?</a></h2> +<h2><a name="T3">T3. How can I use fetchmail with smail?</a></h2><p> Smail 3.2 is very nearly plug-compatible with sendmail, and will work fine out of the box.<P> @@ -961,7 +984,7 @@ without hacking potentially fragile startup scripts. To get around it, just touch(1) the logfile before you run fetchmail (this will have no effect on the contents of the logfile if it already exists).<P> -$Id: fetchmail-FAQ.html,v 1.13 1997/05/11 04:35:35 esr Exp $<p> +$Id: fetchmail-FAQ.html,v 1.14 1997/05/13 15:36:42 esr Exp $<p> <HR> <ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com"><esr@snark.thyrsus.com></A></ADDRESS> |