On Fri, Dec 29, 2006, Paul J Stevens wrote: > Christoph Schug wrote: > > On Thu, Dec 28, 2006, Paul J Stevens wrote: > > > >> That's incorrect. Email addresses are case-insensitive. > > > > Am I missing something? RFC 2821 clearly states ... [...] > > I would rather expect, that this behaviour is maintained even in some > > backend. Even if it's not common case to have two different email > > addresses [EMAIL PROTECTED] and [EMAIL PROTECTED], IMHO any serious > > email software should be able to behave RFC compliant by default. > > I disagree. Dbmail is *not* an SMTP server so we don't have to follow > smtp rules. I'm sure that if dbmail starts bouncing mail because of > strict case sensitive LHS matching, that would upset a lot of people.
On the otherhand it doesn't make any sense to separate information during the SMTP transport just to intermix it finally at the DBMail backend. Then it should be clearly stated in the README file, that RFC conformant setups like mentioned above cannot be implemented with DBMail. Furthermore man pages need to be fixed up, especially dbmail-lmtpd(8) quoting | dbmail-lmtpd - receive messages from an MTA supporting the Lightweight | Mail Transport Protocol, as specified in RFC 2033. as in return RFC 2033 states (without any further exception regarding the local part of the address) | The LMTP protocol is identical to the SMTP protocol SMTP [SMTP] | [HOST-REQ] with its service extensions [ESMTP], except as modified by | this document. referencing RFC 821, which has been obsoleted by RFC 2821. I agree with you that this is not a very common setup, nevertheless it is explicitly defined by the standard. Thus, it's more a question of ruling principle here. Violating standards intentionally just to make ignorant people happy might not pay out on the long term. -cs _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
