Re: [fetchmail-devel] broken behavior in Exchange Server 2003 IMAP4rev1

[Rob M. <rob...@gm...>]

On 11/2/07, Adam Simpkins <sim...@ci...> wrote:
> Hi,
<---SNIP--->>
> I tracked down the problem, and it occurs because the Exchange server
> is rewriting the MIME boundary before sending it to the IMAP client.
> It rewrites the boundary differently (using a different randomly
> generated string) for each IMAP request.  Because fetchmail downloads
> the headers and body separately, this results in a different boundary
> in the Content-Type header than in the message body.
<---SNIP--->
> In case it helps, my IMAP server reports itself as:
>   Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1

Can you use POP instead, and if so does it have the same bug?

I'd personally suggest filing a bug with Microsoft.  Re-writing emails
like that probably runs the risk of breaking digitally signed emails
that include headers (DKIM springs to mind, though I suspect it
doesn't sign that header by default).  Of course, I'd expect the
answer to be "Upgrade to the latest version" :)

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche