Hi friends,
confirm that setting "report_safe 0" on backup MX, does what I asked,
and that is, it allows the main server to move messages marked as spam
in the relative directory, as the following logs show:
SERVER BACKUP MX:
Nov 14 17:51:07 server2 spamd[4728]: spamd: connection from local
Il 2017-11-13 11:01 Matus UHLAR - fantomas ha scritto:
[.]
this is your problem: your backup MX packs spam to a non-spam mail
set report_safe 0 on backup MX
Well, I've set "report_safe 0" on backup MX,
Now I verify what happens ;-)
Very very thanks for your help.
You had already hinted at thi
Il 2017-11-07 10:10 Matus UHLAR - fantomas ha scritto:
[..]
Thus, messages received from the world will be scored locally, messages
received from backup MX will be scored on backup MX.
Then, your sieve filter will work as expected.
[..]
Well, but could I make a Sieve filter that put to (prima
Il 2017-11-05 16:26 Matus UHLAR - fantomas ha scritto:
[..]
Is there any method to tell "primary server spamassassin"
automatically move spam (forwarded by backup MX) to (primary) spam
folder?
SA does NOT move mail, it only scores mail.
..sorry, I expressed myself badly
However, you ca
Matus UHLAR - fantomas ha scritto:
[..]
sieve does not work on backup MX, since sieve runs at delivery time
which
does not happen on backup MX (unless you hack it to)
Well
Actually the backup MX server when mark an email as spam simply
forward to primary
and this is exactly how backup MX
Hi Friends,
on Debian Jessie environment, using spamass-milter 0.3.2-1 and
spamassassin 3.4.0-6,
I would like to make sure that automatically all messages marked as spam
and forwarded by the backup server mx to the primary server, the
(primary server) sieve filter moves them to the spam folder.
Il 2017-10-02 18:13 Noel ha scritto:
[..]
DKIM will stop forged senders in your domain, but it won't stop mail
to a random recipient in your domain. Each server *must* have a list
of valid recipients. The secondary MX will use
relay_recipients_maps for this.
You can still use postscreen indepe
Il 2017-09-28 18:41 Noel ha scritto:
[..]
First, [...] If the two hosts
aren't physically close -- on the same switch -- this just isn't
practical.
Eh, my two VPS are in two different geographic locations.
This spoils everything
Secondly, [..]And if the
postscreen cache is on the primary an
Il 2017-09-28 16:48 Reindl Harald ha scritto:
[..]
no, you have both the same machine, frankly you do nothing else than
add the IP aof the backup-mx to the box and tell postscreen with
"postscreen_whitelist_interfaces" which one is *always* a 450 response
OK
there is no "primary MX down" -
Il 2017-09-27 18:40 Reindl Harald ha scritto:
it's trivial, just give the primary MX the IP auf the backup-MX as
alias and if you are at it enable "postscreen_dnsbl_sites" and
"postscreen_greet_action" - after that your smtpd process only faces
a
few percent of all spam at all
I've read from
Il 2017-09-25 10:17 Lucio Chiappetti ha scritto:
[..]
(*) which does not mean SA is useless, as it was demonstrated
recently when an OS upgrade temporarily disabled amavisd (which is
what triggers spamassassin) and the SA-filtered spam came through. As
an order of magnitude, graylisting filters
Il 2017-09-25 00:12 David Jones ha scritto:
[..]
If you do this, then you need to make sure the secondary servers
are setup identically to the primary to filter identically.
the two setup are identically.
As mentioned above, just use them in an active/active way like
smtp.ena.net. If this
Il 2017-09-24 20:09 Matus UHLAR - fantomas ha scritto:
On 22.09.17 18:19, Davide Marchi wrote:
On Debian Jessie, Postfix 2.11.3 and Spamassassin 3.4.0-6, I've just
setup an MX email backup server and now I realize that new spam come
from the MX backup server..
Is there any way to te
Am 22.09.2017 um 18:19 schrieb Davide Marchi:
Hi friends,
On Debian Jessie, Postfix 2.11.3 and Spamassassin 3.4.0-6, I've just
setup an MX email backup server and now I realize that new spam come
from the MX backup server..
Is there any way to tell to reject any mail coming to the MX b
Hi friends,
On Debian Jessie, Postfix 2.11.3 and Spamassassin 3.4.0-6, I've just
setup an MX email backup server and now I realize that new spam come
from the MX backup server..
Is there any way to tell to reject any mail coming to the MX backup
server, if the primary server is up?
And again, m
15 matches
Mail list logo