> Yesterday, we processed 2430 messages. > About 39% of those were identified as spam. > Out of that, about 50 were false positives.
2 questions:
A.) With "identified as spam" you mean they reached the hold value?
B.) With 2430 processed msgs you mean inbound + outbound?
In this case 39% is a very high value if you've not some spammers as
client that create outgoing spam.
My statement is based on the values of our actual report. (see attached
pdf ) We calculate the spam ratio only on incoming msgs because our 100%
smtp-auth-clients doesn't send spam. I think it's not possible to
indicate precise values that have general validity for every server.
This especially during the christmas/new year-days.
I would only say that the most of all messages - I hope always >50% -
will never reach the hold value because they aren't spam. I tought that
it is not too much work to implement this option. Scott already answered
that is not so. Both you and we doesn't need this option but for example
if the isp where I worked before (> 50000 msgs/day) want to implement an
antispam-module he will ask for it.
Another note:
2430 msgs/day
39% = 947 msgs hold msgs
50 fp's = around 5%
We've begun to record our fp's/day a week ago as you can see in the
report. There we're from 0 to 4 (=2,8%) fp's/day. Most of them caused by
SpamChk because our test criterias are in developement. Probably this
value will increase on both your and our side in the next days when
people returned from holidays begin to send real msgs.
I think it can be very dangerous for the helpdesk if the customers
understand that fp's "can occur". They will call to ask if there is a fp
even if there is something wrong on your system/internet access and he
can't retrieve any mail.
Markus
spam_report.PDF
Description: Adobe PDF document
