In message <[email protected]>, Paul Wouters <[email protected]> writes
>On Mon, 15 Jun 2015, John Levine wrote: > >>> Allow the client to lowercase (initially, or as a fallback) - I think >>> everybody agrees there is no harm in this *in practice*, then encode >>> with split base32. ... >> >> No, for two reasons. One is that RFC 5321 clearly says that case >> folding is forbidden, and the mail world is very big. > >And I have repeatedly asking for a single deployment where FOO != foo >and not heard a single answer back. here's one (and it took me about 5 minutes to find it...) <http://www.sevenforums.com/browsers-mail/229536-yahoo-disposable- address-case-sensitivity.html> though you'll see that Yahoo decided it confused too many people and changed it. But that's pragmatism by a large provider introducing a new feature, not "fixing a bug" and certainly (and this is fundamentally John's point) not "having to change my mail system which has been working just fine for the last 30 years". >It is only the least bad way if you make the assumption that I've only >seen made by you. John is an expert on email and so the other experts on email don't need to correct him ... When (implausibly) he says something which is not correct then you will see other email experts (of which there are a few on this list, but probably not all that many) will undoubtedly chip in >That case sensitive mailboxes exist in the real >(non-cardboard box) world. -- Dr Richard Clayton <[email protected]> tel: 01223 763570, mobile: 07887 794090 Computer Laboratory, University of Cambridge, CB3 0FD
signature.asc
Description: PGP signature
_______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
