Nate,

> I know we can whitelist/blacklist domains by adding "@domain.com"
> to mailaddr table.  We can do individual emails by adding
> "[EMAIL PROTECTED]" to mailaddr table.
>
> I would like to expand the capabilities and be able to add
> "@*.domain.com" and "[EMAIL PROTECTED]" as well to catch all
> sub-domains of a domain as well.

As Gary noted, this is not currently available.
You will need to modify subroutine make_query_keys
to generate additional search key(s).

I'm not sure that having the same mailbox name at different subdomains
to actually imply the same user is a good idea. I'd think the mail
system organization could benefit from some cleaning. Perhaps
MTA could map aliases to a single canonical email address before
feeding a content filter, and a back-end mail delivery could
deliver user's mail to their preferred workstations.

It would be possible to preserve the host (subdomain) name by
mapping it to address extension, e.g.:

MTA front-end: [EMAIL PROTECTED] -> [EMAIL PROTECTED]
amavisd looks up [EMAIL PROTECTED] and [EMAIL PROTECTED]
MTA back-end: [EMAIL PROTECTED] -> [EMAIL PROTECTED]

  Mark

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to