http://bugzilla.spamassassin.org/show_bug.cgi?id=3277
------- Additional Comments From blacksir@number.ru 2004-06-21 07:58 -------
Hi all again! After two month I've catch subject bug several times and today
I've unable to save message body that crashes spamd. But unfortunatly after
testing this message on 3 of our servers I've found that it crashes only on 2
of them, while all software configuration is the same. On the server where no
crash spamd eats about 75Mb additional RAM according to vmstat while checking
this 1.5Mb message. On the other 2 servers spamd eats >300Mb in first 10
seconds and countinue before I'll kill -9 it. I've put archived message body to
http://number.ru/blacksir/spamd-chash-email.tar.gz (~1.2Mb)
Some notes about my servers:
#uname -a
FreeBSD inet.vnii.number.ru 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Thu May 13
14:27:58 MSD 2004
root@inet.vnii.number.ru:/usr/obj/usr/src/sys/number_ru_20040303 i386
#perl -v
--cut--
This is perl, version 5.005_03 built for i386-freebsd
--cut--
#spamassassin -V
SpamAssassin version 2.63
P.S. Actually I've already found some workaround - do not permit exim check
messages bigger than, for example, 256Kb. It can be done by putting those to
lines in EXIM `configure` file in acl_check_content section before spamcheck
lines but after mime-errs/virus-checking and etc...
accept hosts = 127.0.0.1:+relay_from_hosts # Do not
check mail from trusted relays
accept condition = ${if >{$message_size}{256k}{1}{0}} # Do not
check mail if bigger than 256Kb
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Additional Comments From blacksir@number.ru 2004-06-21 07:58 -------
Hi all again! After two month I've catch subject bug several times and today
I've unable to save message body that crashes spamd. But unfortunatly after
testing this message on 3 of our servers I've found that it crashes only on 2
of them, while all software configuration is the same. On the server where no
crash spamd eats about 75Mb additional RAM according to vmstat while checking
this 1.5Mb message. On the other 2 servers spamd eats >300Mb in first 10
seconds and countinue before I'll kill -9 it. I've put archived message body to
http://number.ru/blacksir/spamd-chash-email.tar.gz (~1.2Mb)
Some notes about my servers:
#uname -a
FreeBSD inet.vnii.number.ru 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Thu May 13
14:27:58 MSD 2004
root@inet.vnii.number.ru:/usr/obj/usr/src/sys/number_ru_20040303 i386
#perl -v
--cut--
This is perl, version 5.005_03 built for i386-freebsd
--cut--
#spamassassin -V
SpamAssassin version 2.63
P.S. Actually I've already found some workaround - do not permit exim check
messages bigger than, for example, 256Kb. It can be done by putting those to
lines in EXIM `configure` file in acl_check_content section before spamcheck
lines but after mime-errs/virus-checking and etc...
accept hosts = 127.0.0.1:+relay_from_hosts # Do not
check mail from trusted relays
accept condition = ${if >{$message_size}{256k}{1}{0}} # Do not
check mail if bigger than 256Kb
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.