You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Kaleb Hosie <kh...@spectraaluminum.com> on 2010/03/29 17:40:00 UTC

trusted_networks

I'm having a problem with the trusted_networks option. Right now I have it set to:

trusted_networks 10.0.1/24

In postfix, I need to have spamassassin listed under "smtpd_recipient_restrictions" so that it will only scan incoming emails however it would be handy to get this option working if at all possible so it won't scan outgoing emails.

When I try to use this option; I login through telnet port 25, and send the test spam string (from the 10.0.1.0 subnet) it still gets caught in spam. Am I doing something wrong or is there another option I need to choose?

Thanks!
Kaleb

Re: trusted_networks

Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Mon, 2010-03-29 at 11:40 -0400, Kaleb Hosie wrote:
> I'm having a problem with the trusted_networks option. Right now I have
> it set to:
> 
> trusted_networks 10.0.1/24

> When I try to use this option; I login through telnet port 25, and send
> the test spam string (from the 10.0.1.0 subnet) it still gets caught
> in spam. Am I doing something wrong or is there another option I need
> to choose?

Please re-read the documentation about trusted_networks again. It is
*not* an option for bypassing SA.

In fact, there is no such option. SA will scan whatever it gets fed. So
if you want to bypass SA for mail generated from a particular network,
you need to adjust the glue that calls SA to just not do that.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}


RE: trusted_networks

Posted by Kaleb Hosie <kh...@spectraaluminum.com>.
> On 29.3.2010 18:40, Kaleb Hosie wrote:
> > I'm having a problem with the trusted_networks option.
> Right now I have it set to:
> >
> > trusted_networks 10.0.1/24
> >
> > In postfix, I need to have spamassassin listed under
> "smtpd_recipient_restrictions" so that it will only scan
> incoming emails however it would be handy to get this option
> working if at all possible so it won't scan outgoing emails.
> >
> > When I try to use this option; I login through telnet port
> 25, and send the test spam string (from the 10.0.1.0 subnet)
> it still gets caught in spam. Am I doing something wrong or
> is there another option I need to choose?
> >
>
> What is your glue to SpamAssassin? How is it called?
>
> I call SA from maildrop or procmail, which automatically
> makes it for incoming only. There are so many ways to do it.
>
> --
> http://www.iki.fi/jarif/
>
> You've been leading a dog's life.  Stay off the furniture.
>

I thought that with that option, SA is able to decide itself as to whether to scan it or not.

The program that I use to interface with SA is a rather unknown program called SpamAssassin Quarantine (SAQ). If SA isn't able to decide for itself to not scan particular emails depending upon whether it's from the internal network or not then I'll have to see about reprogramming SAQ to work.

Kaleb

Re: trusted_networks

Posted by Jari Fredriksson <ja...@iki.fi>.
On 29.3.2010 18:40, Kaleb Hosie wrote:
> I'm having a problem with the trusted_networks option. Right now I have it set to:
> 
> trusted_networks 10.0.1/24
> 
> In postfix, I need to have spamassassin listed under "smtpd_recipient_restrictions" so that it will only scan incoming emails however it would be handy to get this option working if at all possible so it won't scan outgoing emails.
> 
> When I try to use this option; I login through telnet port 25, and send the test spam string (from the 10.0.1.0 subnet) it still gets caught in spam. Am I doing something wrong or is there another option I need to choose?
> 

What is your glue to SpamAssassin? How is it called?

I call SA from maildrop or procmail, which automatically makes it for
incoming only. There are so many ways to do it.

-- 
http://www.iki.fi/jarif/

You've been leading a dog's life.  Stay off the furniture.


Re: trusted_networks

Posted by Matt Kettler <mk...@verizon.net>.
On 3/29/2010 11:40 AM, Kaleb Hosie wrote:
> I'm having a problem with the trusted_networks option. Right now I have it set to:
>
> trusted_networks 10.0.1/24
>
> In postfix, I need to have spamassassin listed under "smtpd_recipient_restrictions" so that it will only scan incoming emails however it would be handy to get this option working if at all possible so it won't scan outgoing emails.
>
> When I try to use this option; I login through telnet port 25, and send the test spam string (from the 10.0.1.0 subnet) it still gets caught in spam. Am I doing something wrong or is there another option I need to choose?
>
> Thanks!
> Kaleb
>
>   

Trusted in this case means "trusted to not forge headers, and while
unlikely to originate spam, this host might relay it." For example, your
front-end MX would be trusted if your SA runs on an internal server the
MX relays to. It will definitely forward whatever spam it gets, because
it forwards all mail.

trusted_networks is not a whitelisting mechanism.

You can check if your trust is working by seeing if messages that are
only handled by trusted hosts match the ALL_TRUSTED rule. This rule
carries a small negative score, but cannot outweigh the GTUBE sample.

In fact, even our whitelist mechanisms won't outweigh a GTUBE. GTUBE is
meant to *ALWAYS* be marked as spam if SA scans it, regardless of
whitelist settings.