[jrabone]

I run a mail server for my own company and my immediate friends and family.

I hope you aren't planning on using one of the many ESPs to do your actual delivery; increasingly I am blacklisting them (and by ASN) since despite any claims to the contrary they don't give two shits about spam or UCE. There may or may not be collateral damage but I really don't care anymore; I have a home-grown analysis script that runs daily over my logs and generates pretty HTML summary reports of who got blocked and why, and 6 months in it's looking pretty good.

One size fits no-one for email (which is why Spamassassin always fails me sooner or later). There are entire ASNs that have no business talking to me and get the firewall. There are entire countries that (on the basis of GeoIP lookup) get aggressively greylisted. Nobody has ever sent any of my users a legitimate email with a utf8-encoded subject. The list of rules just keeps growing.

And finally, if anyone reading this has anything to do with

bestpure.co.uk besttip.co.uk bighut.co.uk exclusivetips.co.uk liteme.co.uk officialnow.co.uk opost.co.uk piple.co.uk savertips.co.uk retailrat.co.uk tipmail.co.uk websaveguide.co.uk wepost.co.uk

please go and get an proper job. Or die. I don't mind which.

[mey]

And this is why I stopped running my own email and use gmail. This entirely alone.

[jrabone]

But you're missing out on the all the fun of managing your own DKIM & ADSP DNS records! And debugging mobile device SSL issues. And Courier-IMAP IDLE support for various broken IMAP clients. Not to mention Outlook's amusing approach to TLS. What do you DO all day?

Also, does Gmail do S/MIME? I see a Firefox plugin, and Penango which appears to be Firefox/IE. What about Chrome / Android?

[kijin]

> Nobody has ever sent any of my users a legitimate email with a utf8-encoded subject.

I suppose you and your users only ever communicate with Westerners. Or are all of your Japanese correspondents (for example) kind enough to encode their subjects in EUC-JP instead of UTF-8?

[jrabone]

You suppose correct; obviously that might change, but for now it's the case that in 20 years of email not one single legitimate message has had a non-7 bit ASCII subject line, whereas there's always plenty of ⋎Іǎḡɾǎ, ѵἲàɠṝà and ѷἰẫǧʀẫ to go around (in the form =?utf-8?Q?=E2=8B=8E=D0=86=C7=8E=E1=B8=A1=C9=BE=C7=8E?= of course)

Pro tip: if anyone is trying to block this shit without blocking legitimate Unicode, you'll be wanting Unicode::Normalize and something like

    utf8::decode($rawSubject);
    my $normalised = NFKD($rawSubject);
    $normalised =~ s/\p{NonspacingMark}//g;

to strip the composing diacritics before you reach for the regexes. Good luck.