> On 27.01.2024 at 03:23 Grant Taylor via mailop wrote: > On 1/26/24 16:06, Gellner, Oliver via mailop wrote: >> Independent of this I wouldn’t use r...@hostname.example.org as a sender >> address to external recipients. This doesn’t look professional, > > I'll agree that sending from root@<HostFQDN> is not best practice. But I > don't know if it's unprofessional per se.
If I as a customer or business partner would receive emails which are coming from apa...@webserver1.company.tld then I‘d be under the impression that this company lost control of their infrastructure. But maybe that’s just me. >> makes replying to those emails impossible > > I question the veracity of that. > > Including a Reply-To: and / or an MX for <HostFQDN> to a reachable mail > server that is a smart host that knows how to deliver email to a host that's > not directly reachable seems viable to me. I should have been more precise: Technically it’s of course possible to send emails to @hostfqdn, there is nothing special about this email address after all. However the original question in this thread was that it’s too much work to add and maintain TXT entries for all host FQDNs. I conclude from this that the same applies to adding and maintaining MX entries for all host FQDNs, let alone modify all emails to include Reply-To headers. >> and in case hostname.example.org doesn’t have a public IP address it might >> also increase the risk that those messages are treated as spam or rejected, >> because they are coming from an unresolvable domain. > > I question the veracity of anything that balks at a valid MX via smart host > for a <HostFQDN> that is in and of itself unreachble. > > After all, what is the effective difference in a host that's in a private > network using a smart host for outbound and inbound mail and a host usually > fully reachable / on the Internet that happens to be offline do to an > extended power outage caused by a winter storm? I didn’t write that the hosts have to be reachable. Chances are that the FQDN of at least some of the hosts in the company network are not publicly resolvable, because for example they are not reachable from the internet anyway. That means looking up A / AAAA / MX of hostname.example.com would yield NXDOMAIN. This may cause deliverability problems. — BR Oliver ________________________________ dmTECH GmbH Am dm-Platz 1, 76227 Karlsruhe * Postfach 10 02 34, 76232 Karlsruhe Telefon 0721 5592-2500 Telefax 0721 5592-2777 dmt...@dm.de<mailto:dmt...@dm.de> * www.dmTECH.de<http://www.dmtech.de> GmbH: Sitz Karlsruhe, Registergericht Mannheim, HRB 104927 Geschäftsführer: Christoph Werner, Martin Dallmeier, Roman Melcher ________________________________ Datenschutzrechtliche Informationen Wenn Sie mit uns in Kontakt treten, beispielsweise wenn Sie an unser ServiceCenter Fragen haben, bei uns einkaufen oder unser dialogicum in Karlsruhe besuchen, mit uns in einer geschäftlichen Verbindung stehen oder sich bei uns bewerben, verarbeiten wir personenbezogene Daten. Informationen unter anderem zu den konkreten Datenverarbeitungen, Löschfristen, Ihren Rechten sowie die Kontaktdaten unserer Datenschutzbeauftragten finden Sie hier<https://www.dm.de/datenschutzerklaerung-kommunikation-mit-externen-493832>. _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
