Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 107:32:00 |
Calls: | 290 |
Files: | 905 |
Messages: | 76,677 |
Is is just Gmail or is there more I don't understand?
The objective here is just learning how things work. I asked
myself---is it possible to get mail sent to someone@example.com without
an a-record fore example.com? I think the answer should be ``yes''
But after the deletion of the a-record example.com, I noticed Gmail
[...] after the deletion of the a-record example.com, I noticed Gmail
seems not to deliver emails to me anymore. As soon as I created it back
and send a new message, it arrived just fine.
Is is just Gmail or is there more I don't understand?
Followup-To: comp.mail.misc
The objective here is just learning how things work. I asked
myself---is it possible to get mail sent to someone@example.com without
an a-record fore example.com? I think the answer should be ``yes''
because I thought an SMTP would do a type-mx dns query, learn that >example.com mail is handled by mx.example.com, would get the ip address
of mx.example.com and reach the server just fine.
So I made an experiment using my domain---example.com, say. I've been
geting mail just fine every day. Then I deleted the a-record for >example.com. My mail system is not really dependent on it in any way as
far as I know. So the experiment has the set up:
# host -t a example.com
example.com has no A record
# host -t mx example.com
example.com mail is handled by 10 mx.example.com.
# host -t a mx.example.com
mx.example.com has address 1.2.3.4
But after the deletion of the a-record example.com, I noticed Gmail
seems not to deliver emails to me anymore. As soon as I created it back
and send a new message, it arrived just fine.
Is is just Gmail or is there more I don't understand?
The email standards do not require a-record ...
... so this must one of Gmail's quirks.
If you want help, you need to tell us the actual domain. Otherwise we'd
just be guessing what you did.
Salvador Mirzo wrote:
The objective here is just learning how things work. I asked
You might want to read the fine RFCs, e.g., RFC 5321
5.1. Locating the Target Host
....
The lookup first attempts to locate an MX record associated with the
name. [[...]]
myself---is it possible to get mail sent to someone@example.com without
an a-record fore example.com? I think the answer should be ``yes''
Correct.
But after the deletion of the a-record example.com, I noticed Gmail
Since you haven't given real data it's hard to say what you did
wrong. Maybe your MX record is incorrect or hasn't propagated yet.
On 12/22/24 12:07, Kalevi Kolttonen wrote:
The email standards do not require a-record ...
Not for the domain name with the MX record.
But there needs to be an A and / or AAAA record for the FQDN that the
MX record references.
... so this must one of Gmail's quirks.
I wonder if this might be a Google'ism wherein they saw / cached an A
record and are now cross that there isn't one. <something>
<something> security <something> false test result.
[...] What stopped working for me is my IMAP client that
for some reason is not seeing the messages arrive after I deleted the a-record of antartida.xyz, but then I tried another client and it sees
them all, so it's a client (Gnus) configuration issue. (That's
another investigation I need to make, but it's not important.) I
apologize for the confusion.