egh.. hacking the standards is required sometimes. in that
case it *is*. actually i can't understand why some of the people
here argue about that. does anyone have ane example of a mail
software which reject relaying from/to e-mail addresses with
dots in them?
regards,
d.
Q: the same rfc defines that the e-mail address is case insensitive,
but the actual accounts are case sensitive so what will happen
if you have "blabla" and "BlaBla" logins at the same server
and you send an email to blabla@server? what the rfc says about
that?
"William X. Walsh" wrote:
>
> I think you missed his point. As a business, if you tell a customer
> they can't complete this transaction because their ISP gave them a
> non-standard email address, the customer will blame you, not the ISP,
> regardless of how "right" you are about the standard. They will see
> that their email has worked fine up until now, and that the problem
> must be on your end.
>
> Standards are nice, but in this case, it doesn't pay to be rigid about
> them. In this case, by accepting the email, we are not destroying
> interoperability, we are merely being forgiving about the mistakes of
> others. (to the benefit of our customers, as well)
>
> --
> Best regards,
> William mailto:william@userfriendly.com
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:38 EDT