bugSpamAssassin Milter Plugin - Bugs: bug #11179, spamass-milter generates Could not...

 
 

bug #11179: spamass-milter generates Could not extract score from <>

Submitter:  None
Submitted:  Tue 30 Nov 2004 11:25:08 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 01 Aug 2020 06:50:11 PM UTC, comment #2: 

Confirmed still happening with 0.4.0

Greg Troxel <gdt>
Group Member
Sat 01 Aug 2020 04:40:26 PM UTC, comment #1: 

Doesn't seem to happen with 0.4.0.

Greg Troxel <gdt>
Group Member
Tue 30 Nov 2004 11:25:08 PM UTC, original submission:  

I'm running the latest CVS with SpamAssassin 3.0.1, not that it matters for this particular issue:

Unless you have spamc/spamd specifically configured to handle messages larger than 250k, then spamc won't hand off the message to spamd and consequently, SpamAssassin won't scan the message.

When spamass-milter tries to look for the appropriate SpamAssassin header, it will of course not be there and hence you see the following error:

spamass-milter: Could not extract score from <>

While you can configure spamc/spamd to have a higher tolerance for very large messages, in reality, messages of that size (with really big attachments usually) are almost certainly not spam and processing them would be a waste of resources.

spamass-milter should either silently ignore the lack of a SpamAssassin header and recognize that it hasn't been processed, or there should be some sort of command-line option to disable this message for this particular case.  I presume other people have run across this issue as well.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gdt (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-08-01 gdt Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code