Re: spamassassin 3.4.5 wide chars
Le 03/09/2021 à 19:16, Benny Pedersen a écrit : On 2021-09-03 18:12, John Wilcock wrote: FWIW, I see no warning with today's rules on SA 3.4.6 and perl 5.34 on gentoo. Benny, why don't you simply upgrade to 3.4.6? Sure, it hasn't yet been marked as stable by the gentoo maintainers, but it works perfectly. 3.4.6-r1 is masked unstable, so this is indeed fix perl 5.34 issue ? https://bugs.gentoo.org/807781 I've no idea what the origin of this issue is, just that it occurs for you with 3.4.5 and that it doesn't appear for me on 3.4.6. I trust spamassassin sufficiently to unmask it; I've no idea why the gentoo package maintainer thinks it isn't stable-worthy. -- John
Re: spamassassin 3.4.5 wide chars
FWIW, I see no warning with today's rules on SA 3.4.6 and perl 5.34 on gentoo. Benny, why don't you simply upgrade to 3.4.6? Sure, it hasn't yet been marked as stable by the gentoo maintainers, but it works perfectly. -- John Le 03/09/2021 à 16:37, Benny Pedersen a écrit : On 2021-08-12 04:03, Benny Pedersen wrote: https://bugs.gentoo.org/807781 is it solved in 3.4.6 ? reply to myself if its matters, rule sets from current sa-update today is now showing this wide charters warning step to reproduce in gentoo: sa-update sa-compile before sa-compile call re2c its shown 2 warning lines spamassassin version 3.4.5 perl version 5.34 from one of my friends with slackware 14.2 its not a problem with perl 5.22 slackware current have perl 5.34 aswell, but i dont use slackware :=) seems pmc members does not either spamassassin should be stable from perl 5.8 and upwards, but its not :/
Re: replacetag "" matches "g", "r", "o" and "0"?
So as to hit viggra, xonox and the like? If that is the intention, maybe a MISSPELT_DRUGS rule would be better suited, and avoid potential FPs on other replace_tag rules. Just my €0.02, FWIW! John Le 12/08/2020 à 21:48, John Hardin a écrit : Can anybody suggest a plausible reason for the replace tag to match the letters "g", "r" and "o" and the numeral zero? I'm trying to figure out why it's like this: replace_tag A (?:[gra…0o]|…) ...and has been that way since creation of the plugin.
Re: Extending the entries in 60_whitelist_spf.cf
My SA platform has very good results with thousands of whitelist_auth entries but 98% of the SA users are not going to know to create/manage these entries themselves. Combined with other rules this also helps with spoofing legit senders like the IRS, Bank of America, etc. I am not suggesting we put thousands of entries in the new 60_whitelist_auth.cf but the common, high-profile, large senders that often get spoofed. Make it dynamic? At dnswl.org we now also provide domain-based trust info (which should only be applied to properly authenticated domains, obviously). Can SA do this today (with a dnswl lookup metad with DKIM_VALID or similar)? Or would a new plugin be needed to do the job properly? -- John
Re: Call for Vote on 3.4.0-rc1
Le 19/06/2013 18:50, Kevin A. McGrail a écrit : Because of this change, if you use Bayes and you are upgrading from a version prior to 3.4.0, you should be consider wiping your database tokens and starting fresh. Nitpicking here: s/be consider/consider/ And possibly: s/database tokens/database/ -- John
Re: Spamd cannot listen to more than one IP address (or to v4/v6 at the same time)
[replying to dev@ to avoid bugspam] --- Comment #3 from Greg Troxelg...@ir.bbn.com --- I checked an apache server that listens on both v4 and v6 and the config file has Listen 0.0.0.0:80 Listen [::]:80 So I don't follow single bind. (I suspect that on systems that have v6only set to 0, listening on [::] will result in handling v4 connections as mapped addresses.) The documentation for apache's Listen directive is actually very helpful in explaining the situation with regard to IPv4-mapped IPv6 addresses and BSD's different default. http://httpd.apache.org/docs/2.2/en/bind.html#ipv6 John. -- -- Over 5000 webcams from ski resorts around the world - www.snoweye.com -- Translate your technical documents and web pages- www.tradoc.fr
Re: IPv6 Mirror testing
Le 13/09/2011 06:11, Kevin A. McGrail a écrit : I've got our mirror up and running on IPv6 with an A quad record for sa-update.pccc.com. We've got more issues to work out with sa-update to allow pure IPv6 systems to get updates but I am hoping some people might be able to test if they can get to http://sa-update.pccc.com/ in pure IPv6. My experience with IPv6 is very limited so I've only worked with the router, ip6tables and the web server in a very limited capacity and would appreciate knowing if it appears to be working correctly. Regards, KAM That seems to be responding fine over IPv6, yes. $ wget http://sa-update.pccc.com/ --2011-09-13 09:02:24-- http://sa-update.pccc.com/ Resolving sa-update.pccc.com 2001:550:2a00:1::2, 38.124.232.61 Connecting to sa-update.pccc.com.|2001:550:2a00:1::2|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 742 [text/html] John. -- -- Over 4000 webcams from ski resorts around the world - www.snoweye.com -- Translate your technical documents and web pages- www.tradoc.fr
