Bug#388460: exim4-daemon-light: sender verification is not working

[George B.]

On 20/09/06, Andreas Metzler <ametzler at downhill.at.eu.org> wrote:
>
> The interesting bit is this one:
>
> [...]
> > check !verify = sender
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > Verifying sdokdkdo at dsaodpojdopj.com
> [...]
> > dsaodpojdopj.com in "! +local_domains"? yes (end of list)
> > R: smarthost for sdokdkdo at dsaodpojdopj.com
> > calling smarthost router
> > smarthost router called for sdokdkdo at dsaodpojdopj.com
> >   domain = dsaodpojdopj.com
> [...]
> > routed by smarthost router
> >   envelope to: sdokdkdo at dsaodpojdopj.com
> >   transport: remote_smtp_smarthost
> >   host smtp.blueyonder.co.uk [195.188.53.60]
> > ----------- end verify ------------
> > sender sdokdkdo at dsaodpojdopj.com 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

I tried changing to "verify = sender/callout" but the address is still
accepted. If I understand the log correctly then it contacts my ISP's
SMTP server for the call out, which accepts it (probably because they
don't do recipient verification).

Why on earth does Exim call the smarthost for a local address? :-/

> 2# setting no_verify on the smarthost router and having a dnslookup
> router with verify_only doing the verification.

Could you go into a little more detail please. I'm still not to sure
how the router thing works (and ties in with the ACLs). As I said, my
knowledge of Exim is still a little basic.

> Perhaps you previously had callouts setup?

No, but then the two Sarge boxes that work use the "internet"
configuration. The Etch box is my personal server at home that I use
as a backup MX record on my domain, so I use a smarthost because I
don't have a static IP address.


George.