On 8/15/2012 6:08 PM, John Evans wrote:
I added the patch and it hung in the same place. The 'spamassassin -D
-t < bad' command eventually went through after a LONG timeout. I
didn't capture the results of the SA command (forgot to redirect
output), but the patch to substr(X, 0, 30000) didn't seem to help any.
Could be that 30,000 is too long? That delves deep into the
attachment, and I'm wondering if the top-end of the attachment (within
that 30k range) has content that triggers a regex that doesn't like
what it sees?
Just throwing some ideas out there.
Thoughts?
Henrik wrote the patch which I have not reviewed (or don't remember
reviewing) but as noted, we are flying a bit blind. We are guessing the
issue is a wrong MIME type in the container of the email.
I could argue such a malformed message is a danger to any system and you
should use glue to discard the message.
But without seeing the message, I really can't expend much time on this
shotgun approach.
I recommend you ask the sender if it's ok to send the email to
priv...@spamassassin.apache.org so at least the PMC members can look at it.
Regards,
KAM
