From 828b8f6279f5bdd0eb9d53de892209e1fd679cde Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Tue, 17 Feb 1998 20:20:19 +0000 Subject: *** empty log message *** svn path=/trunk/; revision=1642 --- fetchmail-FAQ.html | 75 +++++++++++++++++------------------------------------- 1 file changed, 23 insertions(+), 52 deletions(-) diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index 4f6b9d57..c075d349 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -10,7 +10,7 @@
Back to Fetchmail Home Page To Site Map -$Date: 1998/02/16 16:07:28 $ +$Date: 1998/02/17 20:20:19 $

Frequently Asked Questions About Fetchmail

@@ -82,7 +82,6 @@ when I may have multiple login sessions going?
R6. Fetchmail dumps core when I use a .netrc file but works otherwise.
R7. Running fetchmail in daemon mode doesn't work.
R8. Fetchmail hangs when used with pppd.
-R9. Fetchmail fails when used with a dynamic PPP link.

Disappearing mail

@@ -377,16 +376,29 @@ generally available on IMAP servers.

G9. Is any special configuration needed to use a dynamic IP address?

-No. Fetchmail itself doesn't care whether the IP address you use is -static (fixed) or dynamic (varying, allocated at connection time by -your ISP from an address pool). In fact, fetchmail normally doesn't -use your address explicitly at all; it only cares that you have a -working gateway.

+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.

-Sendmail, however, can get get confused by dynamic addresses in a way -that looks like a fetchmail problem; see R9

. +This, however, 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.

+ +Since the new IP address (looked up at RCPT TO interpretation time) +doesn't match the original, the most benign possible result is that +your MTA thinks it's seeing a relaying attempt and refuses. More +frequently, fetchmail will try to connect top a nonexistent host +address and time out. Worst case, you could up forwarding your mail +to the wrong machine!

-Only one fetchmail option interacts with your IP address at all, +Use the smtpaddress option to force the appended hostname +to one with a (fixed) IP address of 127.0.0.1 in your +/etc/hosts. (The name `localhost' will usually work; or +you can use the IP address itself).

+ +Only one fetchmail option interacts directly with your IP address, `interface'. This option can be used to set the gateway device and restrict the IP address range fetchmail will use. Such a restriction is sometimes useful for security reasons, especially on @@ -1269,47 +1281,6 @@ Your problem may be with pppd's `demand' option. We have a report that fetchmail doesn't play well with it, but works with pppd if `demand' is turned off. We have no idea why this is.

-

-

R9. Fetchmail fails when used with a dynamic PPP link.

- -The diagnostic of this problem is that your MTA, on the receiving end -of an SMTP forward from fetchmail, interprets the RCPT TO delivery -address as arequest to relay. If relaying is disabled, sendmail will -refuse with the complaint 551 ... we do not relay. If -relaying is allowed, your MTA may send a "host misconfiguration" -error notification to postmaster, and bounce the message (ouch).

- -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.

- -This, however, can create problems when your MTA is running in daemon -mode and outlasts the dynamic IP address assignment your client -machine had when the MTA started up. Since the new IP address (looked -up at RCPT TO interpretation time) doesn't match the original, your -MTA thinks it's seeing a relaying attempt and refuses.

- -The simplest way to fix this is to use the smtpaddress -option to force the appended hostname to one with a (fixed) IP address -of 127.0.0.1 in your /etc/hosts. (The name `localhost' -will usually work).

- -If your MTA is sendmail, another possible fix is to restart each time -you connect to your ISP:

- -

-        kill -HUP `head -1 /var/run/sendmail.pid`
-
- -If neither of these fixes the problem, you might have to put your -dynamic IP address in whatever your sendmail is using for a cw file -(/etc/sendmail.cw). Ryan Murray reports "my ip-up script for PPP puts -my fully qualified domain name at the bottom of /etc/hosts (building -from a template), sends the name off to sendmail.cw, restarts -sendmail, and then starts fetchmail." (This script is available in -the contrib directory of the fetchmail source distribution.)

-

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

@@ -1806,7 +1777,7 @@ Re-ordering messages is a user-agent function, anyway.

Back to Fetchmail Home Page To Site Map -$Date: 1998/02/16 16:07:28 $ +$Date: 1998/02/17 20:20:19 $

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