From 461d0c77f05f6e88e34d36228e31abe20302cea0 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Wed, 16 Apr 1997 20:09:34 +0000 Subject: Added qmail material. svn path=/trunk/; revision=960 --- fetchmail-FAQ.html | 81 ++++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 70 insertions(+), 11 deletions(-) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index 374abbd7..1e1c2f3f 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -9,24 +9,23 @@

Frequently Asked Questions About Fetchmail

-$Id: fetchmail-FAQ.html,v 1.1 1997/04/16 20:05:46 esr Exp $

+$Id: fetchmail-FAQ.html,v 1.2 1997/04/16 20:09:34 esr Exp $

-(Add a link to Chris Cheyney's atexit patch.)

+(Added C6 on working with qmail)

Before reporting any bug, please read G3 for advice on how to include diagnostic information that will get your bug fixed -as quickly as possible. -

+as quickly as possible.

+ If you have a question or answer you think ought to be added to this FAQ list, mail it to fetchmail's maintainer, Eric S. Raymond, at -esr@snark.thyrsus.com. -

+esr@snark.thyrsus.com.

+ There is a fetchmail-friends reflector for people who want to discuss fixes and improvements in fetchmail. It's at -fetchmail-friends@thyrsus.com; -Eric -can put you on it. -

+fetchmail-friends@thyrsus.com +and is a SmartList reflector; sign up in the usual way.

General questions:

G1. What is fetchmail and why should I bother?
@@ -53,6 +52,7 @@ can put you on it. C3. How do I know what interface and address to use with --interface?
C4. How can I get fetchmail to work with ssh?
C5. How can I set up support for sendmail's anti-spam 571 response?
+C6. How can I use fetchmail multidrop mode with qmail?

Runtime fatal errors:

@@ -544,7 +544,66 @@ to allow sendmail to process the message further and generate an error message to the sender.

R1. I think I've set up fetchmail correctly, but I'm not getting any mail.

C6. How can I use fetchmail multidrop mode with qmail?

+ +(This information is thanks to Robert de Bath +<robert@mayday.cix.co.uk>.)

+ +If a mailhost is using the qmail package (see http://pobox.com/~djb/qmail.html) +then, providing the local hosts are also using qmail, it is possible +to setup one fetchmail link to be reliably collect the mail for an +entire domain.

+ +One of the basic features of qmail is the `Delivered-To:' message +header. Whenever qmail deliver a message to a local mailbox it puts +the username and hostname of the envelope recipient on this line. The +major reason for this is to prevent mail loops.

+ +To set up qmail to batch mail for a disconnected site the isp-mailhost +will have normally put that site in its `virtualhosts' control file so +it will add a prefix to all mail addresses for this site. This results +in mail sent to 'username@userhost.userdom.dom.com' having a +'Delivered-To:' line of the form:

+ +

+ Delivered-To: mbox-userstr-username@userhost.userdom.dom.com + + +A single host maildrop will be slightly simpler: + ++ Delivered-To: mbox-userstr-username@userhost.dom.com + + +The ISP can make the 'mbox-userstr-' prefix anything they choose +but a string matching the user host name is likely.

+ +To use this line you must:

+ +

Ensure the option `envelope Delivered-To:' is in the fetchmail + config file. + +
Ensure you have a localdomains containing 'userdom.dom.com' or + `userhost.dom.com' respectively. +

+ +So far this reliably delivers messages to the correct machine of the +local network, to deliver to the correct user the 'mbox-userstr-' +prefix must be stripped off of the user name. This can be done by +setting up an alias within the qmail MTA on each local machine. +Simply create a dot-qmail file called '.qmail-mbox-userstr-default' +in the alias directory (normally /var/qmail/alias) with the contents:

+ +

+ | ../bin/qmail-inject -a -f"$SENDER" "${LOCAL#mbox-userstr-}@$HOST}" + + +Note this does require a modern /bin/sh.

+ +

R1. I think I've set up fetchmail correctly, but I'm not getting any mail.

Maybe you have a .forward or alias set up that you've forgotten about. You should probably remove it.

-- cgit v1.2.3