Egregoros

@mia I needed this kick in the pants

@mia Yeah, in fact much less hard than dealing with connecting an email client to the Google/O365/… horrors.

@georgia lmk if you have any questions about it; i basically set it up from scratch so i’m familiar with how all the pieces fit together

@aetios the nice thing about email is that your stuff can go down for weeks and other servers will keep trying to deliver mail. you still receive stuff oncet it’s back up

@aetios @mia In fact email greylisting works via "huh, unknown server, tempfail it in case it's a basic spam script"

@lanodan @aetios yep. that btw is the main reason why email that should be instant sometimes takes 10-15 minutes to arrive in your inbox

@mia

IIRC it's not quite "weeks" (more like 2–6 days depending on sending-server configuration) but it's still nice to know that servers will retry. Also, annoyingly some mail-hosts (particularly the big-name ones) will re-send from a different IP address which makes gray-trapping more challenging ☹

(but yes, still totally worth running your own mail-server)

@aetios

@gumnos @lanodan @pitrh @mia @aetios modern greylisting/greytrapping essentially requires you track not based by IP address but an entire subnet (/24 or /64). it's a mess. It's been like this since idk... at least 2012 to my memory.

@feld

I really wish I could dig up the @pitrh where he goes into detail on the pain Outlook-dot-com and such cause by resending from different addresses, but my web-search-fu is failing me. 😑

@gumnos @pitrh I even had issues once at old ISP_JOB where Google would send to us on ipv6, get greylisted, and retry in the future with ipv4

@feld

🤦

@pitrh

@aetios @mia I also have a fallback server in another location that acts as a backup. When the main server is back, the backup sends everything it has received to it.

@mia ngl i wonder where the idea even came from, outside of getting your domain to not get filtered to spam which is just a matter of waiting a bit most of the time (in my limited exp at least)