Subj : Re: email.can additions
To   : Time Warrior
From : Digital Man
Date : Thu Sep 22 2005 08:00 pm

  Re: Re: email.can additions
  By: Time Warrior to Digital Man on Thu Sep 22 2005 09:57 pm

 > From Newsgroup: alt.bbs.synchronet
 > 
 >   To: Digital Man
 >   Re: Re: email.can additions
 >   By: Digital Man to Frank Vest on Fri Sep 23 2005 01:38 am
 > 
 >  >  > I would like to know/understand how the filter works. I still receive
 >  >  > spam messages from "@optonline.com" even though the domain is in the
 >  >  > email.can file. :(
 > 
 >  > You need to specify "*@optonline.com" if you wish to filter all e-mail
 >  > addresses from that domain.
 > 
 > I use *.domain.com and this "appears" to work also.

Probably not as you intended. If "*.domain.com" is in your host.can file, for
example, it would disallow connections from "somehost.domain.com", but would
*allow* connections from "domain.com". If you "*.domain.com" is in your
email.can file, for example, it would disallow e-mail messages from
"someuser@somehost.domain.com", but would *allow* e-mail from
"someuser@domain.com".

 >  > Personally, I think filtering *strictly* on SMTP server addresses, mail
 >  > envelopes, or mail header content is not very effective. The body of the
 >  > message must be included in the filtering process for it to be truly effe
 >  > and this is were utilities like POPfile come into play.
 > 
 >  Will this ever be a Synchronet feature? 

Likely. Probably in form of a external mail processor script.

 > Sounds interesting.

The hooks are already there for it. In the mean-time, there's POPfile.

                                                  digital man

Snapple "Real Fact" #47:
Giraffes have no vocal chords.

.