Atomicorp

Posted: **Wed Apr 13, 2011 6:02 pm**

We host all our e-mails on Google Apps, but we use the mail() function in PHP to send out e-mails. This worked perfectly until yesterday, when I updated our server with the latest packages from our ASL subscription. Now all messages being sent from application on our server are not being sent. This is the error I see in the maillog?

I tried checking the host config, the qmail host config, restarting qmail, reconfiguring qmail, restarting the server, but nothing works. Is anybody else having this issue?

Code: Select all

Apr 13 17:03:44 phoenix qmail-queue-handlers[5451]: Handlers Filter before-queue for qmail started ...
Apr 13 17:03:44 phoenix qmail-queue-handlers[5451]: from=#@[]
Apr 13 17:03:44 phoenix qmail-queue-handlers[5451]: to=postmaster@phoenix.fantasydomain.com
Apr 13 17:03:44 phoenix qmail-queue-handlers[5451]: hook_dir = '/var/qmail//handlers/before-queue'
Apr 13 17:03:44 phoenix qmail-queue-handlers[5451]: recipient[3] = 'postmaster@phoenix.fantasydomain.com'
Apr 13 17:03:44 phoenix qmail-queue-handlers[5451]: handlers dir = '/var/qmail//handlers/before-queue/recipient/postmaster@phoenix.fantasydomain.com'
Apr 13 17:03:44 phoenix qmail-queue-handlers[5451]: starter: submitter[5456] exited normally
Apr 13 17:03:44 phoenix qmail-scanner[5439]: Clear:RC:1(127.0.0.1): 0.146767 3132 #@[] postmaster@phoenix.fantasydomain.com failure_notice <130273222410265439@phoenix.fantasydomain.com> orig-phoenix.fantasydomain.com13027322247985439:3132 1302732224.5441-0.phoenix.fantasydomain.com:2940 
Apr 13 17:03:44 phoenix qmail: 1302732224.304003 bounce msg 21823782 qp 5439
Apr 13 17:03:44 phoenix qmail: 1302732224.304042 end msg 21823782
Apr 13 17:03:44 phoenix qmail: 1302732224.304276 new msg 21823781
Apr 13 17:03:44 phoenix qmail: 1302732224.304298 info msg 21823781: bytes 3432 from <#@[]> qp 5456 uid 10015
Apr 13 17:03:44 phoenix qmail: 1302732224.311784 starting delivery 18: msg 21823781 to remote postmaster@phoenix.fantasydomain.com
Apr 13 17:03:44 phoenix qmail: 1302732224.311826 status: local 0/10 remote 1/20
Apr 13 17:03:44 phoenix qmail-remote-handlers[5459]: Handlers Filter before-remote for qmail started ...
Apr 13 17:03:44 phoenix qmail-remote-handlers[5459]: from=#@[]
Apr 13 17:03:44 phoenix qmail-remote-handlers[5459]: to=postmaster@phoenix.fantasydomain.com
Apr 13 17:03:44 phoenix qmail: 1302732224.320933 delivery 18: failure: Sorry,_I_couldn't_find_any_host_named_phoenix.fantasydomain.com._(#5.1.2)/
Apr 13 17:03:44 phoenix qmail: 1302732224.321025 status: local 0/10 remote 0/20
Apr 13 17:03:44 phoenix qmail: 1302732224.321090 triple bounce: discarding bounce/21823781
Apr 13 17:03:44 phoenix qmail: 1302732224.321110 end msg 21823781

Posted: **Thu Apr 14, 2011 2:19 am**

Code: Select all

Sorry,_I_couldn't_find_any_host_named_phoenix.fantasydomain.com._(#5.1.2)/

This indicates that something is wrong with the name resolution. Can you ping phoenix.fantasydomain.com?

What does

Code: Select all

nslookup phoenix.fantasydomain.com

show?

and what do you mean by " the latest packages from our ASL subscription"? yum upgrade? or asl -u? I don't think any of the normal packages or rules from ASL could mess with name resolution or qmail...

Posted: **Thu Apr 14, 2011 10:27 pm**

and what do you mean by " the latest packages from our ASL subscription"? yum upgrade? or asl -u? I don't think any of the normal packages or rules from ASL could mess with name resolution or qmail...

Correct, nothing in ASL or any ASL update touches either qmail or DNS resolution.

Do you mean some packages from the free atomic repository?

Posted: **Sat Apr 16, 2011 12:07 am**

Yes, we use the Atomic repository so it is difficult to separate the ASL packages from the atomic repository packages. This started happening after we did the latest yum update. We have been looking for two days into it and also asked support from Softlayer - but of course, they cannot support us because we have a custom kernel.

Hope to find something soon. Nslookup shows no problem and the hostname seems to be configured correctly.

Posted: **Sat Apr 16, 2011 12:45 am**

they cannot support us because we have a custom kernel.

Wow, thats a very lame excuse on their part! The kernel, as I'm sure you know, has got nothing to do with qmail and is certainly not your problem (it was working fine, the kernel didnt change, hmmm probably not the kernel).

If thats their only excuse for not delivering, then boot into the default kernel, make em fix it, and then boot back into the ASL kernel and go find another hosting company. Thats about as lame a cop out as I've ever heard.

I'm positive the kernel is not your issue, but if thats what you have to do to get someone from using a lame excuse like that to do their job, hey go for it!

Atomicorp

Qmail Broken After the Last Update?

Qmail Broken After the Last Update?

Re: Qmail Broken After the Last Update?

Re: Qmail Broken After the Last Update?

Re: Qmail Broken After the Last Update?

Re: Qmail Broken After the Last Update?