> On 1 Jul 2022, at 10:00, Paul Smith via mailop <mailop@mailop.org> wrote:
>
> On 01/07/2022 09:52, Laura Atkins via mailop wrote:
>>
>>> It has a single MX record pointed at:
>>>
>>> mail.admin.mailchimp.com <http://mail.admin.mailchimp.com/>
>>>
>>> That hostname exists, but it doesn't have an A RECORD.
>>
>> Again, what’s the problem? Not every mailserver needs to have a
>> corresponding website.
> Normally, an MX record would point to an A record.
>
Yeah, I get it now. I thought the complaint was about domains not having
websites. I missed the chained MXs.
> A records are not exclusively for websites, they have many other uses. For
> instance, *ALL* mail servers intended for incoming mail using the standard
> SMTP system must have an A record pointing to them.
>
> Without an A record here, mail to b...@list-manage.com
> <mailto:b...@list-manage.com> has nowhere to go.
>
Which is fine because there are no email addresses in that domain.
> f you don't want to accept mail for a domain, usually, you'd accomplish that
> by simply not having an MX record. Having an MX record which points nowhere
> is odd, but not illegal - it just means that mail is undeliverable.
>
Understood.
>>> It in turn has just a single MX Record.
>>>
>>> inbound-mx1.mailchimpapp.net <http://inbound-mx1.mailchimpapp.net/>
>>>
>>> Kind of a strange MX delegation.. I assume to avoid CNAME's
>>>
>>> But it does seem very strange. Comments anyone? I didn't have an answer
>>> for him..
>>
>> What’s so strange about it?
> 'mail.admin.mailchimp.com' having an MX record is fine, it means that mail to
> 'b...@mail.admin.mailchimp.com <mailto:b...@mail.admin.mailchimp.com>' has
> somewhere to go.
>
> But it doesn't mean that mail to 'b...@list-manage.com
> <mailto:b...@list-manage.com>' has anywhere to go. You can't chain MX records
> like that.
>
Right. I missed that point. Thank you for clarifying.
laura
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
