Re: Null recipient address accepted - wrongly IMO

2007-10-20 Thread Charlie Brady
On Sat, 20 Oct 2007, Peter J. Holzer wrote: On 2007-10-19 11:34:32 -0400, Charlie Brady wrote: On Thu, 18 Oct 2007, David Nicol wrote: FWIW, later on http://cr.yp.to/im/address.html Bernstein says "Do not use an empty box part; it cannot appear in SMTP requests." I think Bernstein is mista

Re: Null recipient address accepted - wrongly IMO

2007-10-20 Thread Peter J. Holzer
On 2007-10-19 11:34:32 -0400, Charlie Brady wrote: > On Thu, 18 Oct 2007, David Nicol wrote: > >FWIW, later on http://cr.yp.to/im/address.html Bernstein says > > > >"Do not use an empty box part; it cannot appear in SMTP requests." I think Bernstein is mistaken here. He should have written "it req

Re: Null recipient address accepted - wrongly IMO

2007-10-19 Thread Ask Bjørn Hansen
On Oct 19, 2007, at 8:34 AM, Charlie Brady wrote: Anyway, will some or all of the patch be accepted and committed? No, we'll bikeshed it to death first! :-) Thanks for sticking through with it. See my other mail, we'll get you setup so you can commit it yourself. - ask -- http://de

Re: Null recipient address accepted - wrongly IMO

2007-10-19 Thread Charlie Brady
On Thu, 18 Oct 2007, David Nicol wrote: FWIW, later on http://cr.yp.to/im/address.html Bernstein says "Do not use an empty box part; it cannot appear in SMTP requests." That's actually an open question, due to what appears to be a drafting error in RFC2821. In 4.1.2 Command Argument Syntax,

Re: Null recipient address accepted - wrongly IMO

2007-10-18 Thread Guy Hulbert
On Thu, 2007-10-18 at 17:29 -0500, David Nicol wrote: > FWIW, later on http://cr.yp.to/im/address.html Bernstein says > > "Do not use an empty box part; it cannot appear in SMTP requests." I should have read past the first paragraph ... Bernstein was writing before RFC 2822 was final, I believe.

Re: Null recipient address accepted - wrongly IMO

2007-10-18 Thread Ask Bjørn Hansen
On Oct 18, 2007, at 9:27 AM, Charlie Brady wrote: qpsmtpd currently accepts <""@domain.name> as a recipient address, and (unless rejected for some other reason) will queue to @domain.name. I don't think conforms with RFC2821, and I don't think it's ever needed. I thought it was technic

Re: Null recipient address accepted - wrongly IMO

2007-10-18 Thread David Nicol
FWIW, later on http://cr.yp.to/im/address.html Bernstein says "Do not use an empty box part; it cannot appear in SMTP requests."

Re: Null recipient address accepted - wrongly IMO

2007-10-18 Thread Guy Hulbert
On Thu, 2007-10-18 at 12:27 -0400, Charlie Brady wrote: > qpsmtpd currently accepts <""@domain.name> as a recipient address, and > (unless rejected for some other reason) will queue to @domain.name. > I don't think conforms with RFC2821, and I don't think it's ever needed. RFC 2821 says that loca

Null recipient address accepted - wrongly IMO

2007-10-18 Thread Charlie Brady
qpsmtpd currently accepts <""@domain.name> as a recipient address, and (unless rejected for some other reason) will queue to @domain.name. I don't think conforms with RFC2821, and I don't think it's ever needed. This patch to check_badrcptto would fix: sub hook_rcpt { my ($self, $transac