search for: l3665

Hi, I'm not entirely sure whether this issue is with exim or with dovecot. First some background: I'm using exim with dovecot-auth which in turn is using LDAP for authentication. When using AUTH PLAIN with the optional initial response argument, everything is fine. However when using AUTH PLAIN without the optional response argument, instead of getting an empty challenge ("334

...g in >> Exim's implementation of the AUTH command rather peculiar. Still, I >> managed to decipher at least part of it. >> >> That error is produced when FAIL status is returned from the driver: >> >> https://github.com/Exim/exim/blob/master/src/src/smtp_in.c#L3665 >> >> This FAIL status can be returned by the driver itself, but -- in this >> case more likely -- the Dovecot driver in Exim also returns FAIL status >> when Dovecot auth service returns "FAIL": >> >> https://github.com/Exim/exim/blob/master/src/src/au...

...the Exim error handling in > Exim's implementation of the AUTH command rather peculiar. Still, I > managed to decipher at least part of it. > > That error is produced when FAIL status is returned from the driver: > > https://github.com/Exim/exim/blob/master/src/src/smtp_in.c#L3665 > > This FAIL status can be returned by the driver itself, but -- in this > case more likely -- the Dovecot driver in Exim also returns FAIL status > when Dovecot auth service returns "FAIL": > > https://github.com/Exim/exim/blob/master/src/src/auths/dovecot.c#L472 &gt...

...39;s implementation of the AUTH command rather peculiar. Still, I >>> managed to decipher at least part of it. >>> >>> That error is produced when FAIL status is returned from the driver: >>> >>> https://github.com/Exim/exim/blob/master/src/src/smtp_in.c#L3665 >>> >>> This FAIL status can be returned by the driver itself, but -- in this >>> case more likely -- the Dovecot driver in Exim also returns FAIL status >>> when Dovecot auth service returns "FAIL": >>> >>> https://github.com/Exim/exi...