> On 16 Feb 2016, at 11:24, Rich Kulawiec <[email protected]> wrote: > > On Wed, Feb 03, 2016 at 10:52:43AM -0800, Brandon Long wrote: >> We rolled out a RFC 5321 compliant parser to smtp in Aug/Sept of last year, >> to much gnashing of teeth for a small set of users with some crappy >> software. We rolled it back for MSA (just silently replace with the >> auth-user), because apparently virtually all embedded devices (security >> cameras, mostly) send garbage at MAIL FROM. > > As you know, I'm not a big fan of Gmail, but I fully support your > rollout of this and encourage you to enforce it for MSA as well.
I’d love to see that, but it’s so, so hard. Apple can’t get this right, for example. Apparently, they can’t spell "undisclosed recipients:;" when sending email to groups. They’ve always insisted on saying something like this: "undisclosed recipients:<>;", which isn’t valid. I filed a bug on this for the original beta of OSX, back in 2000, when they had a nice feature that you could send an email to a group in your address book, and the To: header would use the group name. But, it didn’t work because they couldn’t get the syntax right. They tried various ways of spelling ":;", but never got it right. In the end, they decided that if you left "When sending to a group, show all member addresses" unchecked, you wouldn’t see the addresses, but the recipients would. So don’t do that. Check the box, so you can see when you’re breaking your local data protection legislation! On the positive side, they do usually now produce syntactically correct "To:" headers. -- Ian Eiloart Postmaster, University of Sussex +44 (0) 1273 87-3148 _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
