LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 04-22-2007, 08:15 AM   #1
baronsam
Member
 
Registered: Oct 2003
Posts: 44

Rep: Reputation: 15
applying c.k. davis qmail buffer patch to live qmail server


Hello --

I need to apply Christopher K. Davis' qmail buffer patch to my live production qmail server. (to solve the CNAME lookup failed temporarily problem)

What are the steps I need to take ?

This is a RH9 box, with a qmailrocks install (more or less).

I imagine I need to stop some processes, apply the patch, recompile parts or all of qmail, and restart some processes...

Anything more precise than that would be greatly appreciated,

All best,

--Sam
 
Old 04-22-2007, 09:07 AM   #2
baronsam
Member
 
Registered: Oct 2003
Posts: 44

Original Poster
Rep: Reputation: 15
Actually, it seems that this patch is already part of a patch pack that I installed originally with qmailrocks. So the problem is : why am I getting all this

delivery 19608: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/

for all my messages output by ezmlm ?

--Sam
 
Old 04-22-2007, 02:07 PM   #3
JimBass
Senior Member
 
Registered: Oct 2003
Location: New York City
Distribution: Debian Sid 2.6.32
Posts: 2,100

Rep: Reputation: 49
That looks like a DNS error of some sort. The machine that is trying to send can't find the CNAME it is looking up. I would use the tool "dig" to see if the name has a resolution issue. If the domain you are trying to send to is named example.com, then this command will lookup the mailserver's name and IP -

Code:
dig -t mx example.com
You'll get a mess of IP's and names. Make sure everything resolves to the correct IP of the receiving mail server. If it does resolve correctly, then something is wrong with the configuration of the server.

By the way, running anything on RH9 is an extremely poor choice. That OS is ancient, and hasn't been supported in 2+ years. All the software it installs is just as old. If you like Red Hat, then move up to Red Hat Enterprise 4 or 5, or get the free versions of it, CentOS or Whitebox. Fedora Core 6 is also popular. I doubt that is the source of your errors, but it certainly doesn't help any.

Peace,
JimBass
 
Old 04-22-2007, 02:28 PM   #4
baronsam
Member
 
Registered: Oct 2003
Posts: 44

Original Poster
Rep: Reputation: 15
Thank you for your reply.
dig doesn't seem to return consistent results :

[root@yoruban qmail-send]# dig murez.com

; <<>> DiG 9.2.1 <<>> murez.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7372
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;pams.com. IN MX

;; ANSWER SECTION:
pams.com. 7200 IN MX 10 MAIL.pams.com.

;; ADDITIONAL SECTION:
MAIL.HEADSWELL.com. 2970 IN A 66.119.206.14

;; Query time: 6 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Apr 22 20:25:07 2007
;; MSG SIZE rcvd: 78

[root@yoruban qmail-send]# dig murez.com

; <<>> DiG 9.2.1 <<>> murez.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28858
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;murez.com. IN A

;; ANSWER SECTION:
murez.com. 172800 IN A 205.147.48.4

;; Query time: 287 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sun Apr 22 20:25:42 2007
;; MSG SIZE rcvd: 43

that seems a bit weird.

--Sam
 
Old 04-22-2007, 03:02 PM   #5
JimBass
Senior Member
 
Registered: Oct 2003
Location: New York City
Distribution: Debian Sid 2.6.32
Posts: 2,100

Rep: Reputation: 49
I get consistent results. You got different results because you didn't specify the -t mx part of the command. The first time you asked for a mail exchanger (mx), the second you asked for an A record (default).

Code:
jim@jimsworktop:~$ dig -t mx murez.com

; <<>> DiG 9.3.4 <<>> -t mx murez.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30164
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 4

;; QUESTION SECTION:
;murez.com.                     IN      MX

;; ANSWER SECTION:
murez.com.              172800  IN      MX      10 mail.murez.com.
murez.com.              172800  IN      MX      20 mx2.murez.com.

;; AUTHORITY SECTION:
murez.com.              172800  IN      NS      dns0.zam.net.
murez.com.              172800  IN      NS      dns1.zam.net.

;; ADDITIONAL SECTION:
mail.murez.com.         172800  IN      A       205.147.48.8
mx2.murez.com.          172800  IN      A       205.147.48.3
dns0.zam.net.           172800  IN      A       205.147.48.2
dns1.zam.net.           172800  IN      A       205.147.48.3

;; Query time: 276 msec
;; SERVER: 192.168.68.1#53(192.168.68.1)
;; WHEN: Sun Apr 22 14:51:22 2007
;; MSG SIZE  rcvd: 177
From another location, with different DNS servers:

Code:
jim@ns2:~$ dig -t mx murez.com

; <<>> DiG 9.2.4 <<>> -t mx murez.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25883
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 4

;; QUESTION SECTION:
;murez.com.                     IN      MX

;; ANSWER SECTION:
murez.com.              172800  IN      MX      20 mx2.murez.com.
murez.com.              172800  IN      MX      10 mail.murez.com.

;; AUTHORITY SECTION:
murez.com.              172795  IN      NS      dns0.zam.net.
murez.com.              172795  IN      NS      dns1.zam.net.

;; ADDITIONAL SECTION:
mx2.murez.com.          172800  IN      A       205.147.48.3
mail.murez.com.         172800  IN      A       205.147.48.8
dns0.zam.net.           172795  IN      A       205.147.48.2
dns1.zam.net.           172795  IN      A       205.147.48.3

;; Query time: 184 msec
;; SERVER: 66.207.47.66#53(66.207.47.66)
;; WHEN: Sun Apr 22 15:12:11 2007
;; MSG SIZE  rcvd: 186
So you should be sending to mail.murez.com, and mx2.murez.com. I get consistent addresses for them, 205.147.48.3 and 205.147.48.8.

The output you gave included looking for things like ";; QUESTION SECTION:
;pams.com. IN MX", which makes no sense. You should not be asking for anything having to do with pams.com, as a trace shows the full path from the roots up to your mail exchangers:

Code:
jim@jimsworktop:~$ dig -t mx murez.com +trace

; <<>> DiG 9.3.4 <<>> -t mx murez.com +trace
;; global options:  printcmd
.                       20956   IN      NS      M.ROOT-SERVERS.NET.
.                       20956   IN      NS      A.ROOT-SERVERS.NET.
.                       20956   IN      NS      B.ROOT-SERVERS.NET.
.                       20956   IN      NS      C.ROOT-SERVERS.NET.
.                       20956   IN      NS      D.ROOT-SERVERS.NET.
.                       20956   IN      NS      E.ROOT-SERVERS.NET.
.                       20956   IN      NS      F.ROOT-SERVERS.NET.
.                       20956   IN      NS      G.ROOT-SERVERS.NET.
.                       20956   IN      NS      H.ROOT-SERVERS.NET.
.                       20956   IN      NS      I.ROOT-SERVERS.NET.
.                       20956   IN      NS      J.ROOT-SERVERS.NET.
.                       20956   IN      NS      K.ROOT-SERVERS.NET.
.                       20956   IN      NS      L.ROOT-SERVERS.NET.
;; Received 436 bytes from 192.168.68.1#53(192.168.68.1) in 34 ms

com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
com.                    172800  IN      NS      M.GTLD-SERVERS.NET.
com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
;; Received 487 bytes from 202.12.27.33#53(M.ROOT-SERVERS.NET) in 191 ms

murez.com.              172800  IN      NS      dns0.zam.net.
murez.com.              172800  IN      NS      dns1.zam.net.
;; Received 104 bytes from 192.42.93.30#53(G.GTLD-SERVERS.NET) in 91 ms

murez.com.              172800  IN      MX      10 mail.murez.com.
murez.com.              172800  IN      MX      20 mx2.murez.com.
murez.com.              172800  IN      NS      dns1.zam.net.
murez.com.              172800  IN      NS      dns0.zam.net.
;; Received 177 bytes from 205.147.48.2#53(dns0.zam.net) in 88 ms
There is no mention of pams.com in there, so the DNS on your network is screwy in some way.

Peace,
JimBass
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
How to patch qmail fw12 Linux - Server 1 02-16-2007 09:03 PM
qmail qmailqueue patch teoz Linux - Software 3 06-13-2006 10:07 AM
Can't 'Make' Qmail Patch ServerStorm Linux - Software 2 01-11-2005 10:46 AM
qmail +qmail-qfilter + qmail-scanner-queue+qmail-user-masq.pl problem countcobolt Linux - Networking 0 07-08-2004 12:29 PM
How do I install qmail-queue patch post install of qmail? cmisip Linux - Software 0 04-29-2003 12:10 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 01:42 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration