>>> Can you turn off the 8BITMIME extension that postfix advertises? It >>> seems >>> from the RFC (http://tools.ietf.org/html/rfc4952), if 8BITMIME isn't >> >> That seems to be the right logic but I can't find the proper way to do >> it >> with postfix. >> >> Anyway, I'm not sure about the whole 8BITMIME thing and whether it >> counts >> for message content or envelope or both? >> It it counts for both, why does Cyrus lmtp advertise 8BITMIME and then >> refuses to accept mail with 8bit envelope. >> I'm really confused and from looking at different list archives I see >> that >> I'm not alone. > > Agreed. > > From what I can see, the original 8BITMIME extension was 8-bit message > content, but has been updated to include 8-bit SMTP transaction envelopes > as > well. It might be a mismatch between that over time (eg postfix changed at > 2.4.5 as well) Okay, so you confirm my impression that message content and envelope seem to be treated the same way now (for example with postfix). Then, wouldn't it make sense to do the same with Cyrus? Could parseaddr() be relaxed to do this? Simon ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
