Strange, then why does authentication work fine with correct data? It's
only the incorrect data (decided by a separate server which is contacted
by my PAM module) that causes a temporary error code in Exim instead of
a permanent. I don't understand the rest of the message Exim writes, I
have no idea where it all comes from. Do I need to know that?
-Yves
-------- Ursprüngliche Nachricht --------
Von: Jeremy Harris via Exim-users <exim-users@???>
Gesendet: Dienstag, 29. Dezember 2020, 01:26 MEZ
Betreff: [exim] Authentication returns code 435 instead of 535
On 29/12/2020 00:05, Yves Goergen via Exim-users wrote:
I see a lot of lines like this in the mainlog:
2020-12-27 20:04:00 login authenticator failed for (USER)
[199.192.16.253]: 435 Unable to authenticate at present
(set_id=scanner@???): Permission denied
So it returns the temporary code 435 instead of the permanent code 535.
Why's that? I'm using the suggested config from the Exim manual. Should
there be a "fail" or "false" somewhere in the expansion?
Depending on your OS, you may have a permissions issue. Note the last para.
in the docs for the pam expansion condition, and also
http://wiki.wlug.org.nz/EximSmtpAuth
