At 6:52 PM -0600 9/10/02, LuKreme imposed structure on a stream of electrons, yielding: >On Monday, September 9, 2002, at 08:53 PM, Geoff Canyon wrote: >>But the POP3 server doesn't have access to that information? >>[EMAIL PROTECTED] logs in to get his email, and the POP3 server >>doesn't have any way of knowing whether is fred from firstdom.com >>or fred from seconddom.com? > >How could it? Both users are named "fred" > >Or are you suggesting that SIMS break RFC and force the cumbersome >and annoying "[EMAIL PROTECTED]" as the login name?
Others do that, and I'm not clear on where that's at variance with any RFC. RFC1939 is the definitive POP3 standard, but it doesn't actually define any limitations on the argument to the USER command beyond the protocol-wide requirements that all keywords and arguments be printable ASCII characters, and that arguments be <40 characters. There WOULD be breakage of some obscure subsidiary gadgetry defined in RFC's (i.e. the POP3 URL schema) if 2 were to appear in a POP3 account name, but that's a function of other RFC's relying on character limits that just aren't in the standard. -- Bill Cole [EMAIL PROTECTED] ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
