Re: hostname does not resolve to address warning

2020-11-23 Thread Wietse Venema
> postfix/smtpd[24986]: warning: hostname server17-ams1.internet-census.org > does not resolve to address 107.6.163.34: Name or service not known This is a type 4 error (the name->address mapping does not exist). > postfix/smtpd[24986]: connect from unknown[107.6.163.34] > postfix/smtpd[24986]: N

Re: hostname does not resolve to address warning

2020-11-23 Thread Eugene Podshivalov
Thanks for the reply. The warning says that "hostname does not resolve to address" (case #4) but then the log says that connection is rejected because it cannot find a hostname (case #2). So which one is the actual rejection reason? Doesn't it feel a bit confusing? Regards

Re: hostname does not resolve to address warning

2020-11-23 Thread Wietse Venema
Eugene Podshivalov: > Hi all, > I have the following config > > > smtpd_client_restrictions = > > reject_unknown_client_hostname > > smtpd_helo_required = yes > > smtpd_helo_restrictions = > > reject_invalid_helo_hostname, > > reject_non_fqdn_helo_hostname, > > reject_unknown_helo_

Re: hostname does not resolve

2015-02-01 Thread LuKreme
> On Jan 31, 2015, at 8:59 PM, Bill Cole > wrote: > > I do not use that rejection criteria but instead use > reject_unknown_reverse_client_hostname, I do use that, and have for a long time. > which only requires that a PTR exists. On other systems I manage, I mostly DO > use reject_unknown_

Re: hostname does not resolve

2015-01-31 Thread Viktor Dukhovni
On Sun, Feb 01, 2015 at 05:50:44AM +0100, li...@rhsoft.net wrote: > Am 01.02.2015 um 05:45 schrieb Viktor Dukhovni: > >On Sun, Feb 01, 2015 at 05:11:15AM +0100, li...@rhsoft.net wrote: > >>>Nearly every SMTP client using an IP with a PTR whose name does not > >>>resolve back to that IP sends nothi

Re: hostname does not resolve

2015-01-31 Thread li...@rhsoft.net
Am 01.02.2015 um 05:45 schrieb Viktor Dukhovni: On Sun, Feb 01, 2015 at 05:11:15AM +0100, li...@rhsoft.net wrote: Nearly every SMTP client using an IP with a PTR whose name does not resolve back to that IP sends nothing but spam bullshit - in the real world that's not true The message you

Re: hostname does not resolve

2015-01-31 Thread Viktor Dukhovni
On Sun, Feb 01, 2015 at 05:11:15AM +0100, li...@rhsoft.net wrote: > >Nearly every SMTP client using an IP with a PTR whose name does not > >resolve back to that IP sends nothing but spam > > bullshit - in the real world that's not true The message you were responding too was generally helpful wi

Re: hostname does not resolve

2015-01-31 Thread li...@rhsoft.net
Am 01.02.2015 um 04:59 schrieb Bill Cole: On 31 Jan 2015, at 17:33, LuKreme wrote: What should I do about these warnings? Is there any reason not to reject the IPs in question? And if not, how do I do so? mail_version = 2.11.3 warning hostname 102-253-144-216.static.reverse.lstn.net does not r

Re: hostname does not resolve

2015-01-31 Thread Bill Cole
On 31 Jan 2015, at 17:33, LuKreme wrote: What should I do about these warnings? Is there any reason not to reject the IPs in question? And if not, how do I do so? mail_version = 2.11.3 warning hostname 102-253-144-216.static.reverse.lstn.net does not resolve to address 216.144.253.102 hostna