3 ms·
This is really the only way to reject AMP4Email: Refuse to allow it, so that companies wanting to reach their customers can't implement it. However, it's unlike
by ocdtrekkie 9y ago
This is really the only way to reject AMP4Email: Refuse to allow it, so that companies wanting to reach their customers can't implement it. However, it's unlikely large mail providers would choose to do this, I can't imagine Microsoft or Yahoo taking such a stand.
My own provider FastMail, has said they of course, can't promise they won't support AMP4Email since compatibility is a major goal of theirs, and I can't fault them for that. (And I significantly appreciate the contribution their blog has made to the discussion on the topic.) I'd love if I had the option to opt into behavior like this though, at least on a personal level.
But if only a few percent of users (or more than likely, a fraction of a percent) are rejecting the mail, it won't dissuade anyone. Companies will pick up AMP4Email so they can push dynamic advertising directly in people's inboxes.
- tankenmate 9y agoIf you run Amavis you can add a MIME type to the $banned_filename_re in a conf file (on debian based derivatives you'll normally find that in /etc/amavis/conf.d/20-debian_defaults). qr'^application/amp+html$'i, is what I use. If you want to put it in a separate file (such as a local config file) then you can just push(@$banned_filename_re,qr'^application/amp+html$'i);
- rav 9y agoIsn't the plus sign a special character in Perl regexes? That is, wouldn't you need to use this instead: qr'^application/amp\+html$'i,
- tankenmate 9y agoYou're right, thanks! I still forget sometimes the differences between BRE, SRE, and ERE (mostly due to vim defaulting one thing and perl the other).