On 2017-08-06 10:37, Scott wrote:
> Centos7
> Posftfix 3.2.2
> Amavisd 2.11.0
> spamassassin-3.4.0
> To: r...@mail2.myserver.com
> From: logwa...@mail2.myserver.com
Since these are locally submitted messages (i.e. not SMTP), IMO the best
and cleanest way to deal with it is to tell the MTA not
On Sun, 6 Aug 2017 10:37:36 -0700 (MST)
Scott wrote:
> Centos7
> Posftfix 3.2.2
> Amavisd 2.11.0
> spamassassin-3.4.0
>
> I have a logwatch output that gets mailed to me daily. Spamassassin
> is scoring it high enough as exceed my threshold for whacking it as
> spam.
>
> While this is not
On 08/06/2017 05:10 PM, msxc wrote:
I have a logwatch output that gets mailed to me daily. Spamassassin is
scoring it high enough as exceed my threshold for whacking it as spam.
Please subscribe to the list for future posts.
However, I would argue that this is expected behavior because your
>> I have a logwatch output that gets mailed to me daily. Spamassassin is
>> scoring it high enough as exceed my threshold for whacking it as spam.
>Please subscribe to the list for future posts.
>
>However, I would argue that this is expected behavior because your
>logwatch notice almost
Hi,
> I have the server's IP address (y.y.y.y) in my lists of trusted and internal
> as so:
> trusted_networks xx.xx.xx.xx
> trusted_networks y.y.y.y
> trusted_networks z.z.z.z
>
> internal_networks xx.xx.xx.xx
> internal_networks y.y.y.y
> internal_networks z.z.z.z
>
> I don't see that that made
On 8/6/2017 1:37 PM, Scott wrote:
I have a logwatch output that gets mailed to me daily. Spamassassin is
scoring it high enough as exceed my threshold for whacking it as spam.
Please subscribe to the list for future posts.
However, I would argue that this is expected behavior because your
