just as an fyi, Gmail switched to sending out utf-8 (for messages we compose) by default in 2014 and removed the feature that allowed users to override this a year ago. Downgrading from utf-8 to some charset that handles a much smaller subset of characters seems mostly unnecessary at this point. We still have some stragglers for other Google services, but we're working through them.
We're still playing with trying to switch all utf-8 text messages to 8bit encoding, unfortunately brower generated html often generates lines that are too long... but it's something we're playing with. Well, obviously 6532 messages are 8bit, but still a small fraction of those. I'm sure there is some small fraction of older software out there which can't handle it, but at this point, it really is a tiny fraction. Brandon On Mon, Apr 11, 2016 at 5:25 AM, Robert Mueller <[email protected]> wrote: > Reported by one of our users... > > --- > Diagnostic information for administrators: > > Generating server: AM4PR0601MB1986.eurprd06.prod.outlook.com > > [email protected] > Remote Server returned '550 5.6.0 CAT.InvalidContent.Exception: > InvalidCharsetException, Character set name (ISO-8859-10) is invalid or > not installed.; cannot handle content of message with InternalId > 5093831213990, InternetMessageId <...>.' > --- > > Really? > > -- > Rob Mueller > [email protected] > > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
