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.
On 16.06.18 19:06, Benny Pedersen wrote:
not correct
spamassassin need to know all wan ips your own
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_networks.
Matus UHLAR - fantomas skrev den 2018-06-16
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
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
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
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
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
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
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
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
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).
J Doe skrev den 2018-06-16 00:44:
$ spamassassin --debug --lint
--config-file=/etc/spamassassin/local.custom.cf
dont use --lint and --config-file at same time to do lint testing
if this is a error, please create a bug
--debug does not make it more simple, and mostly only developpers
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). I manually added this to a custom
14 matches
Mail list logo
