From b626c82489752c09374fe3feec2130205a40d1c2 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Sat, 26 Feb 2000 03:16:53 +0000 Subject: Eliminate the popclient conversion stuff. svn path=/trunk/; revision=2773 --- fetchmail-FAQ.html | 84 ++++++++++-------------------------------------------- 1 file changed, 15 insertions(+), 69 deletions(-) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index 7f4b0f00..8a6ad66b 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -10,7 +10,7 @@
Back to Fetchmail Home Page To Site Map -$Date: 2000/02/24 05:57:57 $ +$Date: 2000/02/26 03:16:53 $

Frequently Asked Questions About Fetchmail

@@ -51,8 +51,7 @@ IP address?
F1. Why does my old .fetchmailrc no longer work?
F2. The .fetchmailrc parser won't accept my all-numeric user name.
F3. The .fetchmailrc parser won't accept my host or username beginning with `no'.
-F4. I'm migrating from popclient. How do I need to modify my .poprc?
-F5. I'm getting a `parse error' message I don't understand.
+F4. I'm getting a `parse error' message I don't understand.

Configuration questions:

@@ -573,17 +572,6 @@ site.

The specific recipe for using fetchmail with a firewall is at K1

-

-

B1. Lex bombs out while building the fetchmail lexer.

- -In the immortal words of Alan Cox the last time this came up: ``Take -the Solaris lex and stick it up the backside of a passing Sun -salesman, then install flex and use that. All -will be happier.''

- -I couldn't have put it better myself, and ain't going to try now.

-

G12. Is any special configuration needed to send mail?

@@ -619,6 +607,17 @@ No. Fetchmail is a mail transport agent, best understood as a protocol gateway between POP3/IMAP servers and SMTP. Disconnected operation requires an elaborate interactive client. It's a very different problem.

+

+

B1. Lex bombs out while building the fetchmail lexer.

+ +In the immortal words of Alan Cox the last time this came up: ``Take +the Solaris lex and stick it up the backside of a passing Sun +salesman, then install flex and use that. All +will be happier.''

+ +I couldn't have put it better myself, and ain't going to try now.

+

B2. I get link failures when I try to build fetchmail.

@@ -745,60 +744,7 @@ Upgrade to a 5.0.6 or later fetchmail, or put string quotes around your token.

-

F4. I'm migrating from popclient. How do I need to modify my .poprc?

- -If you have been using popclient (the ancestor of this program) -at version 3.0b6 or later, start with this

- -

-(cd; mv .poprc .fetchmailrc)
-
- -and do fetchmail -V to see if fetchmail's parser understands -your configuration.

- -Be aware that some of popclient's unnecessary options have been -removed (see the NOTES file in the distribution for explanation). You -can't deliver to a local mail file or to standard output any more, and -using an MDA for delivery is discouraged. If you throw those options -away, fetchmail will now forward your mail into your system's normal -Internet-mail delivery path.

- -Actually, using an MDA is now almost always the wrong thing; the MDA -facility has been retained only for people who can't or won't run a -sendmail-like SMTP listener on port 25. The default, SMTP forwarding -to port 25, is better for at least three major reasons. One: it feeds -retrieved POP and IMAP mail into your system's normal delivery path -along with local mail and normal Internet mail, so all your normal -filtering/aliasing/forwarding setup for local mail works. Two: -because the port 25 listener returns a positive acknowledge, fetchmail -can be sure you're not going to lose mail to a disk-full or some other -resource-exhaustion problem. Three: it means fetchmail doesn't have -to know where the system mailboxes are, or futz with file locking -(which makes two fewer places for it to potentially mess up).

- -If you used to use -mda "procmail -d -<you>" or something similar, forward to port -25 and do "| procmail -d <you>" in -your ~/.forward file.

- -As long as your new .fetchmailrc file does not use the removed -`localfolder' option or `limit' (which now takes a -maximum byte size rather than a line count), a straight move or copy -of your .poprc will often work. (The new run control file syntax also -has to be a little stricter about the order of options than the old, -in order to support multiple user descriptions per server; thus you -may have to rearrange things a bit.)

- -Run control files in the minimal .poprc format (without the `username' -token) will trigger a warning. To eliminate this warning, add the -`username' keyword before your first user entry per server (it is -already required before second and subsequent user entries per server.

- -In some future version the `username' keyword will be required.

- -

-

F5. I'm getting a `parse error' message I don't understand.

+

F4. I'm getting a `parse error' message I don't understand.

The most common cause of mysterious parse errors is putting a server option after a user option. Check the manual page; you'll probably @@ -2654,7 +2600,7 @@ terminate it.

Back to Fetchmail Home Page To Site Map -$Date: 2000/02/24 05:57:57 $ +$Date: 2000/02/26 03:16:53 $

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