RE: disabling ALL_TRUSTED
From: Arvinn Løkkebakken [mailto:[EMAIL PROTECTED]
>
> Bowie Bailey wrote:
>
> >From: Arvinn Løkkebakken [mailto:[EMAIL PROTECTED]
> >
> >>jdow wrote:
> >>
> >>>Do not disable it. Fix the cause.
> >>>
> >>>It's time to hit the wiki and learn how.
> >>>{^_^}
> >>
> >>I hit the wiki and found this patch:
> >>
> >>http://bugzilla.spamassassin.org/attachment.cgi?id=2508
> >>
> >>Is it the fix you were thinking about?
> >
> >I doubt that was what he was referring to. You just need to
> >configure your trust path so that ALL_TRUSTED will know what to
> >trust. Add a trusted_networks entry in your local.cf for each of
> >your mailservers (or one for each of your networks) and that should
> >fix your problem.
> >
> >For details see the manpage for Mail::SpamAssassin::Conf.
>
>http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.h
tml
>
> No, that's not correct. Trusted_networks is not a mandatory
> setting. ALL_TRUSTED shall not be triggered by messages with
> Received headers with hosts that doesn't exist in
> trusted_networks and friends. It's the other way around.
> ALL_TRUSTED only kicks in when all Received headers only contains
> hosts that are_defined in trusted_networks and/or friends.
Right, but if trusted_networks is not defined, Courier assumes that
most recent mailserver with a public address is your gateway
mailserver. If your actual gateway server has a NAT address,
Courier will start trusting every mailserver that sends you mail.
It's not a mandatory setting, but as many times as I've seen this
question on the list, it probably should be mandatory.
> You probably didn't read what I posted carefully enough. The
> problem is that ALL_TRUSTED some times get triggered when it
> shouldn't, i.e. it gets triggered even when one or more of the
> Received headers contains a foreign host that is not in
> trusted_networks, internal_networks or in a network "near by",
> because it failed to parse the actual header. The wiki article
> (bug 3949) I found describes this situation exactly as it appears
> to me. It seems to me that this bug made it to 3.0.2 even though
> the wiki article is dated early in November.
You're right. I lost track of your original post and assumed you
were having the same problem most everyone else seems to have with
the ALL_TRUSTED rule. Sorry about the confusion.
Bowie
Re: disabling ALL_TRUSTED
Arvinn Løkkebakken wrote:
Bowie Bailey wrote:
From: Arvinn Løkkebakken [mailto:[EMAIL PROTECTED]
jdow wrote:
Do not disable it. Fix the cause.
It's time to hit the wiki and learn how.
{^_^}
I hit the wiki and found this patch:
http://bugzilla.spamassassin.org/attachment.cgi?id=2508
Is it the fix you were thinking about?
I doubt that was what he was referring to. You just need to
configure your trust path so that ALL_TRUSTED will know what to
trust. Add a trusted_networks entry in your local.cf for each of
your mailservers (or one for each of your networks) and that should
fix your problem.
For details see the manpage for Mail::SpamAssassin::Conf.
http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.ht
ml
Bowie
No, that's not correct. Trusted_networks is not a mandatory setting.
ALL_TRUSTED shall not be triggered by messages with Received headers
with hosts that doesn't exist in trusted_networks and friends. It's the
other way around. ALL_TRUSTED only kicks in when all Received headers
only contains hosts that are_defined in trusted_networks and/or friends.
You probably didn't read what I posted carefully enough.
The problem is that ALL_TRUSTED some times get triggered when it
shouldn't, i.e. it gets triggered even when one or more of the Received
headers contains a foreign host that is not in trusted_networks,
internal_networks or in a network "near by", because it failed to parse
the actual header. The wiki article (bug 3949) I found describes this
situation exactly as it appears to me. It seems to me that this bug made
it to 3.0.2 even though the wiki article is dated early in November.
The article may be dated early november but the bug itself is still open
and being worked on which is why it still exists in 3.0.2. I imagine it
will be resolved shortly after they get some issues worked out. (From
reading the bug report).
-Jim
Re: disabling ALL_TRUSTED
Bowie Bailey wrote:
From: Arvinn Løkkebakken [mailto:[EMAIL PROTECTED]
jdow wrote:
Do not disable it. Fix the cause.
It's time to hit the wiki and learn how.
{^_^}
I hit the wiki and found this patch:
http://bugzilla.spamassassin.org/attachment.cgi?id=2508
Is it the fix you were thinking about?
I doubt that was what he was referring to. You just need to
configure your trust path so that ALL_TRUSTED will know what to
trust. Add a trusted_networks entry in your local.cf for each of
your mailservers (or one for each of your networks) and that should
fix your problem.
For details see the manpage for Mail::SpamAssassin::Conf.
http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.ht
ml
Bowie
No, that's not correct. Trusted_networks is not a mandatory setting.
ALL_TRUSTED shall not be triggered by messages with Received headers
with hosts that doesn't exist in trusted_networks and friends. It's the
other way around. ALL_TRUSTED only kicks in when all Received headers
only contains hosts that are_defined in trusted_networks and/or friends.
You probably didn't read what I posted carefully enough.
The problem is that ALL_TRUSTED some times get triggered when it
shouldn't, i.e. it gets triggered even when one or more of the Received
headers contains a foreign host that is not in trusted_networks,
internal_networks or in a network "near by", because it failed to parse
the actual header. The wiki article (bug 3949) I found describes this
situation exactly as it appears to me. It seems to me that this bug made
it to 3.0.2 even though the wiki article is dated early in November.
Arvinn
RE: disabling ALL_TRUSTED
From: Arvinn Løkkebakken [mailto:[EMAIL PROTECTED]
>
> jdow wrote:
>
> >Do not disable it. Fix the cause.
> >
> >It's time to hit the wiki and learn how.
> >{^_^}
>
> I hit the wiki and found this patch:
>
> http://bugzilla.spamassassin.org/attachment.cgi?id=2508
>
> Is it the fix you were thinking about?
I doubt that was what he was referring to. You just need to
configure your trust path so that ALL_TRUSTED will know what to
trust. Add a trusted_networks entry in your local.cf for each of
your mailservers (or one for each of your networks) and that should
fix your problem.
For details see the manpage for Mail::SpamAssassin::Conf.
http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.ht
ml
Bowie
Re: disabling ALL_TRUSTED
jdow wrote:
Do not disable it. Fix the cause.
It's time to hit the wiki and learn how.
{^_^}
I hit the wiki and found this patch:
http://bugzilla.spamassassin.org/attachment.cgi?id=2508
Is it the fix you were thinking about?
Can anyone advice me on how to apply the patch correctly?
Thanks.
Arvinn
Re: disabling ALL_TRUSTED
Do not disable it. Fix the cause.
It's time to hit the wiki and learn how.
{^_^}
- Original Message -
From: "Arvinn Løkkebakken" <[EMAIL PROTECTED]>
> How do I disable the ALL_TRUSTED test?
>
> It's hitting spam more and more often by misinterpreting Received:
> headers, i.e. claiming the mail passed through trusted hosts when it
didn't.
> That makes it a very dangerous setting since it may trigger
> auto-learning spam as ham. It allready has several times on my server.
>
> I can of course set the score to 0 for ALL_TRUSTED but it's cleaner to
> totally disable it so it won't hit the message headers as well.
>
> Arvinn
Re: disabling ALL_TRUSTED
any score of zero will disable a rule... -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 Arvinn Løkkebakken wrote: Martin Hepworth wrote: Arvinn set the score to zero in local.cf score ALL_TRUSTED 0 Will this disable the test too, or just set the score too 0? I don't want the ALL_TRUSTED score result in header either because it shouldn't be there the times when it's false. or.. define "trusted_networks ip.add.re.ss[/mask] ... (default: none)" - see the docs http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.html What do you mean? I have my trusted networks in trusted_networks. The problem is that ALL_TRUSTED some times bugs and triggers on messages that have passed through relays that belongs to completely different networks. I think this happens when SA fails to parse the Received: header containing the foreign host. Arvinn ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote confirms that this email message has been swept for the presence of computer viruses and is believed to be clean. **
Re: disabling ALL_TRUSTED
Martin Hepworth wrote: Arvinn set the score to zero in local.cf score ALL_TRUSTED 0 Will this disable the test too, or just set the score too 0? I don't want the ALL_TRUSTED score result in header either because it shouldn't be there the times when it's false. or.. define "trusted_networks ip.add.re.ss[/mask] ... (default: none)" - see the docs http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.html What do you mean? I have my trusted networks in trusted_networks. The problem is that ALL_TRUSTED some times bugs and triggers on messages that have passed through relays that belongs to completely different networks. I think this happens when SA fails to parse the Received: header containing the foreign host. Arvinn
Re: disabling ALL_TRUSTED
Arvinn set the score to zero in local.cf score ALL_TRUSTED 0 or.. define "trusted_networks ip.add.re.ss[/mask] ... (default: none)" - see the docs http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.html -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 Arvinn Løkkebakken wrote: How do I disable the ALL_TRUSTED test? It's hitting spam more and more often by misinterpreting Received: headers, i.e. claiming the mail passed through trusted hosts when it didn't. That makes it a very dangerous setting since it may trigger auto-learning spam as ham. It allready has several times on my server. I can of course set the score to 0 for ALL_TRUSTED but it's cleaner to totally disable it so it won't hit the message headers as well. Arvinn ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote confirms that this email message has been swept for the presence of computer viruses and is believed to be clean. **
disabling ALL_TRUSTED
How do I disable the ALL_TRUSTED test? It's hitting spam more and more often by misinterpreting Received: headers, i.e. claiming the mail passed through trusted hosts when it didn't. That makes it a very dangerous setting since it may trigger auto-learning spam as ham. It allready has several times on my server. I can of course set the score to 0 for ALL_TRUSTED but it's cleaner to totally disable it so it won't hit the message headers as well. Arvinn
