3 ms·
Anyone sending text/x-amp-html should still be including a text/html part, which won’t have JavaScript et al. Unless just about everyone starts supporting AMPHT
by chrismorgan 9y ago
Anyone sending text/x-amp-html should still be including a text/html part, which won’t have JavaScript et al. Unless just about everyone starts supporting AMPHTML Email, the text/html parts will still be necessary.
- JoshMnem 9y agoThere are many companies that try to force you to load external resources in an HTML version by putting the content in images. The same thing could happen with AMP, where only an AMP version contains the actual content.
- adrianN 9y agoThere is always the "mark as spam" button.
- chrismorgan 9y agoBe careful with that spam button: it probably won’t do what you want, but will instead make your spam filter worse. Eventually a sufficiently capable filter will be likely to figure out that the thing these emails have in common is a poor text/plain part and adjust its weighting appropriately, but I’d expect it to take somewhere between “quite some time” and “a long time” to figure that out; in the mean time, it’ll mostly just serve to confuse the poor filter. (How customised spam filters work, in a nutshell: take your various signals—e.g. has HTML, has remote images, has no text, is sent from a known-spammy IP address, mentions large sums of money—and figure out which factors occur more often in spam than ham, and increase the importance assigned to them; if the email reaches a chosen threshold, it’s showing sufficient characteristics of a spam message to be considered probably spam.) SpamAssassin is probably the most widely-used spam filtering platform; I’m not certain that its standard rules are capable of deciding to filter on this sort of thing directly. I believe it has something around detecting overly short or non-representative text/plain parts, which is probably the primary signal this would coalesce around.
- simias 9y agoLike most emails send nowadays use HTML but still include a text/plain part. Here's a live example from my INBOX: https://svkt.org/~simias/mail-hp.png https://svkt.org/~simias/mail-hp.png Notice that this is from HP, not some small shop. Nowadays people expect you to be able to parse HTML emails and don't bother to have it work in plain text (I'd actually prefer if they got rid of the text/plain in this situation, this way mutt would know to display the HTML instead). If AMP becomes popular enough and gets integrated by the big players I have no doubt that we'll see the same thing. Then it means you won't be able to process email in any significant way without a full blown Web engine (probably including JS). First they ported everything to the web, now they're porting the web to everything else. I don't want the web. The web is bloated crap. Stop it. Please. Stop it.
- JoshMnem 9y agoEmbrace, Extend, Extinguish, then walled garden and/or broken things. Emails should not include any JavaScript. It would give anyone a way to send immediately executing code into your inbox. CSS animation in email is already bad enough. Maybe an AMP filter could check the plain text content against AMP and HTML content and bounce the email with a custom message if there is no plain text or standard-HTML way to read the content.