Blocking a specific to address in mappings
Hi,
I am trying to blocking sending access to a specific address on our front end mta using the mappings file.
The mappings file seems to work if I block on an entire domain, but a specific email address does not work. For example:
SEND_ACCESS
tcp_*|*|*|darren@ourdomain.com $NMail$ Blocked <--does not block the email
BUT
SEND_ACCESS
tcp_*|*|*|*@ourdomain.com $NMail$ Blocked <works and blocks all email to the ourdomain.com domain.
Can I not go as fine as a specific email address?
[546 byte] By [
DarrenLCC] at [2007-11-26 11:27:09]
# 1
Yes, you can go as far as a specific address, but you have to put in what the MTA is seeing at that point.
Note that imsimta test -rewrite will check your address-based *_ACCESS
mapping tables and is quick and convenient to use. But to make really
effective use of this, you need to use all relevant switches (so that the
input makes sense) and enable enough debugging in the output so that you
can see what the probe turned out to be. If you have trouble figuring out
how to use all the test -rewrite switches appropriately to get a meaningful
test, then you will need to resort instead to enabling slave_debug on the
relevant incoming tcp_* channels (as well as, say, MM_DEBUG=3 in option.dat).
For imsimsimta test -rewrite, a starting point might be:
imsimta test -rewrite -from=user2@domB.com -debug=level=3 CO.AAA@CI.domA.com
But depending upon your configuration, you might also need to use switches
such as -source_channel, -sender, -check_expansions, etc.
