You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by SM <sm...@resistor.net> on 2008/04/11 06:55:48 UTC

Re: CommuniGate Pro Received header (was: whitelist_from_rcvd not working)

At 23:03 09-04-2008, Victor Sudakov wrote:
>whitelist_from_rcvd now works, but not quite in the manner I have
>expected. In fact, it works only if the relay is NOT in the
>trusted_networks list.

Can you post the debug output?

>I wonder if this is by design. In my opinion, whitelisting should
>always work.

You can only trust the Received: headers inserted by your mail servers.

Regards,
-sm 


Re: CommuniGate Pro Received header (was: whitelist_from_rcvd not working)

Posted by Victor Sudakov <su...@sibptus.tomsk.ru>.
SM wrote:
> >whitelist_from_rcvd now works, but not quite in the manner I have
> >expected. In fact, it works only if the relay is NOT in the
> >trusted_networks list.
> 
> Can you post the debug output?


In this case 212.73.124.135 is trusted so the sender was not
whitelisted!!!
http://vas.tomsk.ru/sa2.txt

And here is what happens when I remove 212.73.124.135 from the trusted
list, the sender got whitelisted: 
http://vas.tomsk.ru/sa3.txt

> 
> >I wonder if this is by design. In my opinion, whitelisting should
> >always work.
> 
> You can only trust the Received: headers inserted by your mail servers.

The topmost Received: header is always inserted by my mail server.
But if the relay mentioned in this topmost header is in the list of
trusted_networks, whitelist_from_rcvd does not work.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:sudakov@sibptus.tomsk.ru