lled via CPAN, uses
the SA default paths. That explains why it didn't clear up this problem
of report_safe -- it's non-0 by default.
> animalhead:~ $ spamassassin -D --lint 2>&1 | grep "site rules"
> Mar 2 07:33:27.529 [75068] dbg: config: using "/e
onf(3), the former included
/var/db/spamassassin/3.003001 in its "default" list and
/usr/local/etc/mail/spamassassinin its "site-specific" list
(the latter is where my local.cf with report_safe 0 is located)
Running spamassassin with the -D debug switch also
amAssassin::Conf(3), the former included
>
> /var/db/spamassassin/3.003001 in its "default" list and
> /usr/local/etc/mail/spamassassinin its "site-specific" list
> (the latter is where my local.cf with report_safe 0 is located)
>
>
On Mar 1, 2011, at 6:35 AM, Karsten Bräckelmann wrote:
On Tue, 2011-03-01 at 06:00 -0800, macke...@animalhead.com wrote:
In my file /usr/local/etc/mail/spamassassin/local.cf there are 4
comment lines and 1 active line:
report_safe 0
Since a recent upgrade to SA 3.3.1, SA attaches emails
On Tue, 2011-03-01 at 06:00 -0800, macke...@animalhead.com wrote:
> In my file /usr/local/etc/mail/spamassassin/local.cf there are 4
> comment lines and 1 active line:
> report_safe 0
> Since a recent upgrade to SA 3.3.1, SA attaches emails that it tags, rather
> than just ad
x27;
> # for details of what can be tweaked.
> #
> report_safe 0
>
> The active line ends with a return. I've grepped all the configuration
> files and directories noted in the man pages, and can see no non-comment
> line that changes report_safe.
>
> Since a recent up
In my file /usr/local/etc/mail/spamassassin/local.cf there are 4
comment lines
and 1 active line:
## SA-VINSTALL VERSION: 3.2.5
# Add your own customisations to this file. See 'man
Mail::SpamAssassin::Conf'
# for details of what can be tweaked.
#
report_safe 0
The active line e
In case anyone else uses a script to scan the SA injected message headers
to build log records (to detail matched tests, etc), and that script cares
about the *order* of the headers, then please take note that in 3.3.1 the
position of the 'report_safe 0' command in your .cf files r
Marc Perkel wrote:
but still getting this:
Spam detection software, running on the system "pascal.ctyme.com", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have
Justin Mason wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Perkel writes:
but still getting this:
Spam detection software, running on the system "pascal.ctyme.com", has
identified this incoming email as possible spam. The original message
has been attached to this so you can vie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Perkel writes:
> but still getting this:
>
> Spam detection software, running on the system "pascal.ctyme.com", has
> identified this incoming email as possible spam. The original message
> has been attached to this so you can view it (if it is
but still getting this:
Spam detection software, running on the system "pascal.ctyme.com", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the
12 matches
Mail list logo
