Autor: Peter Bowyer Datum: To: Exim users mailing list Betreff: Re: [exim] Exim 550 error
On 13/02/07, Martin Timbro <mtimbro@???> wrote: > Ok here goes:
Thanks - makes it much easier to see what's going on. The 550 is a
result of the sender address failing to verify - here's the relevant
bit of output:
>>> check verify = sender
>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>> routing nagios@???
>>> crm.deev.com in "@ : lsearch;/etc/mail/local_domains : mysql;select domain from domains where domain = 'crm.deev.com'"? no (end of list) >>> crm.deev.com in "! +local_domains"? yes (end of list)
>>> calling dnslookup router
>>> 192.168.0.68 in "0.0.0.0/8 : 10.0.0.0/8 : 172.16.0.0/12 : 192.168.0.0/16 : 127.0.0.0/8 : 169.254.0.0/16 : 192.0.2.0/24 :
192.88.99.0/24 : 198.18.0.0/15 : 224.0.0.0/4 : 240.0.0.0/4"? yes
(matched "192.168.0.0/16") >>> dnslookup router declined for nagios@???
>>> "more" is false: skipping remaining routers
>>> no more routers
>>> ----------- end verify ------------
>>> require: condition test failed
So crm.deev.com is resolving to 192.168.0.68 (not sure if by A or MX,
but it matters little). You have a 'ignore_target_hosts' directive in
your dnslookup router which tells it to ignore 192.168.0.0/16, so the
router declines. No other router is able to route mail to
crm.deev.com, so the verify fails and the ACL rejects the message.
Presumably you never need to deliver mail back to @crm.deev.com, so
you could exempt that domain from the verify=sender ACL, or provide a
verify_only router to make the verify work: