On 11/27/2013 12:12 PM, Gilles Chehade wrote: > Hi, > > The latest snapshots are what we're going to release in a few days. > > They are running on large production systems and they've undergone a bit > of stress testing since last week.
First of all many thanks for OpenSMTPD, converting from Postfix was quite easy :) > > We would appreciate if you could run this snapshot and let us know: I've been running 201311201704 on a OpenBSD 5.4 amd64 box and I've just upgraded to opensmtpd-201311281209. I've set /etc/malloc.conf to SRF, to help detect issues. > > - what features you are using and confirm that they work; I only have one user receiving mail, called edwin, everything else eventually aliases to it, sample entries from /etc/mail/aliases: # send all messages for root to a subfolder in my account # On Postfix I used just edwin+root, with OpenSMTPD I have to use the full email address root: [email protected] hostmaster: root # typos edvin: edwin I have tested that sending an e-mail to the alias properly delivers e-mail to the account. Sending mail from OpenSMTPD (locally or via submission port by a MUA) to Postfix on another box works, and receiving mail from Postfix also works. I have also subscribed the OpenSMTPD box to a few mailing lists, and seems to work mostly fine so far, see below for some errors though. Signing via the DKIMproxy also works. Here is my smtpd.conf: table aliases db:/etc/mail/aliases.db # Local mail listen on lo0 hostname "mx.etorok.net" # External mail # TLS certificates pki mx.etorok.net key "/etc/ssl/private/mx.etorok.net.key" pki mx.etorok.net certificate "/etc/ssl/mx.etorok.net.crt" # pki mx.etorok.net ca "/etc/ssl/mx.etorok.net.ca" #table domains { "etorok.net", "*.etorok.net" } table domains { "mx.etorok.net" } listen on egress secure pki mx.etorok.net accept from any for domain <domains> alias <aliases> deliver to maildir #accept from any for domain <domains> virtual { "edwin" => "edwin", "root" => "[email protected]", "@" => "[email protected]" } deliver to maildir # MUA submission, STARTTLS, and AUTH is mandatory # authenticated users will be considered local users listen on egress port submission pki mx.etorok.net tls-require auth mask-source # DKIM signing # Mail from authenticated users gets sent to dkimproxy on port 10027, # and received back on port 10028. listen on lo0 port 10028 tag DKIM mask-source # We relay only DKIM signed email accept tagged DKIM for any relay # local users, and authenticated users can relay to any domain # after the DKIMproxy signs it accept from local for any relay via smtp://127.0.0.1:10027 queue compression > - test as many features as you can and let us know that they work; Known issue that mask-source on mail from localhost doesn't work, and Spamassassin doesn't like the format, perhaps it should be mentioned in smtpd.conf(5): X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,RP_MATCHES_RCVD,UNPARSEABLE_RELAY autolearn=ham version=3.3.2 [....] Received: from localhost (1000@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 1530f98c; for <[email protected]>; Thu, 28 Nov 2013 23:12:15 +0200 (EET) I used grep -E ' [0-9]{3} ' on /var/log/maillog, and I see 3 kinds of errors, none of them look serious to me: 1) 452 Too many messages sent Looks like it sends the error twice, is that expected? Anyway vger.kernel.org retries, and keeps delivering more messages in another smtp session. Nov 28 21:56:25 mx smtpd[24311]: delivery: Ok for 2f378d9099f1c2f4: from=<[email protected]>, to=<[email protected] k.net>, user=edwin, method=maildir, delay=0s, stat=Delivered Nov 28 21:56:25 mx smtpd[22113]: smtp-in: Failed command on session 03e27e4ad1a31e1c: "MAIL From:<[email protected]> BODY=8BITMIME SIZE=3646" => 452 Too many messages sent Nov 28 21:56:36 mx smtpd[22113]: smtp-in: Failed command on session 03e27e4ad1a31e1c: "MAIL From:<[email protected]> BODY=8BITMIME SIZE=3646" => 452 Too many messages sent Nov 28 21:56:46 mx smtpd[22113]: smtp-in: Disconnecting session 03e27e4ad1a31e1c: session not moving forward Nov 28 21:56:56 mx smtpd[22113]: smtp-in: New session 03e27e4b6010118c from host vger.kernel.org [209.132.180.67] 2) 500 Pipelining not supported Apparently this was my MUA (connecting to the submission port), but I can't reproduce the failure now: Nov 24 00:06:40 mx smtpd[21545]: smtp-in: New session 83832b91b55975ad from host 86-125-252-205.rdsnet.ro [86.125.252.205] Nov 24 00:06:40 mx smtpd[21545]: smtp-in: Bad input on session 83832b91b55975ad: 500 Pipelining not supported Nov 24 00:06:40 mx smtpd[21545]: smtp-in: Closing session 83832b91b55975ad 3) 500 Line too long Happened only once: Nov 25 01:00:04 mx smtpd[22113]: smtp-in: New session 03e27590f8fd6f3b from host vger.kernel.org [209.132.180.67] Nov 25 01:00:05 mx smtpd[22113]: smtp-in: Bad input on session 03e27590f8fd6f3b: 500 Line too long Nov 25 01:00:05 mx smtpd[22113]: smtp-in: Closing session 03e27590f8fd6f3b I received the message on my other box with postfix, and indeed the line was longer than 2k. Postfix chose to break the line after the limit, OpenSMTPD chose to reject the message, both are fine for me. Best regards, --Edwin -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
