this post was submitted on 13 Nov 2026
359 points (99.4% liked)
Programmer Humor
34091 readers
996 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The problem with SMTP is that it is too simple. There is a complete lack of security, so different implementations have had layers added on top to harden them, which adds to the complexity. Not all layers are standardised or compatible, which means that what should be relatively simple becomes an untenable mess.
It isn’t something that can be proprietarised easily so companies need to also add their own proprietary layers in order to monetise their product, which adds more untenable.
If your “senior network engineer” is more concerned about your SMTP server becoming a SPAM relay than your product being usable for its intended purpose, which is why it is still down.
A spam relay quickly becomes unusable.
The app server isn't running the SMTP server, it can't connect to one. We would also be happy for them to run their own SMTP server and point it at that instead if they wish.