I just finished installing 3.0.1 over a two-years old 2.42 installation
on a Sun (don't know which model, sorry) with 0.5 GB ram and 1.2 GB swap
serving less than 1000 users with smtp and pop services, about 15000
local deliveries per working day.
Undesired mail jumped from an average 1% of two ye
>If you would like that to be an official part of the future SA releases, you
>should open a bugzilla ticket and attach a *.cf file with that rule in it.
Thanks for the tip, I just did it (but I put the translation in the
message body).
>> full __h_exename_q
>> /\bname=("?).+?\.(?:bas|bat|cmd|com|cpl|exe|js|jse|msi|mst|pcd|pif|reg|scr|sct|vb|vbe|vbs|wsc|wsf|wsh|xsl)\1[[:blank:]]*(?:;|$)/mi
>> rawbody __b_exename_q
>> /\bname=("?).+?\.(?:bas|bat|cmd|com|cpl|exe|js|jse|msi|mst|pcd|pif|reg|scr|sct|vb|vbe|vbs|
full __h_exename_q
/\bname=("?).+?\.(?:bas|bat|cmd|com|cpl|exe|js|jse|msi|mst|pcd|pif|reg|scr|sct|vb|vbe|vbs|wsc|wsf|wsh|xsl)\1[[:blank:]]*(?:;|$)/mi
rawbody __b_exename_q
/\bname=("?).+?\.(?:bas|bat|cmd|com|cpl|exe|js|jse|msi|mst|pcd|pif|reg|scr|sct|vb|vbe|vbs|wsc|wsf|wsh|
clear_unsafe_report_template
unsafe_report * ATTENZIONE: il messaggio originale non รจ testo puro, e
unsafe_report * potrebbe essere pericoloso da aprire con alcuni programmi di
unsafe_report * posta. Ad esempio, potrebbe contenere un virus, o confermare
unsafe_report * ad un mittente di spam che
header spammer_from From =~ /%FROM_USER@/
describe spammer_from Ignorant spammer: variables in From:
scorespammer_from 5.0
header spammer_messageid Message-Id =~ /%MESSAGEID@|RND_LC_CHAR/
describe spammer_messageid Ignorant spammer: variables in Mess
Works on Sun. Timeout is lower with greater load average.
TIMEOUT=250 ## don't wait too long for children
SHELL=/usr/local/bin/bash ## it was set to the user's shell
EX_TEMPFAIL=75 # temporary failure: requeue
SPAMC=/usr/local/bin/spamc
SOCKETPATH=/var/
