Hmm...
> On Jan 3, 2015, at 7:17 AM, salvi...@gmx.ch wrote:
>
> Hi,
>
> I'm a long-time happy user of qpsmtpd with a small site, and right now I'm in the process of setting up my site on a new server and reinstalling qpsmtpd. I want to use auth_imap, which is in HEAD but not in 0.94, so I decided to try HEAD, but HEAD is broken: it does not announce "AUTH" at all. So I went for commit ee01a07 (2014-12-22 15:01:12 -0800), except for the following issue:
That's a feature. By default, QP only advertises AUTH if there's an AUTH provider AND the connection is secured. See the contents of config/tls_before_auth
Matt
on https://github.com/smtpd/qpsmtpd/wiki/Install.Authentication suggests that you set up authentication without tls (it's commented out in config.sample) and only activate tls in a third step. Only the third page says
"Notice now that the previous authentication mechanisms are gone! When SSL is enabled, authentication is not advertised unless the connection is secure. This is a VERY good default, but it can be changed by editing config/tls_before_auth."
So, "AUTH" should be there as long as you don't have tls.
At the risk of beating a dead horse,
5c8f6b6 - Merge pull request #181 from jaredj/more-data-respond-tests (2015-01-01 18:59:21 -0800)
would stall after...
4729 4729 Loaded logging/warn 6
4729 4729 Connection from ###
4729 4729 (connect) earlytalker: pass, not spontaneous
4729 4729 (connect) relay: skip, no match
4729 4729 (connect) dnsbl: karma -1 (-2)
4729 4729 (connect) dnsbl: fail, NAUGHTY, zen.spamhaus.org
4729 4729 220 ### ESMTP qpsmtpd 0.95/v0.94-310-g5c8f6b6 ready; send us your mail, but not your spam.
4729 4729 dispatching EHLO [192.168.123.13]
4729 4729 250-### Hi ###
4729 4729 250-PIPELINING
4729 4729 250-8BITMIME
... and then time out later with...
4729 FATAL PLUGIN ERROR [logging::file_3a7]: Can't call method "notes" on unblessed reference at /home/smtpd/qpsmtpd/plugins/logging/file line 275, <STDIN> line 1.
4729 4729 (post-connection) connection_time: 101.698 s.
Note the missing "STARTTLS" above. Maybe it wasn't specifically "AUTH" missing but just the last option ("AUTH" if no tls, "STARTTLS" if with tls).
The new current HEAD
3db87b8 - Merge pull request #188 from msimerson/dbm-default-perm (2015-01-04 14:40:38 -0600)
does not have this problem anymore, both with the same config!
So I'm on HEAD/3db87b8 now.
Hans
Gesendet: Sonntag, 04. Januar 2015 um 06:44 Uhr
Von: "Matt Simerson" <m...@tnpi.net>
An: salvi...@gmx.ch
Cc: qpsmtpd@perl.org
Betreff: Re: Issues in the current HEAD
Von: "Matt Simerson" <m...@tnpi.net>
An: salvi...@gmx.ch
Cc: qpsmtpd@perl.org
Betreff: Re: Issues in the current HEAD
> On Jan 3, 2015, at 7:17 AM, salvi...@gmx.ch wrote:
>
> Hi,
>
> I'm a long-time happy user of qpsmtpd with a small site, and right now I'm in the process of setting up my site on a new server and reinstalling qpsmtpd. I want to use auth_imap, which is in HEAD but not in 0.94, so I decided to try HEAD, but HEAD is broken: it does not announce "AUTH" at all. So I went for commit ee01a07 (2014-12-22 15:01:12 -0800), except for the following issue:
That's a feature. By default, QP only advertises AUTH if there's an AUTH provider AND the connection is secured. See the contents of config/tls_before_auth
Matt
