Hot. Too bad our 3rd party libraries don't seem to concat spanned values like that. Lame. I had read some RFCs (but of course not that one). It would still be preferable if I could override dbmail/gmime to prevent that since the message did not seem to come in that way. Thanks!
Kristian Oye, Software Engineer -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tomas Kuliavas Sent: Tuesday, October 09, 2012 6:45 PM To: DBMail mailinglist Subject: Re: [Dbmail] Mangled MIME Content-Type in dbmail 2.2.17? 2012.10.10 01:49 Kris Oye rašė: > > Some of the messages being retrieved from our dbmail store seem to > have a mangled Content-Type. The boundary for the > multipart/alternative message is being stored as: > > Content-Type: multipart/alternative; > > boundary*0=----0000000000000000000000000000000000000000000000000000000000; > boundary*1=00000 > > > The Exim configuration also sends out a copy of the original message > and my client I see: > > > Content-Type: multipart/alternative; boundary= > "----000000000000000000000000000000000000000000000000000000000000000" > > > > Exim spawns dbmail-smtp to deliver the message to MySQL. Does the > Content-Type get rewritten during this process? (Seems to). Has > anyone else seen this behavior and "fixed it?" See rfc2231 Header is valid. -- Tomas _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
