From a265e608020ddefc6fcc6e17ff2ec38e94791838 Mon Sep 17 00:00:00 2001
From: Matthias Andree
If you have a question or answer you think ought to be added to -this FAQ list, mail it to fetchmail's maintainer, Eric S. Raymond, -at esr@thyrsus.com.
+this FAQ list, file it to one of the trackers at our BerliOS + project site or post to one of the fetchmail mailing lists (see +below).Yes I will, provided you include enough diagnostic information for me to go on. Send bugs to fetchmail-friends. +href="mailto:fetchmail-users@lists.berlios.de">fetchmail-users. When reporting bugs, please include the following:
If your bug is something that used to work but stopped working when you upgraded, then you can help pin the bug down by trying intermediate versions +href="http://download.berlios.de/fetchmail/">intermediate versions of fetchmail until you identify the revision that broke your feature. The smart way to do this is by binary search on the version sequence. First, try the version halfway between your last @@ -420,7 +421,7 @@ fetchmail simple so it stays reliable.
features (such as password encryption, or multiple concurrent polls from the same instance of fetchmail) see ESR's design -notes. Note that this document is partially obsoleted by the +notes. Note that this document is partially obsoleted by the updated design notes.Fetchmail is a mature project, no longer in constant active @@ -452,14 +453,18 @@ directory.
There is a fetchmail-friends list -(fetchmail-friends@lists.ccil.org) for people who want to discuss +
There is a fetchmail-users list (fetchmail-users@lists.berlios.de) +for bug reports and people who want to discuss configuration issues of +fetchmail. It's a Mailman list, see http://lists.berlios.de/mailman/listinfo/fetchmail-users.
+There is a fetchmail-devel list +(fetchmail-devel@lists.berlios.de) for people who want to discuss fixes and improvements in fetchmail and help co-develop it. It's a -MailMan list, which you can sign up for at http://lists.ccil.org/mailman/listinfo/fetchmail-friends. +Mailman list, which you can sign up for at http://lists.berlios.de/mailman/listinfo/fetchmail-devel. There is also an announcements-only list, -fetchmail-announce@lists.ccil.org, which you can sign up for at http://lists.ccil.org/mailman/listinfo/fetchmail-announce.
+fetchmail-announce@lists.berlios.de, which you can sign up for at http://lists.berlios.de/mailman/listinfo/fetchmail-announce.H?J?Delivered-To: $u -Mmdrop, P=/usr/bin/procmail, F=lsDFMqSPfhnu9J, +Mmdrop, P=/usr/bin/procmail, F=lsDFMqSPfhnu9J, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrToSMTP, T=DNS/RFC822/X-Unix, A=procmail -Y -a $u -d $h @@ -2165,7 +2170,7 @@ daemon, that option is not available in this case. OpenSSL utility toolkit, something like this may work:-poll MYSERVER port 993 plugin "openssl s_client -connect %h:%p" +poll MYSERVER port 993 plugin "openssl s_client -connect %h:%p" protocol imap username MYUSERNAME password MYPASSWORD@@ -2551,7 +2556,7 @@ configuration of sendmail. You must enable the 'nodns' and
FEATURE(nodns) @@ -2559,7 +2564,7 @@ configuration of sendmail. You must enable the 'nodns' and
# m4 sendmail-mine.cf > /etc/sendmail.cf @@ -2980,7 +2985,7 @@ turn each dangerous start-of-line From into a >From, preventing programs further downstream from acting up.
-X4.X4. My mail is being mangled in a new and different way
@@ -3095,7 +3100,7 @@ or mangled.
Fetchmail doesn't discard attachments; fetchmail doesn't have any idea that attachments are there. Fetchmail treats the body of each message as an uninterpreted byte stream and passes it through without alteration. -If you are not receiving attachments through fetchmail, it is because +If you are not receiving attachments through fetchmail, it is because your mailserver is not sending them to you.
The fix for this is to replace your mailserver with one that works. @@ -3105,8 +3110,8 @@ seem especially prone to mangle attachments. If you are running one of these, replacing your server with a Unix machine is probably the only effective solution.
-We've had sporadic reports of problems with Microsoft Exchange and -Outlook servers. These sometimes randomly fail to ship +
We've had sporadic reports of problems with Microsoft Exchange and +Outlook servers. These sometimes randomly fail to ship attachments to your client. This is a known bug, acknowledged by Microsft.
@@ -3282,7 +3287,7 @@ the message doesn't end with a line terminator, the IMAP client sees:- + ....blahblah)...@@ -3339,13 +3344,13 @@ is biff y -Change this to +Change this to
biff n-to solve the problem system-wide. +to solve the problem system-wide.