Re: Re5: Filter

[Elton <ehd@xxxxxxxxxxx>]

Glenn,

There is a "Harvested" valid user address in the spoofed header, allowing SPAM to pass through PO to our users; thus this Config setting will not stop the SPAM.

A Filter will.
 

Elton

"Glenn A. Bookout" wrote:

> Howdy:
> On 11/19/2002 13:48 USA PT (-0800),
> ehd@xxxxxxxxxxx ( Elton ), wrote...
> >I use the Config. setting you
> outline(I think it is the "Default") and I
> >"return" mail to Unknown Users.  However, that will
> not handle SPAM'er
> >Header Spoofing.
>    Whether they spoof or not, if it's not addressed in some
> way to a
> valid account the server should reject the msg. ( ours seems to work
> fine
> for hundreds of users ).
> >We get mail all the time from
> SPAM'ers who send to users
> >we don't have, ie: I filter "Header To":
> >*undisclosed*|*recip*|*<>*|*hello*|*reply*|*offer*|*send*,
> etc.
>    The reason you get msgs. w/ "undisclosed" is
> that a valid address is
> in the BCC area ( or somewhere ).
> >I would do more in the "Header
> To:", if my "Subject and Body Filters" did
> >not get most of the SPAM that is addressed to all sorts of invalid
> user
> >names -- just responded to Marcs message as to how to do it.
>    If the above mentioned Config. is set you should get no
> mail for
> account addresses that are not a current and valid user.
>    I would assume the
> "Subject and Body Filters" are probably catching
> their SPAM before the server gets a chance to act on the valid
> user
> choice ( only Tenon knows the order of msgs. through the system ). 
> If
> so, I would think they would want to reverse the order so the
> filters
> don't have to work so hard ( i.e.:  if it's a valid user, then
> invoke any
> applicable filters ).
> Glenn