You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Emails on the nixos.org domain are mostly mailing lists. However, we occasionally enable people to send emails from nixos.org addresses.
That isn't possible with the current mail-test.nixos.org infrastructure.
@Mic92 tells me that we don't have to figure this out before launching the new mailserver, because currently the only use case for sending emails is elections@, which isn't needed right now (the SC election recently finished).
We don't want to store incoming emails, or serve them over IMAP/pop3. Instead, we should just forward emails.
This means we don't need dovecot. It's a little tricky to get rid of it, though:
With this change, mailing lists can now have associated login
accounts, which allow folks to send emails via SMTP from a `@nixos.org`
email address.
This completes NixOS#510
I opted to keep dovecot around. We're not using it for IMAP, just for
`SASL` authentication. It would have requires some (brittle) overriding of
settings from `nixos-mailserver` to get rid of dovecot. If we really
want to get rid of dovecot someday, I believe we should try to add an
option upstream in `simple-nixos-mailserver`.
Relates to #485.
Emails on the
nixos.org
domain are mostly mailing lists. However, we occasionally enable people to send emails from nixos.org addresses.elections@
, which isn't needed right now (the SC election recently finished).smtpd_sasl_path
. This is documented by postfix here: https://www.postfix.org/SASL_README.html#server_cyrusvirtual_alias_maps
file. We may want to encrypt these, so it may make sense to re-use the infrastructure in https://github.com/NixOS/infra/blob/master/non-critical-infra/modules/mailserver/mailing-lists.nix to do this.virtual_transport
setting (see nixos-mailserver setting and the postfix docs). I'm not sure what exactly we'd set it to.mailbox_transport
setting, but I'm not sure it's relevant here.The text was updated successfully, but these errors were encountered: