Re: My apologies
On 2023-08-02 15:49, Loren Wilton wrote: I've blocked him on my mail server, as well. I don't know that I'd block him, but you do need to take anything he says witha few horselicks of salt. I (who have almost nothing to contribute to Spamassassin itself, other than being a user) think he should be blocked. I've been online for over 40 years, and it's rare to have someone so actively hostile right out of the gate -- I admit, it made me worried what kind of environment was fostered on the Spamassassin list when I asked my newbie question, and was outright mocked by him. And so, while I have zero sway as a team member or anything like that, as a newbie mailing list member, looking for help, I humbly submit that he's not someone you want being the first interaction a new list member has. $.02, YMMV, etc. -Ken
Re: Really hard-to-filter spam
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, I'm not sure why the OP's rule didn't match the target message, but it is NOT because of the Base64 encoding of parts with the 'text' primary MIME type. If I had to guess, I'd look for invisible characters hidden in the text (e.g. Unicode "zero width non-joiner" marks and the like) that break the pattern and for lookalike non-ASCII characters (often Cyrillic or Greek) in the target string. 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. Much appreciated! -Ken
Solved: Re: Large messages not being scanned.
On 2015-08-06 11:53, RW wrote:
On Thu, 06 Aug 2015 11:38:56 -0400
Ken D'Ambrosio wrote:
Hi! I'm getting headers like this:
Aug 4 04:24:58 agrajag spamc[2557]: skipped message, greater than
max message size (512000 bytes)
Now, I'm just not sure where to *change* that; apparently, it's set
via the -s max_size for spamc, but I have no idea where/how that
gets invoked by spamd.
It doesn't, spamc passes the mail to spamd.
Ah; silly me, I'd assumed the daemon invoked the standalone.
You can set the argument in whatever glue calls spamc. or set it in
spamc.conf.
Right. Finding the glue was somewhat trickier, though. Finally
realized that it was postfix that was invoking spamc in the
/etc/postfix/master.cf file. My line now reads thusly:
root@agrajag:/etc/postfix# grep spamc master.cf
user=spamd argv=/usr/bin/spamc -s 1048576 -e /usr/sbin/sendmail
-oi -f ${sender} ${recipient}
Thanks for the pointers, all! Got me down the road...
Large messages not being scanned.
Hi! I'm getting headers like this: Aug 4 04:24:58 agrajag spamc[2557]: skipped message, greater than max message size (512000 bytes) Now, I'm just not sure where to *change* that; apparently, it's set via the -s max_size for spamc, but I have no idea where/how that gets invoked by spamd. Suggestions? Thanks! -Ken
