Author: Peter Bowyer Date: To: exim users Subject: Re: [exim] Email DNS Issue
On 14/03/2008, Matt <lm7812@???> wrote: > > IF you are doing sender-verify, you will have to expect that a
> > significant number of sending hosts will not pass.
> >
> > Faulty 'vanilla' DNS entries aside, many will be in large ISP 'pools'
> > where incoming/outgoing are separate, and may not be properly listed in
> > DNS, or just not configured to respond as you wish they would.
> >
> > Others may treat your query as possible spambot probing and shut *you*
> > out. Still others have delays or greylsting that will look like a fail
> > in any reasonable time, hence drop the connection.
>
>
> Its not a sender-verify like that. I THINK all it does is make sure
> the sending email adresses domain has an mx record. I did not add
> this to my exim config its just been there for years.
>
> ---
> # Deny unless sender address can be verified:
> # This statement requires the sender address to be verified before any
> # subsequent ACL statement can be used. If verification fails, the incoming
> # recipient address is refused. Verification consists of trying to route the
> # address, to see if a bounce message could be delivered to it. In the case of
> # remote addresses, basic verification checks only the domain.
>
> require verify = sender
> ---
>
> Does anyone else have this in the exim.conf? This 4.6 Exim.
Of course they do.... the comment from the default config that you
pasted tells you what happens - Exim tries to route the address... in
other words, it runs the address through its router config to see if
the address would 'work' if a message were to be sent there. It stops
after the routihg phase, no transports are called - so no attempt is
actually made to deliver a message.
You have to specifically configure the callout functionality. The docs
are a good resource here...
