On Thu, 26 Apr 2018 16:21:01 -0400
Bill Cole wrote:
> On 26 Apr 2018, at 3:04 (-0400), Palvelin Postmaster wrote:
>
> > Received: by palvelin.fi (CommuniGate Pro PIPE 6.2.3)
>
> That may be your first problem. SA can't parse that as a proper
> Received header, which may trigger it to not cla
On 26 Apr 2018, at 3:04 (-0400), Palvelin Postmaster wrote:
Hi,
I relay mail from another server to my main mail server. I have set
its IP 52.28.104.67 in my spamassassin conf in the internal_networks
and trusted_networks. I assumed that would prevent spamassassin from
scanning the messages
On Thu, 26 Apr 2018 10:04:32 +0300
Palvelin Postmaster wrote:
> Hi,
>
> I relay mail from another server to my main mail server. I have set
> its IP 52.28.104.67 in my spamassassin conf in the internal_networks
> and trusted_networks. I assumed that would prevent spamassassin from
> scanning the
On 26.04.18 10:04, Palvelin Postmaster wrote:
I relay mail from another server to my main mail server. I have set its IP
52.28.104.67 in my spamassassin conf in the internal_networks and
trusted_networks. I assumed that would prevent spamassassin from scanning
the messages but no. Why does this
Hi,
I relay mail from another server to my main mail server. I have set its IP
52.28.104.67 in my spamassassin conf in the internal_networks and
trusted_networks. I assumed that would prevent spamassassin from scanning the
messages but no. Why does this happen?
X-Spam-Status: Yes, score=6.1 r