this post was submitted on 14 Apr 2024
32 points (92.1% liked)

Selfhosted

40198 readers
569 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
32
Recommendation for outgoing-only SMTP server (lemmy.world)
submitted 7 months ago by markstos@lemmy.world to c/selfhosted@lemmy.world
34 comments fedilink hide all child comments
 

I'm looking for a simple sendmail replacement to receive local mail, such as from cron and service failures and forward it to on to a real SMTP server.

I have used msmtpd successfully but thought I'd ask if folks have other solutions they like.

you are viewing a single comment's thread
view the rest of the comments
[–] markstos@lemmy.world 2 points 7 months ago (1 children)

The one problem with msmtp is that it doesn't rewrite headers, like "From: root / To: root". These are not required for SMTP, but they are required by some mail providers who will reject email that doesn't have an "@" sign in these headers. The author or msmtp has said he does not plan to add this feature.

I worked around the issue with my own sendmail wrapper that rewrites local addresses in From and To headers before passing the message to msmtp. Someone else posted such a script in this bug report:

https://github.com/marlam/msmtp/issues/98

[–] vegetaaaaaaa@lemmy.world 1 points 7 months ago* (last edited 7 months ago) (1 children)

You can definitely replace senders with correct mail addresses for relaying through SMTP servers that expect them (this is what I do):

# /etc/msmtprc
account default
...
host smtp.gmail.com
auto_from on
auth on
user myaddress
password hunter2

# Replace local recipients with addresses in the aliases file
aliases /etc/aliases

# /etc/aliases
mailer-daemon: postmaster
postmaster: root
nobody: root
hostmaster: root
usenet: root
news: root
webmaster: root
www: root
ftp: root
abuse: root
noc: root
security: root
root: default
www-data: root
default: myaddress@gmail.com

(the only thing I changed from the defaults in the aliases file is adding the last line)

This makes it so all/most system accounts susceptible to send mail are aliased to root, and root in turn is aliased to my email address (which is the one configured in host/user/password in msmtprc)

Edit: I think it's actually the auto_from option which interests you. Check the msmtp manpage

[–] markstos@lemmy.world 2 points 7 months ago (1 children)

In the issue I linked, the msmtp author makes a distinction with changing the envelope recipient, which msmtp can do, with rewriting the email headers like “To”, which msmtp does not do.

[–] vegetaaaaaaa@lemmy.world 2 points 7 months ago

https://github.com/chriswayg/ansible-msmtp-mailer/issues/14 While msmtp has features to alter the envelope sender and recipient, it doesn't alter the "To:" or "From:" message itself. When the Envelope doesn't match these details, it can be considered spam

Oh I didn't know that, good to know!

The proposed one-line wrapper looks like a nice solution