From 0e6209d16ed63bd59728ed54822180a57ae1face Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Wed, 16 Dec 1998 16:54:21 +0000 Subject: FAQ cleanup. svn path=/trunk/; revision=2279 --- fetchmail-FAQ.html | 37 +++++++++++++++++++++---------------- 1 file changed, 21 insertions(+), 16 deletions(-) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index aea4bf5b..899ea8e5 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -10,7 +10,7 @@
Back to Fetchmail Home Page To Site Map -$Date: 1998/12/14 15:10:26 $ +$Date: 1998/12/16 16:54:19 $

Frequently Asked Questions About Fetchmail

@@ -96,7 +96,7 @@ IP address?

Disappearing mail

D1. I think I've set up fetchmail correctly, but I'm not getting any mail.
-D2. All my mail seems to disappear after an interrupt.
+D2. All my mail seems to disappear after a dropped connection.
D3. Mail that was being fetched when I interrupted my fetchmail seems to have been vanished.

Multidrop-mode problems:

@@ -199,7 +199,7 @@ It is helpful if you include your .fetchmailrc file, but not necessary unless your symptom seems to involve an error in configuration parsing.

If fetchmail seems to run and fetch mail, but the headers look mangled -(that is headers are missing, or blank lines are inserted in the +(that is, headers are missing or blank lines are inserted in the headers) then read the FAQ items in section X before submitting a bug report. Pay special attention to the item on diagnosing mail mangling. There are @@ -284,9 +284,9 @@ in the Subject line unsubscribes you, and "help" returns general list help)

G6. So, what's this I hear about a fetchmail paper?

-Now it can be told! The fetchmail development was also a sociological -experiment, an extended test to see if my theory about the critical -features of the Linux development model is correct.

+The fetchmail development was also a sociological experiment, an +extended test to see if my theory about the critical features of the +Linux development model is correct.

The experiment was a success. I wrote a paper about it titled The @@ -449,10 +449,11 @@ his mail ;-)

Yes. In order to avoid giving indigestion to certain picky MTAs (notably exim), fetchmail always makes the RCPT TO address it feeds the MTA a fully qualified one with a hostname part. -Normally it does this by appending @ and your client machine's -hostname.

+Normally it does this by appending @ and "localhost", but when you are +using Kerberos or ETRN mode it will append @ and your machine's +fully-qualified domain name (FQDN).

-This, however, can create problems when fetchmail is running in daemon +Appending the FQDN can create problems when fetchmail is running in daemon mode and outlasts the dynamic IP address assignment your client machine had when it started up.

@@ -1664,7 +1665,7 @@ Or you may not be connecting to the SMTP listener. Run fetchmail -v and see R1.

-

D2. All my mail seems to disappear after an interrupt.

+

D2. All my mail seems to disappear after a dropped connection.

One POP3 daemon used in the Berkeley Unix world that reports itself as POP3 version 1.004 actually throws the queue away. 1.005 fixed that. @@ -1716,11 +1717,15 @@ Solution: switch to an IMAP4 server.

M1. I've declared local names, but all my multidrop mail is going to root anyway.

-Somehow your fetchmail is never matching the hostname part of -recipient names to the name of the mailserver machine. This probably -means it is unable to recognize hostname parts as being DNS names of -the mailserver, and indicates some kind of DNS configuration -problem either on the server or your client machine.

+Somehow your fetchmail is never recognizing the hostname part of +recipient names it parses out of To/Cc/envelope-header lines as +matching the name of the mailserver machine. To check this, run +fetchmail in foreground with -v -v on. You will probably see a lot of +messages with the format ``line rejected, %s is not an alias of the +mailserver'' or ``no address matches; forwarding to %s.''

+ +These errors usually indicate some kind of DNS configuration problem +either on the server or your client machine.

The easiest workaround is to add a `via' option (if necessary) and add enough aka declarations to cover all of your @@ -2207,7 +2212,7 @@ Re-ordering messages is a user-agent function, anyway.

Back to Fetchmail Home Page To Site Map -$Date: 1998/12/14 15:10:26 $ +$Date: 1998/12/16 16:54:19 $

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