You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Robb <ro...@unrealstyle.com> on 2006/01/21 22:42:16 UTC

X-Spam Status

Hello All,
    I am working with a customer who is complainiing that Spam Assassin is not working correctly becuase it is not putting headers into some emails. 

So does SA mark EVERY email with the:
X-Spam-Status: Yes/No  header?

The customer gave header information which seems to be lacking pertinent information about who the mail is going to.

Received: from omc2-s8.bay6.hotmail.com ([65.54.249.18]) by ctswim.org with MailEnable ESMTP; Fri, 20 Jan 2006 08:36:20 -0500
Received: from hotmail.com ([65.54.173.11]) by omc2-s8.bay6.hotmail.com with Microsoft SMTPSVC(6.0.3790.211);
  Fri, 20 Jan 2006 05:36:16 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
  Fri, 20 Jan 2006 05:36:15 -0800
Message-ID: <BA...@phx.gbl>
Received: from 67.131.237.13 by by5fd.bay5.hotmail.msn.com with HTTP;
 Fri, 20 Jan 2006 13:36:15 GMT
X-Originating-IP: [81.199.172.116]
X-Originating-Email: [liverpoollottery_2006@msn.com]
X-Sender: liverpoollottery_2006@msn.com
From: "michael fowler" <li...@msn.com>
Bcc: 
Subject: WINNING VERIFICATION FORM....
Date: Fri, 20 Jan 2006 13:36:15 +0000
Mime-Version: 1.0
Content-Type: text/html; format=flowed
X-OriginalArrivalTime: 20 Jan 2006 13:36:15.0936 (UTC) FILETIME=[7CB14400:01C61DC6]
Return-Path: liverpoollottery_2006@msn.com

This is using SA 3.0 with Plesk 7.5 

I looked at her emails in the /cur and /new dirs on her mail account and ALL of them have the X-Spam-Status header.

Is the customer making this up? 

Thanks for any imput,
Robb


Re: X-Spam Status

Posted by Robert Blayzor <rb...@inoc.net>.
Spam Ass wrote:
> The only time I have run into an email not being tagged is when the
> email was over a certain size.  I believe the default max size is
> 256kb.  This can be changed on a per user or global basis though.


Other times this will happen is when you're using spamd/spamc and a
timeout occurs between the client and the server.  If that happens spamc
returns the original message as unscanned.  If you have a high volume
server environment you have to do a lot of timeout tweaking to insure
most of your emails are scanned relatively quickly without deadlocking
the mail server or running the spamd box out of resources. ;-)

-- 
Robert Blayzor, BOFH
INOC, LLC
rblayzor\@(inoc.net|gmail.com)
PGP: 0x66F90BFC @ http://pgp.mit.edu
Key fingerprint = 6296 F715 038B 44C1 2720  292A 8580 500E 66F9 0BFC

Any sufficiently advanced bug is indistinguishable from a feature.  -
Kulawiec

Re: X-Spam Status

Posted by jdow <jd...@earthlink.net>.
From: "Gene Heskett" <ge...@verizon.net>

> On Sunday 22 January 2006 14:08, Jerry Gaiser wrote:
>>On Saturday 21 January 2006 09:03 pm, Gene Heskett wrote:
>>> One facility that kmail seems to be missing, is the ability to send
>>> such crap to /dev/null, all I get are error messages when thats
>>> attempted.
>>
>>Not really /dev/null but Trash, but I do this to a couple of folks I
>> *never* want to see again.
>>
>>Set up a filter keyed to the 'From' address. In 'Filter Action' box,
>> click 'More' for an additonal action. First action, 'Mark as' 'Read'.
>> Second action, 'File into Folder' 'trash'. Make sure the filter is
>> the first on your list. Bye Bye..
> 
> The problem with that is that kmail doesn't empty the trash till you 
> quit it, which may be 2-3 weeks down the log as I reboot to a new 
> kernel, currently 2.6.16-rc1.  Now if it had a cron interface to make 
> it dump the trash daily, that would be nice.

Heh, I collect ham and spam "rough counts" by leaving the spams unread
in my spam folder. Then I mark all the "Deleted Items" folder contents
unread and get a ROUGH compare of spam to ham ratios. Then I delete all
the spam and manually empty the deletia. (In OE its right click on the
"Deleted Items" folder and select "Empty....") I do that once a day
before I turn off the monitor for the night.

{^_-}


Re: X-Spam Status

Posted by Gene Heskett <ge...@verizon.net>.
On Sunday 22 January 2006 14:08, Jerry Gaiser wrote:
>On Saturday 21 January 2006 09:03 pm, Gene Heskett wrote:
>> One facility that kmail seems to be missing, is the ability to send
>> such crap to /dev/null, all I get are error messages when thats
>> attempted.
>
>Not really /dev/null but Trash, but I do this to a couple of folks I
> *never* want to see again.
>
>Set up a filter keyed to the 'From' address. In 'Filter Action' box,
> click 'More' for an additonal action. First action, 'Mark as' 'Read'.
> Second action, 'File into Folder' 'trash'. Make sure the filter is
> the first on your list. Bye Bye..

The problem with that is that kmail doesn't empty the trash till you 
quit it, which may be 2-3 weeks down the log as I reboot to a new 
kernel, currently 2.6.16-rc1.  Now if it had a cron interface to make 
it dump the trash daily, that would be nice.

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: X-Spam Status

Posted by Jerry Gaiser <je...@gaiser.org>.
On Saturday 21 January 2006 09:03 pm, Gene Heskett wrote:
> One facility that kmail seems to be missing, is the ability to send such
> crap to /dev/null, all I get are error messages when thats attempted.

Not really /dev/null but Trash, but I do this to a couple of folks I *never* 
want to see again.

Set up a filter keyed to the 'From' address. In 'Filter Action' box, click 
'More' for an additonal action. First action, 'Mark as' 'Read'. Second 
action, 'File into Folder' 'trash'. Make sure the filter is the first on your 
list. Bye Bye..

-- 
Jerry Gaiser in North Plains, Oregon USA (Zone8a) - 45.6933N 123.0418W


Re: X-Spam Status

Posted by jdow <jd...@earthlink.net>.
From: "Craig McLean" <cr...@fukka.co.uk>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Gene Heskett wrote:
>> 
>> No I'm not, Joanne!  Fetchmail is run from rc.local and delivers the 
>> mail from vz and gmail to /var/spool/mail/gene on a 10 minute repeating 
>> loop.
>> Kmail, then, completely asynchronously but on the same basic 10 
>> minute repeat timing, grabs the contents of that file and sorts it into 
>> its various folders after pipeing _some_ of the mail through SA.
> [snip]
>> 
>> Now, it looks as if I should make /etc/procmail/procmailrc be owned by 
>> gene:gene, and that I should set kmail to pipe the mail, using 
>> 
>> procmail -pm /etc/procmail/procmailrc
>> 
>> from the man pages, but I'm not sure what other arguments might be 
>> needed.  I've copied your recipe into /etc/procmail/procmailrc 
>> and /etc/procmail/* is owned by gene:gene.
> 
> Erm, I think you should use per-user procmail recipes rather than tinker
> with the globals. I believe your ~/.procmailrc can sort this out.
> 
>> So I think the next step is to add the filtering rule to kmail and fire 
>> a message off to the fedora list for effect, which will generate 
>> testing mails aplenty.
>> 
> 
> Gene, I'm a little confused about your setup, why not just get fetchmail
> to deliver all mail to procmail as the local MDA (man fetchmail will
> help you out), then let procmail sort into folders and spam check as
> necessary, and then use KMail as what it essentially is - a mail reader.
> Have I missed something obvious?

Enh - deliver direct to the mailbox via procmail as the default mda.
{^_-}


Re: X-Spam Status

Posted by Craig McLean <cr...@fukka.co.uk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gene Heskett wrote:
> 
> No I'm not, Joanne!  Fetchmail is run from rc.local and delivers the 
> mail from vz and gmail to /var/spool/mail/gene on a 10 minute repeating 
> loop.
> Kmail, then, completely asynchronously but on the same basic 10 
> minute repeat timing, grabs the contents of that file and sorts it into 
> its various folders after pipeing _some_ of the mail through SA.
[snip]
> 
> Now, it looks as if I should make /etc/procmail/procmailrc be owned by 
> gene:gene, and that I should set kmail to pipe the mail, using 
> 
> procmail -pm /etc/procmail/procmailrc
> 
> from the man pages, but I'm not sure what other arguments might be 
> needed.  I've copied your recipe into /etc/procmail/procmailrc 
> and /etc/procmail/* is owned by gene:gene.

Erm, I think you should use per-user procmail recipes rather than tinker
with the globals. I believe your ~/.procmailrc can sort this out.

> So I think the next step is to add the filtering rule to kmail and fire 
> a message off to the fedora list for effect, which will generate 
> testing mails aplenty.
> 

Gene, I'm a little confused about your setup, why not just get fetchmail
to deliver all mail to procmail as the local MDA (man fetchmail will
help you out), then let procmail sort into folders and spam check as
necessary, and then use KMail as what it essentially is - a mail reader.
Have I missed something obvious?

Kind Regards,
C.

- --
Craig McLean		http://fukka.co.uk
craig@fukka.co.uk	Where the fun never starts
	Powered by FreeBSD, and GIN!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFD083GMDDagS2VwJ4RAjDuAJ9jPcoSOeJx3mDvtVNEX3oeqnqX5ACfTq9J
r8CxJhkwuN1js79c/ig18a4=
=5ICI
-----END PGP SIGNATURE-----

Re: X-Spam Status

Posted by jdow <jd...@earthlink.net>.
From: "Gene Heskett" <ge...@verizon.net>

> On Sunday 22 January 2006 04:15, jdow wrote:
>>From: "Gene Heskett" <ge...@verizon.net>
> [...]
>>>>> One facility that kmail seems to be missing, is the ability to
>>>>> send such crap to /dev/null, all I get are error messages when
>>>>> thats attempted.
>>>>
>>>>I don't remember if you use procmail or not.
>>>
>>> No, I'm using fetchmail.  But is there a way to pipe fetchmails
>>> output thru a prefilter such as procmail?  Yeah, I know, man
>>> procmail to the rescue....  Looks doable, but when I have both eyes
>>> open simultainously I think.  Right now its only one.  Getting
>>> sleepy out and all that.
>>>
>>>>This is from my
>>>> .procmailrc recipe set:
>>>># Uncomment either /dev/null or /$HOME/mail/uol_crap, your choice.
>>>># Modify the latter as appropriate for your userlevel mail storage
>>>>
>>>>:0:
>>>>
>>>>* ^From: AntiSpam UOL <.*...@uol.com.br>
>>>>#/dev/null
>>>>/$HOME/mail/uol_crap
>>>>
>>>>
>>>>{^_-}
>>
>>That's right. You're using KMail to run fetchmail so you're helpless.
>
> No I'm not, Joanne!  Fetchmail is run from rc.local and delivers the
> mail from vz and gmail to /var/spool/mail/gene on a 10 minute repeating
> loop.  Kmail, then, completely asynchronously but on the same basic 10
> minute repeat timing, grabs the contents of that file and sorts it into
> its various folders after pipeing _some_ of the mail through SA.  This
> list for obvious reasons is picked off first and never see's an SA
> inspection.  There are several other fairly clean lists that get picked
> off before the SA inspection.  Unforch for the SA workload, lkml isn't
> one of them as most of the servers at vger seem to be fairly wide open
> & take even blank mails from spammers just clearing the barrels for the
> next barrage.

I use a .procmailrc file on a per user basis. (That way I can hack mine
without screwing up Loren's.)

I include this line up at the top:
defaults mda "/usr/bin/procmail -d jdow"

And I include a private .procmailrc with just a boatload of little nifties
in it. Some of them include these:
#############################################################################
# Necessary generic definitions
#############################################################################
DROPPRIVS=yes
VERBOSE=yes
LOGNAME=procmail

## rawmbox is no longer needed at this time.
#:0c: clone.lock
##* ^List-Id: .*(spamassassin\.apache.\org)
#$HOME/mail/rawmbox

#############################################################################
# Then we install some deaths and diversions
#############################################################################

:0:
* ^From: MAILER-DAEMON@ceres\.concept\.net\.nz
/dev/null

:0:
* ^From: *.fleagroups.com
$HOME/mail/fleagroups.com

:0:
* ^From: Postmaster@intellitron.com.au
/dev/null

:0:
* ^From: AntiSpam UOL <.*...@uol.com.br>
#/dev/null
/$HOME/mail/uol_crap

:0:
* ^From: MAILER-DAEMON@c1-sec.com
/dev/null

:0:
* From: postmaster@elrond.mrc.ac.za
/dev/null

:0:
* ^From: .*survey.com
/dev/null
#.... and so forth

#############################################################################
# Then we kill forged spam assassin headers. (Helps with test later on.)
#############################################################################

:0
* ^X-Spam-Status:
{
    :0 fw
    | formail -R "X-Spam-Status:" "X-False-Spam-Status:"

    :0 fw
    | formail -A "X-Nasty: Aren't we?"
}

:0
* ^X-Spam-Level
{
    :0 fw
    | formail -R "X-Spam-Level" "X-False-Spam-Level"
}

:0
* ^X-Spam-Checker-Version:
{
    :0 fw
    | formail -R "X-Spam-Checker-Version:" "X-False-Spam-Checker-Version:"
}


#############################################################################
# Then we have another "save the mails" option point.
#############################################################################

#:0c: clone.lock
##* ^List-Id: .*(spamassassin\.apache.\org)
#$HOME/mail/rawmbox

# Use these two lines and this incantation:  "procmail procmailrc_test <nasty1"
# with the appropriately named test procmailrc.
#:0:
#$HOME/processed

#############################################################################
# Special customer email tricks. Play a sound when their email comes in.
# Hey, it IS a misuse. But it works. {^_-}
#############################################################################

:0
* ^From: .*\@<CUSTOMER'S>\.com
{
   :0 ic
   | play /usr/share/sounds/KDE_Startup.wav -v 1.0

   :0 fw
   | formail -i "Reply-to: addr1@<CUSTOMER'S>.com, addr2@aol.com"
}

##############################################################################
# Rewrite Reply-To: for SpamAssassin user list
##############################################################################

:0 fw
* ^List-Id: .*(users\@spamassassin\.apache\.org|users\.spamassassin\.apache\.org)
| formail -A "$PROCMAILMATCH SpamAssassin user list" -i "Reply-to: 
users@spamassassin.apache.org"

##############################################################################
# run spamassassin on things not from the spamassassin list
##############################################################################

:0
* < 500000
* !^List-Id: .*(spamassassin\.apache.\org)
{
   :0 fw: spamassassin.lock
   | /usr/bin/spamc -t 150 -u jdow
}

# Diagnostic tag used to trace spamassassin not working
#:0 fw
| formail -A "X-Jdow: user $LOGNAME"

# And here we go looking for a broken spamc above.
:0 fw
* !^X-Spam-Checker-Version:
* < 500000
* !^List-Id: .*(spamassassin\.apache.\org)
{
   :0 fw
   | nice -n 1 /usr/bin/spamassassin

   :0 fw
   | Formail -A "X-JdowMissed: SpamAssassin checks bombed first time."

#   :0 fw
#   | sed -e 's/Subject:/Subject: [ZZ Missed]/'

#   :0c: clone1.lock
#   $HOME/mail/sa_failed
}

# Phew - Done!
===8<--- (There's more I edited out. But this gives a hint of what I did.

> Now, it looks as if I should make /etc/procmail/procmailrc be owned by
> gene:gene, and that I should set kmail to pipe the mail, using
>
> procmail -pm /etc/procmail/procmailrc
>
> from the man pages, but I'm not sure what other arguments might be
> needed.  I've copied your recipe into /etc/procmail/procmailrc
> and /etc/procmail/* is owned by gene:gene.

I found I did not like the way global procmailrc acted. Now, with a
better understanding than what I had "back then" a global one might
work. But for two users I'm not motivated to change.

{^_^} 



Re: X-Spam Status

Posted by Gene Heskett <ge...@verizon.net>.
On Sunday 22 January 2006 04:15, jdow wrote:
>From: "Gene Heskett" <ge...@verizon.net>
[...]
>>>> One facility that kmail seems to be missing, is the ability to
>>>> send such crap to /dev/null, all I get are error messages when
>>>> thats attempted.
>>>
>>>I don't remember if you use procmail or not.
>>
>> No, I'm using fetchmail.  But is there a way to pipe fetchmails
>> output thru a prefilter such as procmail?  Yeah, I know, man
>> procmail to the rescue....  Looks doable, but when I have both eyes
>> open simultainously I think.  Right now its only one.  Getting
>> sleepy out and all that.
>>
>>>This is from my
>>> .procmailrc recipe set:
>>># Uncomment either /dev/null or /$HOME/mail/uol_crap, your choice.
>>># Modify the latter as appropriate for your userlevel mail storage
>>>
>>>:0:
>>>
>>>* ^From: AntiSpam UOL <.*...@uol.com.br>
>>>#/dev/null
>>>/$HOME/mail/uol_crap
>>>
>>>
>>>{^_-}
>
>That's right. You're using KMail to run fetchmail so you're helpless.

No I'm not, Joanne!  Fetchmail is run from rc.local and delivers the 
mail from vz and gmail to /var/spool/mail/gene on a 10 minute repeating 
loop.  Kmail, then, completely asynchronously but on the same basic 10 
minute repeat timing, grabs the contents of that file and sorts it into 
its various folders after pipeing _some_ of the mail through SA.  This 
list for obvious reasons is picked off first and never see's an SA 
inspection.  There are several other fairly clean lists that get picked 
off before the SA inspection.  Unforch for the SA workload, lkml isn't 
one of them as most of the servers at vger seem to be fairly wide open 
& take even blank mails from spammers just clearing the barrels for the 
next barrage.

Now, it looks as if I should make /etc/procmail/procmailrc be owned by 
gene:gene, and that I should set kmail to pipe the mail, using 

procmail -pm /etc/procmail/procmailrc

from the man pages, but I'm not sure what other arguments might be 
needed.  I've copied your recipe into /etc/procmail/procmailrc 
and /etc/procmail/* is owned by gene:gene.

So I think the next step is to add the filtering rule to kmail and fire 
a message off to the fedora list for effect, which will generate 
testing mails aplenty.

>Good luck, Kemo Sabe!
>
>{^_-}

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: X-Spam Status

Posted by jdow <jd...@earthlink.net>.
From: "Gene Heskett" <ge...@verizon.net>

> On Sunday 22 January 2006 00:31, jdow wrote:
>>From: "Gene Heskett" <ge...@verizon.net>
>>
>>> On Saturday 21 January 2006 22:06, Theo Van Dinter wrote:
>>>>On Sat, Jan 21, 2006 at 09:44:54PM -0500, Gene Heskett wrote:
>>>>> Ok, I just set that up in kmail, triggered by <any header> 'does
>>>>> not contain' "X-Spam-Status"
>>>>
>>>>It's worth noting that you're likely to cause a mail loop on your
>>>> machine. If the header doesn't exist after passing through SA the
>>>> first time, the header will likely not be added by passing it
>>>> through again.
>>>
>>> Its been running about an hour now without doing so.  And I don't
>>> see how it could since the filter rules are processed in the list
>>> order shown by kmail.  So there is no way for it to loop that I can
>>> see.
>>>
>>> My instant problem is a veritable flood of about 3 bounces from the
>>> *(&^$^%$()_)(!! uol.com.br for every message I post to the fedora
>>> list.
>>>
>>> What that isp, and no I won't dignify it by uppercaseing it,
>>> seriously needs is the 20 lbs of 50+ year old nitro I found laying
>>> in an abandoned mine site about 20 years ago, applied right in the
>>> center of the net rack room.  Unforch, its a very long drive to
>>> deliver it.
>>>
>>> One facility that kmail seems to be missing, is the ability to send
>>> such crap to /dev/null, all I get are error messages when thats
>>> attempted.
>>
>>I don't remember if you use procmail or not.
> 
> No, I'm using fetchmail.  But is there a way to pipe fetchmails output 
> thru a prefilter such as procmail?  Yeah, I know, man procmail to the 
> rescue....  Looks doable, but when I have both eyes open simultainously 
> I think.  Right now its only one.  Getting sleepy out and all that.
> 
>>This is from my 
>> .procmailrc recipe set:
>># Uncomment either /dev/null or /$HOME/mail/uol_crap, your choice.
>># Modify the latter as appropriate for your userlevel mail storage
>>
>>:0:
>>
>>* ^From: AntiSpam UOL <.*...@uol.com.br>
>>#/dev/null
>>/$HOME/mail/uol_crap
>>
>>
>>{^_-}

That's right. You're using KMail to run fetchmail so you're helpless.
Good luck, Kemo Sabe!

{^_-}


Re: X-Spam Status

Posted by Gene Heskett <ge...@verizon.net>.
On Sunday 22 January 2006 00:31, jdow wrote:
>From: "Gene Heskett" <ge...@verizon.net>
>
>> On Saturday 21 January 2006 22:06, Theo Van Dinter wrote:
>>>On Sat, Jan 21, 2006 at 09:44:54PM -0500, Gene Heskett wrote:
>>>> Ok, I just set that up in kmail, triggered by <any header> 'does
>>>> not contain' "X-Spam-Status"
>>>
>>>It's worth noting that you're likely to cause a mail loop on your
>>> machine. If the header doesn't exist after passing through SA the
>>> first time, the header will likely not be added by passing it
>>> through again.
>>
>> Its been running about an hour now without doing so.  And I don't
>> see how it could since the filter rules are processed in the list
>> order shown by kmail.  So there is no way for it to loop that I can
>> see.
>>
>> My instant problem is a veritable flood of about 3 bounces from the
>> *(&^$^%$()_)(!! uol.com.br for every message I post to the fedora
>> list.
>>
>> What that isp, and no I won't dignify it by uppercaseing it,
>> seriously needs is the 20 lbs of 50+ year old nitro I found laying
>> in an abandoned mine site about 20 years ago, applied right in the
>> center of the net rack room.  Unforch, its a very long drive to
>> deliver it.
>>
>> One facility that kmail seems to be missing, is the ability to send
>> such crap to /dev/null, all I get are error messages when thats
>> attempted.
>
>I don't remember if you use procmail or not.

No, I'm using fetchmail.  But is there a way to pipe fetchmails output 
thru a prefilter such as procmail?  Yeah, I know, man procmail to the 
rescue....  Looks doable, but when I have both eyes open simultainously 
I think.  Right now its only one.  Getting sleepy out and all that.

>This is from my 
> .procmailrc recipe set:
># Uncomment either /dev/null or /$HOME/mail/uol_crap, your choice.
># Modify the latter as appropriate for your userlevel mail storage
>
>:0:
>
>* ^From: AntiSpam UOL <.*...@uol.com.br>
>#/dev/null
>/$HOME/mail/uol_crap
>
>
>{^_-}

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: X-Spam Status

Posted by jdow <jd...@earthlink.net>.
From: "Gene Heskett" <ge...@verizon.net>

> On Saturday 21 January 2006 22:06, Theo Van Dinter wrote:
>>On Sat, Jan 21, 2006 at 09:44:54PM -0500, Gene Heskett wrote:
>>> Ok, I just set that up in kmail, triggered by <any header> 'does not
>>> contain' "X-Spam-Status"
>>
>>It's worth noting that you're likely to cause a mail loop on your
>> machine. If the header doesn't exist after passing through SA the
>> first time, the header will likely not be added by passing it through
>> again.
> 
> Its been running about an hour now without doing so.  And I don't see 
> how it could since the filter rules are processed in the list order 
> shown by kmail.  So there is no way for it to loop that I can see.
> 
> My instant problem is a veritable flood of about 3 bounces from the 
> *(&^$^%$()_)(!! uol.com.br for every message I post to the fedora list.
> 
> What that isp, and no I won't dignify it by uppercaseing it, seriously 
> needs is the 20 lbs of 50+ year old nitro I found laying in an 
> abandoned mine site about 20 years ago, applied right in the center of 
> the net rack room.  Unforch, its a very long drive to deliver it.
> 
> One facility that kmail seems to be missing, is the ability to send such 
> crap to /dev/null, all I get are error messages when thats attempted.

I don't remember if you use procmail or not. This is from my .procmailrc
recipe set:
# Uncomment either /dev/null or /$HOME/mail/uol_crap, your choice.
# Modify the latter as appropriate for your userlevel mail storage
:0:
* ^From: AntiSpam UOL <.*...@uol.com.br>
#/dev/null
/$HOME/mail/uol_crap


{^_-}


Re: X-Spam Status

Posted by Gene Heskett <ge...@verizon.net>.
On Saturday 21 January 2006 22:06, Theo Van Dinter wrote:
>On Sat, Jan 21, 2006 at 09:44:54PM -0500, Gene Heskett wrote:
>> Ok, I just set that up in kmail, triggered by <any header> 'does not
>> contain' "X-Spam-Status"
>
>It's worth noting that you're likely to cause a mail loop on your
> machine. If the header doesn't exist after passing through SA the
> first time, the header will likely not be added by passing it through
> again.

Its been running about an hour now without doing so.  And I don't see 
how it could since the filter rules are processed in the list order 
shown by kmail.  So there is no way for it to loop that I can see.

My instant problem is a veritable flood of about 3 bounces from the 
*(&^$^%$()_)(!! uol.com.br for every message I post to the fedora list.

What that isp, and no I won't dignify it by uppercaseing it, seriously 
needs is the 20 lbs of 50+ year old nitro I found laying in an 
abandoned mine site about 20 years ago, applied right in the center of 
the net rack room.  Unforch, its a very long drive to deliver it.

One facility that kmail seems to be missing, is the ability to send such 
crap to /dev/null, all I get are error messages when thats attempted.

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: X-Spam Status

Posted by Loren Wilton <lw...@earthlink.net>.
How is SA being called?

Some of the integration tools do not use SA headers at all, they install
their own.

Others will only install the SA headers if the mail is classified as spam,
and leave the pristine message if for whatever reason it wasn't classified
as spam (thus making it impossible to see what rules hit and make
adjustments!)

        Loren


Re: X-Spam Status

Posted by jdow <jd...@earthlink.net>.
From: "Theo Van Dinter" <fe...@apache.org>

On Sat, Jan 21, 2006 at 09:44:54PM -0500, Gene Heskett wrote:
> Ok, I just set that up in kmail, triggered by <any header> 'does not 
> contain' "X-Spam-Status"

It's worth noting that you're likely to cause a mail loop on your machine.
If the header doesn't exist after passing through SA the first time,
the header will likely not be added by passing it through again.

<<jdow>> Most emphatically not so if the reason the markup is missing
is the PerMsgStatus.pm bug in the evalstr's. That is a big if, however.

{^_^}



Re: X-Spam Status

Posted by Theo Van Dinter <fe...@apache.org>.
On Sat, Jan 21, 2006 at 09:44:54PM -0500, Gene Heskett wrote:
> Ok, I just set that up in kmail, triggered by <any header> 'does not 
> contain' "X-Spam-Status"

It's worth noting that you're likely to cause a mail loop on your machine.
If the header doesn't exist after passing through SA the first time,
the header will likely not be added by passing it through again.

-- 
Randomly Generated Tagline:
The only time a dog gets complimented is when he doesn't do anything.
 		-- C. Schulz

Re: X-Spam Status

Posted by Gene Heskett <ge...@verizon.net>.
On Saturday 21 January 2006 20:42, jdow wrote:
>From: "Gene Heskett" <ge...@verizon.net>
[...]
>> An interesting thought just came to mind, Joanne.  Could one check
>> for the header added, and if not present, just repeat the scan by
>> pipeing it thru spamc again?  What you say would tend to show that
>> lightning doesn't strike twice.  I know better, and so do you, but
>> this isn't lightning were discussing here. :)
>
>Yes. That's what I just said.
>{^_^}

Ok, I just set that up in kmail, triggered by <any header> 'does not 
contain' "X-Spam-Status"

Now we fire for effect...

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: X-Spam Status

Posted by jdow <jd...@earthlink.net>.
From: "Gene Heskett" <ge...@verizon.net>
> On Saturday 21 January 2006 18:40, jdow wrote:
>>From: "Spam Ass" <as...@gmail.com>
>>
>>On 1/21/06, Robb <ro...@unrealstyle.com> wrote:
>>>   So does SA mark EVERY email with the:
>>> X-Spam-Status: Yes/No  header?
>>
>>The only time I have run into an email not being tagged is when the
>> email was over a certain size.  I believe the default max size is
>> 256kb.  This can be changed on a per user or global basis though.
>>
>>Ian
>>
>><<jdow>> There are certain settings for SpamAssassin which can cause
>>this, unfortunately. The prevailing wisdom is that it's a perl bug
>>that hits randomly. If you see this bug you will see both ham and spam
>>that failed to acquire a markup.
>>
>>The triggering method is to allow per user rules in addition to
>> scores. Then have a rawbody rule. (There are two or three other types
>> which lead to the "evalstr" error.) What you will find is that there
>> is an PerMsgStatus.pm error logged and no SpamAssassin markup at all
>> on the message. It also seems to be dependant on a small timing
>> window with two concurrent scans.
>>
>>I use procmail. So I can run SpamAssassin, look to see that the markup
>>is present or not, and if it is not present run it through again. I've
>>never seen the bug hit twice in a row. As it happens the normal scan
>>takes place with spamc. If that fails I use spamassassin raw.
>>
>>{^_^}
> 
> An interesting thought just came to mind, Joanne.  Could one check for 
> the header added, and if not present, just repeat the scan by pipeing 
> it thru spamc again?  What you say would tend to show that lightning 
> doesn't strike twice.  I know better, and so do you, but this isn't 
> lightning were discussing here. :)

Yes. That's what I just said.
{^_^}


Re: X-Spam Status

Posted by Gene Heskett <ge...@verizon.net>.
On Saturday 21 January 2006 18:40, jdow wrote:
>From: "Spam Ass" <as...@gmail.com>
>
>On 1/21/06, Robb <ro...@unrealstyle.com> wrote:
>>   So does SA mark EVERY email with the:
>> X-Spam-Status: Yes/No  header?
>
>The only time I have run into an email not being tagged is when the
> email was over a certain size.  I believe the default max size is
> 256kb.  This can be changed on a per user or global basis though.
>
>Ian
>
><<jdow>> There are certain settings for SpamAssassin which can cause
>this, unfortunately. The prevailing wisdom is that it's a perl bug
>that hits randomly. If you see this bug you will see both ham and spam
>that failed to acquire a markup.
>
>The triggering method is to allow per user rules in addition to
> scores. Then have a rawbody rule. (There are two or three other types
> which lead to the "evalstr" error.) What you will find is that there
> is an PerMsgStatus.pm error logged and no SpamAssassin markup at all
> on the message. It also seems to be dependant on a small timing
> window with two concurrent scans.
>
>I use procmail. So I can run SpamAssassin, look to see that the markup
>is present or not, and if it is not present run it through again. I've
>never seen the bug hit twice in a row. As it happens the normal scan
>takes place with spamc. If that fails I use spamassassin raw.
>
>{^_^}

An interesting thought just came to mind, Joanne.  Could one check for 
the header added, and if not present, just repeat the scan by pipeing 
it thru spamc again?  What you say would tend to show that lightning 
doesn't strike twice.  I know better, and so do you, but this isn't 
lightning were discussing here. :)

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: X-Spam Status

Posted by jdow <jd...@earthlink.net>.
From: "Spam Ass" <as...@gmail.com>

On 1/21/06, Robb <ro...@unrealstyle.com> wrote:
>
>   So does SA mark EVERY email with the:
> X-Spam-Status: Yes/No  header?
>

The only time I have run into an email not being tagged is when the email
was over a certain size.  I believe the default max size is 256kb.  This can
be changed on a per user or global basis though.

Ian

<<jdow>> There are certain settings for SpamAssassin which can cause
this, unfortunately. The prevailing wisdom is that it's a perl bug
that hits randomly. If you see this bug you will see both ham and spam
that failed to acquire a markup.

The triggering method is to allow per user rules in addition to scores.
Then have a rawbody rule. (There are two or three other types which lead
to the "evalstr" error.) What you will find is that there is an
PerMsgStatus.pm error logged and no SpamAssassin markup at all on the
message. It also seems to be dependant on a small timing window with
two concurrent scans.

I use procmail. So I can run SpamAssassin, look to see that the markup
is present or not, and if it is not present run it through again. I've
never seen the bug hit twice in a row. As it happens the normal scan
takes place with spamc. If that fails I use spamassassin raw.

{^_^}


Re: X-Spam Status

Posted by Spam Ass <as...@gmail.com>.
On 1/21/06, Robb <ro...@unrealstyle.com> wrote:
>
>   So does SA mark EVERY email with the:
> X-Spam-Status: Yes/No  header?
>

The only time I have run into an email not being tagged is when the email
was over a certain size.  I believe the default max size is 256kb.  This can
be changed on a per user or global basis though.

Ian