1 <!doctype HTML public "-//W3O//DTD W3 HTML 3.2//EN">
4 <TITLE>The Fetchmail FAQ</TITLE>
5 <link rev=made href="mailto:esr@thyrsus.com">
6 <meta name="description" content="Frequently asked questions about fetchmail.">
7 <meta name="keywords" content="fetchmail, POP, POP2, POP3, IMAP, remote mail">
10 <table width="100%" cellpadding=0><tr>
11 <td width="30%">Back to <a href="index.html">Fetchmail Home Page</a>
12 <td width="30%" align=center>To <a href="/~esr/sitemap.html">Site Map</a>
13 <td width="30%" align=right>$Date: 2002/03/26 14:41:17 $
16 <H1>Frequently Asked Questions About Fetchmail</H1>
18 <p>Before reporting any bug, please read <a href="#G3">G3</a> for advice
19 on how to include diagnostic information that will get your bug fixed
20 as quickly as possible.
22 <p>If you have a question or answer you think ought to be added to
23 this FAQ list, mail it to fetchmail's maintainer, Eric S. Raymond, at
24 <A HREF="mailto:esr@thyrsus.com">esr@thyrsus.com</A>.
26 <h1>General questions:</h1>
28 <a href="#G1">G1. What is fetchmail and why should I bother?</a><br>
29 <a href="#G2">G2. Where do I find the latest FAQ and fetchmail sources?</a><br>
30 <a href="#G3">G3. I think I've found a bug. Will you fix it?</a><br>
31 <a href="#G4">G4. I have this idea for a neat feature. Will you add it?</a><br>
32 <a href="#G5">G5. Is there a mailing list for exchanging tips?</a><br>
33 <a href="#G6">G6. So, what's this I hear about a fetchmail paper?</a><br>
34 <a href="#G7">G7. What is the best server to use with fetchmail?</a><br>
35 <a href="#G8">G8. What is the best mail program to use with fetchmail?</a><br>
36 <a href="#G9">G9. How can I avoid sending my password en clair?</a><br>
37 <a href="#G10">G10. Is any special configuration needed to use a dynamic
39 <a href="#G11">G11. Is any special configuration needed to use firewalls?</a><br>
40 <a href="#G12">G12. Is any special configuration needed to <em>send</em> mail?</a><br>
41 <a href="#G13">G13. Is fetchmail Y2K-compliant?</a><br>
42 <a href="#G14">G14. Is there a way in fetchmail to support disconnected IMAP mode?</a><br>
43 <a href="#G15">G15. How will fetchmail perform under heavy loads?</a><br>
45 <h1>Build-time problems:</h1>
47 <a href="#B1">B1. Make coughs and dies when building on FreeBSD.</a><br>
48 <a href="#B2">B2. Lex bombs out while building the fetchmail lexer.</a><br>
49 <a href="#B3">B3. I get link failures when I try to build fetchmail.</a><br>
51 <h1>Fetchmail configuration file grammar questions:</h1>
53 <a href="#F1">F1. Why does my old .fetchmailrc no longer work?</a><br>
54 <a href="#F2">F2. The .fetchmailrc parser won't accept my all-numeric user name.</a><br>
55 <a href="#F3">F3. The .fetchmailrc parser won't accept my host or username beginning with `no'.</a><br>
56 <a href="#F4">F4. I'm getting a `parse error' message I don't understand.</a><br>
58 <h1>Configuration questions:</h1>
60 <a href="#C1">C1. Why do I need a .fetchmailrc when running as root on my own machine?</a><br>
61 <a href="#C2">C2. How can I arrange for a fetchmail daemon to get killed when I log out?</a><br>
62 <a href="#C3">C3. How do I know what interface and address to use with --interface?</a><br>
63 <a href="#C4">C4. How can I set up support for sendmail's anti-spam features?</a><br>
64 <a href="#C5">C5. How can I poll some of my mailboxes more/less often than others?</a><br>
65 <a href="#C6">C6. Fetchmail works OK started up manually, but not from an init script.</a><br>
66 <a href="#C7">C7. How can I forward mail to another host?.</a><br>
68 <h1>How to make fetchmail play nice with various MTAs:</h1>
70 <a href="#T1">T1. How can I use fetchmail with sendmail?</a><br>
71 <a href="#T2">T2. How can I use fetchmail with qmail?</a><br>
72 <a href="#T3">T3. How can I use fetchmail with exim?</a><br>
73 <a href="#T4">T4. How can I use fetchmail with smail?</a><br>
74 <a href="#T5">T5. How can I use fetchmail with SCO's MMDF?</a><br>
75 <a href="#T6">T6. How can I use fetchmail with Lotus Notes?</a><br>
76 <a href="#T7">T7. How can I use fetchmail with Courier IMAP?</a><br>
78 <h1>How to make fetchmail work with various servers:</h1>
80 <a href="#S1">S1. How can I use fetchmail with qpopper?</a><br>
81 <a href="#S2">S2. How can I use fetchmail with Microsoft Exchange?</a><br>
82 <a href="#S3">S3. How can I use fetchmail with Compuserve RPA?</a><br>
83 <a href="#S4">S4. How can I use fetchmail with Demon Internet's SDPS?</a><br>
84 <a href="#S5">S5. How can I use fetchmail with usa.net's servers?</a><br>
85 <a href="#S6">S6. How can I use fetchmail with HP OpenMail?</a><br>
86 <a href="#S7">S7. How can I use fetchmail with geocities POP3 servers?</a><br>
87 <a href="#S8">S8. How can I use fetchmail with Hotmail?</a><br>
88 <a href="#S9">S9. How can I use fetchmail with MSN?</a><br>
89 <a href="#S10">S10. How can I use fetchmail with SpryNet?</a><br>
90 <a href="#S11">S11. How can I use fetchmail with FTGate?</a><br>
91 <a href="#S12">S12. How can I use fetchmail with MailMax?</a><br>
92 <a href="#S13">S13. How can I use fetchmail with Novell GroupWise?</a><br>
93 <a href="#S14">S14. How can I use fetchmail with InterChange?</a><br>
94 <a href="#S15">S15. How can I use fetchmail with GMX?</a><br>
96 <h1>How to set up well-known security and authentication methods:</h1>
98 <a href="#K1">K1. How can I use fetchmail with SOCKS?</a><br>
99 <a href="#K2">K2. How can I use fetchmail with IPv6 and IPsec?</a><br>
100 <a href="#K3">K3. How can I get fetchmail to work with ssh?</a><br>
101 <a href="#K4">K4. What do I have to do to use the IMAP-GSS protocol?</a><br>
102 <a href="#K5">K5. How can I use fetchmail with SSL?</a><br>
104 <h1>Runtime fatal errors:</h1>
106 <a href="#R1">R1. Fetchmail isn't working, and -v shows `SMTP connect failed' messages.</a><br>
107 <a href="#R2">R2. When I try to configure an MDA, fetchmail doesn't work.</a><br>
108 <a href="#R3">R3. Fetchmail dumps core when given an invalid rc file.</a><br>
109 <a href="#R4">R4. Fetchmail dumps core in -V mode, but operates normally otherwise.</a><br>
110 <a href="#R5">R5. Running fetchmail in daemon mode doesn't work.</a><br>
111 <a href="#R6">R6. Fetchmail randomly dies with socket errors.</a><br>
112 <a href="#R7">R7. Fetchmail running as root stopped working after an OS upgrade</a><br>
113 <a href="#R8">R8. Fetchmail is timing out after fetching certain
114 messages but before deleting them</a><br>
115 <a href="#R9">R9. Fetchmail is timing out during message fetches</a><br>
116 <a href="#R10">R10. Fetchmail is dying with SIGPIPE.</a><br>
118 <h1>Hangs and lockups:</h1>
120 <a href="#H1">H1. Fetchmail hangs when used with pppd.</a><br>
121 <a href="#H2">H2. Fetchmail hangs during the MAIL FROM exchange.</a><br>
122 <a href="#H3">H3. Fetchmail hangs while fetching mail.</a><br>
124 <h1>Disappearing mail:</h1>
126 <a href="#D1">D1. I think I've set up fetchmail correctly, but I'm not getting any mail.</a><br>
127 <a href="#D2">D2. All my mail seems to disappear after a dropped connection.</a><br>
128 <a href="#D3">D3. Mail that was being fetched when I interrupted my fetchmail seems to have been vanished.</a><br>
130 <h1>Multidrop-mode problems:</h1>
132 <a href="#M1">M1. I've declared local names, but all my multidrop mail is going to root anyway.</a><br>
133 <a href="#M2">M2. I can't seem to get fetchmail to route to a local domain properly.</a><br>
134 <a href="#M3">M3. I tried to run a mailing list using multidrop, and I have a mail loop!</a><br>
135 <a href="#M4">M4. My multidrop fetchmail seems to be having DNS problems.</a><br>
136 <a href="#M5">M5. I'm seeing long DNS delays before each message is processed.</a><br>
137 <a href="#M6">M6. How do I get multidrop mode to work with majordomo?</a><br>
138 <a href="#M7">M7. Multidrop mode isn't parsing envelope addresses from
139 my Received headers as it should.</a><br>
140 <a href="#M8">M8. Users are getting multiple copies of messages.</a><br>
142 <h1>Mangled mail:</h1>
144 <a href="#X1">X1. Spurious blank lines are appearing in the headers of fetched mail.</a><br>
145 <a href="#X2">X2. My mail client can't see a Subject line.</a><br>
146 <a href="#X3">X3. Messages containing "From" at start of line are being split.</a><br>
147 <a href="#X4">X4. My mail is being mangled in a new and different way.</a><br>
148 <a href="#X5">X5. Using POP3, retrievals seems to be fetching too much!</a><br>
149 <a href="#X6">X6. My mail attachments are being dropped or mangled.</a><br>
150 <a href="#X7">X7. Some mail attachments are hanging fetchmail.</a><br>
151 <a href="#X8">X8. A spurious ) is being appended to my messages.</a><br>
153 <h1>Other problems:</h1>
155 <a href="#O1">O1. The --logfile option doesn't work if the logfile doesn't exist.</a><br>
156 <a href="#O2">O2. Every time I get a POP or IMAP message the header is
157 dumped to all my terminal sessions.</a><br>
158 <a href="#O3">O3. Does fetchmail reread its rc file every poll cycle?</a><br>
159 <a href="#O4">O4. Why do deleted messages show up again when I take
160 a line hit while downloading?</a><br>
161 <a href="#O5">O5. Why is fetched mail being logged with my name, not the real From address?</a><br>
162 <a href="#O6">O6. I'm seeing long sendmail delays or hangs near the start of each poll cycle.</a><br>
163 <a href="#O7">O7. Why doesn't fetchmail deliver mail in date-sorted order?</a><br>
164 <a href="#O8">O8. I'm using pppd. Why isn't my monitor option working?</a><br>
165 <a href="#O9">O9. Why does fetchmail keep retrieving the same messages
166 over and over?</a><br>
167 <a href="#O10">O10. Why is the received date on all my messages the same?</a><br>
171 <h2><a name="G1">G1. What is fetchmail and why should I bother?</a></h2>
173 <p>Fetchmail is a one-stop solution to the remote mail retrieval problem
174 for Unix machines, quite useful to anyone with an intermittent PPP or
175 SLIP connection to a remote mailserver. It can collect mail using any
176 variant of POP or IMAP and forwards via port 25 to the local SMTP
177 listener, enabling all the normal forwarding/filtering/aliasing
178 mechanisms that would apply to local mail or mail arriving via a
179 full-time TCP/IP connection.
181 <p>Fetchmail is not a toy or a coder's learning exercise, but an
182 industrial-strength tool capable of transparently handling every
183 retrieval demand from those of a simple single-user ISP connection up
184 to mail retrieval and rerouting for an entire client domain.
185 Fetchmail is easy to configure, unobtrusive in operation, powerful,
186 feature-rich, and well documented.
188 <p>Fetchmail is <a href="http://www.opensource.org">open-source</a>
189 software. The openness of the sources is the strongest assurance of
190 quality you can have. Extensive peer review by a large,
191 multi-platform user community has shown that fetchmail is as near
192 bulletproof as the underlying protocols permit.
194 <p>Fetchmail is licensed under the <a
195 href="http://gnu.org//copyleft/gpl.html">GNU General Public
198 <p>If you found this FAQ in the distribution, see the README for fetchmail's
202 <h2><a name="G2">G2. Where do I find the latest FAQ and fetchmail
205 <p>The latest HTML FAQ is available alongside the latest fetchmail
206 sources at the fetchmail home page:
207 <a href="http://www.tuxedo.org/~esr/fetchmail">
208 http://www.tuxedo.org/~esr/fetchmail</a>. You can also usually find
210 href="http://sunsite.unc.edu/pub/Linux/system/mail/pop/!INDEX.html">POP
211 mail tools directory on Sunsite</a>.
213 <p>A text dump of this FAQ is included in the fetchmail
214 distribution. Because it freezes at distribution release time, it may
215 not be completely current.
218 <h2><a name="G3">G3. I think I've found a bug. Will you fix it?</a></h2>
220 <p>Yes I will, provided you include enough diagnostic information for me
221 to go on. Send bugs to <a
222 href="mailto:fetchmail-friends@ccil.org">fetchmail-friends</a>. When reporting
223 bugs, please include the following:
226 <li>Your operating system.
227 <li>Your compiler version, if you built from source; otherwise, the
228 name and origin ogf the RPM or other binary package you installed.
229 <li>A copy of your POP or IMAP server's greeting line.
230 <li>The name and version of the SMTP listener or MDA you are forwarding to.
231 <li>Any command-line options you used.
232 <li>The output of fetchmail -V called with whatever other
233 command-line options you used.
236 <p>If you have FTP access to your remote mail account, and you have any
237 suspicion that the bug was triggered by a particular message, please
238 include a copy of the message that triggered the bug.
240 <p>Often, the first thing I will do when you report a bug is tell you to
241 upgrade to the newest version of fetchmail, and then see if the
242 problem reproduces. So you'll probably save us both time if you
243 upgrade and test with the latest version <em>before</em> sending in a
246 <p>If your bug is something that used to work but stopped working when
247 you upgraded, then you can help pin the bug down by trying <a
248 href="ftp://ftp.ccil.org/pub/esr/fetchmail/">intermediate versions of
249 fetchmail</a> until you identify the revision that broke your
250 feature. The smart way to do this is by binary search on the version
251 sequence. First, try the version halfway between your last good one
252 and the current one. If it works, the failure was introduced in the
253 upper half of the sequence; if it doesn't, the failure was introduced
254 in the lower half. Now bisect that half in the same way. In a very
255 few tries, you should be able to identify the exact adjacent pair
256 of versions between which your bug was introduced -- and with
257 information like that, I can usually come up with a fix very quickly.
259 <p>Another useful thing you can do, if you're using POP3, is to test for
260 IMAP4 support on your mailserver using the autoprobe function of
261 fetchmailconf. If you have IMAP4, and fetchmailconf doesn't tell you
262 it's broken, switch immediately. POP3 is a weak, poorly-designed
263 protocol with chronic problems, and the later versions after RFC1725
264 actually get worse rather than better. Changing over to IMAP4 may well
265 make your problem go away -- and if your ISP doesn't have IMAP4
266 support, bug them to supply it.
268 <p>It is helpful if you include your .fetchmailrc file, but not necessary
269 unless your symptom seems to involve an error in configuration
270 parsing. If you do send in your .fetchmailrc, mask the passwords
273 <p>If fetchmail seems to run and fetch mail, but the headers look mangled
274 (that is, headers are missing or blank lines are inserted in the
275 headers) then read the FAQ items in section <a href="#X1">X</a>
276 before submitting a bug report. Pay special attention to the item on
277 <a href="#generic_mangling">diagnosing mail mangling</a>. There are
278 lots of ways for other programs in the mail chain to screw up that
279 look like fetchmail's fault, but you may be able to fix these by
280 tweaking your configuration.
282 <p>A transcript of the failed session with -v -v (yes, that's
283 <em>two</em> -v options, enabling debug mode) will almost always be useful.
284 It is very important that the transcript include your POP/IMAP server's
285 greeting line, so I can identify it in case of server problems. This
286 transcript will not reveal your passwords, which are specially masked
287 out precisely so the transcript can be passed around.
289 <p>If you upgraded your fetchmail and something broke, you should include
290 session transcripts with -v -v of both the working and failing
291 versions. Very often, the source of the problem can instantly
292 identified by looking at the differences in protocol transactions.
294 <p>If the bug involves a core dump or hang, a gdb stack trace is good to have.
295 (Bear in mind that you can attach gdb to a running but hung process by
296 giving the process ID as a second argument.) You will need to
300 CFLAGS=-g LDFLAGS=" " ./configure
303 and then rebuild in order to generate a version that can be gdb-traced.
305 <p>Best of all is a mail file which, when fetched, will reproduce the
306 bug under the latest (current) version.
308 <p>Any bug I can reproduce will usually get fixed very quickly, often
309 within 48 hours. Bugs I can't reproduce are a crapshoot. If the
310 solution isn't obvious when I first look, it may evade me for a long
311 time (or to put it another way, fetchmail is well enough tested that the
312 easy bugs have long since been found). So if you want your bug fixed
313 rapidly, it is not just sufficient but nearly <em>necessary</em> that
314 you give me a way to reproduce it.
317 <h2><a name="G4">G4. I have this idea for a neat feature. Will you add it?</a></h2>
319 Probably not. Most of the feature suggestions I get are for ways to
320 set various kinds of administrative policy or add more spam filtering
321 (the most common one, which I used to get about four million times a week
322 and got <em>really</em> tired of, is for tin-like kill files).
324 <p>You can do spam filtering better with procmail or maildrop on the
325 server side and (if you're the server sysadmin) sendmail.cf domain
326 exclusions. You can do other policy things better with the
327 <CODE>mda</CODE> option and script wrappers around fetchmail. If
328 it's a prime-time-vs.-non-prime-time issue, ask yourself whether a
329 wrapper script called from crontab would do the job.
331 <p>I'm not going to do these; fetchmail's job is transport, not policy, and I
332 refuse to change it from doing one thing well to attempting many things badly.
333 One of my objectives is to keep fetchmail simple so it stays reliable.
335 <p>For reasons fetchmail doesn't have other commonly-requested features
336 (such as password encryption, or multiple concurrent polls from the
337 same instance of fetchmail) see the <a
338 href="http://www.tuxedo.org/~esr/fetchmail/design-notes.html">design notes</a>.
340 <p>Fetchmail is a mature project, no longer in constant active
341 development. It is no longer my top project, and I am going to be
342 quite reluctant to add features that might either jeopardize its
343 stability or involve me in large amounts of coding.
345 <p>All that said, if you have a feature idea that really is about a transport
346 problem that can't be handled anywhere but fetchmail, lay it on me. I'm
347 very accommodating about good ideas.
350 <h2><a name="G5">G5. Is there a mailing list for exchanging tips?</a></h2>
352 <p>There is a fetchmail-friends list
353 (fetchmail-friends@lists.ccil.org) for people who want to discuss fixes
354 and improvements in fetchmail and help co-develop it. It's a MailMan
355 list, which you can sign up for at
356 <a href="http://lists.ccil.org/mailman/listinfo/fetchmail-friends">http://lists.ccil.org/mailman/listinfo/fetchmail-friends</a>.
357 There is also an announcements-only list,
358 fetchmail-announce@lists.ccil.org, which you can sign up for at <a href="http://lists.ccil.org/mailman/listinfo/fetchmail-announce">http://lists.ccil.org/mailman/listinfo/fetchmail-announce</a>.
361 <h2><a name="G6">G6. So, what's this I hear about a fetchmail paper?</a></h2>
363 <p>The fetchmail development was also a sociological experiment, an
364 extended test to see if my theory about the critical features of the
365 Linux development model is correct.
367 <p>The experiment was a success. I wrote a paper about it titled <a
368 href="http://www.tuxedo.org/~esr/writings/cathedral.html">The
369 Cathedral and the Bazaar</a> which was first presented at Linux
370 Kongress '97 in Bavaria and very well received there. It was also
371 given at Atlanta Linux Expo, Linux Pro '97 in Warsaw, and the first
372 Perl Conference, at UniForum '98, and was the basis of an invited
373 presentation at Usenix '98. The folks at Netscape tell me it helped
375 href="http://www.netscape.com/newsref/pr/newsrelease558.html"> give
376 away the source for Netscape Communicator</a>.
378 <p>If you're reading a non-HTML dump of this FAQ, you can find the paper
379 on the Web with a search for that title.
382 <h2><a name="G7">G7. What is the best server to use with fetchmail?</a></h2>
384 <p>The short answer: IMAP 2000 running over Unix.
386 <p>Here's a longer answer:
388 <p>Fetchmail will work with any POP, IMAP, ETRN, or ODMR server that
389 conforms to the relevant RFCs (and even some outright broken ones like
390 <a href="#S2">Microsoft Exchange</a> and <a href="#S12">Novell
391 GroupWise</a>). This doesn't mean it works equally well with all,
392 however. POP2 servers, and POP3 servers without LAST, limit
393 fetchmail's capabilities in various ways described on the manual
396 <p>Most modern Unixes (and effectively all Linux/*BSD systems) come with
397 POP3 support preconfigured (but beware of the horribly broken POP3
398 server mentioned in <a href="#D2">D2</a>). An increasing minority
399 also feature IMAP (you can detect IMAP support by running fetchmail in
400 AUTO mode, or by using the `Probe for supported protocols' function in
401 the fetchmailconf utility).
403 <p>If you have the option, we recommend using or installing an IMAP4rev1
404 server; it has the best facilities for tracking message `seen' states.
405 It also recovers from interrupted connections more gracefully than
406 POP3, and enables some significant performance optimizations. The new
407 <a href="ftp://ftp.cac.washington.edu/imap/imap.tar.Z">IMAP 2000</a>
408 is particularly nice, as it supports CRAM-MD5 so you don't have to
409 ship your mail password over the net en clair (fetchmail autodetects
410 this capability). Older versions had support for GSSAPI giving a
413 <p>Don't be fooled by NT/Exchange propaganda. M$ Exchange is just plain
414 broken (see item <a href="#S2">S2</a>) and NT cannot handle the
415 sustained load of a high-volume remote mail server. Even Microsoft
416 itself knows better than to try this; their own Hotmail service runs
417 over Solaris! For extended discussion, see John Kirch's excellent <a
418 href="http://unix-vs-nt.org/kirch/">white paper</a> on Unix
421 <p>Source for a high-quality supported implementation of POP is available
422 from the <a href="ftp://ftp.qualcomm.com/eudora/servers/unix/popper/">Eudora
423 FTP site</a>. Don't use 2.5, which has a rather restrictive license.
424 The 2.5.2 version appears to restore the open-source license of
428 <h2><a name="G8">G8. What is the best mail program to use with fetchmail?</a></h2>
430 <p>Fetchmail will work with all popular <a href="#T1">mail transport
431 programs</a>. It also doesn't care which user agent you use, and user
432 agents are as a rule almost equally indifferent to how mail is
433 delivered into your system mailbox. So any of the popular Unix mail
434 agents -- <a href="http://www.myxa.com/old/elm.html">elm</a>, <a
435 href="http://www.washington.edu/pine/">pine</a>, <a
436 href="http://www.cs.indiana.edu/docproject/mail/mh.html">mh</a>, or <a
437 href="http://www.mutt.org">mutt</a> -- will work fine with fetchmail.
439 <p>All this having been said, I can't resist putting in a discreet plug
440 for <a href="http://www.mutt.org">mutt</a>. My own personal mail
441 setup is sendmail plus fetchmail plus mutt. Mutt's interface is only
442 a little different from that of its now-moribund ancestor elm, but its
443 excellent handling of MIME and PGP put it in a class by itself. You
444 won't need its built-in POP3 support, though; most of the mutt
445 developers will cheerfully admit that fetchmail's is better :-).
448 <h2><a name="G9">G9. How can I avoid sending my password en clair?</a></h2>
450 <p>Depending on what your mail server you are talking to, this ranges
451 from trivial to impossible. It may even be next to useless.
453 <p>Most people use fetchmail over phone wires, which are hard to tap.
454 Anybody with the skill and resources to do this could get into your
455 server mailbox with much less effort by subverting the server host.
456 So if your provider setup is modem wires going straight into a service
457 box, you probably don't need to worry.
459 <p>In general there is little point in trying to secure your fetchmail
460 transaction unless you trust the security of the server host you are
461 retrieving mail from. Your vulnerability is more likely to be an
462 insecure local network on the server end (e.g. to somebody with a TCP/IP
463 packet sniffer intercepting Ethernet traffic between the modem
464 concentrator you dial in to and the mailserver host).
466 <p>Having realized this, you need to ask whether password encryption
467 alone will really address your security exposure. If you think you
468 might be snooped between server and client, it's better to use
469 end-to-end encryption on your whole mail stream so none of it can be
470 read. One of the advantages of fetchmail over conventional SMTP-push
471 delivery is that you may be able to arrange this by using ssh(1); see
472 <a href="#K3">K3</a>.
474 <p>Note that ssh is not a complete privacy solution either, as your mail
475 could have been snooped in transit to your POP server from wherever it
476 originated. For best security, agree with your correspondents to use
477 a tool such as <a href="http://www.gnupg.org/">GPG</a> (Gnu Privacy
478 Guard) or PGP (Pretty Good Privacy).
480 <p>If ssh/sshd isn't available, or you find it too complicated for you to
481 set up, password encryption will at least keep a malicious cracker
482 from deleting your mail, and require him to either tap your connection
483 continuously or crack root on the server in order to read it.
485 <p>You can deduce what encryptions your mail server has available
486 by looking at the server greeting line (and, for IMAP, the
487 response to a CAPABILITY query). Do a <code>fetchmail -v</code>
488 to see these, or telnet direct to the server port (110 for POP3, 143 for
491 <p>If your mailserver is using IMAP 2000, you'll have CRAM-MD5 support
492 built in. Fetchmail autodetects this; you can skip the rest of this
495 <p>The POP3 facility you are most likely to have available is APOP. This is a
496 POP3 feature supported by many servers (fetchmailconf's autoprobe
497 facility will detect it and tell you if you have it). If you see
498 something in the greeting line that looks like an
499 angle-bracket-enclosed Internet address with a numeric left-hand part,
500 that's an APOP challenge (it will vary each time you log in). You can
501 register a secret on the host (using <code>popauth(8)</code> or some
502 program like it). Specify the secret as your password in your
503 .fetchmailrc; it will be used to encrypt the current challenge, and
504 the encrypted form will be sent back the the server for
507 <p>Alternatively, you may have Kerberos available. This may require you
508 to set up some magic files in your home directory on your client
509 machine, but means you can omit specifying any password at all.
511 <p>Fetchmail supports two different Kerberos schemes. One is a POP3
512 variant called KPOP; consult the documentation of your mail server to
513 see if you have it (one clue is the string "krb-IV" in the greeting
514 line on port 110). The other is an IMAP and POP3 facility described
515 by RFC1731 and RFC1734. You can tell if this one is present by looking
516 for AUTH=KERBEROS_V4 in the CAPABILITY response.
518 <p>If you are fetching mail from a CompuServe POP3 account, you can use
519 their RPA authentication (which works much like APOP). See <a
520 href="#S3">S3</a> for details. If you are fetching mail from
521 Microsoft Exchange using IMAP, you will be able to use NTLM.
523 <p>Your POP3 server may have the RFC1938 OTP capability to use one-time
524 passwords (if it doesn't, you can get OTP patches for the 2.2 version
525 of the Qualcomm popper from <a href="#cmetz">Craig Metz</a>). To check
526 this, look for the string "otp-" in the greeting line. If you see it,
527 and your fetchmail was built with OPIE support compiled in (see the
528 distribution INSTALL file), fetchmail will detect it also. When using
529 OTP, you will specify a password but it will not be sent en clair.
531 <p>You can get both POP3 and IMAP OTP patches from <a name="cmetz">Craig
533 href="http://www.inner.net/pub/">http://www.inner.net/pub/</a>.<p>
534 These patches use a SASL authentication method named "X-OTP" because
535 there is not currently a standard way to do this; fetchmail also uses
536 this method, so the two will interoperate happily. They better,
537 because this is how Craig gets his mail ;-)
539 <p>Finally, you can use <a href="#K5">SSL</a> for complete
540 end-to-end encryption if you have an SSL-enabled mailserver.
543 <h2><a name="G10">G10. Is any special configuration needed to use a dynamic IP address?</a></h2>
545 <p>Yes. In order to avoid giving indigestion to certain picky MTAs
546 (notably <a href="#T3">exim</a>), fetchmail always makes the RCPT TO
547 address it feeds the MTA a fully qualified one with a hostname part.
548 Normally it does this by appending @ and "localhost", but when you are
549 using Kerberos or ETRN mode it will append @ and your machine's
550 fully-qualified domain name (FQDN).
552 <p>Appending the FQDN can create problems when fetchmail is running in daemon
553 mode and outlasts the dynamic IP address assignment your client
554 machine had when it started up.
556 <p>Since the new IP address (looked up at RCPT TO interpretation time)
557 doesn't match the original, the most benign possible result is that
558 your MTA thinks it's seeing a relaying attempt and refuses. More
559 frequently, fetchmail will try to connect to a nonexistent host
560 address and time out. Worst case, you could up forwarding your mail
561 to the wrong machine!
563 <p>Use the <code>smtpaddress</code> option to force the appended hostname
564 to one with a (fixed) IP address of 127.0.0.1 in your
565 <code>/etc/hosts</code>. (The name `localhost' will usually work; or
566 you can use the IP address itself).
568 <p>Only one fetchmail option interacts directly with your IP address,
569 `<code>interface</code>'. This option can be used to set the gateway
570 device and restrict the IP address range fetchmail will use. Such a
571 restriction is sometimes useful for security reasons, especially on
572 multihomed sites. See <a href="#C3">C3</a>.
574 <p>I recommend against trying to set up the <code>interface</code> option
575 when initially developing your poll configuration -- it's never
576 necessary to do this just to get a link working. Get the link working
577 first, observe the actual address range you see on connections, and
578 add an <code>interface</code> option (if you need one) later.
580 <p>You can't use ETRN if you have a dynamic IP address (your ISP changes
581 your IP address occasionally, possibly with every connect). You need
582 to have your own registered domain and a definite IP address
583 registered for that domain. The server needs to be configured to
584 accept mail for your domain but then queue it to forward to your
585 machine. ETRN just tells to server to flush its queue for your
586 domain. Fetchmail doesn't actually get the mail in that case.
588 <p>You can use On-Demand Mail Relay (ODMR) with a dynamic IP address;
589 that's what it was designed for, and it provides capabilities very
590 similar to ETRN. Unfortunately ODMR servers are not yet widely
591 deployed, as of early 2001.
593 <p>If you're using a dynamic-IP configuration, one other (non-fetchmail)
594 problem you may run into with outgoing mail is that some sites will
595 bounce your email because the hostname your giving them isn't real
596 (and doesn't match what they get doing a reverse DNS on your
597 dynamically-assigned IP address). If this happens, you need to hack
598 your sendmail so it masquerades as your host. Setting
604 in your <code>sendmail.cf</code> will work, or you can set<p>
607 MASQUERADE_AS(smarthost.here)
610 in the m4 configuration and do a reconfigure. (In both cases, replace
611 <code>smarthost.here</code> with the actual name of your mailhost.)
612 See the <a href="http://www.lege.com/sendmail-FAQ.txt">sendmail
613 FAQ</a> for more details.
616 <h2><a name="G11">G11. Is any special configuration needed to use firewalls?</a></h2>
618 <p>No. You can use fetchmail with SOCKS, the standard tool for
619 indirecting TCP/IP through a firewall. You can find out about SOCKS,
620 and download the SOCKS software including server and client code, at
621 the <a href="http://www.socks.nec.com/">SOCKS distribution
624 <p>The specific recipe for using fetchmail with a firewall is at <a
628 <h2><a name="G12">G12. Is any special configuration needed to <em>send</em> mail?</a></h2>
630 <p>A user asks: but how do we send mail out to the POP3 server? Do I need
631 to implement another tool or will fetchmail do this too?
633 <p>Fetchmail only handles the receiving side. The sendmail or other
634 preinstalled MTA on your client machine will handle sending mail
635 automatically; it will ship mail that is submitted while the
636 connection is active, and put mail that is submitted while
637 the connection is inactive into the outgoing queue.
639 <p>Normally, sendmail is also run periodically (every 15 minutes on most
640 Linux systems) in a mode that tries to ship all the mail in the
641 outgoing queue. If you have set up something like pppd to
642 automatically dial out when your kernel is called to open a TCP/IP
643 connection, this will ensure that the mail gets out.
646 <h2><a name="G13">G13. Is fetchmail Y2K-compliant?</a></h2>
648 Fetchmail is fully Y2K-compliant.<p>
650 Fetchmail could theoretically have problems when the 32-bit time_t
651 counters roll over in 2038, but I doubt it. Timestamps aren't used
652 for anything but log entry generation. Anyway, if you aren't running
653 on a 64-bit machine by then, you'll deserve to lose.
656 <h2><a name="G14">G14. Is there a way in fetchmail to support disconnected IMAP mode?</a></H2>
658 <p>No. Fetchmail is a mail transport agent, best understood as a protocol
659 gateway between POP3/IMAP servers and SMTP. Disconnected operation
660 requires an elaborate interactive client. It's a very different problem.
663 <h2><a name="G15">G15. How will fetchmail perform under heavy loads?</a></h2>
665 <p>Fetchmail streams message bodies line-by-line; the most core it
666 ever requires per message is enough memory to hold the RFC822 header, and
667 that storage is freed when body processing begins. It is, accordingly,
668 quite economical in its use of memory.
670 <p>After startup time, a fetchmail running in daemon mode stats its
671 configuration file once per poll cycle to see whether it has changed
672 and should be rescanned. Other than that, a fetchmail in normal
673 operation doesn't touch the disk at all; that job is left up to the
674 MTA or MDA the fetchmail talks to.
676 <p>Fetchmail's performance is usually bottlenecked by latency on the POP
677 server or (less often) on the TCP/IP link to the server. This is not
678 a problem readily solved by tuning fetchmail, or even by buying more
679 TCP/IP capacity (which tends to improve bandwidth but not necessarily
683 <h2><a name="B1">B1. Make coughs and dies when building on FreeBSD.</a></h2>
685 <p>The vendor-supplied make on FreeBSD systems can only be used within
686 FreeBSD's "scope", e.g. the ports collection. Type "gmake" to run GNU
687 make and better things will happen.
690 <h2><a name="B2">B2. Lex bombs out while building the fetchmail lexer.</a></h2>
692 <p>In the immortal words of Alan Cox the last time this came up: ``Take
693 the Solaris lex and stick it up the backside of a passing Sun
694 salesman, then install <a
695 href="ftp://ftp.gnu.org/pub/non-gnu/flex/">flex</a> and use that. All
698 <p>I couldn't have put it better myself, and ain't going to try now.
700 <p>(The same problem has been reported under HP-UX v10.20 and IRIX)
703 <h2><a name="B3">B3. I get link failures when I try to build fetchmail.</a></h2>
705 If you get errors resembling these
708 mxget.o(.text+0x35): undefined referenceto `__res_search'
709 mxget.o(.text+0x99): undefined reference to`__dn_skipname'
710 mxget.o(.text+0x11c): undefined reference to`__dn_expand'
711 mxget.o(.text+0x187): undefined reference to`__dn_expand'
712 make: *** [fetchmail] Error 1
715 then you must add "-lresolv" to the LOADLIBS line in your Makefile
716 once you have installed the `bind' package.
718 <p>If you get link errors involving <tt>dcgettext</tt>, like this:
721 rcfile_y.o: In function `yyparse':
722 rcfile_y.o(.text+0x3aa): undefined reference to `dcgettext__'
723 rcfile_y.o(.text+0x4f2): undefined reference to `dcgettext__'
724 rcfile_y.o(.text+0x5ee): undefined reference to `dcgettext__'
725 rcfile_y.o: In function `yyerror':
726 rcfile_y.o(.text+0xc7c): undefined reference to `dcgettext__'
727 rcfile_y.o(.text+0xcc8): undefined reference to `dcgettext__'
728 rcfile_y.o(.text+0xdf9): more undefined references to `dcgettext__' follow
731 reconfigure with <tt>configure --with-included-gettext</tt>. This is
732 due to some brain-damage in the GNU internationalization libraries.
735 <h2><a name="F1">F1. Why does my old .fetchmailrc file no longer work?</a></h2>
737 <h3>If your file predates 5.8.9</h3>
739 <p>If you were using ETRN mode, change your <tt>smtphost</tt> option to
740 a <tt>fetchdomains</tt> option.
742 <h3>If your file predates 5.8.3</h3>
744 <p>The `via localhost' special case for use with ssh tunnelling is gone.
745 Use the %h feature of <tt>plugin</tt> instead.
747 <h3>If your file predates 5.6.8</h3>
749 <p>In 5.6.8, the <tt>preauth</tt> keyword and option were changed back to
750 <tt>auth</tt>. The <tt>preauth</tt> synonym will still be supported
751 through a few more point releases.
753 <p><h3>If your file predates 5.6.5</h3>
755 The <tt>imap-gss</tt>, <tt>imap-k4</tt>, and <tt>imap-login</tt>
756 protocol types are gone. This is a result of a major re-factoring
757 of the authentication machinery; fetchmail can now use Kerberos V4
758 and GSSAPI not just with IMAP but with POP3 servers that have RFC1734
759 support for the AUTH command.
761 <p>When trying to identify you to an IMAP or POP mailserver, fetchmail
762 now first tries methods that don't require a password (GSSAPI,
763 KERBEROS_IV); then it looks for methods that mask your password
764 (CRAM-MD5, X-OTP); and only if it the server doesn't support any of
765 those will it ship your password en clair.
767 <p>Setting the <tt>preauth</tt> option to any value other than `password'
768 will prevent from looking for a password in your <tt>.netrc</tt> file
769 or querying for it at startup time.<p>
771 <h3>If your file predates 5.1.0</h3>
773 In 5.1.0, the <tt>auth</tt> keyword and option were changed to
776 <p><h3>If your file predates 4.5.5</h3>
778 If the <code>dns</code> option is on (the default), you may need to
779 make sure that any hostname you specify (for mail hosts or for an SMTP
780 target) is a canonical fully-qualified hostname). In order to avoid
781 DNS overhead and complications, fetchmail no longer tries to derive
782 the fetchmail client machine's canonical DNS name at startup.
784 <p><h3>If your file predates 4.0.6:</h3>
786 Just after the `<CODE>via</CODE>' option was introduced, I realized
787 that the interactions between the `<CODE>via</CODE>',
788 `<CODE>aka</CODE>', and `<CODE>localdomains</CODE>' options were out
789 of control. Their behavior had become complex and confusing, so much so
790 that I was no longer sure I understood it myself. Users were being
791 unpleasantly surprised.
793 <p>Rather than add more options or crock the code, I re-thought it. The
794 redesign simplified the code and made the options more orthogonal, but
795 may have broken some complex multidrop configurations.
797 Any multidrop configurations that depended on the name just after the
798 `<CODE>poll</CODE>' or `<CODE>skip</CODE>' keyword being still
799 interpreted as a DNS name for address-matching purposes, even in the
800 presence of a `<CODE>via</CODE>' option, will break.
802 <p>It is theoretically possible that other unusual configurations (such
803 as those using a non-FQDN poll name to generate Kerberos IV tickets) might
804 also break; the old behavior was sufficiently murky that we can't be
805 sure. If you think this has happened to you, contact the maintainer.
807 <p><h3>If your file predates 3.9.5:</h3>
809 The `<code>remote</code>' keyword has been changed to `<code>folder</code>'.
810 If you try to use the old keyword, the parser will utter a warning.
812 <p><h3>If your file predates 3.9:</h3>
814 It could be because you're using a .fetchmailrc that's written in the
815 old popclient syntax without an explicit `<CODE>username</CODE>'
816 keyword leading the first user entry attached to a server entry.
818 This error can be triggered by having a user option such as `<CODE>keep</CODE>'
819 or `<CODE>fetchall</CODE>' before the first explicit username. For
820 example, if you write
823 poll openmail protocol pop3
824 keep user "Hal DeVore" there is hdevore here
827 the `<CODE>keep</CODE>' option will generate an entire user entry with
828 the default username (the name of fetchmail's invoking user).
830 <p>The popclient compatibility syntax was removed in 4.0. It complicated
831 the configuration file grammar and confused users.
833 <p><h3>If your file predates 2.8:</h3>
835 The `<CODE>interface</CODE>', `<CODE>monitor</CODE>' and
836 `<CODE>batchlimit</CODE>' options changed after 2.8.
838 <p>They used to be global options with `<CODE>set</CODE>' syntax like the
839 batchlimit and logfile options. Now they're per-server options, like
840 `<CODE>protocol</CODE>'.
842 <p>If you had something like
845 set interface = "sl0/10.0.2.15"
848 in your .fetchmailrc file, simply delete that line and insert
849 `interface sl0/10.0.2.15' in the server options part of your `defaults'
852 <p>Do similarly for any `<CODE>monitor</CODE>' or `<CODE>batchlimit</CODE>' options.
855 <h2><a name="F2">F2. The .fetchmailrc parser won't accept my all-numeric user name.</a></h2>
857 Either upgrade to a post-5.0.5 fetchmail or put string quotes around it. :-)
859 <p>The configuration file parser in older fetchmail versions treated any
860 all-numeric token as a number, which confused it when it was
861 expecting a name. String quoting forces the token's class.
863 <p>The lexical analyzer in 5.0.6 and beyond is smarter and assumes
864 any token following "username" or "password" is a string.
867 <h2><a name="F3">F3. The .fetchmailrc parser won't accept my host or username beginning with `no'.</a></h2>
869 See <a href="#F2">F2</a> You're caught in an unfortunate crack between
870 the newer-style syntax for negated options (`no keep', `no rewrite'
871 etc.) and the older style run-on syntax (`nokeep', `norewrite'
874 <p>Upgrade to a 5.0.6 or later fetchmail, or put string quotes around your
878 <h2><a name="F4">F4. I'm getting a `parse error' message I don't understand.</a></h2>
880 The most common cause of mysterious parse errors is putting a server
881 option after a user option. Check the manual page; you'll probably
882 find that by moving one or more options closer to the `poll' keyword
883 you can eliminate the problem.
885 <p>Yes, I know these ordering restrictions are hard to understand.
886 Unfortunately, they're necessary in order to allow the `defaults'
890 <h2><a name="C1">C1. Why do I need a .fetchmailrc when running as root on my own machine?</a></h2>
892 Ian T. Zimmerman <itz@rahul.net> asked:
894 <p>On the machine where I'm the only real user, I run fetchmail as root
895 from a cron job, like this:
898 fetchmail -u "itz" -p POP3 -s bolero.rahul.net
901 This used to work as is (with no .fetchmailrc file in root's home
902 directory) with the last version I had (1.7 or 1.8, I don't
903 remember). But with 2.0, it RECPs all mail to the local root user,
904 unless I create a .fetchmailrc in root's home directory containing:
907 skip bolero.rahul.net proto POP3
911 It won't work if the second line is just "<CODE>user itz</CODE>". This is silly.
913 <p>It seems fetchmail decides to RECP the `default local user' (i.e. the
914 uid running fetchmail) unless there are local aliases, and the
915 `default' aliases (itz->itz) don't count. They should.
919 <p>No they shouldn't. I thought about this for a while, and I don't much
920 like the conclusion I reached, but it's unavoidable. The problem is
921 that fetchmail has no way to know, in general, that a local user `itz'
924 <p>"Ah!" you say, "Why doesn't it check the password file to see if the remote
925 name matches a local one?" Well, there are two reasons.
927 <p>One: it's not always possible. Suppose you have an SMTP host declared
928 that's not the machine fetchmail is running on? You lose.
930 <p>Two: How do you know server itz and SMTP-host itz are the same person?
931 They might not be, and fetchmail shouldn't assume they are unless
932 local-itz can explicitly produce credentials to prove it (that is, the
933 server-itz password in local-itz's .fetchmailrc file.).
935 <p>Once you start running down possible failure modes and thinking about
936 ways to tinker with the mapping rules, you'll quickly find that all the
937 alternatives to the present default are worse or unacceptably
938 more complicated or both.
941 <h2><a name="C2">C2. How can I arrange for a fetchmail daemon to get killed when I log out?</a></h2>
943 The easiest way to dispatch fetchmail on logout (which will work
944 reliably only if you have just one login going at any time) is to
945 arrange for the command `fetchmail -q' to be called on logout. Under
946 bash, you can arrange this by putting `fetchmail -q' in the file
947 `~/.bash_logout'. Most csh variants execute `~/.logout' on logout.
948 For other shells, consult your shell manual page.
950 <p>Automatic startup/shutdown of fetchmail is a little harder to arrange
951 if you may have multiple login sessions going. In the contrib
952 subdirectory of the fetchmail distribution there is some shell code
953 you can add to your .bash_login and .bash_logout profiles that will
954 accomplish this. Thank James Laferriere <babydr@nwrain.net> for
957 <p>Some people start up and shut down fetchmail using the ppp-up and
958 ppp-down scripts of pppd.
961 <h2><a name="C3">C3. How do I know what interface and address to use with --interface?</a></h2>
963 This depends a lot on your local networking configuration (and right
964 now you can't use it at all except under Linux and the newer BSDs). However,
965 here are some important rules of thumb that can help. If they don't
966 work, ask your local sysop or your Internet provider.
968 <p>First, you may not need to use --interface at all. If your machine
969 only ever does SLIP or PPP to one provider, it's almost certainly by a
970 point to point modem connection to your provider's local subnet that's
971 pretty secure against snooping (unless someone can tap your phone or
972 the provider's local subnet!). Under these circumstances, specifying
973 an interface address is fairly pointless.
975 <p>What the option is really for is sites that use more than one
976 provider. Under these circumstances, typically one of your provider
977 IP addresses is your mailserver (reachable fairly securely via the
978 modem and provider's subnet) but the others might ship your packets
979 (including your password) over unknown portions of the general
980 Internet that could be vulnerable to snooping. What you'll use
981 --interface for is to make sure your password only goes over the
984 <p>To determine the device:
987 <li> If you're using a SLIP link, the correct device is probably sl0.
988 <li> If you're using a PPP link, the correct device is probably ppp0.
989 <li> If you're using a direct connection over a local network such as
990 an ethernet, use the command `netstat -r' to look at your routing table.
991 Try to match your mailserver name to a destination entry; if you don't
992 see it in the first column, use the `default' entry. The device name
993 will be in the rightmost column.
996 To determine the address and netmask:
999 <li> If you're talking to slirp, the correct address is probably 10.0.2.15,
1000 with no netmask specified. (It's possible to configure slirp to present
1001 other addresses, but that's the default.)
1003 <li> If you have a static IP address, run `ifconfig <device>', where <device>
1004 is whichever one you've determined. Use the IP address given after
1005 "inet addr:". That is the IP address for your end of the link, and is
1006 what you need. You won't need to specify a netmask.
1008 <li> If you have a dynamic IP address, your connection IP will vary randomly
1009 over some given range (that is, some number of the least significant bits
1010 change from connection to connection). You need to declare an address
1011 with the variable bits zero and a complementary netmask that sets
1015 To illustrate the rule for dynamic IP addresses, let's suppose you're
1016 hooked up via SLIP and your IP provider tells you that the dynamic
1017 address pool is 255 addresses ranging from 205.164.136.1 to
1018 205.164.136.255. Then
1021 interface "sl0/205.164.136.0/255.255.255.0"
1024 would work. To range over any value of the last two octets
1025 (65536 addresses) you would use
1028 interface "sl0/205.164.0.0/255.255.0.0"
1032 <h2><a name="C4">C4. How can I set up support for sendmail's anti-spam features?</a></h2>
1034 This answer covers versions of sendmail from 8.9.3-20 (the version
1035 installed in Red Hat 6.2) upwards. If you have an older version,
1036 upgrade to sendmail 8.9.
1038 <p>Stock sendmails can now do anti-spam exclusions based on a database of
1039 filter rules. The human-readable form of the database is at
1040 <tt>/etc/mail/access</tt>. The database itself is at
1041 <tt>/etc/mail/access.db</tt>.
1043 <p>The table itself uses email addresses, domain names, and network
1044 numbers as keys. For example,</P>
1046 spammer@aol.com REJECT
1047 cyberspammer.com REJECT
1050 <p>would refuse mail from spammer@aol.com, any user from
1051 cyberspammer.com (or any host within the cyberspammer.com domain), and
1052 any host on the 192.168.212.* network. (This feature can be used to
1053 do other things as well; see the <a
1054 href="http://www.sendmail.org/m4/anti-spam.html">sendmail
1055 documentation</a> for details)</P>
1057 To actually set up the database, run
1060 makemap hash deny <deny
1064 <p>To test, send a message to your mailing address from that host and
1065 then pop off the message with fetchmail, using the -v argument. You
1066 can monitor the SMTP transaction, and when the FROM address is parsed,
1067 if sendmail sees that it is an address in spamlist, fetchmail will
1068 flush and delete it.
1070 <p>Under no circumstances put your <strong>mailhost</strong> or <strong>any host
1071 you accept mail from</strong> using fetchmail into your reject file. You
1072 <strong>will</strong> lose mail if you do this!!!
1075 <h2><a name="C5">C5. How can I poll some of my mailboxes more/less
1076 often than others?</a></h2>
1078 Use the <cite>interval</cite> keyword on the ones that should be
1079 checked less often. For example, if you do a poll every 5 minutes,
1080 and want to poll some mailboxes every 5 minutes and some every 30
1081 minutes, use something like this:
1084 poll mainsite.example.com proto pop3 user ....
1085 poll secondary.example.com proto pop3 interval 6 user ...
1088 Then secondary.example.com will be polled every 6th time that
1089 mainsite.example.com is polled, which with a polling interval of every
1090 5 minutes means that secondary.example.com will be polled every 30
1094 <h2><a name="C6">Fetchmail works OK started up manually, but not from an init script.</a></h2>
1096 Often, startup scripts have a different environment than an interactive
1097 login shell. For instance, $HOME might point to "/root" when you are
1098 logged in as root, but it might be either unset, or set to "/" when the
1099 startup scripts are running. That means fetchmail at startup can't find
1102 <p>Pick a location (such as /etc/fetchmailrc) and use fetchmail's -f
1103 option to point fetchmail at it. That should solve the problem.
1106 <h2><a name="C7">C7. How can I forward mail to another host?</a></h2>
1108 To forward mail to a host other than the one you are running fetchmail
1109 on, use the <code>smtphost</code> or <code>smtpname</code> option.
1110 See the manual page for details.
1113 <h2><a name="T1">T1. How can I use fetchmail with sendmail?</a></h2>
1115 For most sendmails, no special configuration is required. Eric Allman
1116 tells me that if <code>FEATURE(always_add_domain)</code> is included
1117 in sendmail's configuration, you can leave the <code>rewrite</code>
1120 <p>If your sendmail complains ``sendmail does not relay'', make sure
1121 your sendmail.cf file says <code>Cwlocalhost</code>
1122 so that sendmail recognizes `localhost' as a name of its host.
1124 <p>If you're mailing from another machine on your local network, also
1125 ensure that its IP address is listed in ip_allow or name in name_allow
1126 (usually in /etc/mail/)
1128 <p>If you find that your sendmail doesn't like the address
1129 `FETCHMAIL-DAEMON@localhost' (which is used in the bouncemail
1130 that fetchmail generates), you may have to set
1131 <code>FEATURE(accept_unqualified_senders)</code>.
1133 <p>Günther Leber reports that Digital Unix sendmails won't work with
1134 fetchmail. The symptom is an error message "<code>553 Local configuration
1135 error, hostname not recognized as local</code>". The problem is that
1136 fetchmail normally feeds sendmail with the client machine's host
1137 address in the MAIL FROM line. These sendmails think this means
1138 they're seeing the result of a mail loop and suppress the mail. You
1139 may be able to work around this by running in <code>--invisible</code> mode.
1141 <p>If you want to support multidrop mode, and you can get access to your
1142 mailserver's sendmail.cf file, it's a good idea to add this rule:
1145 H?l?Delivered-To: $h
1148 This will cause the mailserver's sendmail to reliably write the
1149 appropriate envelope address into each message before fetchmail sees
1150 it, and tell fetchmail which header it is. With this change,
1151 multidrop mode should work reliably even when the Received header
1152 omits the envelope address (which will typically be the case when
1153 the message has multiple recipients). However it will still not
1154 distinguish the recipients, your only advantage is that no bounce
1155 will be sent if a message is BCC addressed to multiple users at
1156 your site. To fix even that problem, you might want to try the
1157 following hack, which is however untested and quite experimental:
1160 H?J?Delivered-To: $u
1162 Mmdrop, P=/usr/bin/procmail, F=lsDFMqSPfhnu9J,
1163 S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrToSMTP,
1164 T=DNS/RFC822/X-Unix,
1165 A=procmail -Y -a $u -d $h
1168 For both hacks, you have to declare `<CODE>envelope "Delivered-To:"</CODE>' on
1169 the fetchmail side, to put the virtual domain (e.g. `domain.com')
1170 with RELAY permission into your access file and to add a line
1171 reading `<CODE>domain.com local:local-pop-user</CODE>' for the first and
1172 `<CODE>domain.com mdrop:local-pop-user</CODE>' for the second hack to your
1175 <p>You will notice that if the mail already has a Delivered-To header,
1176 sendmail will not add another. Further, editing sendmail.cf
1177 directly is not very comfortable. Solutions for both problems
1178 can be found in Peter `Rattacresh' Backes' `hybrid' patch against
1179 sendmail. Have a look at it, you can find it in the contrib
1182 <p>Feel free to try Martijn Lievaart's detailed recipe in the contrib
1183 subdirectory of the fetchmail source distribution, it attempts
1184 to realize multidrop mailboxes with an external script.
1187 <h2><a name="T2">T2. How can I use fetchmail with qmail?</a></h2>
1189 Turn on the <CODE>forcecr</CODE> option; qmail's listener mode doesn't like
1190 header or message lines terminated with bare linefeeds.
1192 <p>(This information is thanks to Robert de Bath
1193 <robert@mayday.cix.co.uk>.)
1195 <p>If a mailhost is using the qmail package (see <a
1196 href="http://pobox.com/~djb/qmail.html">http://pobox.com/~djb/qmail.html</a>)
1197 then, providing the local hosts are also using qmail, it is possible
1198 to set up one fetchmail link to be reliably collect the mail for an
1201 <p>One of the basic features of qmail is the `Delivered-To:' message
1202 header. Whenever qmail delivers a message to a local mailbox it puts
1203 the username and hostname of the envelope recipient on this line. The
1204 major reason for this is to prevent mail loops.
1206 <p>To set up qmail to batch mail for a disconnected site the ISP-mailhost
1207 will have normally put that site in its `virtualhosts' control file so
1208 it will add a prefix to all mail addresses for this site. This results
1209 in mail sent to 'username@userhost.userdom.dom.com' having a
1210 'Delivered-To:' line of the form:
1213 Delivered-To: mbox-userstr-username@userhost.userdom.dom.com
1216 A single host maildrop will be slightly simpler:
1219 Delivered-To: mbox-userstr-username@userhost.dom.com
1222 The ISP can make the 'mbox-userstr-' prefix anything they choose
1223 but a string matching the user host name is likely.
1225 <p>To use this line you must:
1228 <li>Ensure the option `envelope Delivered-To:' is in the fetchmail
1231 <li>Ensure you have a localdomains containing 'userdom.dom.com' or
1232 `userhost.dom.com' respectively.
1235 So far this reliably delivers messages to the correct machine of the
1236 local network, to deliver to the correct user the 'mbox-userstr-'
1237 prefix must be stripped off of the user name. This can be done by
1238 setting up an alias within the qmail MTA on each local machine.
1239 Simply create a dot-qmail file called '.qmail-mbox-userstr-default'
1240 in the alias directory (normally /var/qmail/alias) with the contents:
1243 | ../bin/qmail-inject -a -f"$SENDER" "${LOCAL#mbox-userstr-}@$HOST"
1246 Note this <em>does</em> require a modern /bin/sh.
1248 <p>Peter Wilson adds:
1250 <p>``My ISP uses "alias-unzzippedcom-" as the prefix, which means that I
1251 need to name my file ".qmail-unzzippedcom-default". This is due to
1252 qmail's assumption that a message sent to user-xyz is handled by the
1253 file ~user/.qmail-xyz (or ~user/.qmail-default).''
1255 <p>Luca Olivetti adds:
1257 <p>If you aren't using qmail locally, or you don't want to set up the
1258 alias mechanism described above, you can use the option `<code>qvirtual
1259 "mbox-userstr-"</code>' in your fetchmail config file to strip the prefix
1260 from the local user name.
1263 <h2><a name="T3">T3. How can I use fetchmail with exim?</a></h2>
1265 <p>If you have <CODE>rewrite</CODE> on:
1267 <p>There is an RFC1123 requirement that MAIL FROM and RCPT TO addresses
1268 you pass to it have to be canonical (e.g. with a fully qualified
1269 hostname part). Therefore fetchmail tries to pass fully qualified
1270 RCPT TO addresses. But exim does not by default accept `localhost' as
1271 a fully qualified domain. This can be fixed.
1273 <p>In exim.conf, add `localhost' to your local_domains declaration if it's not
1274 already present. For example, the author's site at thyrsus.com would
1275 have a line reading:
1278 local_domains = thyrsus.com:localhost
1281 If you have <CODE>rewrite</CODE> off:
1283 <p>MAIL FROM is a potential problem if the MTAs upstream from your fetchmail
1284 don't necessarily pass canonicalized From and Return-Path addresses,
1285 and fetchmail's <CODE>rewrite</CODE> option is off. The specific case
1286 where this has come up involves bounce messages generated by sendmail
1287 on your mailer host, which have the (un-canonicalized) origin address
1290 <p>The right way to fix this is to enable the <CODE>rewrite</CODE> option and
1291 have fetchmail canonicalize From and Return-Path addresses with the
1292 mailserver hostname before exim sees them. This option is enabled by
1293 default, so it won't be off unless you turned it off.
1295 <p>If you must run with <CODE>rewrite</CODE> off, there is a switch in exim's
1296 configuration files that allows it to accept domainless MAIL FROM
1297 addresses; you will have to flip it by putting the line
1300 sender_unqualified_hosts = localhost
1303 in the main section of the exim configuration file. Note that this
1304 will result in such messages having an incorrect domain name attached
1305 to their return address (your SMTP listener's hostname rather than
1306 that of the remote mail server).
1309 <h2><a name="T4">T4. How can I use fetchmail with smail?</a></h2>
1311 <p>Smail 3.2 is very nearly plug-compatible with sendmail, and may work
1312 fine out of the box.
1314 <p>We have one report that when processing multiple messages from a
1315 single fetchmail session, smail sometimes delivers them in an
1316 order other than received-date order. This can be annoying because it
1317 scrambles conversational threads. This is not fetchmail's problem,
1318 it is an smail `feature' and has been reported to the maintainers
1321 <p>Very recent smail versions require an <code>-smtp_hello_verify</code>
1322 option in the smail config file. This overrides smail's check to see
1323 that the HELO address is actually that of the client machine, which
1324 is never going to be the case when fetchmail is in the picture.
1325 According to RFC1123 an SMTP listener <em>must</em> allow this
1326 mismatch, so smail's new behavior (introduced sometime between
1327 3.2.0.90 and 3.2.0.95) is a bug.
1329 <p>You may also need to say
1330 <code>-smtp_hello_broken_allow=127.0.0.1</code>
1331 in order for smail to accept the "localhost" that fetchmail normally
1332 appends to recipient addresses.
1335 <h2><a name="T5">T5. How can I use fetchmail with SCO's MMDF?</a></h2>
1337 <p>MMDF itself is difficult to configure, but it turns out that
1338 connecting fetchmail to MMDF's SMTP channel isn't that hard.
1340 href="http://www.aplawrence.com/Unixart/uucptofetch.html">
1341 MMDF recipe</a> that describes replacing a UUCP link with
1342 fetchmail feeding MMDF.
1345 <h2><a name="T6">T6. How can I use fetchmail with Lotus Notes?</a></h2>
1347 <p>The Lotus Notes SMTP gateway tries to deduce when it should convert \n
1348 to \r\n, but its rules are not the intuitive and correct-for-RFC822
1349 ones. Use `forcecr'.
1351 <a name="T7">T7. How can I use fetchmail with Courier IMAP?</a></h2>
1353 <p>The courier mta doesn't like RCPT addresses that look like
1354 <code>someone@localhost</code>. Work around this with an
1355 <code>smtphost</code> or <code>smtpaddress</code>.
1358 <h2><a name="S1">S1. How can I use fetchmail with qpopper?</a></h2>
1360 Qualcomm's qpopper is probably the best-of-breed among POP3 servers, and
1361 is very widely deployed. Nevertheless, it has some problems which
1362 fetchmail exposes. We recommend using <a href="#G7">IMAP</a> instead if at
1363 all possible. If you must talk to qpopper, here are some problems to
1366 <p><h3>Problems with retrieving large messages from qpopper 2.53</h3>
1368 Tony Tang <a href="mailto:tony@atn.com.hk"><tony@atn.com.hk></a>
1369 reports that there is a bad intercation between fetchmail and qpopper
1370 2.5.3 under Red Hat Linux versions 5.0 to 5.2, kernels 2.0.34 to
1371 2.0.35. When fetching very large messages (over 700K) from 2.5.3,
1372 fetchmail will hang with a socket error.
1374 <p>This is probably not a fetchmail bug, but rather a symptom of some
1375 problem in the networking stack that qpopper's transmission pattern is
1376 tickling, as fetchpop (another Linux POP client) also displays the hang
1377 but Netscape running under Win95 does not. The problem can also be
1379 href="http://www.eudora.com/freeware/qpop.html">upgrading to qpopper
1382 <p><h3>Bad interaction with fetchmail 4.4.2 to 4.4.7</h3>
1384 Versions of fetchmail from 4.4.2 through 4.4.7 had a bad interaction
1385 with Eudora qpopper versions 2.3 and later. See <a href="#X5">X5</a>
1386 for details. The solution is to upgrade your fetchmail.
1389 <h2><a name="S2">S2. How can I use fetchmail with Microsoft Exchange?</a></h2>
1391 <p>It's been reliably reported that Exchange 2000's POP3 support is so
1392 broken that it's unusable. One symptom is that messages without
1393 a terminating newline get the POP3 message termination dot emitted --
1394 you guessed it -- right after the last character of the message, with
1395 no terminating newline added. This will hang fetchmail or any other
1396 RFC-compliant server. IMAP is alleged to work OK, though.
1398 <p>Older versions of Exchange are semi-usable.
1400 <p>Fetchmail using IMAP supports the proprietary NTLM mode used with
1401 M$ Exchange servers. To enable this, configure fetchmail with the
1402 --enable-NTLM option and recompile it. Specify a user option value
1403 that looks like `user@domain': the part to the left of the @ will
1404 be passed as the username and the part to the right as the NTLM domain.
1406 <p>M$ Exchange violates the POP3 and IMAP RFCs. Its LIST command does
1407 not reveal the real sizes of mail in the pop mailbox, but the sizes of
1408 the compressed versions in the exchange mail database (thanks to Arjan
1409 De Vet and Guido Van Rooij for alerting us to this problem).
1411 <p>Fetchmail works with M$ Exchange, despite this brain damage. Two
1412 features are compromised. One is that the --limit option will not
1413 work right (it will check against compressed and not actual sizes).
1414 The other is that a too-small SIZE argument may be passed to your
1415 ESMTP listener, assuming you're using one (this should not be a
1416 problem unless the actual size of the message is above the listener's
1417 configured length limit).
1419 <p>Somewhat belatedly, I've learned that there's supposed to be a
1420 registry bit that can fix this breakage:
1423 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MsExchangeIs\Parameters
1424 System\Pop3 Compatibility
1427 This is a bitmask that controls the variations from the standard protocol.
1428 The bits defined are:
1432 <DD>Report exact message sizes for the LIST command
1434 <DD>Allow arbitrary linear whitespace between commands and arguments
1436 <DD>Enable the LAST command
1438 <DD>Allow an empty PASS command (needed for users with blank
1439 passwords, but illegal in the protocol)
1441 <DD>Relax the length restrictions for arguments to commands (protocol
1442 requires 40, but some user names may be longer than that).
1444 <DD>Allow spaces in the argument to the USER command.
1447 There's another one that may be useful to know about:
1450 KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MsExchangeIs\Parameters
1451 System\Pop3 Performance
1456 <DD>Render messages to a temporary stream instead of sending directly
1457 from the database (should always be on)
1459 Flag unrenderable messages (instead of just failing commands)
1460 (should only be on if you are seeing the problems reported
1463 <DD>Return from the QUIT command before all messages have been deleted.
1466 The Microsoft pod-person who revealed this information to me admitted
1467 that he couldn't find it anywhere in their public knowledge base.
1469 <p>Another specific problem we have seen with Exchange servers has as its
1470 symptom a response to LOGIN that says "NO Ambiguous Alias". Grant
1473 This means that Exchange Server is too f*&#ing stupid to figure
1474 out which mailbox belongs to you. Instead of actually keeping
1475 track of which inbox belongs to which user, it uses some
1476 half-witted, guess-o-matic heuristic to try to guess your
1477 mailbox name from your username.
1479 <p>In your case it doesn't work because your username maps to more
1480 than one mailbox. For some people it doesn't work because
1481 their username maps to zero mailboxes. This is yet another
1482 inept, lame, almost criminally negligent design decision from
1483 our friends in Redmond.
1485 <p>You've got several options:
1489 Get your administrator to configure the server so that
1490 usernames and mailbox names are the same.
1492 Get your administrator to add an alias that maps your
1493 username explicitly to your mailbox name.
1496 <p>But, the best option involves a tactical nuclear weapon (an old
1497 ASROC will do), pissing off a lot people who live downwind from
1498 Redmond, and your choice of any Linux, NetBSD, FreeBSD, or
1501 <p>I'll provide the CD.
1504 <h2><a name="S3">S3. How can I use fetchmail with CompuServe RPA?</a></h2>
1506 First, make sure your fetchmail has the RPA support compiled in.
1507 Stock fetchmail binaries (such as you might get from an RPM) don't.
1508 You can check this by looking at the output of <code>fetchmail -V</code>;
1509 if you see the string "+RPA" after the version ID you're good to go,
1510 otherwise you'll have to build your own from sources (see the INSTALL
1511 file in the source distribution for directions).<p>
1513 Give your CompuServe pass-phrase in lower case as your password. Add
1514 `@compuserve.com' to your user ID so that it looks like `user
1515 <UserID>@compuserve.com', where <UserID> can be either
1516 your numerical userID or your E-mail nickname. An RPA-enabled
1517 fetchmail will automatically check for csi.com in the POP server's
1518 greeting line. If that's found, and your user ID ends with
1519 `@compuserve.com', it will query the server to see if it
1520 is RPA-capable, and if so do an RPA transaction rather than a
1521 plain-text password handshake.
1523 <p><strong>Warning:</strong> the debug (-v -v) output of fetchmail will show
1524 your pass-phrase in Unicode!
1526 <p>These two .fetchmailrc entries show the difference between an RPA and
1527 non-RPA configuration:
1530 # This version will use RPA
1531 poll csi.com via "pop.site1.csi.com" with proto POP3 and options no dns
1532 user "CSERVE_USER@compuserve.com" there with password "CSERVE_PASSWORD"
1533 is LOCAL_USER here options fetchall stripcr
1535 # This version will not use RPA
1536 poll non-rpa.csi.com via "pop.site1.csi.com" with proto POP3 and options no dns
1537 user "CSERVE_USER" there with password "CSERVE_POP3_PASSWORD"
1538 is LOCAL_USER here options fetchall stripcr
1542 <h2><a name="S4">S4. How can I use fetchmail with Demon Internet's SDPS?</a></h2>
1544 <h3>Single-drop mode</h3>
1546 You can get fetchmail to download the email for just one user from
1547 Demon Internet's POP3 server by giving it a username consisting of your
1548 Demon user name followed by your account name, with an at-sign between
1551 <p>For example, to download email for the user <philh@vision25.demon.co.uk>,
1552 you could use the following .fetchmailrc file:
1555 set postmaster "philh"
1556 poll pop3.demon.co.uk with protocol POP3:
1557 user "philh@vision25" is philh
1560 <h3>Multi-drop mode</h3>
1562 Demon Internet's SDPS service is an implementation of POP3. All messages
1563 have a Received: header added when they enter the maildrop, like this:
1566 Received: from punt-1.mail.demon.net by mailstore for fred@xyz.demon.co.uk
1567 id 899963657:10:27896:0; Thu, 09 Jul 98 05:54:17 GMT
1570 To enable multi-drop mode you need to tell fetchmail that 'mailstore' is
1571 the name of the host which accepted the mail, and let it know the
1572 hostname part(s) of your E-mail address. The following example assumes
1573 that your hostname is xyz.demon.co.uk, and that you have also bought
1574 "mail forwarding" for the domain my-company.co.uk (in which case your
1575 MTA must also be configured to accept mail sent to user@my-company.co.uk)
1578 poll pop3.demon.co.uk proto pop3 aka mailstore no dns:
1579 localdomains xyz.demon.co.uk my-company.co.uk
1580 user xyz is * fetchall
1583 The `fetchall' command ensures that all mail is downloaded. If you
1584 want to leave mail on the server use `uidl' and `keep'; Demon does not
1585 implement the obsolete `top' command, because SDPS combines messages
1586 residing on two separate punt clusters into a single POP3 maildrop.
1587 If you do use UIDL, be aware that the "user@host" form for fetching
1588 mail from a particular Demon host will confuse fetchmail's UIDL code;
1591 <p>Note that Demon may delete mail on the server which is more than 30
1592 days old; see their <a
1593 href="http://www.demon.net/info/helpdesk/demon_products/mail/sdps-tech.shtml">
1594 POP3 page</a> for details.
1596 <p><h3>The SDPS extension</h3>
1598 There's a different way to do multidrop. It's not necessary on Demon
1599 Internet, since fetchmail can parse Received addresses, but the person
1600 who implemented this didn't know that. It may be useful if Demon
1601 Internet ever changes mail transports.
1603 <p>SDPS includes a non-standard extension for retrieving the envelope of a
1604 message (*ENV), which fetchmail optionally supports if compiled with the
1605 --enable-SDPS option. If you have it, the first line of the fetchmail -V
1606 response will include the string "+SDPS".
1608 <p>Once you have SDPS compiled in, fetchmail in POP3 mode will
1609 automatically detect when it's talking to a Demon Internet host in
1610 multidrop mode, and use the *ENV extension to get an envelope To address.
1612 <p>The autodetection works by looking at the hostname in the POP3
1613 greeting line; if you're accessing Demon Internet through a proxy it
1614 may fail. To force SDPS mode, pick "sdps" as your protocol.
1617 <h2><a name="S5">S5. How can I use fetchmail with usa.net's servers?</a></h2>
1619 Enable `<CODE>fetchall</CODE>'. A user reports that the 2.2 version
1620 of USA.NET's POP server reports that you must use the
1621 `<CODE>fetchall</CODE>' option to make sure that all of the mail is
1622 retrieved, otherwise some may be left on the server. This is almost
1623 certainly a server bug.
1625 <p>The usa.net servers (at least in their 2.2 version, June 1998) don't
1626 handle the TOP command properly, either. Regardless of the argument
1627 you give it, they retrieve only about 10 lines of the message.
1628 Fetchmail normally uses TOP for message retrieval in order to avoid
1629 marking messages seen, but `<CODE>fetchall</CODE>' forces it to use
1632 <p>Also, we're told USA.NET adds a ton of hops to your messages. You may
1633 need to raise the MaxHopCount parameter in your sendmail.cf to avoid having
1634 fetched mail rejected.
1636 <p>(Note: Other failure modes have been reported on usa.net's servers.
1637 They seem to be chronically flaky. We recommend finding another
1641 <h2><a name="S6">S6. How can I use fetchmail with HP OpenMail?</a></h2>
1643 No special configuration is required, but OpenMail versions prior to
1644 6.0 have an annoying bug similar to the big one in <a
1645 href="#S2">Microsoft Exchange</a>. The message sizes it gives in the
1646 LIST are rounded to the nearest 1024 bytes. It also has a nasty habit
1647 of discarding headers it doesn't recognize, such as X- and Resent-
1650 <p>As with M$ Exchange, the only real fix for these problems is to get a
1651 POP (or preferably IMAP) server that isn't brain-dead. OpenMail's
1652 project manager claims these bugs have been fixed in 6.0.
1654 <p>We've had a more recent report (December 2001) that the TOP command
1655 fails, returning only one line regrardless of its argument, on something
1656 identifying itself as "OpenMail POP3 interface".
1659 <h2><a name="S7">S7. How can I use fetchmail with geocities POP3 servers?</a></h2>
1661 Nathan Cutler reports that the the mail.geocities.com POP3 servers
1662 fail to include the first Received line of the message in the send to
1663 fetchmail. This can solve problems if your MUA interprets Received
1664 continuations as body lines and doesn't parse any of the following
1667 <p>Workaround is to use "mda" keyword or "-mda" switch:
1669 mda "sed -e '1s/^\t/Received: /' | formail | /usr/bin/procmail -d <user>"
1671 Replace \t with exactly one tabulation character.
1673 You should also consider using "fetchall" option because Geocities' servers
1674 sometimes think that the first 45 messages have already been read.
1676 <p>Fix: Get an email provider that doesn't suck. The pop-up ads on
1677 Geocities are lame, you should boycott them anyway.
1680 <h2><a name="S8">S8. How can I use fetchmail with Hotmail?</a></h2>
1682 You can't, yet. But <a
1683 href="http://hawkins.emu.id.au/gotmail/">gotmail</a>
1684 might be what you need.
1687 <h2><a name="S9">S9. How can I use fetchmail with MSN?</a></h2>
1689 You can't. MSN uses something that looks like POP3, except the
1690 authentication part is nonstandard. And of course they don't
1691 document it, so nobody but their Windows clients can speak it.
1693 <p>This is a customer lock-in tactic; we recommend boycotting MSN as the
1694 only appropriate response.
1696 <p>As of 5.0.8, we have support for the client side of NTLM
1697 authentication. It's possible this may enable fetchmail to talk to
1698 MSN; if so, somebody should report it so this FAQ can be corrected.
1701 <h2><a name="S10">S10. How can I use fetchmail with SpryNet?</a></h2>
1703 The SpryNet POP3 servers mark a message queried with TOP as seen.
1704 This means that if your connection drops in mid-message, it may end
1705 up invisibly stuck on your mail spool. Use the <code>fetchall</code>
1706 flag to ensure that it's recovered on the next cycle.
1709 <h2><a name="S11">S11. How can I use fetchmail with FTGate?</a></h2>
1711 The FTGate V2 server (and possibly older versions as well) has a weird
1712 bug. It answers OK twice to a TOP request! Use the
1713 <code>fetchall</code> option to force use of RETR and work around this
1717 <h2><a name="S12">S12. How can I use fetchmail with MailMax?</a></h2>
1719 You can't. At least not if you want to be able to see attachments.
1720 MailMax has a bug; it reports the message length with attachments
1721 but doesn't download them on TOP or RETR.
1723 <p>Also, we're told that TOP sometimes fails to retrieve the entire
1724 message even when enough lines have been specified. The MailMax
1725 developers have acknowledged this bug as of 4 May 2000, but there is
1726 no fix yet. If you must use this server, force RETR with the
1727 <tt>fetchall</tt> option.
1730 <h2><a name="S13">S13. How can I use fetchmail with Novell GroupWise?</a></h2>
1732 The Novell GroupWise IMAP server would be better named GroupFoolish;
1733 it is (according to the designer of IMAP) unusably broken. Among
1734 other things, it doesn't include a required content length in its
1735 BODY[TEXT] response.
1737 <p>Fetchmail works around this problem, but we strongly recommend voting
1738 with your dollars for a server that isn't brain-dead. If you stick
1739 with code as shoddy as GroupWise seems to be, you will probably pay
1740 for it with other problems.
1743 <h2><a name="S14">S14. How can I use fetchmail with InterChange?</a></h2>
1745 You can't. At least not if you want to be able to see attachments.
1746 InterChange has a bug similar to the MailMax server; it reports the
1747 message length with attachments but doesn't download them on TOP or
1750 <p>On Jan 9 2001, the people at InfiniteMail sent me mail informing me that
1751 their new 3.61.08 release of InterChange fixes this problem. I don't
1752 have any reports one way or the other yet.
1754 <a name="S15">S15. How can I use fetchmail with GMX?</a></h2>
1756 <p>Use IMAP. The GMX StreamProxy server behaves badly on
1757 authentication failures, sending back a non-conformant error message
1758 (missing an <code>-ERR</code> tag) that confuses fetchmail.
1761 <h2><a name="K1">K1. How can I use fetchmail with SOCKS?</a></h2>
1763 Giuseppe Guerini added a --with-socks option that supports linking
1764 with socks library. If you specify the value of this option as
1765 ``yes'', the configure script will try to find the Rconnect library
1766 and set the makefile up to link it. You can also specify a directory
1767 containing the Rconnect library.
1769 <p>Alan Schmitt has added a similar --with-socks5 option that may work
1770 better if you have a recent version of the SOCKS library.
1773 <h2><a name="K2">K2. How can I use fetchmail with IPv6 and IPsec?</a></h2>
1775 To use fetchmail with IPv6, you need a system that supports IPv6, the "Basic
1776 Socket Interface Extensions for IPv6" (RFC 2133).
1777 This currently means that you need to have a BSD/OS or NetBSD system with
1778 the NRL IPv6+IPsec software distribution or a Linux system with a 2.2 or
1779 later kernel and net-tools. It should not be hard to build fetchmail on
1780 other IPv6 implementations if you can port the inet6-apps kit.
1782 <p>To use fetchmail with networking security (read: IPsec), you need a system that
1783 supports IPsec, the API described in the "Network Security API for Sockets"
1784 (draft-metz-net-security-api-01.txt), and the inet6-apps kit. This currently
1785 means that you need to have a BSD/OS or NetBSD system with the NRL IPv6+IPsec
1786 software distribution. A Linux IPsec implementation supporting this API will
1787 probably appear in the coming months.
1789 <p>The NRL IPv6+IPsec software distribution can be obtained from: <a
1790 href="http://web.mit.edu/network/isakmp">http://web.mit.edu/network/isakmp</a>
1793 <p>The inet6-apps kit can be obtained from <a href="http://ftp.ps.pl/pub/linux/IPv6/inet6-apps/">http://ftp.ps.pl/pub/linux/IPv6/inet6-apps/</a>.
1795 <p>More information on using IPv6 with Linux can be obtained from:
1798 <a href="http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO.html">
1799 http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO.html</a>
1801 <a href="http://www.ipv6.inner.net/ipv6">http://www.ipv6.inner.net/ipv6</a>
1804 <a href="http://www.inner.net/ipv6">http://www.inner.net/ipv6</a> (via IPv4)
1808 <h2><a name="K3">K3. How can I get fetchmail to work with ssh?</a></h2>
1810 <p>Use the <tt>plugin</tt> option. This is dead simple with IMAP:
1813 plugin "ssh %h /usr/sbin/imapd"
1816 <p>You may have to use a different absolute pathname, whatever the
1817 location of imapd on your mailserver is. This option tells fetchmail
1818 that instead of opening a connection on the server's port 143 and
1819 doing standard IMAP authentication, fetchmail should ssh to the server
1820 and run imapd, using the more secure ssh authentication (as well as
1821 getting ssh's end-to-end encryption). Most IMAP daemons will detect
1822 that they've been called from the command line and assume the
1823 connection is peauthenticated.
1825 <p>POP3 daemons aren't quite as smart. They won't know they are
1826 preauthenticated in this mode, so you'll actually have to ship your
1827 password. It will be under ssh encryption, though, so that shouldn't
1831 <h2><a name="K4">K4. What do I have to do to use the IMAP-GSS protocol?</a></h2>
1833 Fetchmail can use RFC1731 GSSAPI authorization to safely identify you
1834 to your IMAP server, as long as you can share Kerberos V credentials
1835 with your mail host and you have a GSSAPI-capable IMAP server.
1836 UW-IMAP (available via FTP at <a
1837 href="ftp://ftp.cac.washington.edu/mail/">ftp.cac.washington.edu</a>)
1838 is the only one I'm aware of and the one I recommend anyway for other
1839 reasons. You'll need version 4.1-FINAL or greater though, and it has
1840 to have GSS support compiled in.
1842 <p>Neither UW-IMAP nor fetchmail compile in support for GSS by default,
1843 since it requires libraries from the Kerberos V distribution
1844 (available via FTP at <a
1845 href="ftp://athena-dist.mit.edu/pub/ATHENA/kerberos">athena-dist.mit.edu</a>).
1846 If you have these, compiling in GSS support is simple: add a
1847 <pre>--with-gssapi=[/path/to/krb5/root]</pre> option to configure. For
1848 instance, I have all of my Kerberos V libraries installed under
1849 /usr/krb5 so I run <pre>configure --with-gssapi=/usr/krb5</pre>
1851 <p>Setting up Kerberos V authentication is beyond the scope of this FAQ
1852 (you may find Jim Rome's paper <a
1853 href="http://www.ornl.gov/~jar/HowToKerb.html"> How to Kerberize your
1854 site</a> helpful), but you'll at least need to add a credential for
1855 imap/[mailhost] to the keytab of the mail server (IMAP doesn't just
1856 use the host key). Then you'll need to have your credentials ready on
1857 your machine (cf. kinit).
1859 <p>After that things are very simple. Set your protocol to imap-gss in your
1860 .fetchmailrc, and omit the password, since imap-gss doesn't need one. You
1861 can specify a username if you want, but this is only useful if your mailbox
1862 belongs to a username different from your Kerberos principal.
1864 <p>Now you don't have to worry about your password appearing in cleartext in
1865 your .fetchmailrc, or across the network.
1868 <h2><a name="K5">K5. How can I use fetchmail with SSL?</a></h2>
1870 You'll need to have the <a href="http://www.openssl.org/">OpenSSL</a>
1871 libraries installed. Configure with --with-ssl. If you have the
1872 OpenSSL libraries installed in the default location (/usr/local/ssl)
1873 this will suffice. If you have them installed in a non-default
1874 location, you'll need to specify it as an argument to --with-ssl after
1877 <p>Note that there is a known bug in the implementation of SSL_peek
1878 under OpenSSL versions 0.9.5 and older that fetchmail occasionally
1879 tripped over, causing hangs. It is recommended that you install 0.9.6
1882 <p>Fetchmail binaries built this way support <code>ssl</code>,
1883 <code>sslkey</code>, and <code>sslcert</code> options that control
1884 SSL encryption. You will need to have an SSL-enabled mailserver
1885 to use these options. See the manual page for details and some words
1886 of care on the limited security provided.
1888 <p>If your open OpenSSL session dies with a message that complains "PRNG
1889 not seeded", update or improve your operating system. This means that
1890 the OpenSSL library on your machine has been unable to locate a source
1891 of random bits from which to seed its random-number generator;
1892 normally these come from the <tt>/dev/urandom</tt>, and this message
1893 probably means your OS doesn't have that device.<p>.
1895 An interactive program could seed the random number generator from
1896 keystroke timings or some other form of user input. Because fetchmail
1897 is primarily designed to run forever as a background daemon, that
1898 option is not available in this case.
1901 <h2><a name="R1">R1. Fetchmail isn't working, and -v shows `SMTP connect failed' messages.</a></h2>
1903 Fetchmail itself is probably working, but your SMTP port 25 listener
1904 is down or inaccessible.
1906 <p>The first thing to check is if you can telnet to port 25 on your smtp
1907 host (which is normally `localhost' unless you've specified an smtp
1908 option in your .fetchmailrc or on the command line) and get a greeting
1909 line from the listener. If the SMTP host is inaccessible or the listener
1910 is down, fix that first.
1912 <p>In Red Hat Linux 6.9, SMTP is disabled by default. To fix this,
1913 set "DAEMON=yes" in your /etc/sysconfig/sendmail file, then restart
1914 sendmail by running "/sbin/service sendmail restart".
1916 <p>If the listener seems to be up when you test with telnet, the most
1917 benign and typical problem is that the listener had a momentary seizure
1918 due to resource exhaustion while fetchmail was polling it -- process
1919 table full or some other problem that stopped the listener process
1920 from forking. If your SMTP host is not `localhost' or something else
1921 in /etc/hosts, the fetchmail glitch could also have been caused by
1922 transient nameserver failure.
1924 <p>Try running fetchmail -v again; if it succeeds, you had one of these
1925 kinds of transient glitch. You can ignore these hiccups, because a
1926 future fetchmail run will get the mail through.
1928 <p>If the listener tests up, but you have chronic failures trying to
1929 connect to it anyway, your problem is more serious. One way to work
1930 around chronic SMTP connect problems is to use --mda. But this only
1931 attacks the symptom; you may have a DNS or TCP routing problem. You
1932 should really try to figure out what's going on underneath before it
1933 bites you some other way.
1935 <p>We have one report (from toby@eskimo.com) that you can sometimes solve
1936 such problems by doing an <CODE>smtp</CODE> declaration with an IP
1937 address that your routing table maps to something other than the
1938 loopback device (he used ppp0).
1940 <p>We also have a report that this error can be caused by having an
1941 /etc/hosts file that associates your client host name with more than
1944 <p>It's also possible that your DNS configuration isn't
1945 looking at <code>/etc/hosts</code> at all. If you're using libc5,
1946 look at <code>/etc/resolv.conf</code>; it should say something like
1952 so your <code>/etc/hosts</code> file is checked first. If you're
1953 running GNU libc6, check your <code>/etc/nsswitch.conf</code> file. Make
1954 sure it says something like
1960 again, in order to make sure <code>/etc/hosts</code> is seen first.
1962 <p>If you have a hostname set for your machine, and this hostname does
1963 not appear in /etc/hosts, you will be able to telnet to port 25 and
1964 even send a mail with rcpt to: user@host-not-in-/etc/hosts, but
1965 fetchmail can't seem to get in touch with sendmail, no matter what you
1968 <p>We had another report from a Linux user of fetchmail 2.1 who solved his SMTP
1969 connection problem by removing the reference to -lresolv from his link
1970 line and relinking. Apparently in some older Linux distributions the
1971 libc bind library version works better.
1973 <p>As of 2.2, the configure script has been hacked so the bind library is
1974 linked only if it is actually needed. So under Linux it won't be, and
1975 this particular cause should go away.
1978 <h2><a name="R2">R2. When I try to configure an MDA, fetchmail doesn't work.</a></h2>
1980 (I hear this one from people who have run into the blank-line problem in <a href="#X1">X1</a>.)
1982 <p>Try sending yourself test mail and retrieving it using the
1983 command-line options `<CODE>-k -m cat</CODE>'. This will dump exactly what
1984 fetchmail retrieves to standard output (plus the Received line
1985 fetchmail itself adds to the headers).
1987 <p>If the dump doesn't match what shows up in your mailbox when you
1988 configure an MDA, your MDA is mangling the message. If it doesn't
1989 match what you sent, then fetchmail or something on the server is
1993 <h2><a name="R3">R3. Fetchmail dumps core when given an invalid rc file.</a></h2>
1995 This is usually reported from AIX or Ultrix, but has even been known
1996 to happen on Linuxes without a recent version of <code>flex</code>
1997 installed. The problem appears to be a result of building with an
1998 archaic version of lex.
2000 <p>Workaround: fix the syntax of your .fetchmailrc file.
2002 <p>Fix: build and install the latest version of <a
2003 href="ftp://prep.ai.mit.edu/~ftp/pub/gnu">flex</a> from the Free
2004 Software Foundation. An FSF <a
2005 href="http://www.gnu.ai.mit.edu/order/ftp.html">mirror site</a>
2006 will help you get it faster.
2009 <h2><a name="R4">R4. Fetchmail dumps core in -V mode, but operates normally otherwise.</a></h2>
2011 We've had this reported to us under Linux using libc-5.4.17 and gcc-2.7.2.
2012 It does not occur with libc-5.3.12 or earlier versions.
2014 <p>Workaround: link with GNU malloc rather than the stock C library malloc.
2016 <p>We're told there is some problem with the malloc() code in that
2017 version which makes it fragile in the presence of multiple free()
2018 calls on the same pointer (the malloc arena gets corrupted).
2019 Unfortunately it appears from doing gdb traces that whatever free()
2020 calls producing the problem are being made by the C library itself, not the
2021 fetchmail code (they're all from within fclose, and not an fclose called
2022 directly by fetchmail, either).
2025 <h2><a name="R5">R5. Running fetchmail in daemon mode doesn't work.</a><br></h2>
2027 We have one report from a SunOS 4.1.4 user that trying to run
2028 fetchmail in detached daemon mode doesn't work, but that using the
2029 same options with -N (nodetach) is OK. We have another report of
2030 similar behavior from one Linux user, but many other Linux users
2033 <p>If this happens, you have a specific portability problem with the code
2034 in daemon.c that detaches and backgrounds the daemon fetchmail. The isolated
2035 Linux case has been chased down to a failure in dup(2) that may reflect a
2038 <p>As a workaround, you can start fetchmail with -N and an ampersand
2039 to background it. A Sun user recommends this:
2042 (fetchmail --nodetach <other params> &)
2045 The extra pair of parens is significant --- it makes sure that the process
2046 detaches from the initial shell (one more shell is started and dies
2047 immediately, detaching fetchmail and making it child of PID 1). This is
2048 important when you start fetchmail interactively and than quit
2049 interactive shell. The line above makes sure fetchmail lives after
2053 <h2><a name="R6">R6. Fetchmail randomly dies with socket errors.</a></h2>
2055 Check the MTU value in your PPP interface reported by
2056 <code>/sbin/ifconfig</code>. If it's over 600, change it in your PPP
2057 options file. (<code>/etc/ppp/options</code> on my box). Here are
2058 option values that work:
2065 <p>Another circumstance that can trigger this is if you are polling a
2066 virtual-mail-server name that is round-robin connected to different
2067 actual servers, so you get different IP addresses on different poll
2068 cycles. To work around this, change the poll name either to the real
2069 name of one of the servers in the ring or to a corresponding IP
2073 <h2><a name="R7">R7. Fetchmail running as root stopped working after an OS upgrade</a></h2>
2075 In RH 6.0, the HOME value in the boot-time root environment changed
2076 from /root to / as the result of a change in init. Move your
2077 .fetchmailrc or use a -f option to explicitly point at the file.
2078 (Oddly, a similar problem has been reported from Debian systems.)
2081 <h2><a name="R8">R8. Fetchmail is timing out after fetching certain
2082 messages but before deleting them</a></h2>
2084 There's a TCP/IP stalling problem under Redhat 6.0 (and possibly other
2085 recent Linuxes) that can cause this symptom. Brian Boutel writes:
2088 TCP timestamps are turned on on my Linux boxes (I assume it's now the
2089 default). This uses 12 extra bytes per segment.
2090 When the tcp connection starts, the other end agrees a MSS of 1460,
2091 and then fragments 1460 byte chunks into 1448 and 12, because
2092 is is not allowing for the timestamp.
2094 <p>Then, for reasons I can't explain, it waits a long time (typically 2
2095 minutes) after the ack is sent before sending the next (fragmented)
2096 packet. Turning off tcp timestamps avoids the fragmentation and
2097 restores normal behaviour. To do this, [execute]
2099 <p>echo 0 > /proc/sys/net/ipv4/tcp_timestamps
2101 <p>I'm still unclear about the details of why this is happening. At least
2102 [now] I am now getting good performance and no queue blocking.
2106 <h2><a name="R9">R9. Fetchmail is timing out during message fetches</a></h2>
2108 This is probably a general networking issue. Sending a "RETR" command will
2109 cause the server to start sending large amounts of data, which means
2110 large packets. If your networking layer has a packet-fragmentation
2111 problem, that's where you'll see it.
2114 <h2><a name="R10">R10. Fetchmail is dying with SIGPIPE.</a></h2>
2116 This probably means you have an <code>mda</code> option. Your MDA is
2117 croaking while being passed a message. Best fix is to remove the
2118 <code>mda</code> option and pass mail to your port 25 SMTP listener.
2121 <h2><a name="H1">H1. Fetchmail hangs when used with pppd.</a></h2>
2123 Your problem may be with pppd's `demand' option. We have a report that
2124 fetchmail doesn't play well with it, but works with pppd if `demand'
2125 is turned off. We have no idea why this is.
2128 <h2><a name="H2">H2. Fetchmail hangs during the MAIL FROM exchange.</a></h2>
2130 <p>The symptom: 'fetchmail -v' retrieves mail fine, but appears to hang after
2131 sending the MAIL FROM command
2134 SMTP> MAIL FROM: <someone@somewhere>
2137 <p>The hang is actually occuring when sendmail looks up a sender's
2138 address in DNS. The problem isn't in fetchmail but in the
2139 configuration of sendmail. You must enable the 'nodns' and
2140 'nocanonify' features of sendmail.
2142 <p>Here was my fix for RedHat 7.2:
2146 <li># cp sendmail.mc sendmail-mine.mc
2147 <li>Edit sendmail-mine.mc and add lines:
2152 <li>Build a new sendmail.cf
2154 # m4 sendmail-mine.cf > /etc/sendmail.cf
2156 <li>Restart sendmail.
2159 <p>For more details consult the file /usr/share/sendmail-cf/README.
2162 <h2><a name="H3">H3. Fetchmail hangs while fetching mail.</a></h2>
2164 <p>The symption: 'fetchmail -v' retrieves the first few messages, but
2168 fetchmail: SMTP< 550 5.0.0 Access denied
2169 fetchmail: SMTP> RSET
2170 fetchmail: SMTP< 250 2.0.0 Reset state
2171 .......fetchmail: flushed
2172 fetchmail: POP3> DELE 1
2173 fetchmail: POP3< +OK marked deleted
2176 <p>Check and see if you're allowing sendmail connections through TCP
2179 <p>Adding 'sendmail : ALL' to /etc/hosts.allow could solve this problem.
2182 <h2><a name="D1">D1. I think I've set up fetchmail correctly, but I'm not getting any mail.</a></h2>
2184 Maybe you have a .forward or alias set up that you've forgotten about. You
2185 should probably remove it.
2187 <p>Or maybe you're trying to run fetchmail in multidrop mode as root
2188 without a .fetchmailrc file. This doesn't do what you think it
2189 should; see question <a href="#C1">C1</a>.
2191 <p>Or you may not be connecting to the SMTP listener. Run fetchmail -v
2192 and see <a href="#R1">R1</a>.
2195 <h2><a name="D2">D2. All my mail seems to disappear after a dropped connection.</a></h2>
2197 One POP3 daemon used in the Berkeley Unix world that reports itself as
2198 POP3 version 1.004 actually throws the queue away. 1.005 fixed that.
2199 If you're running this one, upgrade immediately. (It also truncates
2200 long lines at column 1024)
2202 <p>Many POP servers, if an interruption occurs, will restore the whole
2203 mail queue after about 10 minutes. Others will restore it right
2204 away. If you have an interruption and don't see it right away, cross
2205 your fingers and wait ten minutes before retrying.
2207 <p>Some servers (such as Microsoft's NTMail) are mis-designed to restore
2208 the entire queue, including messages you have deleted. If you have
2209 one of these and it flakes out on you a lot, try setting a small
2210 <code>--fetchlimit</code> value. This will result in more IP connects
2211 to the server, but will mean it actually executes changes to the queue
2214 <p>Qualcomm's qpopper, used at many BSD Unix sites, is better behaved.
2215 If its connection is dropped, it will first execute all DELE commands as
2216 though you had issued a QUIT (this is a technical violation of
2217 the POP3 RFCs, but a good idea in a world of flaky phone lines). Then it
2218 will re-queue any message that was being downloaded at hangup time.
2219 Still, qpopper may require a noticeable amount of time to do deletions
2220 and clean up its queue. (Fetchmail waits a bit before retrying in
2221 order to avoid a `lock busy' error.)
2224 <h2><a name="D3">D3. Mail that was being fetched when I interrupted my fetchmail seems to have been vanished.</a></h2>
2226 Fetchmail only sends a delete mail request to the server when either
2227 (a) it gets a positive delivery acknowledgment from the SMTP
2228 listener, or (b) it gets one of the spam-filter errors (see the
2229 description of the <code>antispam></code> option) from the
2230 listener. No interrupt can cause it to lose mail.
2232 <p>However, IMAP2bis has a design problem in that its normal fetch
2233 command marks a message `seen' as soon as the fetch command to get it
2234 is sent down. If for some reason the message isn't actually delivered
2235 (you take a line hit during the download, or your port 25 listener
2236 can't find enough free disk space, or you interrupt the delivery in
2237 mid-message) that `seen' message can lurk invisibly in your server
2240 <p>Workaround: add the `<CODE>fetchall</CODE>' keyword to your fetch options.
2242 <p>Solution: switch to an <a href="http://www.imap.org">IMAP4</a> server.
2245 <h2><a name="M1">M1. I've declared local names, but all my multidrop
2246 mail is going to root anyway.</a></h2>
2248 Somehow your fetchmail is never recognizing the hostname part of
2249 recipient names it parses out of To/Cc/envelope-header lines as
2250 matching the name of the mailserver machine. To check this, run
2251 fetchmail in foreground with -v -v on. You will probably see a lot of
2252 messages with the format ``line rejected, %s is not an alias of the
2253 mailserver'' or ``no address matches; forwarding to %s.''
2255 <p>These errors usually indicate some kind of DNS configuration problem
2256 either on the server or your client machine.
2258 <p>The easiest workaround is to add a `<CODE>via</CODE>' option (if
2259 necessary) and add enough aka declarations to cover all of your
2260 mailserver's aliases, then say `<CODE>no dns</CODE>'. This will take
2261 DNS out of the picture (though it means mail may be uncollected if
2262 it's sent to an alias of the mailserver that you don't have
2265 <p>It would be better to fix your DNS, however. DNS problems can hurt
2266 you in lots of ways, for example by making your machines
2267 intermittently or permanently unreachable to the rest of the net.
2269 <p>Occasionally these errors indicate the sort of header-parsing problem
2270 described in <a href="#M7">M7</a>.
2273 <h2><a name="M2">M2. I can't seem to get fetchmail to route to a local domain properly.</a></h2>
2275 A lot of people want to use fetchmail as a poor man's internetwork
2276 mail gateway, picking up mail accumulated for a whole domain in a single
2277 server mailbox and then routing based on what's in the To/Cc/Bcc lines.
2279 <p>In general, this is not really a good idea. It would be smarter to
2280 just let the mail sit in the mailserver's queue and use fetchmail's
2281 ETRN or ODMR modes to trigger SMTP sends periodically (of course, this means
2282 you have to poll more frequently than the mailserver's expiration period).
2283 If you can't arrange this, try setting up a UUCP feed.
2285 <p>If neither of these alternatives is available, multidrop mode may do
2286 (though you <em>are</em> going to get hurt by some mailing list
2287 software; see the caveats under THE USE AND ABUSE OF MULTIDROP
2288 MAILBOXES on the man page). If you want to try it, the way to do it
2289 is with the `<CODE>localdomains</CODE>' option.
2291 <p>In general, if you use localdomains you need to make sure of two other
2294 <p><strong>1. You've actually set up your .fetchmailrc entry to invoke multidrop mode.</strong>
2296 <p>Many people set a `<CODE>localdomains</CODE>' list and then forget
2297 that fetchmail wants to see more than one name (or the wildcard `*')
2298 in a `<CODE>here</CODE>' list before it will do multidrop routing.
2300 <p><strong>2. You may have to set `no envelope'.</strong>
2302 <p>Normally, multidrop mode tries to deduce an envelope address from a message
2303 before parsing the To/Cc/Bcc lines (this enables it to avoid losing to mailing
2304 list software that doesn't put a recipient address in the To lines).
2306 <p>Some ways of accumulating a whole domain's messages in a single server
2307 mailbox mean it all ends up with a single envelope address that is
2308 useless for rerouting purposes. You may have to set `<CODE>no
2309 envelope</CODE>' to prevent fetchmail from being bamboozled by this.
2311 <p>Check also answer <a href="#T1">T1</a> on a reliable way to do multidrop
2312 delivery if your ISP (or your mail redirection provider) is using qmail.
2315 <h2><a name="M3">M3. I tried to run a mailing list using multidrop, and I have a mail loop!</a></h2>
2317 This isn't fetchmail's fault. Check your mailing list. If the list
2318 expansion includes yourself or anybody else at your mailserver (that is, not on
2319 the client side) you've created a mail loop. Just chop the host part off any
2320 local addresses in the list.
2322 <p>If you use sendmail, you can check the list expansion with
2323 <CODE>sendmail -bv</CODE>.
2326 <h2><a name="M4">M4. My multidrop fetchmail seems to be having DNS problems.</a></h2>
2328 <p>We have one report from a Linux user (not the same one as in <a
2329 href="#R1">R1</a>!) who solved this problem by removing the reference
2330 to -lresolv from his link line and relinking. Apparently in some
2331 older Linux distributions the libc5 bind library version works
2334 <p>As of 2.2, the configure script has been hacked so the bind library
2335 is linked only if it is actually needed. So under Linux it won't be,
2336 and this problem should go away.
2339 <h2><a name="M5">M5. I'm seeing long DNS delays before each message is processed.</a></h2>
2341 <p>Use the `<CODE>aka</CODE>' option to pre-declare as many of your
2342 mailserver's DNS names as you can. When an address's host part
2343 matches an aka name, no DNS lookup needs to be done to check it.
2345 <p>If you're sure you've pre-declared all of your mailserver's DNS names,
2346 you can use the `<CODE>no dns</CODE>' option to prevent other hostname
2347 parts from being looked up at all.
2349 <p>Sometimes delays are unavoidable. Some SMTP listeners try to call DNS
2350 on the From-address hostname as a way of checking that the address is valid.
2353 <h2><a name="M6">M6. How do I get multidrop mode to work with majordomo?</a></h2>
2355 <p>In order for sendmail to execute the command strings in the majordomo
2356 alias file, it is necessary for sendmail to think that the mail it
2357 receives via SMTP really is destined for a local user name. A normal
2358 virtual-domain setup results in delivery to the default mailbox,
2359 rather than expansion through majordomo.
2361 <p>Michael <michael@bizsystems.com> gave us a recipe for dealing
2362 with this case that pairs a run control file like this:
2365 poll your.pop3.server proto pop3:
2367 localdomains virtual.localdomain1.com virtual.localdomain2.com ...
2368 user yourISPusername is root * here,
2369 password yourISPpassword fetchall
2372 with a hack on your local sendmail.cf like this:
2375 #############################################
2376 # virtual info, local hack for ruleset 98 #
2377 #############################################
2379 # domains to treat as direct mapped local domain
2381 CVvirtual.localdomain1.com virtual.localdomain2.com ...
2382 ---------------------------
2384 -------------------------
2385 # handle virtual users
2387 R$+ <@ $=V . > $: $1 < @ $j . >
2388 R< @ > $+ < @ $=V . > $: $1 < @ $j . >
2389 R< @ > $+ $: $1
2390 R< error : $- $+ > $* $#error $@ $1 $: $2
2391 R< $+ > $+ < @ $+ > $: $>97 $1
2394 <p>This ruleset just strips virtual domain names off the addresses of incoming
2395 mail. Your sendmail must be 8.8 or newer for this to work. Michael
2399 I use this scheme with 2 virtual domains and the default ISP
2400 user+domain and service about 30 mail accounts + majordomo on my
2401 inside pop3 server with fetchmail and sendmail 8.83
2405 <h2><a name="M7">M7. Multidrop mode isn't parsing envelope addresses from
2406 my Received headers as it should.</a></h2>
2408 <p>It may happen that you're getting what appear to be well-formed
2409 sendmail Received headers, but fetchmail can't seem to extract an
2410 envelope address from them. There can be a couple of reasons for
2413 <h3>Spurious Received lines need to be skipped:</h3>
2415 <p>First, fetchmail might be looking at the wrong Received header.
2416 Normally it looks only on the first one it sees, on the theory that
2417 that one was last added and is going to be the one containing your
2418 mailserver's theory of who the message was addressed to.
2420 <p>Some (unusual) mailserver configurations will generate extra Received
2421 lines which you need to skip. To arrange this, use the optional
2422 skip prefix argument of the `envelope' option; you may need to say
2423 something like `<code>envelope 1 Received</code>' or `<code>envelope 2
2426 <h3>The `by' clause doesn't contain a mailserver alias:</h3>
2428 <p>When fetchmail parses a Received line that looks like
2431 Received: from send103.yahoomail.com (send103.yahoomail.com [205.180.60.92])
2432 by iserv.ttns.net (8.8.5/8.8.5) with SMTP id RAA10088
2433 for <ksturgeon@fbceg.org>; Wed, 9 Sep 1998 17:01:59 -0700
2436 it checks to see if `iserv.ttns.net' is a DNS alias of your mailserver
2437 before accepting `ksturgeon@fbceg.org' as an envelope address. This
2438 check might fail if your DNS were misconfigured, or if you were using `no dns'
2439 and had failed to declare iserv.ttns.net as an alias of your server.
2442 <h2><a name="M8">M8. Users are getting multiple copies of messages.</a></h2>
2444 <p>It's a consequence of multidrop. What's happening is that you have
2445 N users subscribed to the same list. The list software sends N
2446 copies, not knowing they will end up in the same multidrop box. Since
2447 they are both locally addressed to all N users, fetchmail delivers N
2448 copies to each user.
2450 <p>Fetchmail tries to eliminate adjacent duplicate messages in a
2451 multidrop mailbox. However, this logic depends on the message-ID
2452 being identical in both copies. It also depends on the two copies
2453 being adjacent in the server mailbox. The former is usually the case,
2454 but the latter condition sometimes fails in a timing-dependent way if
2455 the server was processing multiple incoming mail streams.
2457 <p>I could eliminate this problem by keeping a list of all message-IDs
2458 received during a poll so far and dropping any message that matches a
2459 seen mail ID. The trouble is that this is an O(N**2) operation that
2460 might significantly slow down the retrieval of large mail batches.
2463 <h2><a name="X1">X1. Spurious blank lines are appearing in the headers of fetched mail.</a></h2>
2465 <p>What's probably happening is that the POP/IMAP daemon on your
2466 mailserver is inserting a non-RFC822 header (like X-POP3-Rcpt:) and
2467 something in your delivery path (most likely an old version of the
2468 <em>deliver</em> program, which sendmail often calls to do local delivery) is
2469 failing to recognize it as a header.
2471 <p>This is not fetchmail's problem. The first thing to try is installing
2472 a current version of <em>deliver</em>. If this doesn't work, try to
2473 figure out which other program in your mail path is inserting the
2474 blank line and replace that. If you can't do either of these things,
2475 pick a different MDA (such as procmail) and declare it with the
2476 `<CODE>mda</CODE>' option.
2479 <h2><a name="X2">X2. My mail client can't see a Subject line.</a></h2>
2481 <p>First, see <a href="#X1">X1</a>. This is quite probably the same
2482 problem (X-POP3-Rcpt header or something similar being inserted by
2483 the server and choked on by an old version of <em>deliver</em>).
2485 <p>The O'Reilly sendmail book does warn that IDA sendmail doesn't process
2486 X- headers correctly. If this is your problem, all I can suggest is
2487 replacing IDA sendmail, because it's broken and not RFC822 conformant.
2490 <h2><a name="X3">X3. Messages containing "From" at start of line are being split.</a></h2>
2492 <p>If you know the messages aren't split in your server mailbox, then this
2493 is a problem with your POP/IMAP server, your client-side SMTP listener or
2494 your local delivery agent. Fetchmail cannot split messages.
2496 <p>Some POP server daemons ignore Content-Length headers and split messages on
2497 From lines. We have one report that the 2.1 version of the BSD popper
2498 program (as distributed on Solaris 2.5 and elsewhere) is broken this way.
2500 <p>You can test this. Declare an mda of `cat' and send yourself one
2501 piece of mail containing "From" at start of a line. If you see a
2502 split message, your POP/IMAP server is at fault. Upgrade to a more
2505 <p>Sendmail and other SMTP listeners don't split RFC822 messages either.
2506 What's probably happening is either sendmail's local delivery agent or
2507 your mail reader are not quite RFC822-conformant and are breaking
2508 messages on what it thinks are Unix-style From headers. You can
2509 figure out which by looking at your client-side mailbox with vi or
2510 more. If the message is already split in your mailbox, your local
2511 delivery agent is the problem. If it's not, your mailreader is the
2514 <p>If you can't replace the offending program, take a look at your
2515 sendmail.cf file. There will likely be a line something like
2518 Mlocal, P=/usr/bin/procmail, F=lsDFMShP, S=10, R=20/40, A=procmail -Y -d $u
2521 describing your local delivery agent. Try inserting the `E' option in the
2522 flags part (the F= string). This will make sendmail turn each dangerous
2523 start-of-line From into a >From, preventing programs further downstream
2527 <h2><a name="X4">X4.</a><a name="generic_mangling">My mail is being mangled in a new and different way</a></h2>
2529 <p>The first thing you need to do is pin down what program is doing the
2530 mangling. We don't like getting bug reports about fetchmail that are
2531 actually due to some other program's malfeasance, so please go through
2532 this diagnostic sequence before sending us a complaint.
2534 <p>There are five possible culprits to consider, listed here in the order
2535 they pass your mail:
2538 <li> Programs upstream of your server mailbox.
2539 <li> The POP or IMAP server on your mailserver host.
2540 <li> The fetchmail program itself.
2541 <li> Your local sendmail.
2542 <li> Your LDA (local delivery agent), as called by sendmail or
2543 specified by <code>mda</CODE>.
2546 <p>Often it happens that fetchmail itself is OK, but using it exposes
2547 pre-existing bugs in your downstream software, or your downstream
2548 software has a bad interaction with POP/IMAP. You need to pin down
2549 exactly where the message is being garbled in order to deduce what is
2552 <p>The first thing to do is send yourself a test message, and retrieve it
2553 with a .fetchmailrc entry containing the following (or by running with
2554 the equivalent command-line options):
2557 mda "cat >MBOX" keep fetchall
2560 <p>This will capture what fetchmail gets from the server, except for (a)
2561 the extra Received header line fetchmail prepends, (b) header address
2562 changes due to <code>rewrite</code>, and (c) any end-of-line changes
2563 due to the <code>forcecr</code> and <code>stripcr</code> options.
2564 MBOX will in fact contain what programs downstream of fetchmail
2567 <p>The most common causes of mangling are bugs and misconfigurations in
2568 those downstream programs. If MBOX looks unmangled, you will know
2569 that is what is going on and that it is not fetchmail's problem. Take
2570 a look at the other FAQ items in this section for possible clues about
2571 how to fix your problem.
2573 <p>If MBOX looks mangled, the next thing to do is compare it with your
2574 actual server mailbox (if possible). That's why you specified
2575 <code>keep</code>, so the server copy would not be deleted. If your
2576 server mailbox looks mangled, programs upstream of your server mailbox
2577 are at fault. Unfortunately there is probably little you can do about
2578 this aside from complaining to your site postmaster, and nothing at
2579 all fetchmail can do about it!
2581 <p>More likely you'll find that the server copy looks OK. In that case
2582 either the POP/IMAP server or fetchmail is doing the mangling. To
2583 determine which, you'll need to telnet to the server port and simulate
2584 a fetchmail session yourself. This is not actually hard (both POP3
2585 and IMAP are simple, text-only, line-oriented protocols) but requires
2586 some attention to detail. You should be able to use a fetchmail -v
2587 log as a model for a session, but remember that the "*" in your LOGIN
2588 or PASS command dump has to be replaced with your actual password.
2590 <p>The objective of manually simulating fetchmail is so you can see
2591 exactly what fetchmail sees. If you see a mangled message, then your
2592 server is at fault, and you probably need to complain to your
2593 mailserver administrators. However, we like to know what the broken
2594 servers are so we can warn people away from them. So please send
2595 us a transcript of the session including the mangling <em>and the
2596 server's initial greeting line</em>. Please tell us anything else
2597 you think might be useful about the server, like the server host's
2600 <p>If your manual fetchmail simulation shows an unmangled message,
2601 congratulations. You've found an actual fetchmail bug, which is a
2602 pretty rare thing these days. Complain to us and we'll fix it.
2603 Please include the session transcript of your manual fetchmail
2604 simulation along with the other things described in the FAQ entry on
2605 <a href="#G3">reporting bugs</a>.
2608 <h2><a name="X5">X5. Using POP3, retrievals seems to be fetching too much!</a></h2>
2610 <p>This may happen in versions of fetchmail after 4.4.1 and before 4.4.8.
2611 Versions after 4.4.1 use POP3's TOP command rather than RETR, in order
2612 to avoid marking the message seen (leaving it unseen is helpful for
2613 later recovery if you lose your connection in the middle of a
2616 <p>Versions of fetchmail from 4.4.2 through 4.4.7 had a bad interaction
2617 with Eudora qpopper versions 2.3 and later. The TOP bounds check was
2618 fooled by an overflow condition in the TOP argument. Decrementing the
2619 TOP argument in 4.4.7 fixed this.
2621 <p>Fix: Upgrade to a later version of fetchmail.
2623 <p>Workaround: set the <code>fetchall</code> option. Under POP3
2624 this has the side effect of forcing RETR use.
2627 <h2><a name="X6">X6. My mail attachments are being dropped or mangled.</a></h2>
2629 <p>This isn't fetchmail's doing -- fetchmail never drops lines in message
2630 bodies or attachments. It may be your POP server, or it may be the
2631 sender's mail user agent (or a bad combination of both).
2633 <p>The Mail Max POP3 server and the InterChange and Imail IMAP servers
2634 are known to simply drop MIME attachments when uploading messages.
2635 We've had sporadic reports of problems with Microsoft Exchange and
2636 Outlook servers. Windows- and NT-based POP servers seem especially
2637 prone to mangle attachments. If you are running one of these,
2638 replacing your server with a Unix machine is probably the only
2641 <p>We've also had a report that Lotus Notes sometimes trashes the
2642 MIME type of messages. In particular, it seems to modify MIME
2643 headers introducing type application/pdf, mangling the type
2644 to application/octet-stream. It may corrupt other MIME types
2647 <p>The IMAP service of Lotus Domino has a known bug in the way it
2648 generates MIME Content-type headers (observed on Lotus Domino 5.0.2b).
2649 It's a subtle one that doesn't show up when Netscape Messenger and
2650 other clients use a FETCH BODY[] to grab the whole message. When
2651 fetchmail uses FETCH RFC822.HEADER and FETCH RFC822.TEXT to get first
2652 the header and then the body, Domino generates different Boundary tags
2653 for each part, .e.g. one tag is declared in the Content-type header and
2654 another is used to separate the MIME parts in the body. This doesn't
2655 work. (I have heard a rumor that this bug is scheduled to be fixed
2656 in Domino release 6; you can find a workaround at contrib/domino.)
2658 <p>Another rich source of attachment problems is Microsoft Exchange and
2659 Microsoft Outlook. If you see unreadable attachments with a
2660 ContentType of "application/x-tnef", you're having this problem. The
2661 <a href="http://world.std.com/~damned/software.html">TNEF</a> utility
2664 <p>Rob Funk explains: Unfortunately there also remain many mail user
2665 agents that don't write correct MIME messages. One big offender is Sun
2666 MailTool attachments, which are formatted enough like MIME that some
2667 programs could get confused; these are generated by the mailtool and
2668 dtmail programs (the mail programs in Sun's OpenWindows and CDE
2671 <p>One solution to problems related to misformatted MIME attachments is
2672 the <a href="ftp://ftp.uu.se/pub/unix/networking/mail/emil/">emil</a>
2674 href="ftp://ftp.uu.se/pub/unix/networking/mail/emil/TUTORIAL.html">tutorial</a>
2675 file at that site for details on emil. It is useful for
2676 converting character sets, attachment encodings, and attachment
2677 formats. At this writing, emil does not appear to have been
2678 maintained since a patch to version 2.1.0beta9 in late 1997, but it is
2681 <p>One good way of using emil is from within procmail. You can have
2682 procmail look for signs of problematic message formatting, and pipe
2683 those messages through emil to be fixed. emil will not always be able
2684 to fix the problem, in which case the message is unchanged.
2686 <p>A possible rule to be inserted into a .procmailrc file for using emil
2691 * 1^1 ^Content-Type: \/X-sun[^;]*
2692 * 1^1 ^Content-Type: \/application/mac-binhex[^;]*
2693 * 1^1 ^Content-Transfer-Encoding: \/x-binhex[^;]*
2694 * 1^1 ^Content-Transfer-Encoding: \/x-uuencode[^;]*
2696 LOG="Converting $MATCH
2699 | emil -A B -T Q -B BA -C iso-8859-1 -H Q -F MIME \
2700 | gawk '{gsub(/\r\n?/,"\n");print $0}'
2704 <p>The "1^1" in the conditions is a way of specifying to procmail that if
2705 any one of the four listed expressions is found in the message, the
2706 total condition is considered true, and the message gets passed into
2707 emil. These four subconditions check whether the message has a Sun
2708 attachment, a binhex attachment, or a uuencoded attachment; there are
2709 others that could be added to check these things better and to check
2710 other relevant conditions. The "LOG=" line writes a line into the
2711 procmail log; the lone double-quote beginning the following line makes
2712 sure the log entry gets an end-of-line character. The call to gawk
2713 (GNU awk) is for fixing end-of-line conventions, since emil sometimes
2714 leaves those in the format of the originating machine; it could
2715 probably be replaced with a sed subsitution.
2717 <p>The emil call itself tries to ensure that the message uses:
2720 <li> BinHex encoding for any Apple Macintosh-only attachments
2721 <li> Quoted-Printable encoding for text (when necessary)
2722 <li> Base64 Encoding for binary attachments
2723 <li> iso-8859-1 character set for text (unfortunately emil can't yet
2724 convert from windows-1252 to iso-8859-1)
2725 <li> Quoted-Printable encoding for headers
2726 <li> MIME attachment format
2729 <p>Most of these (the primary exceptions being the character set and the
2730 Apple binary format) are as they should be for good internet
2731 interoperability.<p>
2733 <p>Some mail servers (Lotus Domino is a suspect here) mangle
2734 Sun-formatted messages, so the conversion to MIME needs to happen
2735 before such programs see the message. The ideal is to rid the world
2736 of Sun-formatted messages: don't use mailtool for sending attachments
2737 (it doesn't understand MIME anyway, and most of the world doesn't
2738 understand its attachments, so it really shouldn't be used at all),
2739 and make sure dtmail is set to use MIME rather than mailtool's format.
2742 <h2><a name="X7">X7. Some mail attachments are hanging fetchmail.</a></h2>
2744 <p>This isn't fetchmail's problem either; fetchmail doesn't know anything
2745 about mail attachments and doesn't treat them any differently from
2748 <p>The most usual cause of this problem seems to be bugs in your network
2749 transport layer's capability to handle the very large TCP/IP packets
2750 that attachments tend to turn into. You can test this theory by trying to
2751 download the offending message through a webmail account; using HTTP
2752 for the message tends to simulate large-packet stress rather well, and
2753 you will probably find that the messages that seem to be choking
2754 fetchmail will make your HTTP download speed drop to zero.
2756 <p>This problem can be caused by subtle bugs in the packet-reassembly
2757 layer of your TCP/IP stack; these often don't manifest at normal
2758 packet sizes. It may also be caused by malfunctioning path-MTU
2759 discovery on the mailserver. Or, if there's a modem in the link,
2760 it may be because the attachment contains the Hayes mode escape "+++".
2763 <h2><a name="X8">X8. A spurious ) is being appended to my messages.</a></h2>
2765 <p>Blame it on that rancid pile of dung and offal called Microsoft
2766 Exchange. Due to the problem described in <a href="#S2">S2</a>, the
2767 IMAP support in fetchmail cannot follow the IMAP protocol 100%. Most
2768 of the time it doesn't matter, but if you combine it with an SMTP
2769 server that behaves unusually, you'll get a spurious ) at message end.
2771 <p>One piece of software that can trigger this is the Interchange mail
2772 server, as used by, e.g., mailandnews.com. Here's what happens:
2774 <p>1. Someone sends mail to your account. The last line of the message
2775 contains text. So at the SMTP level, the message ends with, e.g.
2778 <p>2. The SMTP handler sees the final "\r\n.\r\n" and recognizes the
2779 end of the message. However, instead of doing the normal thing, which
2780 is tossing out the ".\r\n" and leaving the first '\r\n' as part of the
2781 email body, Interchange throws out the whole "\r\n.\r\n", and leaves
2782 the email body without any line terminator at the end of it. RFC821
2783 does not forbid this, though it probably should.
2785 <p>3. Fetchmail, or some other IMAP client, asks for the message. IMAP
2786 returns it, but it's enclosed inside parentheses, according to the
2787 protocol. The message size in bytes is also present. Because the
2788 message doesn't end with a line terminator, the IMAP client sees:
2792 where the ')' is from IMAP.
2794 <p>4. Fetchmail only deals with complete lines, and can't trust the
2795 stated message size because Microsoft Exchange fscks it up.
2797 <p>5. As a result, fetchmail takes the final 'blahblah)' and puts it
2798 at the end of the message it forwards on. If you have verbosity on,
2799 you'll get a message about actual != expected.
2801 <p>There is no fix for this. The nuke mentioned in <a
2802 href="#S2">S2</a> looks more tempting all the time.
2805 <h2><a name="O1">O1. The --logfile option doesn't work if the logfile doesn't exist.</a></h2>
2807 <p>This is a feature, not a bug. It's in line with normal practice for
2808 system daemons and allows you to suppress logging by removing the log,
2809 without hacking potentially fragile startup scripts. To get around
2810 it, just touch(1) the logfile before you run fetchmail (this will have
2811 no effect on the contents of the logfile if it already exists).
2814 <h2><a name="O2">O2. Every time I get a POP or IMAP message the header
2815 is dumped to all my terminal sessions.</a></h2>
2817 <p>Fetchmail uses the local sendmail to perform final delivery, which
2818 Netscape and other clients doesn't do; the announcement of new messages
2819 is done by a daemon that sendmail pokes. There should be a ``biff''
2820 command to control this. Type
2826 to turn it off. If this doesn't work, try the command
2832 which is essentially what <code>biff -n</code> will do. If this
2833 doesn't work, comment out any reference to ``comsat'' in your
2834 /etc/inetd.conf file and restart inetd.
2836 <p>In Slackware Linux distributions, the last line in /etc/profile is
2848 to solve the problem system-wide.
2851 <h2><a name="O3">O3. Does fetchmail reread its rc file every poll cycle?</a></h2>
2853 <p>No, but versions 5.2.2 and later will notice when you modify your rc
2854 file and restart, reading it.
2857 <h2><a name="O4">O4. Why do deleted messages show up again when I take
2858 a line hit while downloading?</a></h2>
2860 <p>Because you're using a POP3 other than Qualcomm qpopper, or an IMAP
2861 with a long expunge interval.
2863 <p>According to the POP3 RFCs, deletes aren't actually performed until
2864 you issue the end-of-session QUIT command. Fetchmail cannot fix this,
2865 because doing it right takes cooperation from the server. There are
2866 two possible remedies:
2868 <p>One is to switch to qpopper (the free POP3 server from Qualcomm,
2869 the Eudora people). The qpopper software violates the POP3 RFCs by
2870 doing an expunge (removing deleted messages) on a line hangup, as well
2871 as on processing a QUIT command.
2873 <p>The other (which we recommend) is to switch to <a
2874 href="http://www.imap.org">IMAP</a>. IMAP has an explicit expunge
2875 command and fetchmail normally uses it to delete messages immediately
2876 after they are downloaded.
2878 <p>If you get very unlucky, you might take a line hit in the window
2879 between the delete and the expunge. If you've set a longer expunge
2880 interval, the window gets wider. This problem should correct itself
2881 the next time you complete a successful query.
2884 <h2><a name="O5">O5. Why is fetched mail being logged with my name, not the real From address?</a></h2>
2886 <p>Because logging is done based on the address indicated by the sending
2887 SMTP's MAIL FROM, and some listeners are picky about that address.
2889 <p>Some SMTP listeners get upset if you try to hand them a MAIL FROM
2890 address naming a different host than the originating site for your
2891 connection. This is a feature, not a bug -- it's supposed to help
2892 prevent people from forging mail with a bogus origin site. (RFC 1123
2893 says you shouldn't do this exclusion...)
2895 <p>Since the originating site of a fetchmail delivery connection is
2896 localhost, this effectively means these picky listeners will barf on
2897 any MAIL FROM address fetchmail hands them with an @ in it!
2899 <p>Versions 2.1 and up try the header From address first and fall back to
2900 the calling-user ID. So if your SMTP listener isn't picky, the log
2904 <h2><a name="O6">O6. I'm seeing long sendmail delays or hangs near the start of each poll cycle.</a></h2>
2906 <p>Sendmail does a hostname lookup when it first starts up, and also each
2907 time it gets a HELO in listener mode.
2909 <p>Your resolver configuration may be causing one of these lookups to
2910 fail and time out. Check <code>/etc/resolv.conf</code> and
2911 <code>/etc/hosts</code> file. Make sure your hostname and
2912 fully-qualified domain name are both in <code>/etc/hosts</code>, and
2913 that hosts is looked at before DNS is queried. You probably also want
2914 your remote mail server(s) to be in the hosts file.
2916 <p>You can suppress the startup-time lookup if need to by reconfiguring
2917 with <code>FEATURE(nodns)</code>.
2919 <p>Configuring your bind library to cache DNS lookups locally may help,
2920 and is a good idea for speeding up other services as well. Switching to
2921 a faster MTA like qmail or exim might help.
2924 <h2><a name="O7">O7. Why doesn't fetchmail deliver mail in date-sorted order?</a></h2>
2926 <p>Because that's not the order the server hands it to fetchmail in.
2928 <p>Fetchmail getting mail from a POP server delivers mail in the order
2929 that your server delivers mail. Fetchmail can't do anything about
2930 this; it's a limitation of the underlying POP protocol.
2932 <p>In theory it might be possible for fetchmail in IMAP mode to sort
2933 messages by date, but this would be in violation of two basics of
2934 fetchmail's design philosophy: (a) to be as simple and transparent a
2935 pipe as possible, and (b) to <em>hide</em>, rather than emphasize, the
2936 differences between the remote-fetch protocols it uses.
2938 <p>Re-ordering messages is a user-agent function, anyway.
2941 <h2><a name="O8">O8. I'm using pppd. Why isn't my monitor option working?</a></h2>
2943 <p>There is a combination of circumstances that can confuse fetchmail.
2944 If you have set up demand dialing with pppd, and pppd has an idle
2945 timeout, and you have lcp-echo-interval set, then the
2946 lcp-echo-interval time must be longer than the pppd idle timeout.
2947 Otherwise it is going keep increasing the packet counters that fetchmail
2948 relies upon, triggering fetchmail into polling after its own delay
2949 interval and thus preventing the pppd link from ever reaching its
2953 <h2><a name="O9">O9. Why does fetchmail keep retrieving the same messages
2954 over and over?</a></h2>
2956 <p>First, check to see that you haven't enabled the <cite>keep</cite>
2957 and <cite>fetchall</cite> option. If you have, turn <cite>keep</cite> off.
2959 <p>There are various forms of lossage involving the POP3 UIDL feature
2960 that can lead to all your old messages being seen again after a line
2961 drop. I have given up trying to fix these, as the UIDL code breaks
2962 worse every time I touch it. The problem is fundamental; maintaining
2963 and garbage-collecting the right kind of client-side state is just
2964 hard. Whoever put UIDLs in RFC1725 and removed LAST should be hung
2965 up by his thumbs and whipped with scorpions. The right answers are
2966 either (a) live with the occasional breakage, (b) switch to IMAP4,
2967 or (c) fix the code yourself and send me a patch. Unless you choose
2968 (c), I don't want to hear about it.
2970 <p>This can also happen when some other mail client is logged in to your
2971 mail server, if it uses a simple exclusive-locking scheme (and many,
2972 especially most POP3 servers, do exactly that). Your fetchmail is
2973 able to retrieve the messages, but because the mailbox is write-locked
2974 by the other instance yours can neither mark messages seen or delete them.
2975 The solution is to either (a) wait for the other client to finish, or (b)
2978 <p>James Stevens <James.Stevens@kyzo.com> writes:<p>
2981 <p>We had a Linux box dialing the Net and collecting mail from an NT POP3
2982 server. Fetchmail was correctly collecting and deleting each e-mail
2983 one by one. However,the dial-up connection was very unreliable and
2984 would often just drop out in the middle of a session.
2986 <p>Interestingly, unless the TCP POP3 connection was terminated normally
2987 (I guess with a POP3 "QUIT" command) NT would then roll back all the
2990 <p>This meant if the first e-mail was very large it might just end up
2991 continuously collecting it, basically jamming the queue. Or, if the
2992 queue became very full itmight never get a long enough phone
2993 connection to retrieve the entire mailbox, and NT would roll back any
2994 deletes, so it would end up collecting (and delivering) the first few
2995 e-mails again and again. As the POP3 mailbox became fuller and fuller
2996 the chances of getting a connection long enough to collect theentire
2997 mailbox became smaller and smaller.
2999 <p>Our solution was to make fetchmail only collect a few (say 5 or 10)
3000 e-mails at atime, thus trying to ensure that the POP3 connection is
3001 terminated correctly.
3004 <p>Unfortunately, this is exactly the way POP3 servers are supposed
3005 to behave on a line drop, according to the RFCs. I recommend
3006 switching to IMAP and using a short expunge interval.
3009 <h2><a name="O10">O10. Why is the received date on all my messages the same?</a></h2>
3011 This is a design choice in your MTA, not fetchmail. It's taking the received
3012 date from the last Received header.<p>
3015 <table width="100%" cellpadding=0><tr>
3016 <td width="30%">Back to <a href="index.html">Fetchmail Home Page</a>
3017 <td width="30%" align=center>To <a href="/~esr/sitemap.html">Site Map</a>
3018 <td width="30%" align=right>$Date: 2002/03/26 14:41:17 $
3021 <ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com"><esr@thyrsus.com></A></ADDRESS>
3026 compile-command: "(cd ~/WWW; upload fetchmail/fetchmail-FAQ.html)"