Thanks, that's what I thought by reading the manual. So it is the case
that recipient callouts could quite easily be made to 'external'
domains, if there are forwarding arrangements setup that cause it.
This brings me back to my point about "use_sender" on recipient
callouts vs sender callouts - the recipient callout is just as likely
(in this scenario) to cause cascading/possibly looping callouts, is it
not?
Andy
-----Original Message-----
Friday, May 7, 2004, 3:44:08 PM, ph10@??? wrote:
> On Fri, 7 May 2004, Andy Fletcher wrote: >> I was referring to an forwarding via /etc/aliases for example:
>>
>> originalname: newname@newdomain
>>
>> In this case, is newname@newdomain verified by recipient callout? > If you mean this is a server machine, and some other host calls it and
> says > RCPT TO:<originalname@domain> > (you can't tell if it's a sender or a recipient callout) and the server
> has verify=recipient in an ACL? > In that case, yes, the new address is verified.
