On 16 Jun 2018, at 16:00 (-0400), J Doe wrote:
Hi everyone,
Thank you for the feedback. I am still uncertain, however, if I have
to explicitly define the trusted_networks/internal_networks parameters
manually in my case (where SA is running on same host as MTA) ?
Ignoring the --debug I not
On Sat, 16 Jun 2018 16:00:05 -0400
J Doe wrote:
> Hi everyone,
>
> Thank you for the feedback. I am still uncertain, however, if I have
> to explicitly define the trusted_networks/internal_networks
> parameters manually in my case (where SA is running on same host as
> MTA) ?
You shouldn't need
On Fri, 15 Jun 2018 16:24:46 +0300
Reio Remma wrote:
> Hello!
>
> I'm curious, if I turn on DCC learning, does it learn with both the
> learn and report options to sa-learn or only report?
There are two types of DCC test, most people only use the free version
which is purely a bulk mail test.
On Wed, 13 Jun 2018 16:36:02 -0700 (PDT)
John Hardin wrote:
> On Tue, 12 Jun 2018, micah anderson wrote:
>
> > I had a message marked with:
> >
> > 2.3 EMPTY_MESSAGE Message appears to have no textual parts and no
> > Subject:
> >
> > It did not have a subject, but it did have content (although o
Hi everyone,
Thank you for the feedback. I am still uncertain, however, if I have to
explicitly define the trusted_networks/internal_networks parameters manually in
my case (where SA is running on same host as MTA) ?
Ignoring the --debug I note that --lint does warn if I manually specify my MT
Matus UHLAR - fantomas skrev den 2018-06-16 16:37:
not external networks. only external mail servers you trust not to
forge e-mail
headers. They may send spam but are not the spam sources.
not correct
spamassassin need to know all wan ips your own servers use, it does not
need to protect fo
Matus UHLAR - fantomas skrev den 2018-06-16 18:07:
On 16.06.18 10:12, David Jones wrote:
That is basically the same thing worded a little differently. If you
have an internal mail relay and your SA server has a private IP on it,
then that will be an RFC 1918 IP or range in your internal_netwo
On 06/15/2018 05:44 PM, J Doe wrote:
Jun 15 18:39:23.422 [8422] dbg: config: trusted_networks
are not configured; it is recommended that you configure
trusted_networks manually
My question is:
— Should I manually set trusted_networks to have the IP address
of the host it is running on an
Thanks for helping.
Bruce
ser...@megavoice.com
Quoting users-h...@spamassassin.apache.org:
Hi! This is the ezmlm program. I'm managing the
users@spamassassin.apache.org mailing list.
To confirm that you would like
ser...@megavoice.com
removed from the users mailing list, please send a
On 06/16/2018 09:37 AM, Matus UHLAR - fantomas wrote:
On 06/15/2018 05:44 PM, J Doe wrote:
Jun 15 18:39:23.422 [8422] dbg: config: trusted_networks are not
configured; it is recommended that you configure trusted_networks
manually
My question is:
— Should I manually set trusted_networks
On 06/15/2018 05:44 PM, J Doe wrote:
Jun 15 18:39:23.422 [8422] dbg: config: trusted_networks are not
configured; it is recommended that you configure trusted_networks manually
My question is:
— Should I manually set trusted_networks to have the IP address of the host it
is running on and
On 15.06.18 09:04, Matus UHLAR - fantomas wrote:
On Tue, 12 Jun 2018, micah anderson wrote:
I had a message marked with:
2.3 EMPTY_MESSAGE Message appears to have no textual parts and no
Subject:
It did not have a subject, but it did have content (although only
encrypted)
John Hardin
On 06/16/2018 06:33 AM, David Jones wrote:
On 06/15/2018 05:44 PM, J Doe wrote:
Hello,
I am currently using SpamAssassin 3.4.1 on Ubuntu Linux 16.04.4 LTS.
I have SA running on a server with Postfix as the MTA on the same server.
I have a question regarding the trusted_networks configuratio
On 06/15/2018 05:44 PM, J Doe wrote:
Hello,
I am currently using SpamAssassin 3.4.1 on Ubuntu Linux 16.04.4 LTS. I have SA
running on a server with Postfix as the MTA on the same server.
I have a question regarding the trusted_networks configuration parameter (man
Mail::SpamAssassin::Conf).
14 matches
Mail list logo