DKIM, DMARC, SPF, rDNS/PTR, EHLO… all correct and verified in the email “original source,” BY GOOGLE. Still goes to SPAM folder because **** you, apparently. I hate Google.
I stopped thinking of any email as “private” regardless of where it’s hosted, when I realized that everyone I email uses Gmail anyways; so all my emails end up going to Google anyways.
It made me an email nihilist
I hate it. it was supposed to be open standard
Microsoft Exchange and the web-based Outlook probably still has a plurality of email volume, because of their dominance in enterprise. Even on the web based consumer space, Apple and Yahoo still have significant market share.
I work for state government and even we have trouble with email reputation issues from the big orgs. It’s a pain for everyone.
This is done on purpose, to make people to switch to their e-mail or use them for hosting.
Google did the same thing with XMPP (they were welcomed when they joined, then they made it so XMPP users couldn’t message GTalk/Hangouts users, but the other way worked), they tried similar thing with Usenet, but they never get dominance there so they let their services to be major source of spam on Usenet until they were blocked, ultimately removing Usenet indexing from Google).
I would really encourage to contact our local reps (both federal as well as state) and encourage them to introduce legislation that would punish this practice.
If you want you can PM me your dkim and dmarc and SPF policy. Or just send me your url and I’ll look it up. I used to fix these for a living. It’s likely an issue with your SPF not being properly annotated.
That’s cool of you to offer that to them.
Do you have any go to guides or even an overview of how you generally diagnose email problems would be awesome!
Just reading the bounce backs and spam errors when sending to Gmail and other providers.
Me and a couple other people have ran into on the internet have thought that we need to invent “email 2”, a clean slate implementation of email that serves it’s asynchronous long form and attachment friendly function while leaving behind Decades of Cruft . We can make it into an encrypted by default and have conveniences that we never had before. It might even be an actual useful thing instead of just being the thing you sign up for accounts with to get to 2fa codes and spam from websites you buy stuff from
Love this idea!
I feel like Arcane/Delta Chat is a step toward this. It somehow uses an email protocol and it works just like Signal or any other message app! I dunno how the heck it works but it’s super cool.
That’s something I want too: An open standard my friends and family can be on, where “the market” isn’t.
Edit: I see, it seems the issue in the main thread is:
- Gmail blocks custom servers as spam 99% of the time.
- 99% of normieverse uses Gmail. :(
But getting people on other email providers to talk to each other… shouldn’t be an issue then?
“normieverse” hit me like a brick
LOL I honestly can’t tell if that’s good or bad, in this context. XD
Frankly, I’m rather shocked it hasn’t happened by now.
We’ve tried to bandaid over it with various weird things, but fundamentally SMTP is just weird.
I could easily imagine a domain having some SRV record to advertise “hey, I support NeoSMTP”, and peers switching to that instead, possibly pinning on successful NeoSMTP negotiation.
Get rid of a lot of the relaying which has not been useful in modern times and only a liability, and perhaps offer an https option to be less likely to be blocked (a TXT record to indicate url, and a node could declare their NeoSMTP entry point as https://mail.server/NeoSMTP/ or whatever works for them).
Oh, there have been plenty. The issue though is the classic “make a better standard, and now you have N+1 standards”.
Everything is wrong with SMTP. It’s still in use because it’s supported everywhere. Anything that wants to replace it either needs to entirely replace it in one fell swoop, or it needs to be backwards compatible.The result is that occasionally a new thing comes up, a handful of people try it but there isn’t critical mass to make other features really useful so it fades.
It’s fine if Legacy email Remains the thing that could spend whereas email 2 can be used for actual correspondence between people
You’ll have to walk me through what you mean by that. I’m not sure how what I’m hearing you say would improve anything.
Hence my references to DNS records in addition to MX to determine if an endpoint is SMTP only or better. For compatible interop.
But that’s the thing: now you haven’t made an email replacement, you’ve made email more complicated.
If you’re backwards compatible you need a very compelling feature to get people to switch, and using the feature is limited until people switch.
That’s how we added spf, dkim, dmarc and starttls.
The biggest difficulty is managing the layers of compatibility.
Jmap is also an emerging standard. https://jmap.io/
Looks like replacing IMAP rather than SMTP, which is significantly less thorny.
I have this problem for a while as well. Similar to you all mechanisms are implemented multiple sites say the configuration is correct, even headers in Gmail say DKIM and SPF passed. E-mail arrives everywhere except for gmail.
Thanks for posting, at least I know I’m not the only one.
*fuck
Google Groups allows spammers to subscribe you to their groups in a workspace account, but doesn’t allow you to unsubscribe since you’re not part of that workspace account… Worse - all autoresponders for the spam will also be forwarded to all members of said group.
Since I do not participate in Google Groups, the nuclear option is to file all mails from Google Groups as spam with a Sieve script.
Note the
requirepart may be too large as may sieve script also contains more rules than this one.require ["body", "date", "editheader", "envelope", "fileinto", "imap4flags", "mailbox", "regex", "reject", "variables"]; if anyof( header :contains "List-Subscribe" "groups.google.com", header :matches "X-Google-Group-Id" "*" ) { if header :matches "Subject" "*" { set "subject" "${1}"; } else { set "subject" ""; } deleteheader "Subject"; addheader :last "Subject" "[Google-Groups-Spam] ${subject}"; fileinto "Junk"; }autoresponders for the spam will also be forwarded to all members of said group.
This sounds like a pretty effective way to get yourself unsubscribed from groups you don’t want to be in.
They will be drowned in hundreds of „Thanks for your email, but we don’t do support via mail. Please open a ticket at $URL“ and „Thanks for your mail, we will get back to you shortly. Your ticket ID is #123456“. Also everything you add as an auto response will be distributed to all other victims in that group, so I chose to not be a dick.
@laurenceOfSuburbia
This ain’t anything new. They have been doing this for decades and will still do it forever. Just move on with it, since it like trying to figure out something which has no meaning at all.
Just know for sure that every company has systems designed by some developer based on a whimsical mindset of someone at the very top. So, I can care less for these stupid companies and their useless management.It’s basically the same thing Google did with XMPP.
i never had problems with Google, but Outlook always blocks my emails, just because it’s not a standard .com .net etc domain…
I put dog shit in my ass and Google knew five minutes before it happened, filmed it, and sold it back to me as a custom highlight of my home alone shenanigans. I find this a bit egregious, personally.
Self hosting an email server to send mails that don’t get flagged as spam is a nightmare, I’d rather not attempt doing it again. My Lemmy instance is using SMTP2Go and the free tier is more than enough for my current sending capacity needs
They claim its for spam prevention which is why most ISPs actually also block outgoing SMTP port 25.
The dumb thing is, all it really does is push spammers onto using botted/stolen accounts which work way more effectively, and everyone else is forced to set up their email with Google or Microsoft.
If your domain isn’t big enough to be recognized, all that SPF and DMARC won’t mean crap to them.
They claim its for spam prevention which is why most ISPs actually also block outgoing SMTP port 25.
European ISPs block egress port 25, not American ones, generally. Not sure about the rest of the world.
In Europe, one refuge is to send using the GSM networks, which tend not to block egress 25 for some reason.
not American ones, generally.
Well then screw you AT&T lmao
AT&T is the worst of the worst. And I boycott them for countless reasons like snooping on their own customers voluntarily without a warrant. It’s really a hard-right corp. In any case, never tried them so I didn’t know they blocked egress 25.
One trick that works if truth-in-advertising laws are in force: ask the sales people before subscribing if the block port 25. They always say “no, we block nothing” (in my experience). So you subscribe and sign the contract. Then when you see they actually block 25, you have a false advertising situation and also a contract violation (if either verbal contracts are enforcable or if you can get it in writing that nothing is blocked). So you complain. In my experience, they give a gratis upgrade to an enterprise level of service that generally has a static IP and no blocks – for the price of the residential plan you signed up for.
Running your own email server is also a good way to get a ton of headaches from your isp
Wrong. If you aren’t up to the task of hosting email that’s fine but discouraging others from trying is the opposite direction we should be going.
Ngl, I can’t blame most for flocking to Gmail. It’s a lot more of a pain in the rear to self-host something like that, and it’s just plain convenient.
It’s the same reason a lot of the people leaving Gmail go to essentially the Privacy Google (Proton) as the replacement.
Probably bad place to ask but.
Self hosting email is complicated only for sending mails or for receiving mail it’s also hard?
Depending on what you want to do you might not need to actually send any mail.
Also, the anti-spam rules do also apply if you are answering a mail, I suppose it does as a response envelopement doesn’t have any evidence that it’s an actual response. But I have no experience self hosting email.
@daniskarma @laurenceOfSuburbia yeah the complication is not technical so much as bureaucratic. Email itself is simple, but then you have to jump through hoops of tuning various other technical settings for Big Email to allow you in
I think it’s usually to do with sending, so if you’re only interested in receiving I think you’ll be fine (unless your server uptime’s really bad or something)
Self hosting receiving mail is honestly, pretty straightforward, all things considered. Setup your MX record to point at a server you control, configure software to save messages however you want. Perhaps the most complicated step is wiring up certbot or similar software to get your SSL certificate for your mailserver. A Debian Linux system,
apt-get install postfix; apt-get install dovecotwill get you nearly 90% of the way there.Depending on your preference. there are docker containers that can do 100% of the process too, with all sorts of nice bells and whistles. If you don’t care about sending email, you can skip DKIM/SPF/DMARC. (though, if you are never sending from your domain, check here: https://www.cloudflare.com/learning/dns/dns-records/protect-domains-without-email/ – there are some entries you can add to DNS to make sure everyone else knows)








