From: "Clément Lassieur" <clement@lassieur.org>
To: Adam Zimmerman <adam@digitalpirate.ca>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] opensmtpd: Fix crash during authentication
Date: Tue, 12 Jun 2018 10:54:42 +0200 [thread overview]
Message-ID: <8736xs8jvx.fsf@lassieur.org> (raw)
In-Reply-To: <be135a88-319c-74f1-f0d9-2fb3d30ef262@digitalpirate.ca>
Hi Adam,
Adam Zimmerman <adam@digitalpirate.ca> writes:
> Hi all,
>
> I'm running a mail server that I recently migrated to GuixSD, and I
> found this issue when trying to get opensmtpd set up.
>
> When using authentication from a table, opensmtpd would crash whenever I
> tried to authenticate. I found this patch which fixes the issue. It's
> already been merged into the opensmtpd master branch[1], and will be
> fixed in the next release which apparently will be around
> October/November this year.
>
> [1] https://github.com/OpenSMTPD/OpenSMTPD/pull/835
>
> I also noticed another issue which I'm not 100% sure how to solve
> properly. When rebooting the server, opensmtpd fails to start. I think
> the reason is that the shepherd service only has '(loopback) listed in
> its requirements, and I think it might be trying to start the server
> before the network comes up. When I ssh into the server and start it
> manually, it works fine.
>
> My first thought was to change the requirements to '(networking), but
> could that cause issues for people who only use opensmtpd as a local
> delivery server?
I run OpenSMTPD 6.0.3p1 on GuixSD, I use authentication from a table,
and none of the issues you described happened to me.
Here is its configuration:
--8<---------------cut here---------------start------------->8---
pki mail.lassieur.org certificate "/etc/smtpd/certs/fullchain.pem"
pki mail.lassieur.org key "/etc/smtpd/certs/privkey.pem"
table passwd file:/etc/mail/passwd
listen on 0.0.0.0 port 25 tls pki mail.lassieur.org
listen on 0.0.0.0 port 587 tls-require pki mail.lassieur.org auth <passwd>
limit mta for domain gmail.com inet4
accept from local for any relay
reject sender "@lassieur.org" for any
accept from any for any relay via smtp://mail2.lassieur.org
--8<---------------cut here---------------end--------------->8---
I don't understand why your setup would behave differently. Could you
share a bit more of your configuration?
Clément
next prev parent reply other threads:[~2018-06-12 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 22:15 [PATCH] opensmtpd: Fix crash during authentication Adam Zimmerman
2018-06-07 2:17 ` Tobias Geerinckx-Rice
2018-06-12 8:54 ` Clément Lassieur [this message]
2018-06-12 17:13 ` Adam Zimmerman
2018-06-12 17:22 ` Clément Lassieur
2018-06-12 17:46 ` Clément Lassieur
2018-06-12 18:59 ` Adam Zimmerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736xs8jvx.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=adam@digitalpirate.ca \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).