Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-11 Thread John Stoffel
> "Alice" == Alice Wonder writes: Alice> On 2/7/19 2:52 PM, Bill Cole wrote: Alice> *snip* >> >> But your core point is valid: mailing from an AWS instance (or from >> anywhere on an IP with a programmatically derived PTR) in general is >> going to work poorly. There is too little accounta

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-11 Thread Matus UHLAR - fantomas
> On 06.02.19 02:42, Patton, Matthew [Contractor] wrote: I learned the hard way that if you don't set $myhostname to a FQDN you can quickly end up on a black list despite having valid SPF records. > > any evidence about this? On 08.02.19 14:42, Patton, Matthew [Contractor] wrote:

RE: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-08 Thread Patton, Matthew [Contractor]
> > On 06.02.19 02:42, Patton, Matthew [Contractor] wrote: > I learned the hard way that if you don't set $myhostname to a FQDN > you can quickly end up on a black list despite having valid SPF > records. > > > > any evidence about this? The host has both forward and reverse registe

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-07 Thread Alice Wonder
On 2/7/19 2:52 PM, Bill Cole wrote: *snip* But your core point is valid: mailing from an AWS instance (or from anywhere on an IP with a programmatically derived PTR) in general is going to work poorly. There is too little accountability for abuse from the AWS IP pool for it to merit a default

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-07 Thread Bill Cole
On 7 Feb 2019, at 14:09, Matus UHLAR - fantomas wrote: On 06.02.19 02:42, Patton, Matthew [Contractor] wrote: I learned the hard way that if you don't set $myhostname to a FQDN you can quickly end up on a black list despite having valid SPF records. any evidence about this? Returning to th

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-07 Thread Matus UHLAR - fantomas
On 06.02.19 02:42, Patton, Matthew [Contractor] wrote: I learned the hard way that if you don't set $myhostname to a FQDN you can quickly end up on a black list despite having valid SPF records. any evidence about this? Returning to the OP's question, Postfix does append $mydomain to the auto

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-06 Thread Peter
On 06/02/19 17:36, Patton, Matthew [Contractor] wrote: In Internet-connected SMTP (which is something like 99.9% of installations) ... The number of people who run mail servers isolated from the Internet is vanishingly small. Why cater to the oddball environment where anything goes? ... T

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-05 Thread Viktor Dukhovni
> On Feb 6, 2019, at 12:50 AM, Patton, Matthew [Contractor] > wrote: > > By perverting the very definition of what is a hostname, Postfix [...] Such a belligerent, indignant tone never endears an OP to the project maintainers, and creates a strong disincentive to making any effort to address th

RE: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-05 Thread Patton, Matthew [Contractor]
> I repeat, you misunderstood the documentation. Postfix computes its best > guess at the FQDN when you DO NOT *explicitly* set myhostname, in main.cf. The issue is NOT that I wanted Postfix to willy-nilly mangle $myhostname into a FQDN on my behalf. If there were a private keyword of $fqdn th

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-05 Thread Viktor Dukhovni
> On Feb 5, 2019, at 11:36 PM, Patton, Matthew [Contractor] > wrote: > >> You misunderstood the documentation, the domain is only appended when >> computing the *default* value > > No I didn't misunderstand the documentation. I provided both pieces of > information via main.cf and I damn well

RE: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-05 Thread Patton, Matthew [Contractor]
> If that's what you want, and you're setting myhostname explicitly, then it is > your > responsibility to do that. This allows users who do want dotless hostnames to > have those if that's right for them. In Internet-connected SMTP (which is something like 99.9% of installations) if $myh

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-05 Thread Viktor Dukhovni
On Wed, Feb 06, 2019 at 02:42:58AM +, Patton, Matthew [Contractor] wrote: > > Returning to the OP's question, Postfix does append $mydomain to the > > automatically derived value of $myhostname when the latter is not > > explicitly set > > > > -

RE: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-05 Thread Patton, Matthew [Contractor]
> Returning to the OP's question, Postfix does append $mydomain to the > automatically derived value of $myhostname when the latter is not explicitly > set > in main.cf and is not fully qualified. Except that it doesn't. (or I misunderstood what you wrote) I set $myhostname = 'smtp'. $mydomain w

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-05 Thread Viktor Dukhovni
> On Feb 5, 2019, at 3:50 PM, Wietse Venema wrote: > > If someone registers the domain 'foo', then that is a valid name, > and they have right to use "helo foo", "mail from:user@foo", and > so on. > > The problem is not sending helo without a dot, the problem is sending > helo with a name that d

Re: SMTP_HELO_NAME can cause Blacklist triggers

2019-02-05 Thread Wietse Venema
Patton, Matthew [Contractor]: > I learned the hard way that if you don't set $myhostname to a FQDN > you can quickly end up on a black list despite having valid SPF > records. The documentation is IMO insufficiently clear that > $myhostname MUST be fully qualified and that Postfix will NOT tack >