Viktor Dukhovni:
> On Tue, Mar 05, 2013 at 11:16:18PM -0500, Wietse Venema wrote:
>
> > Viktor Dukhovni:
> > > Arguably, all lookup keys in tables should be in "external" (RFC-5322)
> > > form. The suggested doubling of internal spaces is far less important
> > > in practice that avoiding the loss
On Wed, Mar 06, 2013 at 03:51:28AM +, Viktor Dukhovni wrote:
> On Fri, Mar 01, 2013 at 03:19:42PM +0100, Bastian Blank wrote:
> > - The ldap server sanitices the query to (mail=t...@example.com) as
> > mandated by RFC 4717, 4.2.3; it removes the insignificant space.
> I see the "insignificant
On Tue, Mar 05, 2013 at 11:16:18PM -0500, Wietse Venema wrote:
> Viktor Dukhovni:
> > Arguably, all lookup keys in tables should be in "external" (RFC-5322)
> > form. The suggested doubling of internal spaces is far less important
> > in practice that avoiding the loss of leading spaces.
>
> Whic
Viktor Dukhovni:
> Arguably, all lookup keys in tables should be in "external" (RFC-5322)
> form. The suggested doubling of internal spaces is far less important
> in practice that avoiding the loss of leading spaces.
Which external form?
- RFC 5321 and 5322 have different rules.
- Worse, The ma
On Fri, Mar 01, 2013 at 03:19:42PM +0100, Bastian Blank wrote:
> I found that one MTA bounced several mails. The mails where sent to
> " test"@example.com and accepted by Postfix. The backend LMTP then
> rejected the mails.
>
> This is what I found out:
> - RCPT TO:<" test"@example.com>
> - The
Hi
I found that one MTA bounced several mails. The mails where sent to
`" test"@example.com' and accepted by Postfix. The backend LMTP then
rejected the mails.
This is what I found out:
- RCPT TO:<" test"@example.com>
- The ldap table gets the sanitized address: ` t...@example.com'
(note the l
