Kevin P. Fleming wrote:
> Nico Erfurth wrote:
>
>> Kevin P. Fleming wrote:
>>
>>> I'm working on an update to my callout caching patch, that will cache
>>> things like domains that respond negatively to MAIL FROM:<> or that
>>> respond positively to all local parts.
>>
>>
>>
>> What's non conforming on replying ok for ALL local parts?`
>> I do so for my private domain, and i forward everything to my own
>> mailbox.
>
>
> This is fine. What this means to me is that once I have confirmed that
> your server accepts all local parts (or at least a sufficiently random
> one), I can cache that fact and stop sending sender verification
> callouts for your domain. Maybe my choice of "non-conforming" was a bit
> strong here.. Sorry about that.
Ok, that sounds better (still will fill serverlogs with strange stuff),
you can try with @perlgolf.de addresses if you want.
>> And you can't filter for servers that reject bounces in every case, just
>> think of exim, the sender verification is done in the RCPT acl (mostly),
>> how do you know what's denied?
>>
>
> This is only for sender verification callout caching (whew!). With the
> code I'm working on, if the server rejects MAIL FROM:<>, then I'll cache
> that and again stop trying to do sender verification callouts for that
> domain (until the cache record expires, anyway).
Think again ;)
The question is, HOW do you know whats rejected?
rcpt_acl:
deny message = No bounces allowed
senders = :
This would reject the address in RCPT TO: time, so you will not know WHY
the callout was bounced, unless you do many checks.
I hope i get you right, you want to do more than one check at a time?
1.) <> & <$sender_address>
2.) <$receiver_address> & <$sender_address>
3.) <> & <GARBAGE@domain>
4.) <$receiver_address> & <GARBAGE@domain>
if i get you right with this, your server would be the first one i set
on a reject list ;)
ciao
