Subj : Re: email.can additions
To   : Frank Vest
From : Digital Man
Date : Sun Sep 25 2005 02:42 am

  Re: Re: email.can additions
  By: Frank Vest to alt.bbs.synchronet on Sun Sep 25 2005 09:38 am

 > >  > I just gotta ask this (glutton that I am). :-)
 > >  >
 > >  > *@*.somedomain.com
 > >  >
 > >  > would block all sub domains of somedomain.com right?
 > >
 > > No, filters only support one wildcard character be entry.
 > >
 > >  > IE: [anytext]@subdomain.somedomain.com
 > >  >
 > >  > (this can't be that easy) :-D
 > >
 > > No, it's not. You'll need to either filter:
 > >
 > > "*somedomain.com", which has the down-side of also filtering
 > >                    "anything@notsomedomain.com" :-(
 > >
 > > Or use 2 filters:
 > >
 > > "*@somedomain.com" filtering [anytext]@somedomain.com
 > > "*.somedomain.com" filtering [anytext].somedomain.com
 > >
 > > E-mail typically comes from user@somedomain.com however, not
 > > user@host.somedomain.com.
 > 
 > Ok. Next question: Does the filter look at the "From:" or somewhere
 > else? IE: Your from line is
 > "digital.man@vert.synchro.net.remove-dbq-this" which is obviously faked.
 > If I were to filter you, what would I put in the filter?

Well to begin with, we're talking about e-mail filters, for the mail server.
The "From:" address you quoted is from an NNTP article header. NewsLink
doesn't use the email.can filter file (though it could be modified to do so).

But, yes, the mail server compares the value in the SMTP envelope (the e-mail
address given in the SMTP "MAIL FROM" command), as well as the "From" header
field e-mail address against those in the email.can filter file.

                                                  digital man

Snapple "Real Fact" #134:
An ant can lift 50 times its own weight. 

.