Heloo..
My statistics from 2017-11-14 to 2017-11-30:
Server tonda gut internet connect:
[root@tonda ~]# grep -R "CNAME_lookup" /var/log/qmail | wc -l
2
Server franta no gut internet connect:
[root@franta ~]# grep -R "CNAME_lookup" /var/log/qmail |wc -l
7924
The server has no problem
Is the server that is having the issues using djbdns or BIND? There was a
thread on June 21 that discussed the differences in the way djbdns handles
CNAMES and EDNS, vs the way BIND does, and why it causes delivery issues
for qmail.
-Chris
On Wed, Nov 29, 2017 at 9:02 PM, Eric Broch
The server connects to a BIND DNS server. However, this CNAME issue
apparently has been a problem for a long, long time as noted in the link
Eric provided.
Jeff
On 11/30/2017 9:55 AM, Chris wrote:
Is the server that is having the issues using djbdns or BIND? There
was a thread on June 21
It should only upgrade qmail. Without the '-y' flag you'll have a choice
later in the yum process to decline the update.
On 11/30/2017 8:23 AM, Jeff Koch wrote:
Eric - yum upgrade qmail - which pieces of software does that command
upgrade? Jeff
On 11/30/2017 10:03 AM, Eric Broch wrote:
It'd be interesting to see if an upgrade took care of this. Wouldn't
take much.
# qmailctl stop (Make sure it's really stopped and not in the middle of
a send)
# qmailctl stat
# yum upgrade qmail
# qmailctl start
5 minutes at most.
On 11/30/2017 7:59 AM, Jeff Koch wrote:
I don't think I
