Re: Did the whitelist_from_rcvd semantics change?
> On Apr 28, 2023, at 12:17 PM, Philip Prindeville
> wrote:
>
>
>
>> On Apr 28, 2023, at 10:24 AM, Reindl Harald wrote:
>>
>>
>>
>> Am 28.04.23 um 18:11 schrieb Philip Prindeville:
On Apr 25, 2023, at 6:28 AM, Bill Cole
wrote:
On 2023-04-24 at 16:32:55 UTC-0400 (Mon, 24 Apr 2023 14:32:55 -0600)
Philip Prindeville
is rumored to have said:
> I thought the matching included subdomains, and seem to remember that
> working.
It never has. At least not in the past 17 years.
>>> Then how do pools of servers like *.protection.outbound.outlook.com get
>>> handled?
>>
>> as * is always handeled at globbing
>>
>> *.example.com
>> *@example.com
>
>
> Maybe I'm missing something, but the code brackets ${domain} with \Q and \E
> so globbing wouldn't work.
>
> if ($rdns =~ /(?:^|\.)\Q${domain}\E$/i) { $match=1; last }
>
But it *is* anchored on the left hand side by either beginning of line *or* dot.
-Philip
Re: parameters: use_pyzor and use_razor2
On Sun, Apr 30, 2023 at 01:19:53PM +0300, Henrik K wrote: > > Looking at the code, not sure if the is_admin attributes are correct in all > the plugins or not, maybe someone can check if they actually work properly > per-user and fix for 4.0.1. Committed fixes for a bunch of modules, now use_dcc/pyzor/razor2 is allowed for users amongst other things. Download new trunk or wait for 4.0.1.
Re: parameters: use_pyzor and use_razor2
On Sun, Apr 30, 2023 at 10:36:07AM +0200, i...@servermx.com wrote: > thanks John Hardin and Henrik K, > The parameters "use_pyzor" and "use_razor2"think are correct - > https://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.html > I think > > I would like to keep "use_pyzor" and "use_razor2" parameters working per > user-based. I told you, it does not work this way in 4.0. If you want to disable a rule, then use "score RAZOR2_CHECK 0" etc to disable specific rules per user. Looking at the code, not sure if the is_admin attributes are correct in all the plugins or not, maybe someone can check if they actually work properly per-user and fix for 4.0.1.
Re: parameters: use_pyzor and use_razor2
thanks John Hardin and Henrik K, The parameters "use_pyzor" and "use_razor2"think are correct - https://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.html I think I would like to keep "use_pyzor" and "use_razor2" parameters working per user-based. I noticed that putting the values preference = use_pyzor value = 0 preference = use_razor2 value = 0 Spamassassin reads those values. I can see the values on the log use_pyzor\t0 use_razor2\t0 the values is after the "t". (I performed a test putting value=1 and I see use_pyzor\t1 on the log) On 2023-04-30 09:33, Henrik K wrote: On Sat, Apr 29, 2023 at 12:42:43PM +0200, i...@servermx.com wrote: Hello, we have installed Spamassassin (debian 11.6) vesion 4.0 from source. With backend MariaDB 10.5.18-MariaDB-0+deb11u1 - Debian 11. Spamassassin is raising these messages info: config: not parsing, administrator setting: use_pyzor\t0 info: config: failed to parse line in (sql config) (line 9): use_pyzor\t0 info: config: not parsing, administrator setting: use_razor2\t0 info: config: failed to parse line in (sql config) (line 10): use_razor2\t0 Nevertheless, in the execution phase Spamassasin performs RAZOR2 check, here below an excerpt of out log file. at Apr 29 11:11:35 2023 [1768541] info: spamd: result: Y 899 - DMARC_QUAR,FSL_BULK_SIG,GTUBE,NO_RELAYS,PP_MIME_FAKE_ASCII_TEXT,RAZOR2_CF_RANGE_51_100,RAZOR2_CHECK,THIS_AD,TXREP,USER_IN_WELCOMELIST,USER_IN_WHITELIST scantime=10.7,size=29004,use We do not get these messages when we use the old version 3.4.6. Are these parameters still valid or are they deprecated? or what else? In 4.0 they are administrator (site-wide) setting only, 3.4 incorrectly did not have that restriction. To disable rules per-user, set the rule scores to 0 in sql. If you want to disable the plugins completely, then do not load them at all or use the settings in local.cf (can't remember right now if SQL supports site-wide/admin settings). -- with kind regards the servermx.com Team __ Coranto informatica Via Torricelli, 9 09047 Selargius (CA) - Italy Phone & Fax: +39 070 8607521 i...@servermx.com www.servermx.com PGP public key: https://www.servermx.com/en/utility/pgp __ Confidentiality statement: all information included in this communication is intended solely for delivery to authorized use by the addressee identified above. If you are not the intended recipient, please note that any use, distribution or copying of this communication is unauthorized and may be unlawful. If you have received this communication in error, please notify the sender immediately and delete this communication from your computer.
Re: parameters: use_pyzor and use_razor2
On Sat, Apr 29, 2023 at 12:42:43PM +0200, i...@servermx.com wrote: > Hello, > > we have installed Spamassassin (debian 11.6) vesion 4.0 from source. > With backend MariaDB 10.5.18-MariaDB-0+deb11u1 - Debian 11. > > Spamassassin is raising these messages > > info: config: not parsing, administrator setting: use_pyzor\t0 > info: config: failed to parse line in (sql config) (line 9): use_pyzor\t0 > info: config: not parsing, administrator setting: use_razor2\t0 > info: config: failed to parse line in (sql config) (line 10): use_razor2\t0 > > Nevertheless, in the execution phase Spamassasin performs RAZOR2 check, > here below an excerpt of out log file. > > at Apr 29 11:11:35 2023 [1768541] info: spamd: result: Y 899 - > DMARC_QUAR,FSL_BULK_SIG,GTUBE,NO_RELAYS,PP_MIME_FAKE_ASCII_TEXT,RAZOR2_CF_RANGE_51_100,RAZOR2_CHECK,THIS_AD,TXREP,USER_IN_WELCOMELIST,USER_IN_WHITELIST > scantime=10.7,size=29004,use > > We do not get these messages when we use the old version 3.4.6. > > Are these parameters still valid or are they deprecated? or what else? In 4.0 they are administrator (site-wide) setting only, 3.4 incorrectly did not have that restriction. To disable rules per-user, set the rule scores to 0 in sql. If you want to disable the plugins completely, then do not load them at all or use the settings in local.cf (can't remember right now if SQL supports site-wide/admin settings).
