> Note further that whitelist_to, it seems then, would not be usefull
> for the spam_a lists since it never appears in To: and may or may not
> appear in Cc:
I'm confused. Your message has spamassassin-talk in the To: field. So does
this one. In my scan through the last 24 hours worth of message
Harry Putnam wrote:
> Note further that whitelist_to, it seems then, would not be usefull
> for the spam_a lists since it never appears in To: and may or may not
> appear in Cc:
Which may have caused me (and members of the list) some mail bouncing
problems when I initially joined. That is, it w
> My spam_ass mail is never from the list address, nor to the list address.
> So how does whitelisting_from `spamassassin' do any good? I don't
> doubt that it does, or that I have a screwball conception of how it
> works but I don't understand how it would work.
I think CC: works as well as To:
Harry Putnam wrote:
> I'm not sure I see how whitelist_from or to will work, unless the
> `from' is a reference to the berkely format `From ' (note the
> missing :)
>
It works because - well, I don't know. Which is kind of the point.
That is, the syntax, whitelist_from, etc., has nothing to do
Olivier Nicole wrote:
> I noticed that SA do not check the messages that have the X-BeenThere
> header in it.
Nah, I don't think there's anything wrong with your set up. I don't
think SA uses this. You simply need to add your lists to
./spamassassin/user_prefs.
Bryan
--
Labor exploitation hur
Harry Putnam wrote:
> Maybe a little different approach wouldn't require as much huffing
> and puffing:
> header Spama X-BeenThere =~ spamassassin-.*@lists
> score Spama -100
>
> So to get to spam status the score must go over +100.
>
> I haven't tested this much yet. Only started it when I
Craig R Hughes wrote:
> Wecs.com person:
>
> please be smarter about passing sa-talk digest messages through SA and
> then
> sending bounce messages to the mailing list.
>
> Thanks,
>
> C
Hi Craig,
Got any salt to go with this egg all over my face?
Not sure what's going on though. I just swit
On Mon, Jun 03, 2002 at 07:17:16PM -, [EMAIL PROTECTED] wrote:
>= WECS.COM AUTOMATIC NOTICE =
>
> Dear SPAM proliferation victim,
>
> Your email to WECS.COM was identified as SPAM. This can happen because of
> the email's content, its site origin, or bad or forged he
[EMAIL PROTECTED] wrote:
>= WECS.COM AUTOMATIC NOTICE =
>
> Dear SPAM proliferation victim,
>
> Your email to WECS.COM was identified as SPAM. This can happen because of
> the email's content, its site origin, or bad or forged header information.
Wecs.com person:
please
[EMAIL PROTECTED] wrote:
>= WECS.COM AUTOMATIC NOTICE =
Teehee.
Yet another example of why bouncing/devnulling mail tagged as spam is a bad
idea :)
bhoover -- you might want to consider whitelist_toing spamassassin-talk.
rOD.
--
"I'll hide somewhere, and you'll wear bi
= WECS.COM AUTOMATIC NOTICE =
Dear SPAM proliferation victim,
Your email to WECS.COM was identified as SPAM. This can happen because of
the email's content, its site origin, or bad or forged header information.
If you're not a SPAMMER (kind of like asking a lier...), the
11 matches
Mail list logo
