Last modified: 2013-01-06 01:16:38 UTC
There is an issue with the current anti spam tech, that is permitting a large amount og tickets in the form of spam to end up in the otrs system. There is a spam deluge.
Major loss (as selected) of function is detailed by the amount of volunteer work lost in translating a suspect ticket to ensure it is actually spam. This downgrades the effectiveness of the OTRS system.
Fixed.
This problem has been happening (again) for some time (years). It appears (by viewing the email headers) that (some) messages are still being assigned a spam score, but it does not appear anything happens beyond that. A lot of spam (even scored as "possible spam", etc., items are still being directed to the main queues rather than the junk folder. OTRS admins can set filters, which typically could divert any message with an X-Spam-Score higher than X value to the junk filter, but X-Spam-Score does not exist on our list of search options. We have X-Spam-Flag, X-Spam-Level and X-Spam-Status - none of these are even in the email headers.
This issue was fixed by a code commit five years ago. If the same problem (likely due to a different code problem) happens again it's better to file a new bug report (also to get attention) and describe the problem there (plus the summary of this bug report is pretty weak, see https://www.mediawiki.org/wiki/How_to_report_a_bug ). I'm closing this old ticket again - please file a new report. Thanks.
