57
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Aug 2023
57 points (98.3% liked)
Fediverse
28550 readers
376 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
Yes, but that block is normally in a form of being marked as spam. This is different. Mail gets dropped without ever reaching the recipient's mailbox.
As an aside, I have been running my own mailserver for years and it's been working fine since the beginning. Getting marked as spam here and there, but for the most part - fine. I'll shift the mail setup at some point to have proper dkim support, but for now all I can say is - avoid gmail.
old man shouting at clouds
I understand how spam was a problem and why, at a glance, it seemed like a great idea to simply block any email that does not come from a previously known/trusted IP. However, in my opinion, all this has achieved are two things:Interesting. I don't really want to get into troubleshooting, but general curiosity has me wondering a few things since my server gets delivered to Gmail but only marked as spam for a new domain for the first couple weeks.
Is there a hard spf fail? Is your IP or domain on any blacklists? Is it a digital ocean or similar vps provider using their IP pool? Do you get any bounce back from Gmail with a reason or is it silently dropping?
Yes, it's digitalocean and yes, I get a bounced message telling me to use an email provider. I have some plans that involve a wider setup than just my lemmy instance, hence the delay in implementation.