But the point is that *everything* worked greatly before updating to 2.0.6.
Awful situation :-)First: Exim tried to reply the spam messages (mostly to the fake addresses, as you all know); it tried to do that 146 times for the last two days.
And second: I even got a probe message from DBMail mailing list =))I've done a small 'investigation' on this problem on Saturday, but I couldn't figure out why the first query (in the logs that I sent here) from auth_check_user_ext looks like WHERE lower(alias) = lower(''), then it tries to search by the *empty* userid. Sure, after this the result of resolving a user contains DSN_CLASS_FAIL with subject 1.
And that's why it gives EX_NOUSER in main.c...But!!! There is a second try (I do not know how it happens) to resolve a user, and then it makes that very query from auth_check_user_ext correctly ( like WHERE lower(alias) = lower('danil') ). And the message is delivered.
However dsnuser_worstcase_list returns DSN_CLASS_FAIL and still the result is EX_NOUSER.
I've done a (some kind of a bit ugly :-) ) workaround for myself: I've set #define EX_NOUSER EX_OK =))))) Well, I guess it's ok for me for a while because these days noone is running out of quota (I can increase it if it's necessary) and I have some kind of a default delivery address (postmaster, so there is always a user whom to deliver).
Please, tell me: is there already a fix for this problem?? And I was just wasting my time?..
-- Best regards, Danil V. Gerun.
smime.p7s
Description: S/MIME Cryptographic Signature
