Subj : Re: email.can additions
To   : Frank Vest
From : Digital Man
Date : Sat Sep 24 2005 05:28 pm

  Re: Re: email.can additions

 > >  >  >  > Ok. Let me understand this correctly.
 > >  >
 > >  >  >  > I have in my "email.can" file the line "*@optonline.com" <sans qu
 > >  >  >  > I also have in my "email.can" file the line "*.optonline.com" <sa
 > >  >
 > >  >  >  > I just received an email From:someone@optonline.com   Why?
 > >  >
 > >  >  > I don't know, I would need more details. Please forward the e-mail t
 > >  >  > I'll take a look at it.
 > >  >
 > >  > Maybe because you said *. *allows* when you corrected my error when I
 > >  > apparently misunderstood you and that *@ is disallow and *. is allow. I
 > >  > guessing that he is still getting it because if he has both *. and *@ t
 > >  > allows it anyways.
 > >  >
 > >  > Thats my best guess. Please feel free to let me know if I am still
 > >  > misunderstanding you.
 > >
 > > Yeah, you're still misunderstanding. If you block "*@somedomain.com" that 
 > > block e-mail addresses of [anytext]@somedomain.com. If you block
 > > "*.somedomain.com" it will block e-mail addresses of [anytext].somedomain.
 > >
 > > Notice, I didn't use the word "allow". :-)
 > 
 > 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 per 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.

                                                  digital man

Snapple "Real Fact" #105:
You will burn 7% more calories walking on hard dirt than pavement.

.