Re: new plugin: helo

2012-06-15 Thread Matt Simerson
On Jun 15, 2012, at 12:32 PM, Charlie Brady wrote: > On Fri, 15 Jun 2012, Matt Simerson wrote: > >>> In my experience, reverse DNS is frequently managed (or, frequently, not >>> managed) by an ISP, not by the admin of the mail server. >> >> In my experience, every ISP that provides clients wit

Re: new plugin: helo

2012-06-15 Thread Charlie Brady
On Fri, 15 Jun 2012, Matt Simerson wrote: > > In my experience, reverse DNS is frequently managed (or, frequently, not > > managed) by an ISP, not by the admin of the mail server. > > In my experience, every ISP that provides clients with dedicated IPs > also provides the client with the abili

Re: new plugin: helo

2012-06-15 Thread Matt Simerson
On Jun 15, 2012, at 6:44 AM, Charlie Brady wrote: > On Wed, 13 Jun 2012, Matt Simerson wrote: > >> https://github.com/smtpd/qpsmtpd/pull/29 > > I consider this statement to be troublesome also: > > Per RFC 2821, the HELO hostname must be the FQDN of the sending server or > address literal.

Re: new plugin: helo

2012-06-15 Thread Charlie Brady
On Wed, 13 Jun 2012, Matt Simerson wrote: > https://github.com/smtpd/qpsmtpd/pull/29 I consider this statement to be troublesome also: Per RFC 2821, the HELO hostname must be the FQDN of the sending server or address literal. RFC 2821 doesn't say "must". It says neither should nor must, bu

Re: new plugin: helo

2012-06-15 Thread Charlie Brady
On Wed, 13 Jun 2012, Matt Simerson wrote: > https://github.com/smtpd/qpsmtpd/pull/29 Make sure the HELO hostname has an A or record that matches the senders IP address, and make sure that the senders IP has a PTR that resolves to the HELO hostname. This might sound pedantic, but since