On 2006-09-20 "George B." <[EMAIL PROTECTED]> wrote: > On 20/09/06, Marc Haber <[EMAIL PROTECTED]> wrote: [...] > >Try exim4 -d -bh <some-ip-address> and simulate an SMTP session with a > >invalid sender on the terminal. The debug output will probably help. > >If not, send the debug output to the bug report.
> I attach the debug output (thanks, I never thought of using this test mode). > The verification test is run and it succeeds, not sure why though. I'm > afraid my understanding of Exim is still a little basic. The interesting bit is this one: [...] > check !verify = sender > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Verifying [EMAIL PROTECTED] [...] > dsaodpojdopj.com in "! +local_domains"? yes (end of list) > R: smarthost for [EMAIL PROTECTED] > calling smarthost router > smarthost router called for [EMAIL PROTECTED] > domain = dsaodpojdopj.com [...] > routed by smarthost router > envelope to: [EMAIL PROTECTED] > transport: remote_smtp_smarthost > host smtp.blueyonder.co.uk [195.188.53.60] > ----------- end verify ------------ > sender [EMAIL PROTECTED] verified ok i.e. the smarthost router accepts *everything* making the address deliverable for exim and therefore "verified". I actually cannot see how this setup ever could have worked, the only two ways to actually verify addresses whike using a smarthost for delivery are 1# using callouts for verification 2# setting no_verify on the smarthost router and having a dnslookup router with verify_only doing the verification. Perhaps you previously had callouts setup? cu andreas -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken. (c) Jasper Ffforde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
