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

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

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 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 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