Dnia 16.01.2020 o godz. 15:46:31 @lbutlr pisze:
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.

On 17.01.20 10:02, Jaroslaw Rafa wrote:
But it is wrong approach. It is a perfectly correct setup to not have an MX
record for a domain, but to have an A record and receive email under that
address.

There is no requirement (and never was) that to receive email you must have
an MX record.

correct, however I've already noticed discussions about such requirements.
Most of them comes out of problems we are discussing in this thread.

While it would take years to implement (afaik MX took years to implement,
too), it would be cleaner than current wild situation.

The nullmx (IN MX .) is one of approaches but must be supported by
mailservers (luckily it is supported by postfix)

but I find it cleaner to only accept mail for domains with MX than for
everyone with A records.

MX record is only a nice shortcut to avoid specifying the full
domain name of the mailserver in the e-mail address, and instead use only the
mailserver's domain part. Instead of "u...@mailserver.domain.com" you type
only "u...@domain.com" - that's what MX record is for. But
"u...@mailserver.domain.com" is still perfectly valid and mail to such
address *has to be* be delivered.

It might be refused, but delivery will still be tried, which leads to our
problem (this thread).

I was recently forced to add a ridiculous MX record to my domain, pointing
back to the same name (eg. "rafa.eu.org MX 10 rafa.eu.org")

I've seen recommendation to do this (just for sure) long ago. --
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
M$ Win's are shit, do not use it !

Reply via email to