From 779ef8dea7a68becaa52b6c65fd38a132c903eb3 Mon Sep 17 00:00:00 2001
From: Matthias Andree
Date: Fri, 3 Mar 2006 08:50:57 +0000
Subject: Add X9. Missing "Content-Transfer-Encoding" header with Domino IMAP.
Thanks to Anthony Kim.
svn path=/branches/BRANCH_6-3/; revision=4706
---
NEWS | 5 +++++
fetchmail-FAQ.html | 17 ++++++++++++++++-
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 59454999..3d92f325 100644
--- a/NEWS
+++ b/NEWS
@@ -45,6 +45,11 @@ fetchmail 6.3.3 (not yet released):
reported by Roger Lynn.
* --idle can now be specified on the command line, too.
+# DOCUMENTATION:
+* The FAQ item X9, Domino IMAP omits Content-Transfer-Encoding header, was
+ added. Information provided by Anthony Kim on the fetchmail-friends list
+ in March 2006.
+
fetchmail 6.3.2 (released 2006-01-22):
Unless otherwise noted, changes to this release were made by Matthias Andree.
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 3eeb7044..1c826b06 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -241,7 +241,8 @@ mangled.
fetchmail.
X8. A spurious ) is being appended to my
messages.
-
+X9. Missing "Content-Transfer-Encoding" header
+with Domino IMAP
Other problems
O1. The --logfile option doesn't work if the logfile
@@ -3269,6 +3270,20 @@ on, you'll get a message about actual != expected.
There is no fix for this. The nuke mentioned in S2 looks more tempting all the time.
+
+
+Domino 6 IMAP was found by Anthony Kim in February 2006 to
+erroneously omit the "Content-Transfer-Encoding" header in messages
+downloaded through IMAP, causing messages to display improperly. This
+happened with Domino's incoming mail format configured to "Prefers
+MIME". Solution: switch Domino to "Keep in Sender's format".
+
+Reference: Anthony
+ Kim's list post
+
+
Other problems