When tech illiterate joe gets himself a shiny new email address and wants
a shiny new domain as well, he might go to you for that domain. You
configure your system to ignore the standards, since you want the
business. When "it doesn't work" it will of course be your fault, at least
in joe's eyes. Have fun helping him configure Netscape or Outlook Express,
or any other software that has _nothing_ to do with domains.
Personally, I don't want to waste my time when everything breaks because
we don't conform to the RFC. Sometimes it's better to have less business.
Mark Collette
hyperbyte inc.
On Fri, 16 Jun 2000, Derek J. Balling wrote:
> Couldn't agree with you more. :)
>
> D
>
>
> At 10:48 AM -0400 6/16/00, Charles Daminato wrote:
> >RFCs are meant to maintain some semblance of a standard. If systems
> >blatantly break these standards, they are running the risk of having a
> >limited compatability with their new standards. I prefer the usual
> >aaabbb@domain myself, keeps things simple :)
> >
> >"Derek J. Balling" wrote:
> >>
> >> You're right.
> >>
> >> So let's not bitch at them if they want ASFL!*&^$.COM
> >>
> >> I mean, you want the business, right? Who cares if it breaks a standard?
> >>
> >> D
> >>
> >> At 9:06 AM -0400 6/16/00, Justin S. wrote:
> >> >I think overall that those types of e-mail addresses should be allowed. It
> >> >doesn't matter if it doesn't go with RFC822 or whatever, because
> >>some people
> >> >are different. It comes down to: do you want the business, or do
> >>you want to
> >> >bitch and moan at the client for having a '.' before the '@'? I'd rather
> >> >have the business any day!
> >> >
> >> >Justin S...
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:38 EDT