https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7995
--- Comment #16 from Henrik Krohns <apa...@hege.li> --- (In reply to Riccardo Alfieri from comment #15) > Well, two things. One is that we operate on scale, and distributing lists to > hundreds of mirrors in real time is a bandwidth and time consuming process. > If we can shed a few seconds here and there by keeping the lists as > optimized as possible this is what we are going to do. Second, let's say we > observe a dropbox like "u...@gmail.com" , we would need to store hashes for: > > u.s....@gmail.com > us....@gmail.com > u.s...@gmail.com > us...@gmail.com > u.s...@gmail.com > us...@gmail.com > u....@gmail.com > u...@gmail.com > > and then do the same for @googlemail.com > > As you can see this approach doesn't scale Obviously I was not suggesting that it would be feasible to start randomly "dotting" around. All implementations already can remove the dot. The issue was missing domain alias for HashBL, which could easily be handled on the list side. But as it's rspamd feature too, let's try to get it implemented the same. Just need a short moment to think if it would be an email only option, or maybe even a generic rewrite for any kind of found string. -- You are receiving this mail because: You are the assignee for the bug.
