On 1/16/2020 4:46 PM, @lbutlr wrote:
On 16 Jan 2020, at 09:35, Noel Jones <njo...@megan.vbhcs.org> wrote:
On 1/16/2020 3:19 AM, @lbutlr wrote:
<kr...@hotmal.com>: Domain hotmal.com does not accept mail (nullMX)
So perhaps THIS is the issue on your server, you are not respecting nullMX
replies?
Of course not. It's an old list, and I have no incentive to recheck fake
domains.
Recheck? What do you mean> there is no rechecking the VALID domain is looked
up, it does not have an MX record, so postfix does not attempt to deliver it and
immediately bounces the message back to the user.
No, not immediately. The domains have an A record, so postfix
correctly deems them valid domains. They do not have working mail
service, so mail hangs around until $maximal_queue_lifetime.
Apparently hotmal added a nullMX record sometime since I added them
several years ago - nullMX is a relatively recent invention and I
have no incentive to revisit fake domains that are still fake but
are now better behaved.
Maybe some of the others have nullMX now too, but I'm not going to
bother checking the years-old list. Although I probably could have
done that quicker than the time this thread is taking...
This is what works best for my shockingly non computer literate users. I've
tried it both ways. You're welcome to find your own solutions to your own
problems.
I do not have a problem with people sending mail to Romains that do not accept
mail. As I said, that mail is bounced by postfix because of the lack of an MX
record and never leaves the server.
Good for you and your users. I had users with problems and
complaints, and I solved it in a user-friendly manner that requires
near-zero maintenance. Maybe it's not even necessary anymore. But I
don't really care enough to check.
Of course postfix delivers mail all the time without an MX record,
all that's required is an A record. That's unlikely to change.
I think this covers the topic. Over and out.
-- Noel Jones
