https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5590
--- Comment #39 from Mark Martinec <[email protected]> 2010-01-18 10:06:49 UTC --- (In reply to comment #32) > I would imagine that treating the multi-byte characters as individual bytes > might bite us in ways similar to Bug 6183. (In reply to comment #31) > Does everyone agree that this is only isolated to small subsets of messages, > rather than affecting scan speed for all, or a majority of, messages? Yes, I believe this is the case. According to our timing stats charts, switching 'use bytes' on or off is hardly detectable on a plot (showing 5-minute average running times per message). The TIME_LIMIT_EXCEEDED rule (on a 40 second time limit) strikes about 5 times per day on a lightly loaded host (7k msgs/h), so at the expense of possibly passing through a potential spam due to reaching a time limit, it is acceptable as it stands now, at least for our site. > If this is the case, we should go ahead and cut 3.3.0 as it stands, and > leave this as a known issue for a 3.3.1 investigation/fix. Agreed. Putting the the 'use bytes' would conceptually be a step backwards. Advantage of having a message represented as perl characters instead of bytes can be put to good use in several corners. It is very unfortunate that Perl takes such a heavy hit on them. Until this gets targeted as a DoS hole, it need not be turned off. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
