Re: sa-update from Feb 23 to May 8 ALL_TRUST problem

2013-05-09 Thread Kevin A. McGrail
On 5/9/2013 1:29 PM, starlight.201...@binnacle.cx wrote: Figured it out--silly problem. Overlooked setting 'umask 022' before running 'sa-update' and so the permission were all set to 750 instead of 755. SA runs in a restricted UID and so could not read the files. Scored my test-to-self messag

Re: sa-update from Feb 23 to May 8 ALL_TRUST problem

2013-05-09 Thread starlight . 2013q2
Figured it out--silly problem. Overlooked setting 'umask 022' before running 'sa-update' and so the permission were all set to 750 instead of 755. SA runs in a restricted UID and so could not read the files. Scored my test-to-self message 0 since none of the rules were working. Seems odd to me

Re: sa-update from Feb 23 to May 8 ALL_TRUST problem

2013-05-09 Thread Benny Pedersen
starlight.201...@binnacle.cx skrev den 2013-05-09 17:47: spamassassin 2>&1 -D -t msg on both versions should show what happen Ran this and the problem is not reproducible with the command-line SA invocation. Only fails running under MimeDefang. then report this to mimedefang maillist, and p

Re: sa-update from Feb 23 to May 8 ALL_TRUST problem

2013-05-09 Thread starlight . 2013q2
At 16:42 5/9/2013 +0200, Benny Pedersen wrote: > >starlight.201...@binnacle.cx skrev den 2013-05-09 15:56: >> Like I said, I put back the 2/22/2013 >> rules (2/23 was a typo) and it is working >> again. Probably will just leave it >> that way forever unless someone knows >> what was broken by the

Re: sa-update from Feb 23 to May 8 ALL_TRUST problem

2013-05-09 Thread Benny Pedersen
starlight.201...@binnacle.cx skrev den 2013-05-09 15:56: Of course, otherwise why would it work with the older 'sa-update' rules? Perhaps you should read the original query again. spamassassin can guess, but it is not configured to know all defaults that fits all servers out there, for instan

Re: sa-update from Feb 23 to May 8 ALL_TRUST problem

2013-05-09 Thread starlight . 2013q2
At 10:55 5/9/2013 +0200, Benny Pedersen wrote: >starlight.201...@binnacle.cx skrev den 2013-05-08 17:02: > >> Does anyone know what the story is with this? > >perldoc Mail::SpamAssassin::Conf see >trusted_networks and internal_networks, >default is 127.0.0.1 >its your responsely to add all your wan

Re: sa-update from Feb 23 to May 8 ALL_TRUST problem

2013-05-09 Thread Benny Pedersen
starlight.201...@binnacle.cx skrev den 2013-05-08 17:02: Does anyone know what the story is with this? perldoc Mail::SpamAssassin::Conf see trusted_networks and internal_networks, default is 127.0.0.1, is you server on ipv6 ?, its your responsely to add all your wan ips to this settings to

sa-update from Feb 23 to May 8 ALL_TRUST problem

2013-05-08 Thread starlight . 2013q2
Hello, Ran 'sa-update' after a few months and ALL_TRUST stopped scoring for local network systems. Put back the old rules from backup and it works again. Searched for change log or explanation and found nothing. Does anyone know what the story is with this? Running 3.3.2 under 'mimedefang' 2.7