On Fri, 11 Feb 2011, Jeroen van Meeuwen (Kolab Systems) wrote:
Hi there,
(This is a re-posted message from our development mailing list.)
In our IRC channel, it was suggested to look at RFC 2821, section 2.4, quoted
as saying:
However, exploiting the case sensitivity of mailbox
Hi there,
(This is a re-posted message from our development mailing list.)
In our IRC channel, it was suggested to look at RFC 2821, section 2.4, quoted
as saying:
However, exploiting the case sensitivity of mailbox local-parts impedes
interoperability and is discouraged.
The problem
Hello,
Am 11.02.2011 14:11, schrieb Jeroen van Meeuwen (Kolab Systems):
Hi there,
(This is a re-posted message from our development mailing list.)
In our IRC channel, it was suggested to look at RFC 2821, section 2.4,
quoted as saying:
However, exploiting the case sensitivity of mailbox
André Schild wrote:
Hello,
Am 11.02.2011 14:11, schrieb Jeroen van Meeuwen (Kolab Systems):
Long story short; the proposal is to ship with a default
lmtp_downcase_rcpt of 1.
Sound OK for me.
When chaning upper/lowercases we always have to consider character sets.
For the user part
Am 11.02.2011 15:06, schrieb Jeroen van Meeuwen (Kolab Systems):
André Schild wrote:
Hello,
Am 11.02.2011 14:11, schrieb Jeroen van Meeuwen (Kolab Systems):
Long story short; the proposal is to ship with a default
lmtp_downcase_rcpt of 1.
Sound OK for me.
When chaning
André Schild wrote:
@bücher.ch is allowed.
In dns this is represented as a IDN encoded name in the form of***
xn--bcher-kva.ch* is the ACE string, and it is this string that is
entered in the DNS.
Fine, let me rephrase;
The IDN-ACE string conversion, while ASCII-only not being a
