On Tue, Jun 9, 2020 at 12:10 AM Peter wrote:
> On 9/06/20 2:56 pm, Jon LaBadie wrote:
>
> Don't use a backup MX, they are a relic of the 90s when mail servers
> were often times not always online. a sending mail server will
> generally retry the message for up to five days if your MTA is down
On 9/06/20 2:56 pm, Jon LaBadie wrote:
I hit another limitation. My backup MX handler is a 3rd party who
will not use greylisting. Thus all the 1st timers I rejected just
delivered to my alternate MX address and were not blocked at all.
Don't use a backup MX, they are a relic of the 90s when
yeah, then don't use a backup MX server at all. I dropped using one when I
realized most spam prevention would just end up at the backup which didn't
have the same rules
as long as your server has a decent uptime and is never down more than a
few hours and that very rarely, then you really don't
On Sun, Jun 07, 2020 at 05:53:28AM -0700, John Pierce wrote:
> On Sun, Jun 7, 2020, 2:47 AM Nicolas Kovacs wrote:
>
> >
> > My aim is simply to eliminate as much spam as possible (that is, before
> > adding
> > SpamAssassin) while keeping false positives to a minimum.
> >
>
> The one thing
Am 07.06.2020 um 11:46 schrieb Nicolas Kovacs:
Hi,
I'm currently fine-tuning my mail server (Postfix and Dovecot on CentOS 7).
SPF, DKIM and DMARC work fine, now I'd like to limit the spam tsunami.
Besides the official Postfix documentation, I've read a few articles about
Postfix spam
On Sun, Jun 7, 2020, 2:47 AM Nicolas Kovacs wrote:
>
> My aim is simply to eliminate as much spam as possible (that is, before
> adding
> SpamAssassin) while keeping false positives to a minimum.
>
The one thing that stopped the most spam on my last mailserver was
greylisting. Any mta
Hi,
I'm currently fine-tuning my mail server (Postfix and Dovecot on CentOS 7).
SPF, DKIM and DMARC work fine, now I'd like to limit the spam tsunami.
Besides the official Postfix documentation, I've read a few articles about
Postfix spam restrictions, namely these :
7 matches
Mail list logo
