On 12/23/20 2:15 PM, John Hardin wrote:
spamass-milter has a -u flag for a username to pass to SA. If these are single-recipient messages that may be enough to reliably tie into per-user config to disable the RBL check.
It seems as if spamass-milter is using the -u to specify a default user. It also seems as if spamass-milter will attempt to discover the (first) recipient if -x is also used. Spamass-milter will then use -u to pass the username default for first detected to spamc so that spamc can use personalized settings.
I am fairly sure that setting a rule score to zero bypasses the rule (vs. running it and ignoring the result) but you will probably want to test that to confirm whether the RBL is checked anyways. However, if the RBL check is written as a subrule then it can't be disabled this way as subrules don't have scores to set to zero.
ACK This matches my tests.
That last option sounds to me like the first one you should explore.
Thankfully, and to my surprise, SpamAssassin / spamass-milter /is/ attempting personalization.
"-u spamass-milter" was already in place.I added "-x" to cause spamass-milter to try to detect the first user, tweaked permissions (group membership) to allow spamass-milter to run sendmail -bv to detect some other users correctly, and now things seem to be working much closer to how I want.
Initial testing seems very promising use of heavily modified ~/.spamassassin/user_prefs.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
