You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Matt Kettler <mk...@evi-inc.com> on 2004/05/21 22:51:14 UTC
Re: ISP can't fix headers from hitting RCVD_IN_
DYNABLOCK/SORBS?
At 04:12 PM 5/21/2004, Jamie Pratt wrote:
>Hi - I posted a little while back about someone's email who was getting
>tagged here as spam before AWL kicked in... I was told by folks on the
>list that it appeared he was not using his ISP's relay, because his
>dynamic IP was/is showing in the headers, but I have verified that he has
>his client setup correctly, and *is* indeed relaying off his ISP.. Is this
>normal?
No, it's not normal. SA has code specificaly to avoid tagging properly
relayed mail.
May I ask if YOUR mailserver has a reserved IP (ie: 10.*.*.*, 192.168.*.*,
etc)?
If it does, you will trigger a bug in SA's trust path code. The bug causes
SA to assume that the outside ISP's mailserver is actually a part of your
network when it is not.
Fix it by forcing trusted_networks to contain ONLY your server's IP address.
trusted_networks 192.168.1.1
Re: ISP can't fix headers from hitting RCVD_IN_ DYNABLOCK/SORBS?
Posted by Jamie Pratt <ja...@nucdc.org>.
Matt Kettler wrote:
> At 04:12 PM 5/21/2004, Jamie Pratt wrote:
>
>> Hi - I posted a little while back about someone's email who was
>> getting tagged here as spam before AWL kicked in... I was told by
>> folks on the list that it appeared he was not using his ISP's relay,
>> because his dynamic IP was/is showing in the headers, but I have
>> verified that he has his client setup correctly, and *is* indeed
>> relaying off his ISP.. Is this normal?
>
>
> No, it's not normal. SA has code specificaly to avoid tagging properly
> relayed mail.
>
> May I ask if YOUR mailserver has a reserved IP (ie: 10.*.*.*,
> 192.168.*.*, etc)?
>
> If it does, you will trigger a bug in SA's trust path code. The bug
> causes SA to assume that the outside ISP's mailserver is actually a part
> of your network when it is not.
>
> Fix it by forcing trusted_networks to contain ONLY your server's IP
> address.
>
> trusted_networks 192.168.1.1
>
Ok, I tried the above suggestion and added my server's internal IP to
/etc/mail/spamassassin/local.cf... So, now it's only hitting on
RCVD_IN_SORBS and generating a 1.3. Is there anything else I can do,
or is this is "as good as it can get" on my end of things - The Isp
still has not responded to this issue?
thanks to all, especially Matt...
jamie