fetchmail-friends
[Top] [All Lists]

Re: [fetchmail]Domino IMAP and missing Content-Transfer-Encoding

2006-02-16 10:17:46
Anthony Kim <Anthony(_dot_)Kim(_at_)walgreens(_dot_)com> writes:

I'm having a problem with missing Content-Transfer-Encoding
headers.  The server is Domino IMAP4 Server Release 6.5.4FP1.
When reading email via IMAP, everything appears normal.  However,
after fetchmail retrieves the message, I lose the
Content-Transfer-Encoding header and often mails end up looking like
garbage (many =3D=3D=3D etc)

Here are the relevant headers when viewed through an IMAP connection:

Subject: Re: Extended Attributes API
Sender: owner-freebsd-current(_at_)freebsd(_dot_)org
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Original-To: freebsd-current(_at_)freebsd(_dot_)org
Delivered-To: freebsd-current(_at_)freebsd(_dot_)org
References: <20060215124132(_dot_)GA51235(_at_)idkfa(_dot_)ath(_dot_)cx>
        <20060215150037(_dot_)J98052(_at_)fw(_dot_)reifenberger(_dot_)com>
        <20060215163813(_dot_)GA69533(_at_)idkfa(_dot_)ath(_dot_)cx>
        
<20060215174212(_dot_)C67143(_at_)beagle(_dot_)kn(_dot_)op(_dot_)dlr(_dot_)de>
User-Agent: nail 11.2 8/15/04
MIME-Version: 1.0

Curiously, I ran tcpdump and it appears that during the RFC822
HEADER fetch, the Content-Transfer-Encoding is not retrieved:

Excellent debugging. Thank you.

Well, this pretty clearly is a server bug.

There is nothing in fetchmail that would say
"send me all headers but xyz".

I don't know why this is happening.  If I can read the header via
IMAP, why wouldn't fetchmail retrieve it?  Is it a phantom header?
Any ideas?

Yes. fetchmail retrieves header and body separately, near line 950 in
imap.c you'll see

    gen_send(sock, "FETCH %d RFC822.HEADER", number);

In case you're unfamiliar with C: the %d gets replaced by the "number"
in decimal representation.

What does your mailer request?
Does it retrieve header and body separately.
What command does it send?

I am aware of a similar bug in web.de's IMAP server, it omits the
trailing --BOUNDARY-- line in MIME messages that separates the last MIME
part from the epilogue, where retrieval through the web interface was
fine; I conclude that some IMAP servers implement some commands
improperly, and others correctly. Given the complexity and many
varieties in IMAP4r1 (RFC-3501 nowadays), this is not a surprise to me.

I presume the problem is similar. Perhaps if we find an equivalent
command to retrieve the header that works, you can file a bug report
against Domino and if it turns out to be unfixable on their end, they
(IBM) can sponsor a workaround :-)

(All my attempts to contact web.de starved in dead ends, there is no
way to contact them with such issues that would give even an automated
"we're looking at it" response---and I'm not calling 3,63 €/min 0900
premium rate phone numbers to tell them.)

fetchmail -V

This is fetchmail release 6.3.2+POP2+RPA+NTLM+SDPS+SSL+OPIE+NLS.

(gratefully received and removed from the quote).

-- 
Matthias Andree

_______________________________________________
Fetchmail-friends mailing list
Fetchmail-friends(_at_)lists(_dot_)ccil(_dot_)org
http://lists.ccil.org/cgi-bin/mailman/listinfo/fetchmail-friends