From: "M. Lewis" <[EMAIL PROTECTED]>
>If someone hasn't suggested it already, post your trusted_* config lines
>>along with the headers for a message that you think hit wrong, and we can
>>probably help you figure out what is going wrong. The first guess
would be
>>that you don't have trusted_networks set quite *right*, even though
you have
>>it set to *something*.
>>
>> Loren
I really didn't want to hijack the other continuing thread on this, but
I still have problems with my trusted_networks.
The only time I really notice this is when I recieve a spam that isn't
marked as such. In the case below, had it not been for the
trusted_networks, this spam would have clearly been marked as such.
In the first example, I'm using fetchmail to drag down messages from a
remote mailbox on another server. It appears to me that fetchmail is
causing this to appear as it is coming from localhost
(localhost.localdomain) and that is why _I think_ it is hitting the
ALL_TRUSTED.
Mail that comes directly into my network (not via fetchmail) I do not
believe ever has the ALL_TRUSTED as shown in the second example.
My trusted nework configs:
# Trusted
clear_trusted_networks
trusted_networks 192.168.1/24
# Internal
clear_internal_networks
internal_networks 192.168.1/24
Change this last to:
===8<---
# Trusted
clear_trusted_networks
trusted_networks 192.168.1/24 127/8
# Internal
clear_internal_networks
internal_networks 192.168.1/24
===8<---
127/8 is yourself. If you cannot trust your own mail machine who can
you trust?
{^_^}
