3 ms·
> If you have a problem, contact postmaster/webmaster/root/etc. This is a very outdated 1990s mentality. Most modern web users would have no idea that such a
by neilalexander 9y ago
> If you have a problem, contact postmaster/webmaster/root/etc.
This is a very outdated 1990s mentality.
Most modern web users would have no idea that such a thing exists (or should exist), and they're probably the same users who also have no idea that WHOIS exists and know how to find contact details for a domain owner using it.
It's also a little user-hostile to assume that nobody is ever going to question something they receive from an automated system. In that case, why make the user journey unnecessarily difficult by forcing them to find an alternative route to contact you?
- tscs37 9y agoThere is no reason to reply. The emails state as such. A contact email is included. I literally do not care about anyone who thinks they can reply to these emails and I'm not concerned about user hostility. My users aren't the kind of users that will respond to such emails. Again, I don't see a reason to why I need to reply to emails which are explicitly only ever sent if the user chooses to at which point they have been warned about noreply and the emails themselves reinclude such warnings with the proper contact email, especially since this group of users are knowledgeable enough to not reply in the first place.