3 ms·
The last time a company screwed with e-mail at scale was Earthlink. Remember for a couple of years, every time you'd send a message to someone at Earthlink, yo
by reaperducer 8y ago
The last time a company screwed with e-mail at scale was Earthlink.
Remember for a couple of years, every time you'd send a message to someone at Earthlink, you'd get an automated rely demanding that you verify yourself before the message would go through?
Now I can't remember the last time I saw an @earthlink.* e-mail address.
Google has apparently learned from that and put the "error" in the 550 messages, where they can't be seen by the end user, and lead to non-helpful resolutions for sysadmins.
The result is that the blame for missing messages goes to the sender, not to the recipient's email service.
If Gmail at least notified the sender that there was a problem, then a pattern of responsibility could be established. But this is just another dark pattern.
- AJ007 8y agoIf enough expected messages don’t show up, users are going to start thinking gmail is broken. The problem for Google is that they are not the only trusted brand consumers interact with. I’ve seen a lot of stuff start ending up in spam that shouldn’t be there. If enough password resets, customer service responses, and order confirmations aren’t delivered, it looks like Google has a problem. If it doesn’t even make it to the spam box it makes Google look really bad. Google has definitely been changing things, everyone presumes it’s some rogue ML system. My company had solid Gmail delivery for almost 10 years, and at a fairly large volume. Now we can’t get it delivered any more. Very close to showing users a message not to use Gmail.
- luckylion 8y ago> If enough expected messages don’t show up, users are going to start thinking gmail is broken. I doubt that. They will rather consider that the people (or their IT) that send them emails made a mistake. It's Google after all.
- bluGill 8y agoIf several different IT departments all start sending that message though, people start to think maybe google has lost it...
- reaperducer 8y agoIf several different IT departments all start sending that message though, people start to think maybe google has lost it... Many IT departments still build their networks tailored to Windows machines, to the exclusion of others. Inertia is hard to overcome.
- feanaro 8y ago> The problem for Google is that they are not the only trusted brand consumers interact with. The solution to this is to start tarnishing this trust by word of mouth when talking to non-technical users. I take every opportunity to put Google in a bad light until they change their behaviour.
- deleted 8y ago[deleted]
- jvagner 8y agounrelated: i was going through a pile of CDs in my archive this last week, and i noticed an earthlink email address on one of my indie electronic CDs, and i still lament that i can't identify some of my old CDs because there's no discernible artist/album names on the CDs themselves, and neither I.. nor anyone I know locally.. own a CD drive.
- wahern 8y agoHere's the problem with inline filtering of SMTP transactions. 1) The RFCs mandate a server to accept multiple recipients--100 minimum per RFC 5321 (inherited from RFC 2821 and RFC 821). 2) A server can only accept or reject a message for all recipients. Theoretically a global rule shared across all recipients could be implemented in a way that rejects at the transaction level. But because you also have to implementing lazy, per-user filtering (or more importantly, per-user whitelisting), in practice the architectural and engineering focus is on filtering after accepting the message and closing the transaction. Without the ability to provide immediate and accurate failure responses upstream, filtering issues are left to metastasize and fester. (Because of spamming and spoofing mitigations bounces are next to worthless in terms of proper integration into the end-to-end software stack.) One of two things needs to happen with SMTP. 1) RFCs drop the requirement for multiple recipients per transaction. 2) An extension mechanism is added that permits per-recipient transaction responses. I think the only practical option is #1. Both cases require some amount of infrastructure patching, but for #1 it's extremely minimal and in most cases none at all. #2 is infeasible, at least without #1 preceding it (i.e. once you can no longer rely on batch sending as part of the basic SMTP command set, you'll have to support the extension.) Once that's accomplished vendors who don't implement inline filtering can be rightly criticized and shamed. As inline rejections become more prevalent, mail being effectively black-holed will become a thing of the past and we'll finally begin to see proper back-pressure (literal and figurative) return to the e-mail network. There'll be more pressure on large vendors like GMail to improve their systems and policies once the fog of complexity and plausible deniability lifts.