On Fri, Jan 30, 2009 at 02:37:25PM -0600, Vruwink, Timothy Roger wrote:
> Here are the headers of the original outgoing email. When the user replies
> to this message her incoming emails gets scrambled. Only seems to happen for
> her though.
>
> Received: from xxxx
> (1xxxx) with Microsoft SMTP Server (TLS) id 8.1.336.0; Thu, 29 Jan
> 2009 09:54:05 -0600
> Received: from xxxx (xxxxxx]) by
> relay03.cites.uiuc.edu (8.14.2/8.14.2) with ESMTP id n0TFs4B3010014 for
> <xxxxx; Thu, 29 Jan 2009 09:54:05 -0600 (CST)
> Received: by xxxx (Postfix, from userid 65534) id BDC32161F7;
> Thu, 29 Jan 2009 09:54:04 -0600 (CST)
> Date: Thu, 29 Jan 2009 09:54:04 -0600
> To: xxxx>
> From: xxxx>
> Subject: [#572595] Support Ticket Opened
> Message-ID: <[email protected]>
> X-Priority: 3
> X-Mailer: PHPMailer (phpmailer.codeworxtech.com) [version 2.2]
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8bit
> Content-Type: text/plain; charset="UTF-8"
A plain-text message that is not base64 encoded. And does this already
have the unexpected base64 text when the user reads it, or is it just
the replies that do?
In any case the problem is hard to solve remotely. You need to capture
original messages (tcpdump if necessary) at every hop and find out which
MIME parser is screwing up. It is unlikely to be Postfix. Good luck.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[email protected]?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
