Wildcard White/Black Lists?

I know we can whitelist/blacklist domains by adding
"domain.com" to 
mailaddr table.  We can do individual emails by adding 
"userdomain.com" to mailaddr table.

I would like to expand the capabilities and be able to add 
"*.domain.com" and "user*.domain.com" as well to catch all 
sub-domains of a domain as well.

Any suggestions?

- Nate


------------------------------------------------------------
-------------
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
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

On 8/21/07, Nate <nm_listvisp.net> wrote:
> I know we can whitelist/blacklist domains by adding
"domain.com" to
> mailaddr table.  We can do individual emails by adding
> "userdomain.com" to mailaddr table.
>
> I would like to expand the capabilities and be able to
add
> "*.domain.com" and "user*.domain.com" as well to catch all
> sub-domains of a domain as well.
>
> Any suggestions?
>
> - Nate
>

http://www.ijs.si/software/amavisd/README.lookups.txt

userexample.com
user
example.com
.example.com

If you were to use .example.com, this would include all users
at that
domain and subdomains, so user.example.com would already
be included.

You can see how a query might look:
http://marc.info/?l=amavis-user&m=113183777625635

You will notice that user.example.com is not one of
the keys.

-- 
Gary V

------------------------------------------------------------
-------------
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
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

Nate,

> I know we can whitelist/blacklist domains by adding
"domain.com"
> to mailaddr table.  We can do individual emails by
adding
> "userdomain.com" to mailaddr table.
>
> I would like to expand the capabilities and be able to
add
> "*.domain.com" and "user*.domain.com" 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: userhost1.example.com -> user+host1example.com
amavisd looks up user+host1example.com and userexample.com
MTA back-end: user+host1example.com -> userhost1.example.com

  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
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

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

Mark,

Actually from what I read Gary seemed to think it was
possible.  I'll 
quote him.  Perhaps I mis-understood?

Gary wrote:
 >If you were to use .example.com, this would
include all users at that
 >domain and subdomains, so user.example.com would already
be included.

If in fact we can use .example.com and that will match all 
subdomains as well, that meets my goal exactly.  Would 
".example.com" also match an exact domain match
such as 
"userexample.com" if there is no subdomain?

Thanks,

- Nate 


------------------------------------------------------------
-------------
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
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

Nate,

> If in fact we can use .example.com and that will
match all
> subdomains as well

Yes.

> that meets my goal exactly.

> Would ".example.com" also match an exact
domain match such as
> "userexample.com" if there is no
subdomain?

Yes, .example.com matches xxxwhatever.example.com
as well as yyyexample.com (unlike in Postfix, where
a dot domain does not include a domain itself).
See README.lookups.

What I thought you were asking for is to match a specific
user no matter what subdomain it uses, so for example
all the following would be matched by a single entry
(such as jane.example.com) in a lookup table:
  janehost1.example.com
  janexx.subdomain.example.com
  janeexample.com
but that entry would not match bobhost1.example.com.
This is not possible and my answer was about it.

  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
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

At 09:30 AM 8/22/2007, Nate wrote:

> >
> >As Gary noted, this is not currently available.
> >You will need to modify subroutine make_query_keys
> >to generate additional search key(s).
>
>Mark,
>
>Actually from what I read Gary seemed to think it was
possible.  I'll
>quote him.  Perhaps I mis-understood?
>
>Gary wrote:
>  >If you were to use .example.com, this would
include all users at that
>  >domain and subdomains, so user.example.com would already be included.
>
>If in fact we can use .example.com and that will
match all
>subdomains as well, that meets my goal exactly.  Would
>".example.com" also match an exact domain match
such as
>"userexample.com" if there is no
subdomain?

I think I answered my own question.  I put in a .domain.com entry 
and it worked, plus it blocked userdomain.com email as well as

usersub.domain.com email.

I'm impressed! =)

- Nate 


------------------------------------------------------------
-------------
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
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/