It is absolutely not. Even if you are not considering the whole spam thing.
Sending an email with the multitude of clients, MIME which is very complex in itself, network issues, message queuing, retries, unsubscription, bounces, providers feedback loops, rate limiting and what not is very hard.
If you add the whole spam folder + blacklists situation into consideration, sending emails becomes a more than painful thing you don't want to deal with.
I can send a message to my address in 2020 using a 2003 Fedora Core 1 box without a domain using only what's part of the POSIX standard, and I'll receive it just fine.
I just did a few days ago, actually. It even got past my provider's spam filter.
I could probably have done it using earlier software than 2003-era mail/mailx, but that was the quickest way I could find to send an attachment given the software on hand.
However, I, as a receiver of email, get thousands of spam messages a day. So, I use services that block them before they even reach my view, or get sent directly to the spam folder.
If you want to send me an email, that's solved. If you want to send it to ten thousand people on your mailing list, and not have it end up in the spam folder, you may have more work.
For stranger to stranger communication, both business and non-business set up a web form. With a challenge if needed.
For friend to friend communication, use email, friends' address in on a white list.
For business to consumer communication, white list is again used.
For spammer to anyone communication, including business lists that refuse to take you off, not on white list so doesn't get in. Bounce response with reason "non on white list"
It's a cultural change though: an email address won't get through unless you are unblocked, but technically easy.
An email comes in from a sender address which isn't on the whitelist, but is (in fact) a friend. What's the handling?
An email comes in from a sender address which isn't on the whitelist, but is not (in fact) a friend. What's the handling?
Do I never hear from the first friend? Or do I get bombarded with "hey, read this email and see if the sender is a friend" a bunch of times?
Joe manages his whitelist through his mail provider's web UI. Many providers already use the address book as a whitelist; the only difference is they default to filtration instead of assuming spam.
Joe's friend's mail gets routed to the spam box. Joe's friend gets a bounce notification that says "To be added to Joe's whitelist, click here (and optionally solve a captcha/enter Joe's dog's name/submit a blood sample/deposit $0.25 worth of bitcoin into Joe's wallet)." Joe's friend clicks here, and Joe's mail provider adds Joe's friend to the whitelist and promotes the email to the inbox.
Joe's spammer gets the same message and disregards it. Their email stays in spam forever.
Joe's spam box gets bombarded with "hey, read this email and see if the sender is a friend" a bunch of times. He can trawl through them for actual friends if he wishes.
There was a big fit thrown on this website a year or two ago when one transactional mail provider (MailChimp?) said they were banning crypto companies with ICOs from their service. They literally put "ICOs are not welcome" in their Terms of Service. Why? Because first off, ICOs are scams. And that means they buy email lists, and then spam the shit out of people with "buy into our ICO!" emails, which get immediately shitcanned into the spam folder by 99.99% of users -- they're no different than Nigerian Princes, as far as most people care. That behavior tanks the reputation of the sender, and you cannot reason with The Algorithm once it "recognizes" you as spam. That kind of problem is not a minor inconvenience to companies like Mailgun, it's an existential threat.
Pity we'll have to move off them. It was good while it lasted.
You might miss something valuable. Perhaps from a long-lost relative. Or a prospective client or employer.
And once you're actually looking through the spam folder, what good is it really?
tl;dr: Abuse ruins it for everyone.
I work on the filtering side of the world so I see a lot of the challenges that even purportedly good actors face. Each provider does better or worse at controlling abuse. These things all have a cost:
* IPs -- You need to send from a variety of IPs. They have warmup time before they can be safely used. One bad guy can burn that IP and everyone who shares. Most ESPs aren't going to have dedicated IPs for each (or those are for high tiers).
* Dmarc/dkim/spf -- Passing validation can be hard since it requires your client to work with you.
* Abuse reports -- Likely huge volume
* Bounces -- They can count against the customer. How much is OK (e.g. AWS SES will cut you off if your bounce rate gets too high)?
* Throwaway account abuse -- Huge issue, this threshold is a simple hammer (so now bad guys need ~10x more throwaway accounts).
* Account takeover -- That good guy is now sending out crap. Now what?
* Post-abuse cleanup -- Good luck going around and working with major providers to get yourself unblocked. Its a huge time sink.
By using Mailgun, etc all of the above becomes their problem. On top of it they'll offer analytics, help crafting content that works in varying mail clients, etc.
A small business type sender doesn't need much of this (other than maybe the technical help). But at some point, the scales tip.
I'm curious, is that specific to IPv4 or you see the same phenomenon with IPv6 where providers allocate /64 or /48 to customers? Or there simply isn't enough sending volume from IPv6 at the moment to warrant specific filtering?
Blocking via IP on V6 is tricky since it’s not clear what a safe/useful block range would be.
Spamhaus has released a "blocking strategy" for IPv6 to exactly address this issue: https://www.spamhaus.org/news/article/668/spamhaus-releases-...
They specified that it wasn't even if you could ignore the spam issue. I said that it was if you ignored the spam issue. The first post in this thread was "We've made sending electronic mail way too complicated under the guise of fighting spam."
I'm aware that it won't get past every spam filter, but it gets past both Gmail's and my own provider (a smaller, non-American one), which is good enough for my own use. My claim was that sending electronic mail is a solved problem, because it is.
Communication is much more than just broadcasting, just as email is about more than sending emails.
Agreed. I mean, I can _probably_ remember enough to be able to send mail using just telnet without even needing to look anything up. (And that mail, without any mime parts or urls - it very very likely to not fall into any of the spam filtering on my inbound email accounts...)
Iain-2:~ iain$ nc -c gmail-smtp-in.l.google.com 25
220 mx.google.com ESMTP k5si5682618pls.209 - gsmtp
EHLO elided.org
250-mx.google.com at your service, [202.171.181.100]
250-SIZE 157286400
250-8BITMIME
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250 SMTPUTF8
MAIL FROM: <[email protected]>
250 2.1.0 OK k5si5682618pls.209 - gsmtp
RCPT TO: <[email protected]>
250 2.1.5 OK k5si5682618pls.209 - gsmtp
DATA
354 Go ahead k5si5682618pls.209 - gsmtp
Subject: Test
From: [email protected]
To: [email protected]
Date: Fri, 31 Jan 2020 13:07:00 +1100
Foo baz nah
.
250 2.0.0 OK 1580436443 k5si5682618pls.209 - gsmtp
QUIT
221 2.0.0 closing connection k5si5682618pls.209 - gsmtp
Iain-2:~ iain$(Not sure I care enough to try...)
Is this mail relay actually elided.org or is it impersonating elided.org?
There does not appear to be an SPF record for that domain so Gmail cannot determine if this is a fraudulent message, especially if the machine this request came from does not match the IP of the A record for that domain.
If your domain has SPF headers which don't permit mail from the (residential?) IP you're connecting from, that'll be a major factor as well.
I spammed with invite mails to users friends back in 2008 and mail started to end up in spam for a while, but after switching to double opt-in for all mail and making unsubscribing easily available it went back to good. Add some periodic list cleaning of long time inactive subscribers and it works perfectly!
It does get harder if you have to account for bad users, but if you're the only user then you can make sure everything is good.
So, is it hard? That depends entirely on how wanted or unwanted the sent mail is.
Sending an email _is_ trivial - you're right - but getting it delivered to the inbox, instead of the spam folder, is far from trivial. At scale, it is incredibly difficult. Even worse, spammers and fraudsters are utterly relentless. They hammer services like mine and Mailgun's constantly with fraud and phishing and porn and other garbage, inbound and outbound.
AFAIK, SPAM is a still a hard problem, and getting emails delivered isn't trivial.
"Under the guise of Spam" is a very reductionist viewpoint. It's like saying "Under the guise of the measles, we now have an oligopoly of pharmaceuticals." The latter might be true, but its important not to understate the threat of the former.
Answer: It's very difficult. Email is adversarial. Getting to the inbox is incredibly difficult to do _at scale_.
A public service where a lot will be spam and unsolicited emails? Must be hell to run.
I can't just block Amazon SES though, because there's also a ton of legit services that use them for mail transport. We've really helped spammers evade blocking and decrease their infrastructure costs, and because there's so much "normal" traffic on SES, spammers will blend right in. And as long as they pay for services rendered, Amazon couldn't be happier.
You don’t get a choice. That was made for you.
Asking someone's permissions first, tracking their desires and immediately updating your response is what they solve.
Seems trivial? Try doing it for (looks at note) 626 people.
It’s easy to make a proof of concept. Production grade is an entirely different story.
Remember to preserve conversations and forwarding. Make sure file attachments are handled and scanned for viruses. Make sure you watch out for recursive automatic forwarding. Make sure that any html is secure. And make sure it will scale well ... and I mean billions of emails a day well.
It's easy to send an email, but it's way harder to ensure that the emails you send are delivered properly.
All of them passed both SPF and DKIM.
How. Just how did these emails get spam filtered by Google? Everything about them screams that they're legit emails from ourselves to ourselves.
I was recently thinking about the email problem myself, and was reading about IP Warmups. Seems like every provider has different recommendations too. So sounds like not an exact science either. But maybe if it was an exact science it'd be hard to tell the good and bad guys apart. I guess one of the tricky problems with decentralized systems.
The best part about this particular item on the list of "things that have only gotten worse over time": they charge companies more to deliver what is essentially spam, and they conspired to make that spam show up in inboxes and "enhance" it with all sorts of tracking.