You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Warren Robinson <wa...@rakon.co.nz> on 2004/12/16 21:40:38 UTC
Non-trusted IP
How can I correct this problem of not allowing a non-trusted IP
('218.153.91.6') through this check:-
debug: MX lookup of yahoo.com succeeded => Dns available (set dns_available
to hardcode)
debug: is DNS available? 1
debug: looking up PTR record for '218.153.91.6'
debug: PTR for '218.153.91.6': ''
debug: received-header: parsed as [ ip=218.153.91.6 rdns=218.153.91.6
helo=111.111.111.111 by=mta.domain.com ident= ]
debug: received-header: 'by' mta.domain.com has reserved IP 172.20.1.13
debug: received-header: 'by' mta.doman.com has no public IPs
debug: received-header: relay 218.153.91.6 trusted? yes
debug: checking RBL dnsbl.njabl.org., set njabl
Thanks
Warren Robinson
Re: Non-trusted IP
Posted by Matt Kettler <mk...@evi-inc.com>.
At 03:40 PM 12/16/2004, Warren Robinson wrote:
>How can I correct this problem of not allowing a non-trusted IP
>('218.153.91.6') through this check:-
>
>debug: MX lookup of yahoo.com succeeded => Dns available (set dns_available
>to hardcode)
>debug: is DNS available? 1
>debug: looking up PTR record for '218.153.91.6'
>debug: PTR for '218.153.91.6': ''
>debug: received-header: parsed as [ ip=218.153.91.6 rdns=218.153.91.6
>helo=111.111.111.111 by=mta.domain.com ident= ]
>debug: received-header: 'by' mta.domain.com has reserved IP 172.20.1.13
>debug: received-header: 'by' mta.doman.com has no public IPs
>debug: received-header: relay 218.153.91.6 trusted? yes
>debug: checking RBL dnsbl.njabl.org., set njabl
manually set your trusted_networks. SA tries to auto-detect trust, but it
doesn't work if your MTA is NATed or otherwise has a reserved IP.