Created attachment 436918 [details] The output of "emerge --info" opensmtpd-5.9.2.201606071034_p1-r1 core dumps on my ~amd64 system: # systemctl -l status smtpd ● smtpd.service - OpenSMTPD Loaded: loaded (/usr/lib/systemd/system/smtpd.service; enabled; vendor preset: disabled) Active: failed (Result: core-dump) since Wed 2016-06-08 18:53:04 BRT; 1h 58min ago Process: 363 ExecStart=/usr/sbin/smtpd (code=exited, status=0/SUCCESS) Main PID: 377 (code=dumped, signal=SEGV) Jun 08 18:53:01 jrm.no-ip.org systemd[1]: Starting OpenSMTPD... Jun 08 18:53:02 jrm.no-ip.org systemd[1]: Started OpenSMTPD. Jun 08 18:53:04 jrm.no-ip.org systemd[1]: smtpd.service: Main process exited, code=dumped, status=11/SEGV Jun 08 18:53:04 jrm.no-ip.org systemd[1]: smtpd.service: Unit entered failed state. Jun 08 18:53:04 jrm.no-ip.org systemd[1]: smtpd.service: Failed with result 'core-dump'.
Explicitly running smptd I get the following output: # smtpd -vd debug: init ssl-tree debug: init ca-tree debug: init ssl-tree debug: using "fs" queue backend debug: using "ramqueue" scheduler backend debug: using "ram" stat backend info: OpenSMTPD 5.9.1p1 starting fatal: imsg_wait: Connection reset by peer
I can confirm. I have the same issue: smtpd -vd -f /etc/opensmtpd/smtpd.conf debug: init ssl-tree info: loading pki information for mail.totobet.com debug: init ca-tree debug: init ssl-tree info: loading pki keys for mail.totobet.com debug: using "fs" queue backend debug: using "ramqueue" scheduler backend debug: using "ram" stat backend info: OpenSMTPD 5.9.1p1 starting fatal: imsg_wait: Connection reset by peer dmesg: [Sat Jun 18 22:24:32 2016] smtpd[19158]: segfault at 0 ip 0000000e6b77bafb sp 000003e69892ede0 error 4 in smtpd[e6b73a000+78000]
Is this fixed with the most recent snapshot?
(In reply to Jason A. Donenfeld from comment #3) > Is this fixed with the most recent snapshot? Yes, it works with opensmtpd-5.9.2.201607021504_p1-r1.
Is this bug still relevant given that 5.x is not even in ::gentoo any more?
