At 8:46 PM -0600 9/11/02, LuKreme imposed structure on a stream of electrons, yielding: >On Wednesday, September 11, 2002, at 07:13 PM, Bill Cole wrote: >>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. > >Well, it is trivially easy to have a user+ domain that exceeds 40 characters.
Sure, but that's not inherent in supporting user@domain as a POP3 login. It just limits what one can have for both fields. That also is a limitation which is quite arbitrary, arguably pointless. Nothing else in the world will break if a POP3 server suddenly starts supporting a 255-character argument to the USER command. >In fact, with a 31 character limit on the OS filename it only takes >a 5 character domain to break 40 characters (@12345.tld = 41 >characters) > > 1 2 3 4 5 6 >123456789012345678901234567890123456789012345678901234567890 >[EMAIL PROTECTED] >[EMAIL PROTECTED] That's an implementation issue, not anything like an RFC compliance issue. >The way to deal with it would be for SIMS to see the requested >hostname of the connection. So if I have two domains, >IloveAlysonHannigan.com and IhateBrateneySpear.com when I connect to >"mail.IhateBrateneySpear.com" as user "fred" SIMS sees the domain >and looks at the right space. I don't know if that's reasonable. >Or heck, possible. That's not really possible unless each name resolves to a different address and the POP3 server knows about that distinction, for which it should not be trusting DNS because nothing should trust DNS for potentially security-sensitive information. So you'd have a big rearchitecting of SIMS (multiple listeners on multiple IP addresses) and a new bit of configuration that would strike many people as redundant. >On the other hand, it is exceedingly minor and I wouldn't suggest >anyone waste more than a few minutes on it, if that. Well, yes. -- 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]>
