3 ms·
I completely disagree! This is not a reasonable choice. Email forms must confirm to the RFC standards or else there is no standard. The biggest offender I've ru
by chinpokomon 13y ago
I completely disagree! This is not a reasonable choice. Email forms must confirm to the RFC standards or else there is no standard. The biggest offender I've run into is Yahoo. Yahoo's email address filtering won't allow me to use my email address because they reject my TLD. Even lousier, their technical support form also rejects my email address, so I can't even send them email to have them correct the problem.
- rahimnathwani 13y agoI presume you mean the SMTP RFC standards. If so, then it would be unreasonable to respond with 501 (Syntax error in parameters or arguments), just because they don't like your email address format or TLD. However, if I'm offering a service and collecting email addresses as part of that service, my mail form could do additional validation (e.g. I might not want to collect email addresses from the UK (.co.uk) or from .edu or from people with 'john' in their email address. I'm not violating an RFC with my email form, which may provide some benefit (e.g. stop fake email addresses, reject customers I don't care about) at the expense of losing/angering some other customers. That's a business question, not a standards issue. (BTW - I've never restricted email addresses on a form in this way, but can empathise with those who do)