Re: "max_use=1" does not work at a situation

2020-09-03 Thread Wietse Venema
kawakami: > Aug 3 15:10:11 dummy postfix/smtpd[5254]: connect from > example.com[X.X.X.X]:56925 Today is September 3. If you want support, provide the configuration you have NOW, and logging that you get NOW with that configuration. postconf -n postconf -P logging If you can't reproduce the

Re: Mail deferred: TLSA lookup error

2020-09-03 Thread Bill Cole
On 3 Sep 2020, at 0:34, Marcel de Riedmatten wrote: Le mercredi 02 septembre 2020 à 23:11 -0400, Bill Cole a écrit : On 2 Sep 2020, at 19:58, Viktor Dukhovni wrote: On Wed, Sep 02, 2020 at 07:09:28PM -0400, Bill Cole wrote: I do not understand why Postfix didn't see that as a reason to gi

Re: Mail deferred: TLSA lookup error

2020-09-03 Thread Bill Cole
On 3 Sep 2020, at 0:43, Viktor Dukhovni wrote: On Wed, Sep 02, 2020 at 11:11:32PM -0400, Bill Cole wrote: [...] Yes, I see the same: [root@be03 ~]# dig @127.0.0.1 _25._tcp.mail.deaecom.gov. tlsa That's NOT the same, you're not asking for "+dnssec", which Postfix does do when resolving D

Re: Mail deferred: TLSA lookup error

2020-09-03 Thread Viktor Dukhovni
On Thu, Sep 03, 2020 at 06:09:23PM -0400, Bill Cole wrote: > > Your resolver claims to have validated the answer (the AD bit is set), > > what do you get with "posttls-finger"? > > [root@be03 ~]# posttls-finger mail.deaecom.gov > posttls-finger: Connected to mail.deaecom.gov[149.101.26.25]:25 >