Yesterday (at least that's when it was noticed), we started having timeout issues with SpamAssassin again. My average scan time went from 8.5 seconds last week and the week before to 20.5 seconds yesterday with many messages (primarily ham) running near the 120 second range. What happened in updates.spamassassin.org to cause this??
I'll see if I can run some tests to track down more specifically where things get stuck for so long, but at I thought the issue should at least be raised. (Maybe someone else has already seen and tracked it down?) Bret
smime.p7s
Description: S/MIME cryptographic signature
