npub1tj54dz997wrdyqgf8sc36z3upy3ld0ujmwqyx42dtqxcwc7l68fqlx5ry2 (npub1tj5…5ry2) I currently have two mail servers:
1. The primary one is actually a ProtonMail bridge that is configured to manage most of my domains. Actually the ProtonMail bridge *is not* intended to be used on anything other than localhost, so I've modded it a bit by adding an SSH tunnel to its default port (1025) that listens only on my VPN interfaces. Since all of my services internally listen to those interfaces, emails are sent to the VPN address (e.g. 10.0.0.1:1025), so there's no need of NAT/exposing SMTP ports.
2. I also have another personal mail server on one of my Linode boxes. Installing Postfix/Dovecot etc. wasn't a bit deal, but configuring all the DNS records to make sure that your emails are accepted by the most picky servers out there (Google, Microsoft etc.) was a bit of a pain in the ass. Anyway, after a bit of back and forth with Spamhaus and friends to get it whitelisted it works fine and it can deliver emails to all the domains. But, knowing the folks at Spamhaus, I don't think they would have been so keen to whitelist it if instead of running on a Linode IP (which they already consider a kind of gray area) it was running on a residential IP (which they usually consider totally a *black* area).
Even if in theory I could put my mail servers to listen directly on my residential IP, I wouldn't do it because emails from servers running on residential IPs are likely to be dropped by 90% of the other servers out there.
Fabio Manganiello /
npub1v7…ukv0u
2023-08-03 00:21:51
in reply to nevent1q…7705
Author Public Key
npub1v78mmuz20p6qd6nve30axhqu74avwn4f6z4grhug7755rat7wh3syukv0uPublished at
2023-08-03 00:21:51Event JSON
{
"id": "92ace05f6a671938ab73416ba18816f8d328ed6dba73394774b9b4c14036d4ac",
"pubkey": "678fbdf04a787406ea6ccc5fd35c1cf57ac74ea9d0aa81df88f7a941f57e75e3",
"created_at": 1691014911,
"kind": 1,
"tags": [
[
"p",
"5ca95688a5f386d201093c311d0a3c0923f6bf92db8043554d580d8763dfd1d2",
"wss://relay.mostr.pub"
],
[
"p",
"6bcc5d6c6c03ca87494130e65fd4db3e4b0dcd53b331d6bbf9ab538458caff34",
"wss://relay.mostr.pub"
],
[
"e",
"d8bd80e8721851eb00b16eb49a9969a8f062978a392c3f4c527dea24015d2fdd",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://social.platypush.tech/users/blacklight/statuses/110822353241719791"
]
],
"content": "nostr:npub1tj54dz997wrdyqgf8sc36z3upy3ld0ujmwqyx42dtqxcwc7l68fqlx5ry2 I currently have two mail servers:\n\n1. The primary one is actually a ProtonMail bridge that is configured to manage most of my domains. Actually the ProtonMail bridge *is not* intended to be used on anything other than localhost, so I've modded it a bit by adding an SSH tunnel to its default port (1025) that listens only on my VPN interfaces. Since all of my services internally listen to those interfaces, emails are sent to the VPN address (e.g. 10.0.0.1:1025), so there's no need of NAT/exposing SMTP ports.\n\n2. I also have another personal mail server on one of my Linode boxes. Installing Postfix/Dovecot etc. wasn't a bit deal, but configuring all the DNS records to make sure that your emails are accepted by the most picky servers out there (Google, Microsoft etc.) was a bit of a pain in the ass. Anyway, after a bit of back and forth with Spamhaus and friends to get it whitelisted it works fine and it can deliver emails to all the domains. But, knowing the folks at Spamhaus, I don't think they would have been so keen to whitelist it if instead of running on a Linode IP (which they already consider a kind of gray area) it was running on a residential IP (which they usually consider totally a *black* area).\n\nEven if in theory I could put my mail servers to listen directly on my residential IP, I wouldn't do it because emails from servers running on residential IPs are likely to be dropped by 90% of the other servers out there.",
"sig": "93f429ca5da5679d63b8b2f2bc926bf1f9079338effa6d88ee0c818c3041860bfd68b30845701f38b04cebec1545acb2ea9cf4c2a7b96e134af61e20558b5b3b"
}