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
On 10/2/2017 10:03 AM, Davide Marchi wrote:
> Il 2017-09-28 18:41 Noel ha scritto:
> [..]
>
>>
>> If you feel you must have a backup MX, then the backup must have
>> spam controls equal to or more strict than the primary, and backup
>> must have a current recipient list so it can reject unknown
>>
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" -
On 9/28/2017 9:40 AM, Davide Marchi wrote:
> 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
>> fac
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 tell to reject
Zitat von Davide Marchi :
It is true what you say and I am aware of it and even this could be
a solution, but I would like to consider it only as an extreme
solution
The simple question is: what do you gain/expect to gain by a backup MX
host, why do you need it?
If you setup one and got
On Fri, 22 Sep 2017, Davide Marchi wrote:
Is there any way to tell to reject any mail coming to the MX backup
server, if the primary server is up?
Won't that make the secondary MX fail its purpose, which is to quickly
serve incoming legitimate mail if the primary is down ?
We have had since
On 09/24/2017 10:54 AM, Davide Marchi wrote:
*David Jones wrote:*
I tried using tarbaby.junkemailfilter.com as my highest/third MX and
ran into delivery problems due to greylisting. MTAs will back off and
retry at different intervals which can cause very long delays with
greylisting.
Look
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 tell to reject any mail coming to the MX backup
server, if the primar
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 backup
Am 22.09.2017 um 18:19 schrieb Davide Marchi:
> 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,
On 22.09.2017 18:19, Davide Marchi wrote:
> Is there any way to tell to reject any mail coming to the MX backup
> server, if the primary server is up?
Have you not just recently asked this on the Postfix mailing list?
Somebody did. It is not a SpamAssassin issue, since SA only gets
involved after
On 09/22/2017 11:19 AM, Davide Marchi wrote:
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
ser
Yes - that's a favorite trick of spammers to hit the backup server. If
you want you can add a third (fake) backup server:
tarbaby.junkemailfilter.com
It returns 451 on everything and gets rid of some of that spam (spammers
don't retry) and I get some training data for my black lists.
On 09/2
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
19 matches
Mail list logo
