From 7e08945de54104dc78225da10cba24cadac342df Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Wed, 6 Sep 2000 16:39:25 +0000 Subject: Better sendmail configuration. svn path=/trunk/; revision=2958 --- fetchmail-FAQ.html | 54 +++++++++++++++++++++++++++++++++++------------------- 1 file changed, 35 insertions(+), 19 deletions(-) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index dd6b3781..af4485ec 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -10,7 +10,7 @@
Back to Fetchmail Home Page To Site Map -$Date: 2000/08/27 19:50:38 $ +$Date: 2000/09/06 16:39:25 $

Frequently Asked Questions About Fetchmail

@@ -1025,12 +1025,7 @@ in sendmail's configuration, you can leave the rewrite option off.

If your sendmail complains ``sendmail does not relay'', make sure -your sendmail,cf file says - - -Cwlocalhost - - +your sendmail.cf file says Cwlocalhost so that sendmail recognizes `localhost' as a name of its host.

If you're mailing from another machine on your local network, also @@ -1057,16 +1052,38 @@ mailserver's sendmail.cf file, it's a good idea to add this rule:

H?l?Delivered-To: $h -and declare `envelope "Delivered-To:"'. This will cause the -mailserver's sendmail to reliably write the appropriate envelope -address into each message before fetchmail sees it, and tell fetchmail -which header it is. With this change, multidrop mode should work -reliably even when the Received header omits the envelope address -(which will typically be the case when the message has multiple -recipients).

+This will cause the mailserver's sendmail to reliably write the +appropriate envelope address into each message before fetchmail sees +it, and tell fetchmail which header it is.  With this change, +multidrop mode should work reliably even when the Received header +omits the envelope address (which will typically be the case when +the message has multiple recipients).  However it will still not +distinguish the recipients, your only advantage is that no bounce +will be sent if a message is BCC addressed to multiple users at +your site.  To fix even that problem, you might want to try the +following hack, which is however untested and quite experimental:

+ +

+H?l?Delivered-To: $u
+
+Mmdrop,	P=/usr/bin/procmail, 
+	F=lsDFMqSPfhnu9, 
+	S=EnvFromSMTP/HdrFromSMTP, 
+	R=EnvToSMTP/HdrToSMTP,
+	T=DNS/RFC822/X-Unix,
+	A=procmail -Y -a $u -d $h
+
-Martijn Lievart has a more detailed recipe in the contrib subdirectory -of the fetchmail source distribution. +For both hacks, you have to declare `envelope "Delivered-To:"' on +the fetchmail side, to put the virtual domain (e.g. `domain.com') +with RELAY permission into your access file and to add a line +reading `domain.com local:local-pop-user' for the first and +`domain.com mdrop:local-pop-user' for the second hack to your +mailertable.

+ +Feel free to try Martijn Lievaart's detailed recipe in the contrib +subdirectory of the fetchmail source distribution, it attempts +to address this problem with an external script.

T2. How can I use fetchmail with qmail?

@@ -1675,8 +1692,7 @@ man page for several authentication methods.)

 poll mailhost port 1234 via localhost with proto pop3:
-        preconnect "ssh -f -L 1234:mailhost:110 mailhost
-        </dev/null >/dev/null; sleep 5";
+        preconnect "ssh -l username -f mailhost -L 1234:mailhost:110 sleep 5"
The sleep is needed on slower machines to prevent fetchmail from @@ -2892,7 +2908,7 @@ install Linux on your server...

Back to Fetchmail Home Page To Site Map -$Date: 2000/08/27 19:50:38 $ +$Date: 2000/09/06 16:39:25 $

Eric S. Raymond <esr@snark.thyrsus.com>
-- cgit v1.2.3