https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7995
--- Comment #13 from Riccardo Alfieri <riccardo.alfi...@spamteq.com> --- (In reply to Henrik Krohns from comment #12) > > You can't be sure that everyone uses the same normalization code or newest > version of the code. So in my mind it's far more elegant to just support all > possible variants on the list side. Even original addresses without dots > removed etc. That is exactly what we are doing by normalizing addresses and shipping a plugin that normalize the query on the lookup side. You can't really expect that for each gmail.com address we list we also create hashes for every possible variation of that same address :) The final goal is to list bad addresses. Since we know that gmail strips all the dots and it has also the domain googlemail.com aliased, the hashes for gmail addresses are created *after* the normalization. We do store the "original" address that triggered the listing along with other data but only for intel purposes. And I can assure you that we have *plenty* of examples of spammers trying to game filters by adding random dots and changing the domain for their dropboxes. I think it's SpamAssassin that needs to take care of these edge cases, not list mantainers. And just to be clear, this is not a criticism but only a constructive suggestion from a list mantainer. We love SpamAssassin and would love for it to work in the most efficient way with our data. In the end you already have "nodot" and "notag" options, adding another option for aliased domain would probably render SA 4.x more "future proof". And if this is not a feature that will be included in 4.x then we'll need to write another plugin, or ship a dedicated HashBL.pm but this is a suboptimal solution that many people will have some difficulties implementing, resulting in more spam reaching the recipient (that is what we all are trying to avoid) > > If I have time, I'll think about it. If I had the necessary coding abilities I would help you, but unfortunately my coding style is vastly inferior compared to yours :( -- You are receiving this mail because: You are the assignee for the bug.
