While I am abandoning the idea of a strict authenticated sender for
the moment, I have come across something puzzling. You know that:
+-----------------------------------------------------------------------
------+
|verify_only | Use: routers** | Type: boolean |
Default: false|
+-----------------------------------------------------------------------
------+
If this option is set, the router is used only when verifying an
address or
testing with the -bv option, not when actually doing a delivery,
testing with
the -bt option, or running the SMTP EXPN command. It can be further
restricted
to verifying only senders or recipients by means of verify_sender and
verify_recipient.
I had this remnant of the auth sender verification, that I considered
dormant as no acl was calling it:
# verify setter
verify_setter:
driver = redirect
domains = +local_domains
verify_only
verify_sender
condition = ${if !eq{${extract{verified}{$address_data}}}{yes}}
# address_data = ${if eq{$local_part}{$authenticated_id}{verified=yes}
{dummy=yes}} $address_data
address_data = ${if !eq{$local_part}{$authenticated_id}{dummy=yes}
{verified=yes}} $address_data
data = $local_part
debug_print = \n**********\nsetter:$local_part\n$authenticated_id\
\nadd data:$address_data\n${if !eq{$local_part}{$authenticated_id}{a}
{b}}**********\n
note: local_domains, verify_only and verify_sender so this is not
called for any other verification but local domains senders. Well,
why then it was called when it received a sender callout from another
server I manage? I know this as the incorrect line:
data = $local_part (is missing @$domain)
was failing the remote callout for a particular alias (the only one
that ever is used on a domain that is not the default domain).
Does verify_sender not work as advertised? Do I need more caffeine?
Giuliano
--
H U M P H
|| |||
software
Java & C++ Server/Client/Human Interface applications on MacOS - MacOS X
http://www.humph.com/
