Am 25.05.2016 um 17:28 schrieb Dianne Skoll:
On Wed, 25 May 2016 10:17:19 -0500 (CDT)
sha...@shanew.net wrote:
So, for those with more experience, what is the preferred way to run a
backup MX (or two or three, etc.) without losing or breaking the
benefit of spam filtering?
For small install
In 20 years never saw need for backup mx.
If MX pool is down remote MTA should queue it.
Only practical use I've seen is NoListing setup.
I suppose you might run a server in the Arctic which could lose contact for
weeks and you'd want to ensure no bounces. Ymmv.
Sent from my iPhone
> On May
On Wed, 25 May 2016 10:17:19 -0500 (CDT)
sha...@shanew.net wrote:
> So, for those with more experience, what is the preferred way to run a
> backup MX (or two or three, etc.) without losing or breaking the
> benefit of spam filtering?
For small installations, I find a backup MX is more trouble th
On Wed, 25 May 2016, Dianne Skoll wrote:
On Wed, 25 May 2016 13:05:57 +0200
Support SimpleRezo wrote:
We are expecting a problem when emails are coming from our MX2 with
the SPF plugin, because the SPF test is made on the last "Received"
IP and not the first one (as we can expect for a SPF te
On Wed, 25 May 2016 13:05:57 +0200
Support SimpleRezo wrote:
> We are expecting a problem when emails are coming from our MX2 with
> the SPF plugin, because the SPF test is made on the last "Received"
> IP and not the first one (as we can expect for a SPF test).
> Does someone has already notice
You are totally right, fixed! Thank you!
2016-05-25 13:24 GMT+02:00 RW :
>
> It sounds like you haven't setup internal_networks and trusted_networks.
>
> https://wiki.apache.org/spamassassin/TrustPath
>
>
On Wed, 25 May 2016 13:05:57 +0200
Support SimpleRezo wrote:
> Hi,
>
> We are expecting a problem when emails are coming from our MX2 with
> the SPF plugin, because the SPF test is made on the last "Received"
> IP and not the first one (as we can expect for a SPF test).
>
> So if the domain is o
Hi,
We are expecting a problem when emails are coming from our MX2 with the SPF
plugin, because the SPF test is made on the last "Received" IP and not the
first one (as we can expect for a SPF test).
So if the domain is one of our domain, the result is always SPF_PASS when
the email arrived from