Hi y’all, Thanks for bringing this up! It looks like this is an oversight from an old setup that hadn't been updated rather than being intentional. We’ll get that updated so that there’s a proper MX record host for list-manage.
-- Matt Gilbert Deliverability Engineer matthew.gilb...@mailchimp.com > On Jul 1, 2022, at 9:44 AM, Bill Cole via mailop <mailop@mailop.org> wrote: > > On 2022-07-01 at 04:52:32 UTC-0400 (Fri, 1 Jul 2022 09:52:32 +0100) > Laura Atkins via mailop <la...@wordtothewise.com> > is rumored to have said: > >>> On 30 Jun 2022, at 22:00, Michael Peddemors via mailop <mailop@mailop.org> >>> wrote: >>> >>> I know this doesn't look professional, but the question from the team >>> member does this contravene any rules or best practices. >>> >>> list-manage.com >>> >>> This domain does not have any A records. >> >> If there’s no website it doesn’t need an A record. Given how that particular >> domain is used there isn’t a lot of reason to host a website there. > > Absolutely. > >> >>> It has a single MX record pointed at: >>> >>> 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. > > No, but every name that is used as a RHS in a MX record MUST have an A record > so sending SMTP clients know where to connect. The defining RFC for the MX > record (974) makes that explicitly clear, even before the days of formally > defined 'MUST' et al. > > >>> It in turn has just a single MX Record. >>> >>> 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? > > It won't generally work. It is specifically called out as wrong in a relevant > RFC. > > RFC974 sayeth: > > > Implementors should understand that the query and interpretation of > the query is only performed for REMOTE. It is not repeated for the > MX RRs listed for REMOTE. You cannot try to support more extravagant > mail routing by building a chain of MXs. (E.g. UNIX.BBN.COM is an MX > for RELAY.CS.NET and RELAY.CS.NET is an MX for all the hosts in .IL, > but this does not mean that UNIX.BBN.COM accepts any responsibility > for mail for .IL). > > > > -- > Bill Cole > b...@scconsult.com or billc...@apache.org > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
