Lena@??? <Lena@???> (So 14 Sep 2014 13:45:25 CEST):
…
> > Recipient Verification
> > Drop at connect time if the Recipient doesn't exist.
> > deny message = REJECTED - Recipient Verify Failed - User Not Found
> > domains = +all_mail_handled_locally
> > !verify = recipient/callout=2m,defer_ok,use_sender
>
> Recipient callout for domains handled locally (for incoming mail)
> makes no sense and is not performed, the "callout" is ignored.
> "callout" in "verify=recipient" is for outging mail (to remote domains).
Callout recipient verification for locally handled domains *is* useful
in cases where the final destination is not the local host. (Depends on
the scope of "locally".)
outside world ----> [ Exim ] --> [ internal MTA ]
Using callouts for recipient verification takes the pain of managing
a list of internal recpients on the Exim box. Just let Exim do
the callout to verify the existence of the final destination
account/user/whatever.
To avoid bounces in case the internal box does not respond, the
"defer_ok" option should be used (and is used in the example above).
E.g., this is an often used setup with internal MS Exchange boxes.
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: 7CBF764A -
gnupg fingerprint: 9288 F17D BBF9 9625 5ABC 285C 26A9 687E 7CBF 764A -
(gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B)-
