shanti
Verified User
Hi,
since the introduction of exim's AUTH_BLOCK_SENDER_SPOOFING in v1.680 some customers' mailclients and webapps
cannot send via that "old" way anymore resulting inaccording exim-reject-errors.
i would like to see a change in this code to accept granular configs like
/etc/virtual/example.com/spoofing_allowed
( # Format:
)
and the implementation of an additional check like
to allow more control here , because this new limitation though is great but forces many webapps to change .. it would be nice to not just implement that temporary.
RFC
br
-c-
since the introduction of exim's AUTH_BLOCK_SENDER_SPOOFING in v1.680 some customers' mailclients and webapps
cannot send via that "old" way anymore resulting inaccording exim-reject-errors.
i would like to see a change in this code to accept granular configs like
/etc/virtual/example.com/spoofing_allowed
( # Format:
Code:
# authenticated_user:allowed_sender_address
[email protected]:[email protected]
[email protected]:[email protected]
and the implementation of an additional check like
Code:
# NEW: Allow configured spoofing exceptions per domain
condition = ${if exists{/etc/virtual/${domain:$sender_address}/spoofing_allowed}\
{${if !eq{${lookup{$authenticated_id:$sender_address}lsearch{/etc/virtual/${domain:$sender_address}/spoofing_allowed}}}{}}}\
{yes}\
}
to allow more control here , because this new limitation though is great but forces many webapps to change .. it would be nice to not just implement that temporary.
RFC
br
-c-