From ecf8f327f483e1a0f347bff3f17a5c08873fd0a3 Mon Sep 17 00:00:00 2001 From: Matthias Andree Date: Tue, 18 Aug 2009 11:35:54 +0000 Subject: Add X10 on truncated message bodies. svn path=/branches/BRANCH_6-3/; revision=5418 --- fetchmail-FAQ.html | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index c04361ea..b4f38530 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -246,6 +246,9 @@ fetchmail.
messages.
X9. Missing "Content-Transfer-Encoding" header with Domino IMAP
+X10. Fetchmail delivers partial messages
+ +

Other problems

O1. The --logfile option doesn't work if the logfile @@ -3217,6 +3220,24 @@ MIME". Solution: switch Domino to "Keep in Sender's format".

Kim's list post

+

X10. Fetchmail delivers partial + messages

+ +

Fetchmail is sometimes reported to deliver partial messages. This +is usually related to network outages that occur while fetchmail is +downloading a message body. In such cases, fetchmail has downloaded a +complete header, so your header will be intact. The message body will be +truncated, and fetchmail will later attempt to redownload the +message (providing the server is standards conformant).

+ +

The reason for the truncation is that fetchmail streams the body +directly from the POP3/IMAP server into the SMTP/LMTP server or MDA, so +fetchmail has already written a part of the message before it notices it +will be incomplete, and fetchmail cannot abort a transaction it has +started, and it's unclear if it ever will be able to, because this is +not standardized and the outcome will depend on the receiving software +(be it SMTP/LMTP or MDA).

+

Other problems

O1. The --logfile option doesn't work if -- cgit v1.2.3