Bug 5821 - Problem with The Bat cut messages
Summary: Problem with The Bat cut messages
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 3.1.0
Hardware: PC FreeBSD
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on: 5041
Blocks:
  Show dependency tree
 
Reported: 2008-02-11 04:41 UTC by Alexander
Modified: 2019-08-01 15:06 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2008-02-11 04:41:01 UTC 
I use spamassassin + axigen mail server. All is fine, but I noticed that  the 
error "Filtering process timed out" appears when the Bat cuts the letter with 
big attachments into the number of messages... In this case the recipient gets 
only the first part of the message... other parts stop in the queue with 
error "Fail-info: Filter SpamAssassin Filter:[ERROR]: Filtering process timed 
out Status:PROCESSING ERROR". I tested it a few times.

The Axigen Mail Support said: 
----
The processing timeout given by the spamassassin software cannot be
escaped unfortunately. It is caused by spamassassin while it waits for
the message to be formatted in a specific way, although it is not.

We have notified the spamassassin team about this matter, but until this
time, no solution has been provided. As such, messages such as the
logwatch cron message, will be stuck in the queue until dropped.

Please, tell me what to do.. is it a bug of spamassassin?

Thank you!
Alexander
Comment 1 Justin Mason 2008-02-11 07:14:23 UTC 
'We have notified the spamassassin team about this matter, but until this
time, no solution has been provided.'

I don't recall hearing from them.

The message formatting should not affect SA.  message size may do so, though,
which is why we request that large messages not be scanned.
Comment 2 Mark Martinec 2008-02-11 07:56:07 UTC 
> The message formatting should not affect SA.  message size may do so,
> though, which is why we request that large messages not be scanned.

See bug 5041.
Comment 3 Justin Mason 2008-02-12 01:47:40 UTC 
yeah, that does sound like bug 5041.

how big are the "cut" messages?  are they > 500KB in size?
Comment 4 Alexander 2008-02-13 02:52:50 UTC 
The "cut" messages > 500KB in size (1024KB).
Is there any way to say spamassassin not to check messages more than 512KB?
Any ideas how to solve this problem?
Comment 5 Justin Mason 2008-02-13 03:15:10 UTC 
(In reply to comment #4)
> The "cut" messages > 500KB in size (1024KB).
> Is there any way to say spamassassin not to check messages more than 512KB?
> Any ideas how to solve this problem?

If you are using spamc, the "-s" switch tells it the max size to scan.  It's
default is 500KB.  If you are using another tool to pass the message to
spamassassin, it varies depending on the tool.
Comment 6 Alexander 2008-02-13 06:35:42 UTC 
Thank you for the answer! I use Axigen Mail Server + 
SpamAssassin. How can I understand whether I use spamc or not? Where shall I 
the "-s" switch?

Thank you!
Comment 7 Henrik Krohns 2019-08-01 15:06:29 UTC 
Closing old stale bug. Nothing to fix here.