My exim 4.80.1 callout has been fine until recently when for the 2nd time a
valid user has been tagged as "unrouteable" and email rejected. A head of
the callout database looks like:
11-Mar-2151 23:38:25 spethers@??? callout=unknown
postmaster=unknown random=unknown
02-Feb-2015 18:08:58 shannonjergenson@??? callout=reject
03-Feb-2015 01:12:16 ssanborn@??? callout=reject
03-Feb-2015 01:12:21 sb1ar0saxhw@??? callout=reject
03-Feb-2015 01:16:31 bazthk@??? callout=reject
03-Feb-2015 03:57:37 PSoong@??? callout=reject
03-Feb-2015 04:40:43 CKnirk@??? callout=reject
03-Feb-2015 11:39:02 mhess@??? callout=reject
Everything looks normal, except poor spethers, who has the 11-Mar-2151 date
and I have no log entry with their address in it between their last
successful delivery and their first entry noting "unrouteable". There was
about 8 minutes between the last successful delivery yesterday and the first
"unrouteable" log entry.
2015-02-09 21:53:13 1YL3ku-0005mu-Tj => spethers@???
<SPethers@???>...
...
2015-02-09 22:01:30...rejected RCPT <spethers@???>: unrouteable
address
This happened about a week ago and I cleared the item in the callout
database and didn't have an issue until now. Any ideas? Can't seem to find
anything similar in the archive...
Callout config under acl_check_rcpt:
accept domains = +relay_to_domains
endpass
message = unrouteable address
verify = recipient/callout=15s,defer_ok
delay = ${eval:$rcpt_fail_count*5 + 5}s
I run this same config with dozens of other nearly identical mail servers
and have not had this problem.
--
Michael Sullenszino
mylists@???
