#nullmailer — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #nullmailer, aggregated by home.social.
-
"Nullmailer", "Return-Path" y GMail
-
"Nullmailer", "Return-Path" y GMail
-
"Nullmailer", "Return-Path" y GMail
-
"Nullmailer", "Return-Path" y GMail
-
"Nullmailer", "Return-Path" y GMail
-
nullmailer 接 Amazon SES
如同前面「把 wiki 搬回到家裡的機器上」提到的，家裡多了台機器，之前寄信的部分都是走 Postfix，但這台只會寄出去，改用 Amazon SES 這種服務會比較簡單一點... Amazon SES 端的教學這邊就跳過了，重點是要把 domain 認證通過，另外要開票申請離開 sandbox 環境，我是很久前都做完了。 然後是設定 SPF 與 DKIM 的部分，這些也是之前就設定好了，不過剛剛順便巡了一圈發現有些 domain 還是 1024-bit RSA，點幾下就可以換到 2048-bit RSA 了，就順手換過去。(附帶一提，是在 2021 年支援的：「Amazon SES 總算支援 2048 bits RSA key 了」) 安裝完 nullmailer 後就直接到 /etc/nullmailer 下設定就可以了，這邊是用 us-e…
https://blog.gslin.org/archives/2025/03/24/12316/nullmailer-%e6%8e%a5-amazon-ses/
-
nullmailer 接 Amazon SES
如同前面「把 wiki 搬回到家裡的機器上」提到的，家裡多了台機器，之前寄信的部分都是走 Postfix，但這台只會寄出去，改用 Amazon SES 這種服務會比較簡單一點... Amazon SES 端的教學這邊就跳過了，重點是要把 domain 認證通過，另外要開票申請離開 sandbox 環境，我是很久前都做完了。 然後是設定 SPF 與 DKIM 的部分，這些也是之前就設定好了，不過剛剛順便巡了一圈發現有些 domain 還是 1024-bit RSA，點幾下就可以換到 2048-bit RSA 了，就順手換過去。(附帶一提，是在 2021 年支援的：「Amazon SES 總算支援 2048 bits RSA key 了」) 安裝完 nullmailer 後就直接到 /etc/nullmailer 下設定就可以了，這邊是用 us-e…
https://blog.gslin.org/archives/2025/03/24/12316/nullmailer-%e6%8e%a5-amazon-ses/
-
nullmailer 接 Amazon SES
如同前面「把 wiki 搬回到家裡的機器上」提到的，家裡多了台機器，之前寄信的部分都是走 Postfix，但這台只會寄出去，改用 Amazon SES 這種服務會比較簡單一點... Amazon SES 端的教學這邊就跳過了，重點是要把 domain 認證通過，另外要開票申請離開 sandbox 環境，我是很久前都做完了。 然後是設定 SPF 與 DKIM 的部分，這些也是之前就設定好了，不過剛剛順便巡了一圈發現有些 domain 還是 1024-bit RSA，點幾下就可以換到 2048-bit RSA 了，就順手換過去。(附帶一提，是在 2021 年支援的：「Amazon SES 總算支援 2048 bits RSA key 了」) 安裝完 nullmailer 後就直接到 /etc/nullmailer 下設定就可以了，這邊是用 us-e…
https://blog.gslin.org/archives/2025/03/24/12316/nullmailer-%e6%8e%a5-amazon-ses/
-
nullmailer 接 Amazon SES
如同前面「把 wiki 搬回到家裡的機器上」提到的，家裡多了台機器，之前寄信的部分都是走 Postfix，但這台只會寄出去，改用 Amazon SES 這種服務會比較簡單一點... Amazon SES 端的教學這邊就跳過了，重點是要把 domain 認證通過，另外要開票申請離開 sandbox 環境，我是很久前都做完了。 然後是設定 SPF 與 DKIM 的部分，這些也是之前就設定好了，不過剛剛順便巡了一圈發現有些 domain 還是 1024-bit RSA，點幾下就可以換到 2048-bit RSA 了，就順手換過去。(附帶一提，是在 2021 年支援的：「Amazon SES 總算支援 2048 bits RSA key 了」) 安裝完 nullmailer 後就直接到 /etc/nullmailer 下設定就可以了，這邊是用 us-e…
https://blog.gslin.org/archives/2025/03/24/12316/nullmailer-%e6%8e%a5-amazon-ses/
-
nullmailer 接 Amazon SES
如同前面「把 wiki 搬回到家裡的機器上」提到的，家裡多了台機器，之前寄信的部分都是走 Postfix，但這台只會寄出去，改用 Amazon SES 這種服務會比較簡單一點... Amazon SES 端的教學這邊就跳過了，重點是要把 domain 認證通過，另外要開票申請離開 sandbox 環境，我是很久前都做完了。 然後是設定 SPF 與 DKIM 的部分，這些也是之前就設定好了，不過剛剛順便巡了一圈發現有些 domain 還是 1024-bit RSA，點幾下就可以換到 2048-bit RSA 了，就順手換過去。(附帶一提，是在 2021 年支援的：「Amazon SES 總算支援 2048 bits RSA key 了」) 安裝完 nullmailer 後就直接到 /etc/nullmailer 下設定就可以了，這邊是用 us-e…
https://blog.gslin.org/archives/2025/03/24/12316/nullmailer-%e6%8e%a5-amazon-ses/
-
Oh my. Why haven't I learned about #nullmailer years ago? I always wondered why *all* the services happily send email, but obviously not everybody would run their own email server with all the whistles needed nowadays. Here we go.
-
Oh my. Why haven't I learned about #nullmailer years ago? I always wondered why *all* the services happily send email, but obviously not everybody would run their own email server with all the whistles needed nowadays. Here we go.
-
Oh my. Why haven't I learned about #nullmailer years ago? I always wondered why *all* the services happily send email, but obviously not everybody would run their own email server with all the whistles needed nowadays. Here we go.
-
@Anarcat: When I read https://packages.debian.org/sid/rsendmail I expected it to be a replacement for my local #MTA which instead does ssh into another box with a fullblown MTA and calls #sendmail there. But https://gitlab.com/anarcat/rsendmail/-/blob/main/README.md makes it sound much more complex and way less obvious.
Why do I need #rsendmail on the remote host? Why doesn't it conflict with my local MTA? What's the real benefit over `nullmailer`? You write "#nullmailer is almost what we need, but still talks #SMTP" — but what's bad about that?
-
@Anarcat: When I read https://packages.debian.org/sid/rsendmail I expected it to be a replacement for my local #MTA which instead does ssh into another box with a fullblown MTA and calls #sendmail there. But https://gitlab.com/anarcat/rsendmail/-/blob/main/README.md makes it sound much more complex and way less obvious.
Why do I need #rsendmail on the remote host? Why doesn't it conflict with my local MTA? What's the real benefit over `nullmailer`? You write "#nullmailer is almost what we need, but still talks #SMTP" — but what's bad about that?
-
@Anarcat: When I read https://packages.debian.org/sid/rsendmail I expected it to be a replacement for my local #MTA which instead does ssh into another box with a fullblown MTA and calls #sendmail there. But https://gitlab.com/anarcat/rsendmail/-/blob/main/README.md makes it sound much more complex and way less obvious.
Why do I need #rsendmail on the remote host? Why doesn't it conflict with my local MTA? What's the real benefit over `nullmailer`? You write "#nullmailer is almost what we need, but still talks #SMTP" — but what's bad about that?
-
@Anarcat: When I read https://packages.debian.org/sid/rsendmail I expected it to be a replacement for my local #MTA which instead does ssh into another box with a fullblown MTA and calls #sendmail there. But https://gitlab.com/anarcat/rsendmail/-/blob/main/README.md makes it sound much more complex and way less obvious.
Why do I need #rsendmail on the remote host? Why doesn't it conflict with my local MTA? What's the real benefit over `nullmailer`? You write "#nullmailer is almost what we need, but still talks #SMTP" — but what's bad about that?
-
@Anarcat: When I read https://packages.debian.org/sid/rsendmail I expected it to be a replacement for my local #MTA which instead does ssh into another box with a fullblown MTA and calls #sendmail there. But https://gitlab.com/anarcat/rsendmail/-/blob/main/README.md makes it sound much more complex and way less obvious.
Why do I need #rsendmail on the remote host? Why doesn't it conflict with my local MTA? What's the real benefit over `nullmailer`? You write "#nullmailer is almost what we need, but still talks #SMTP" — but what's bad about that?
-
One of my #GitLab instances was no longer able to send e-mails. (It tried to send almost empty e-mails, but its smarthost discarded those.)
It was the one that used #nullmailer as its #MTA. GitLab recommends either #Sendmail or #Postfix as an MTA. Switching to Postfix solved this issue for me.
Making sure that Postfix uses the #StartTLS capability of its smarthost took longer than expected.
It's also rather annoying that on Debian systems, postfix by default accepts connections from anywhere on the Internet even though I asked debconf to set up a “satellite system”.
When using Nullmailer, I just had to put the line “smtp.domain.tld smtp --port=25 --starttls” in /etc/nullmailer/remotes.
For Postfix, I need this:
inet_interfaces = loopback-only
smtp_tls_security_level = encryptYour mileage may vary.
-
One of my #GitLab instances was no longer able to send e-mails. (It tried to send almost empty e-mails, but its smarthost discarded those.)
It was the one that used #nullmailer as its #MTA. GitLab recommends either #Sendmail or #Postfix as an MTA. Switching to Postfix solved this issue for me.
Making sure that Postfix uses the #StartTLS capability of its smarthost took longer than expected.
It's also rather annoying that on Debian systems, postfix by default accepts connections from anywhere on the Internet even though I asked debconf to set up a “satellite system”.
When using Nullmailer, I just had to put the line “smtp.domain.tld smtp --port=25 --starttls” in /etc/nullmailer/remotes.
For Postfix, I need this:
inet_interfaces = loopback-only
smtp_tls_security_level = encryptYour mileage may vary.
-
One of my #GitLab instances was no longer able to send e-mails. (It tried to send almost empty e-mails, but its smarthost discarded those.)
It was the one that used #nullmailer as its #MTA. GitLab recommends either #Sendmail or #Postfix as an MTA. Switching to Postfix solved this issue for me.
Making sure that Postfix uses the #StartTLS capability of its smarthost took longer than expected.
It's also rather annoying that on Debian systems, postfix by default accepts connections from anywhere on the Internet even though I asked debconf to set up a “satellite system”.
When using Nullmailer, I just had to put the line “smtp.domain.tld smtp --port=25 --starttls” in /etc/nullmailer/remotes.
For Postfix, I need this:
inet_interfaces = loopback-only
smtp_tls_security_level = encryptYour mileage may vary.