On Sat, Jul 25, 2015 at 08:39:54PM +0200, Herbert J. Skuhra wrote: > On Sat, Jul 25, 2015 at 08:31:09AM -0700, Seth wrote: > > On Sat, 25 Jul 2015 01:27:00 -0700, Herbert J. Skuhra <[email protected]> > > wrote: > > >anyone else who is running OpenSMTPD on FreeBSD receive broken > > >e-mails? In tcpdump/wireshark the message looks ok, but in the trace log > > >the lines are broken. Receiving the same message with Postfix works! > > > > I haven't seen problem of this sort so far, but I don't have any public > > facing FreeBSD/OpenSMTPD servers, the ones I do have all sit behind > > OpenBSD/OpenSMTPD relays. > > > > When you say 'broken' what exactly does that mean? Only part of the message > > is delivered instead of A complete one? > > Only lines with special characters are cut. I first had this issue when > replying to e-mails from this mailing list: > > http://article.gmane.org/gmane.mail.opensmtpd.general/2842 > > my reply: > > http://article.gmane.org/gmane.mail.opensmtpd.general/2843 > > and: > > http://article.gmane.org/gmane.mail.opensmtpd.general/2849 > > my reply: > > http://article.gmane.org/gmane.mail.opensmtpd.general/2850 > > But I guess in those cases the message must have been corrupted by the > receiving server (mx1.poolp.org). > > Later I had this issue with e-mails from a different mailing list. > Unfortunately those message are missing on gmane. I can reproduce this > issue easily: > > - run OpenSMTPD, request mlm to resend the message ... broken > - run Postfix, request mlm to resend the message ... OK > > I can provide the messages, pcap file and opensmtpd trace. >
I did a bit of tracking and pinpointed the issue. The client sends mail content that uses the msb of each byte but doesn't use the 8BITMIME SMTP extension causing OpenSMTPD to assume each byte is really using 7-bits. I suspect this does not trigger on Postfix because it considers we're in an 8-bit byte world... and I guess in 2015 we can just do the same. I'll remove the code that distinguishes between both and make 8BITMIME a no-op, which fixes your issue as far as I can see. -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
