[qmailtoaster] CNAME lookup failed temporarily.... again.

Hey all, A couple of days ago, my server was complaining with "CNAME lookup failed temporarily" when delivering emails to domain "repsol.com". At first i couldn't understand what the problem was. Querying MX records for that domain returned valid results. I turned to the dns caching server,

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Hi, I was hit by this error on a server running qmail-toaster-1.03-1.3.22 This patch is not included by default in the toaster qmail package? Strange thing is that the error came from a host that has proper MX records (MX pointing to a A record, not CNAME), so I am wondering what exactly is

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Eric, very many thanks for this. I've done the upgrade using the RPMs that you provided and, touch wood, everything seems to be going smoothly. The only problem that I encountered (so far) was with authenticating on submission. This turned out to be a softlimit issue: softlimit had reverted

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Angus, qmail-toaster (and pop3d) i386 RPMS (CNAME lookup removed) in this folder: ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/5/development/i386/ On 2/15/2018 7:16 AM, Angus McIntyre wrote: I'm running a fairly ancient qmail (netqmail-1.0.5, according to the manual) on CentOS 5, and I'm

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Angus, qmail-toaster ( and pop3d) x86_64 RPMS (CNAME lookup removed) in this folder: ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/5/development/x86_64/ On 2/15/2018 7:16 AM, Angus McIntyre wrote: I'm running a fairly ancient qmail (netqmail-1.0.5, according to the manual) on CentOS 5, and

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Jeff, I see your msg below. I have moved boxes around. I found easy to create the new users on the new box and rsync the data over from the old box to the new.. Cleaner and much faster way. Anyhow, that’s my two cents here! Remo > On Feb 15, 2018, at 7:04 AM, Eric Broch

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Angus, is this a 32bit version or 64bit version? On 2/15/2018 7:16 AM, Angus McIntyre wrote: I'm running a fairly ancient qmail (netqmail-1.0.5, according to the manual) on CentOS 5, and I'm starting to get bitten with increasing frequency by the 'CNAME lookup failed temporarily' bug. I

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Thanks for that Jeff, yes YMMV and every situation is different, my old server was a mysql version and didn't have those challenges. For sure set up the new box and test things prior to changing DNS. Until you change DNS, everything is still on the old

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Angus - I would be very cautious about switching if you've been using the non-mysql (cdb) version of the qmail toaster and you have many domains on the mailserver. You'll have to run a bunch of scripts to convert vpasswd and the dot-qmail forwards to the mysql format. And each domain has to be

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

For what it's worth, I was in the same boat last year and made the decision to move it to a new server. Set up a new CentOS 7 box as a virtual server at linode. Which was very painless. The install of the toaster on that box was a breeze, the guys have

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

that is, a version of qmail with cname lookup removed per Dan Bernstein On 2/15/2018 7:21 AM, Eric Broch wrote: I'll try to have a compiled version for centos 5 in a couple of hours...will let you know. On 2/15/2018 7:16 AM, Angus McIntyre wrote: I'm running a fairly ancient qmail

[qmailtoaster] CNAME lookup failed temporarily -- workarounds?

I'm running a fairly ancient qmail (netqmail-1.0.5, according to the manual) on CentOS 5, and I'm starting to get bitten with increasing frequency by the 'CNAME lookup failed temporarily' bug. I urgently need to build a new host with an up-to-date OS and the latest version of qmail and move

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

Good I figured that might be the issue. Will contact them directly and let them know hey have a misconfiguration at hand. Thanks a lot guys. Your help was much appreciated! Sent from my iPhone > On 05 Apr 2016, at 17:31, Aleksander Podsiadły wrote: > > W dniu 05.04.2016, wto o

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

W dniu 05.04.2016, wto o godzinie 09∶40 +0200, użytkownik Sebastian Grewe napisał: > I am currently getting this error message when trying to send a mail > to a domain (audi-kiel.de). There is no domain audi-kiel.de, there is only host www.audi-kiel.de. 8<-- [alex@alexia ~]$ host -a audi-kiel.de

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

Same for the MX but can't test ANY yet. But since your reply is empty it seems that could explain it? Sent from my iPhone > On 05 Apr 2016, at 16:47, Tony White wrote: > > What results do you get when you dig on the qmail server? > > If I dig here I get ... > >

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

What results do you get when you dig on the qmail server? If I dig here I get ... [root@indialau]# dig @61.88.88.88 mx audi-kiel.de ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.6 <<>> @61.88.88.88 mx audi-kiel.de ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<-

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

Sadly not right now but I can probably get access to one this week. And since it's not a common address I send to and my contact there is not available right now I am not sure we can easily test this. I just hope this will stay a single issue and not suddenly crop up with more domains. Will

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

Another question, do you have another QMT that you could send it from, so it can determine that it's not just something with that particular QMT you're running? If you need I could test for you. On 4/5/2016 8:14 AM, Sebastian Grewe wrote: Yes that works so it seems to be a Qmail specific

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

Yes that works so it seems to be a Qmail specific issue. Any hints what to check are appreciated. Sent from my iPhone > On 05 Apr 2016, at 16:04, Sebastian Grewe wrote: > > Silly me, of course I forgot to do that too. > > Anyway, I sent a mail and will check if they send

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

Silly me, of course I forgot to do that too. Anyway, I sent a mail and will check if they send a reply now or if I get another bounce message. Looks fishy though and I still think they changed something that’s causing this. Cheers and thanks, Sebastian > On 05 Apr 2016, at 15:00, Eric

Re: [qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

Did you try sending it from another account like hotmail? On 4/5/2016 1:40 AM, Sebastian Grewe wrote: dig mx audi-kiel.de

[qmailtoaster] CNAME lookup failed temporarily (#4.4.3)

Hey List! I am currently getting this error message when trying to send a mail to a domain (audi-kiel.de). I Googled and figured out that it’s caused by Qmail not handling the ANY DNS request properly when exceeding 512 bytes in answers. Strangely this was linked to a DNS patch in Qmail but

Re: [qmailtoaster] cname lookup failed

Rajesh, Looking at the spec file for CentOS 6 I have: Patch6:qmailtoaster-big-dns.patch And looking at the build.txt http://mirror2.qmailtoaster.com/current/CentOS/6/x86_64/qmail-1.03-0.qt.el6.x86_64.buildlog.txtI have: + echo 'Patch #6 (qmailtoaster-big-dns.patch):' Patch #6

[qmailtoaster] cname lookup failed

hi qmailtoaster 64 bit latest version, on centos 6.6 64 bit version i have bind installed on the same server resolv.conf uses 127.0.0.1 and 8.8.8.8 in the same order. i am getting a frequent errors in the send log mentioning cname lookup failed especially while sending to office 365 or google

[qmailtoaster] CNAME lookup failed temporarily. (#4.4.3)

Hi folks, This probably been covered somewhere before it is so frustrating I want to see if any one can explain this issue. me...@adomain.com.au: CNAME lookup failed temporarily. (#4.4.3) I'm not going to try again; this message has been in the queue too long. The question is this... dig mx

Re: [qmailtoaster] CNAME lookup failed temporarily. (#4.4.3)

Hi Fabian, Turns out it was something like that. The DNS for the remote mail server was utterly screwed up. After 40 minutes of testing here to assure my client it was not my mail server, the DNS entries for the remote magically fixed them selves and the clients email left the queue nicely.

Re: [qmailtoaster] CNAME lookup failed temporarily. (#4.4.3)

Maybe related to this: http://serverfault.com/questions/189366/cname-lookup-failed-temporarily-4-4-3 ??? - Sincerely, Fabian Santiago Sent from my iPhone On Apr 30, 2015, at 3:52 AM, Tony White t...@ycs.com.au wrote: CNAME lookup failed temporarily. (#4.4.3)

Re: [qmailtoaster] CNAME lookup failed temporarily. (#4.4.3)

Yes, that error is usually a DNS issue -- however, sometimes it is an issue with the QMT server's DNS resolution. I've been through this a number of times with people -- your mail server has no need of being a DNS server as well, but it will rely HEAVILY on whatever DNS server you provide it

Re: [qmailtoaster] CNAME lookup failed temporarily. (#4.4.3)

Hi Dan, Correct in all but in this case it actually was their DNS screwed up. I use dnsmasq as my resolver. It easy to configure and quick. It also seems to handle oversized responses as well. Thanks. best wishes Tony White On 1/05/2015 04:12, Dan McAllister wrote: Yes, that error is

[qmailtoaster] Cname Lookup Failed Temporarily - Patch Solution

Hello, I have been recently realized a problem / BUG common to so far 3 qmail toaster installs, that of the dreaded: --- CNAME lookup failed temporarily. (#4.4.3) I'm not going to try again; this message has been in the queue too long. --- found at /var/log/qmail/send/current

Re: [qmailtoaster] Cname Lookup Failed Temporarily - Patch Solution

Hi, Do you run your own DNS caching server? If not try using dnsmasq, simple to install and configure. It might solve your issue as I cannot find that response in my logs. best wishes Tony White On 27/03/2015 04:59, Edwin C wrote: Hello, I have been recently realized a problem / BUG

RE: [qmailtoaster] Cname Lookup Failed Temporarily - Patch Solution

the cname lookup failed temporarily error. I will try dnsmasq. Thank you for the clue. Date: Fri, 27 Mar 2015 11:11:04 +1100 From: t...@ycs.com.au To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Cname Lookup Failed Temporarily - Patch Solution Hi, Do you

[qmailtoaster] CNAME Lookup failed

Hi All, One of our user send email to our clients and he got below message. Please let me know how to fix this kind of issue.It's shows queue too long. This queue issue from our server or recipient server. CNAME lookup failed temporarily. (#4.4.3) I'm not going to try again; this message has been

RE: [qmailtoaster] CNAME Lookup failed

admin From: ChandranManikandan [mailto:kand...@gmail.com] Sent: Friday, September 06, 2013 2:42 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] CNAME Lookup failed Hi All, One of our user send email to our clients

Re: [qmailtoaster] CNAME Lookup failed

** ** ** ** ** ** *From:* ChandranManikandan [mailto:kand...@gmail.com] *Sent:* Friday, September 06, 2013 2:42 PM *To:* qmailtoaster-list@qmailtoaster.com *Subject:* [qmailtoaster] CNAME Lookup failed ** ** Hi All, One of our user send

RE: [qmailtoaster] CNAME Lookup failed

[mailto:kand...@gmail.com] Sent: Friday, September 06, 2013 2:42 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] CNAME Lookup failed Hi All, One of our user send email to our clients and he got below message. Please let me know how to fix this kind of issue.It's shows queue too long

Re: [qmailtoaster] CNAME Lookup failed

** ** ** ** ** ** *From:* ChandranManikandan [mailto:kand...@gmail.com] *Sent:* Friday, September 06, 2013 3:33 PM *To:* qmailtoaster-list@qmailtoaster.com *Subject:* Re: [qmailtoaster] CNAME Lookup failed ** ** Hi Vivek, do i need install in our server or recipient server. And after install do

Re: [qmailtoaster] CNAME Lookup failed

** ** ** ** ** ** *From:* ChandranManikandan [mailto:kand...@gmail.com] *Sent:* Friday, September 06, 2013 2:42 PM *To:* qmailtoaster-list@qmailtoaster.com *Subject:* [qmailtoaster] CNAME Lookup failed ** ** Hi All, One of our

RE: [qmailtoaster] CNAME Lookup failed

No need, but first line should be nameserver 127.0.0.1 From: ChandranManikandan [mailto:kand...@gmail.com] Sent: Friday, September 06, 2013 4:39 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] CNAME Lookup failed Hi Vivek, I made my resolv.conf file our isp two

Re: [qmailtoaster] CNAME Lookup failed

Just to throw my 2-cents worth in... If the other (receiving) domain is using an MX record value that is a CNAME, this error can show... in such a case, this is not a name resolver error, but rather a DNS error. It is a violation of the RFCs for the MX record value to resolve to

Re: [qmailtoaster] CNAME Lookup failed

Dan, I agree. I think this is much more appropriate than changing your server configuration based on a failed CNAME lookup. That's like changing the engine because you ran out of gas. On 09/06/2013 08:04 AM, Dan McAllister wrote:

Re: [qmailtoaster] CNAME lookup failed temporarily. (#4.4.3) error

On 24/06/2012 20:29, Maxwell Smart wrote: On 06/24/2012 11:18 AM, postmas...@seawise-chartering.co.uk wrote: Hello all, I am getting this error if I an e-mail is sent from qmail-toaster server. If I try to send an e-mail

Re: [qmailtoaster] CNAME lookup failed temporarily. (#4.4.3) error

This is what I get... # dig mail.ru ; DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5_7.1 mail.ru ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 25377 ;; flags: qr rd ra; QUERY: 1, ANSWER:

Re: [qmailtoaster] CNAME lookup failed temporarily. (#4.4.3) error

On 25/06/2012 21:18, Postmaster wrote: This is what I get... # dig mail.ru ; DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5_7.1 mail.ru ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY,

[qmailtoaster] CNAME lookup failed temporarily. (#4.4.3) error

Hello all, I am getting this error if I an e-mail is sent from qmail-toaster server. If I try to send an e-mail from any different server, the e-mail goes through without any issues. The error message comes up out of blue and an intermittent error. I suppose the problem could be with DNS? Any

Re: [qmailtoaster] CNAME lookup failed temporarily. (#4.4.3) error

On 06/24/2012 11:18 AM, postmas...@seawise-chartering.co.uk wrote: Hello all, I am getting this error if I an e-mail is sent from qmail-toaster server. If I try to send an e-mail from any different server, the e-mail goes through without any issues. The

[qmailtoaster] CNAME lookup failed temporarily. (#4.4.3)

Hi All, I'm getting CNAME lookup failed temporarily. (#4.4.3) fairly frequently trying to email yahoo.com and gmail.com domains. Can someone confirm if QmailToaster is patched with Big-DNS patch? According to the wiki it is (its at the bottom of this list)

[qmailtoaster] CNAME lookup failed temporarily. (#4.4.3)

Dear All, we have a qmail server for several years and running without any problem. Few days ago, one customer forward me a error msg, which is --error msg start--- Hi. This is the qmail-send program at yahoo.com. I'm afraid I wasn't able to deliver

Re: [qmailtoaster] CNAME Lookup

that is fun coming from spammers! Geo. - Original Message - From: Jake Vickers [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Monday, July 24, 2006 11:38 AM Subject: Re: [qmailtoaster] CNAME Lookup Warren (mailing lists) wrote: Mail eXchangers should never be CNAMEs. If you find

Re: [qmailtoaster] CNAME Lookup

] CNAME Lookup Warren (mailing lists) wrote: Mail eXchangers should never be CNAMEs. If you find anyone who has an MX record pointing to a CNAME rather than to an A record, or even to an IP address they are configured incorrectly. W Correct, according to the RFC. I tried to tell

Re: [qmailtoaster] CNAME Lookup

] CNAME Lookup Warren (mailing lists) wrote: Mail eXchangers should never be CNAMEs. If you find anyone who has an MX record pointing to a CNAME rather than to an A record, or even to an IP address they are configured incorrectly. W Correct, according to the RFC. I tried to tell Sympatico cable

[qmailtoaster] CNAME Lookup

I've got a few users that seem to have repeating CNAME lookup errors that end up being 'severe' enough or persistent enough that the message fails to be deliverd to some recipients. I need to figure out what I can do to fix or work around this. Messages to aol.com addresses seem to be a common

Re: [qmailtoaster] CNAME Lookup

Roxanne Sandesara wrote: I've got a few users that seem to have repeating CNAME lookup errors that end up being 'severe' enough or persistent enough that the message fails to be deliverd to some recipients. I need to figure out what I can do to fix or work around this. Messages to aol.com

Re: [qmailtoaster] CNAME Lookup

Alright. I found the name, and IP, of the mailservers for AOL. I've put one into my smtproutes file. Now ... do I need to stop/start or restart qmail-toaster for this to be effective? On 7/24/06, Jake Vickers [EMAIL PROTECTED] wrote: Roxanne Sandesara wrote: I've got a few users that seem to

Re: [qmailtoaster] CNAME Lookup

Roxanne Sandesara wrote: Alright. I found the name, and IP, of the mailservers for AOL. I've put one into my smtproutes file. Now ... do I need to stop/start or restart qmail-toaster for this to be effective? Just to be safe, I would do a qmailctl restart.

Re: [qmailtoaster] CNAME Lookup

Mail eXchangers should never be CNAMEs. If you find anyone who has an MX record pointing to a CNAME rather than to an A record, or even to an IP address they are configured incorrectly. W Jake Vickers wrote: Roxanne Sandesara wrote: Alright. I found the name, and IP, of the mailservers for

Re: [qmailtoaster] CNAME Lookup

They didn't have CNAMEs. But I'm getting CNAME errors trying to send to them. If you can tell me /why/ I'm getting CNAME errors when people are trying to send to them, great, I'll listen, learn, and try to use that information to fix my problems. But for right now, Jake's offer of solution is my

Re: [qmailtoaster] CNAME Lookup

Warren (mailing lists) wrote: Mail eXchangers should never be CNAMEs. If you find anyone who has an MX record pointing to a CNAME rather than to an A record, or even to an IP address they are configured incorrectly. W Correct, according to the RFC. I tried to tell Sympatico cable that

Re: [qmailtoaster] CNAME Lookup

Roxie, That wasn;t really meant for you specifically, just a general bit of info for the list. WRT what you are doing, AOL gets really pissed off at people who send much mail if anything does not look right. One of the things they say NOT to do is to put the IPs of their MX servers into your

Re: [qmailtoaster] CNAME Lookup

I suspect that the 'problem' from qmail's standpoint may be the fact that AOL seems to have multiple A records for the same name/server to different IP addresses, for their mail servers. - quote - aol.com.2475IN MX 15 mailin-02.mx.aol.com. aol.com.

Re: [qmailtoaster] CNAME Lookup

That is not a problem with qmail, having multiple ip addresses in an A record is allowed. Could you please post the send log where the mail is rejected? Erik On 7/24/06, Roxanne Sandesara [EMAIL PROTECTED] wrote: I suspect that the 'problem' from qmail's standpoint may be the fact that AOL

Re: [qmailtoaster] CNAME Lookup

All I have is multiple CNAME delays. There is no message explicitly stating that the mail has been rejected. The error within the headers of the e-mail says that it simply isn't going to keep trying, that it has been in the queue too long. I can't find anything like that phraseology in any of the

Re: [qmailtoaster] CNAME Lookup

Feel free to mail me off list On 7/24/06, Roxanne Sandesara [EMAIL PROTECTED] wrote: All I have is multiple CNAME delays. There is no message explicitly stating that the mail has been rejected. The error within the headers of the e-mail says that it simply isn't going to keep trying, that it