On 7/28/2023 1:49 AM, Ken D'Ambrosio wrote:
On 7/27/2023 12:08 PM, Ken D'Ambrosio wrote:
Hey, all. I've recently started getting spam that's really hard to
deal with, and I'm open to suggestions as to how to approach it.
Superficially,
Sweet! The assistance of those who actually felt like assisting,
instead of simply critiquing, is much appreciated. I see some
assumptions I made were wrong (e.g., decoding apparently isn't a
problem), and I'm guessing it is probably something stupid like
Unicode. I'll also make sure I match those other rules; my rules
file, I now realize, is ancient, and likely badly needs to be made
more current.
Bill and Dave are correct. It does NOT make a difference on the glue.
Using your sample data as is,
Content-Type: multipart/alternative;
boundary=--boundary_1294650_c95a1e92-a32e-44c3-b4a8-21415b9755c6
----boundary_1294650_c95a1e92-a32e-44c3-b4a8-21415b9755c6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
bW5HUlpJcm1Nd3Z1ZnNRZFJSSuWIkU5saOmjhDEzMi0xNTMyLTEzMzQ=
it works fine and hits your regex. I tested this with SA v3.4.6, PERL
5.26.1. Maybe check for the presence of the MIME::Base64 module and
Unicode::UTF8 modules (something like "instmodsh" option "l").
Just another great mystery; like Bigfoot, Pyramids, UFOs, Crop Circles,
Plains of Nazca, and Microsoft Fax Server.
-- Jared Hall
