SM wrote:
> >This is the standard CommuniGate Pro "Received:" header.
> >When HELO matches the hostname, this header always looks this way,
> >with the word "verified" added to it.
>
> SpamAssassin is not parsing that "Received:" header as one with a
> hostname which has been "verified".
[dd]
>
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.
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
alwa
SM wrote:
> Hi Victor,
> At 21:40 09-04-2008, Victor Sudakov wrote:
> >This is the standard CommuniGate Pro "Received:" header.
> >When HELO matches the hostname, this header always looks this way,
> >with the word "verified" added to it.
>
> SpamAssassin is not parsing that "Received:" header as
Hi Victor,
At 21:40 09-04-2008, Victor Sudakov wrote:
This is the standard CommuniGate Pro "Received:" header.
When HELO matches the hostname, this header always looks this way,
with the word "verified" added to it.
SpamAssassin is not parsing that "Received:" header as one with a
hostname whi
