From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Alternate Incoming Mail Server
Date: Mon, 6 Apr 2020 13:14:35 -0400 [thread overview]
Message-ID: <c4066b87-6ee2-34bb-2b95-4901c2bd4b0a@gentoo.org> (raw)
In-Reply-To: <f9b58bd9-d24a-79a6-171c-a84c9aea7747@spamtrap.tnetconsulting.net>
On 4/6/20 1:02 PM, Grant Taylor wrote:
> On 4/6/20 10:43 AM, Michael Orlitzky wrote:
>> Well, I can't refute an anecdote without more information, but if
>> you're worried about this you can create the same MX record twice so
>> that the "backup" is the primary.
>
> That's not going to work as well as you had hoped.
>
> I've run into many MTAs that check things and realize that the hosts in
> multiple MX records resolve to the same IP and treat them as one.
>
Why don't you say which MTA it is that both (a) combines MX records with
different priorities, and (b) doesn't retry messages to the primary MX?
next prev parent reply other threads:[~2020-04-06 17:14 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 12:35 [gentoo-user] Alternate Incoming Mail Server Ashley Dixon
2020-04-06 12:41 ` Michael Orlitzky
2020-04-06 13:08 ` Ashley Dixon
2020-04-06 13:15 ` Michael Orlitzky
2020-04-06 13:24 ` Ashley Dixon
2020-04-06 16:18 ` [gentoo-user] " Ian Zimmerman
2020-04-06 16:25 ` Ashley Dixon
2020-04-06 19:03 ` Rich Freeman
2020-04-06 19:16 ` Michael Orlitzky
2020-04-06 20:06 ` Grant Taylor
2020-04-08 21:36 ` Neil Bothwick
2020-04-08 21:49 ` Grant Taylor
2020-04-08 22:06 ` Michael Orlitzky
2020-04-08 22:13 ` Ashley Dixon
2020-04-08 22:22 ` Michael Orlitzky
2020-04-09 1:15 ` Grant Taylor
2020-04-06 20:02 ` Grant Taylor
2020-04-06 23:34 ` Rich Freeman
2020-04-11 20:08 ` [gentoo-user] " antlists
2020-04-11 20:17 ` Michael Orlitzky
2020-04-11 20:41 ` Grant Taylor
2020-04-11 20:45 ` Ashley Dixon
2020-04-11 20:50 ` Michael Orlitzky
2020-04-11 20:33 ` Grant Taylor
2020-04-11 22:13 ` antlists
2020-04-12 2:14 ` Grant Taylor
2020-04-06 15:24 ` J. Roeleveld
2020-04-06 15:34 ` Ashley Dixon
2020-04-06 15:51 ` Robert Bridge
2020-04-06 16:02 ` Michael Orlitzky
2020-04-06 16:19 ` J. Roeleveld
2020-04-06 16:43 ` Michael Orlitzky
2020-04-06 17:02 ` Grant Taylor
2020-04-06 17:14 ` Michael Orlitzky [this message]
2020-04-06 17:19 ` J. Roeleveld
2020-04-06 17:24 ` Robert Bridge
2020-04-06 17:27 ` Michael Orlitzky
2020-04-06 17:25 ` Michael Orlitzky
2020-04-06 17:32 ` J. Roeleveld
2020-04-06 17:35 ` Michael Orlitzky
2020-04-06 18:13 ` Stefan Schmiedl
2020-04-07 17:10 ` Michael
2020-04-07 18:34 ` Michael Orlitzky
2020-04-07 18:54 ` Stefan Schmiedl
2020-04-07 19:11 ` Michael Orlitzky
2020-04-07 18:35 ` Stefan Schmiedl
2020-04-07 4:37 ` J. Roeleveld
2020-04-06 17:44 ` Grant Taylor
2020-04-06 17:55 ` Michael Orlitzky
2020-04-06 19:59 ` Grant Taylor
2020-04-06 20:55 ` Michael Orlitzky
2020-04-06 17:00 ` Grant Taylor
2020-04-06 17:34 ` Grant Taylor
2020-04-06 21:17 ` Ashley Dixon
2020-04-06 22:12 ` Grant Taylor
2020-04-07 4:49 ` J. Roeleveld
2020-04-07 10:53 ` Ashley Dixon
2020-04-08 3:18 ` Grant Taylor
2020-04-08 13:39 ` [gentoo-user] " Grant Edwards
2020-04-08 14:11 ` Ashley Dixon
2020-04-08 16:03 ` Grant Taylor
2020-04-08 16:34 ` Grant Edwards
2020-04-08 14:50 ` [gentoo-user] " Neil Bothwick
2020-04-11 19:57 ` antlists
2020-04-08 3:14 ` Grant Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4066b87-6ee2-34bb-2b95-4901c2bd4b0a@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox