it *is* an rfc issue, local parts should be case-sensitive. While its unlikely to actually break anything real it would be better to make case-sensitivity a configurable option, allowing operators to specify non standard behaviour. The RFC's would expect james-user-ON and james-user-on to be two distinct addresses, and anyone working with this knowledge in mind may be bamboozled if we don't provide standard behaviour as standard, but pleased if we allow them to override it.
> -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: 18 November 2002 08:01 > To: James-Dev Mailing List > Subject: Case sensitivity "Bug"? > > > This isn't an RFC issue, but shouldn't these be case insensitive? > > public boolean matchRecipient(MailAddress recipient) { > if (recipient.getHost().equals(listservAddress.getHost())) { > if (recipient.getUser().equals(listservAddress.getUser() + > "-on") > || recipient.getUser().equals(listservAddress.getUser() + > "-off")) { > return true; > } > } > return false; > } > > That is from CommandForListserv.java. I just ran into a situation where a > user was sending e-mail to the list address with a different case than > expected. > > --- Noel > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
