After upgrading to the latest ISPConfig version, I've noticed a problem appearing, at least for me. When emailing to POP3 accounts on the box, there are problems having the mail delivered. Here's the email auto-response from one of the SMTP servers that tried to deliver to the server running ISPConfig. Let me know what could be done to try and solve this. This report relates to a message you sent with the following header fields: Message-id: <[email protected]> Date: Sun, 21 Oct 2007 21:39:59 -0500 From: "DG" <bsregistersATderekgordon.com> To: "AS" <gradrelationsATuaphigam.com> Subject: Re: FW: Phi Alpha - Graduate Chair Your message has been enqueued and undeliverable for 1 day to the following recipients: Recipient address: gradrelationsATuaphigam.com Reason: unable to deliver this message after 1 day Delivery attempt history for your mail: Mon, 22 Oct 2007 22:45:36 -0500 (CDT) Failed MX lookup; try again later Mon, 22 Oct 2007 14:45:30 -0500 (CDT) Failed MX lookup; try again later Mon, 22 Oct 2007 10:44:30 -0500 (CDT) Failed MX lookup; try again later Mon, 22 Oct 2007 06:43:41 -0500 (CDT) Failed MX lookup; try again later Mon, 22 Oct 2007 02:42:41 -0500 (CDT) Failed MX lookup; try again later Mon, 22 Oct 2007 00:42:19 -0500 (CDT) Failed MX lookup; try again later Sun, 21 Oct 2007 22:41:19 -0500 (CDT) Failed MX lookup; try again later Sun, 21 Oct 2007 21:40:39 -0500 (CDT) Failed MX lookup; try again later The mail system will continue to try to deliver your message for an additional 4 days. Any advice? Thanks!
Yes, the MX record points to the main domain on the server so it does exist. From the Named File: www MX 10 www.inter5.org. mail MX 10 mail.uaphigam.com. uaphigam.com. A 207.150.163.134 www A 207.150.163.134 mail A 207.150.163.134
dingle@its:/home/dingle# dig MX uaphigam.com ; <<>> DiG 9.2.4 <<>> MX uaphigam.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11886 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;uaphigam.com. IN MX ;; AUTHORITY SECTION: uaphigam.com. 86400 IN SOA 207.150.163.130. admin.uaphigam.com. 2007102402 28800 7200 604800 86400 ;; Query time: 38 msec ;; SERVER: 207.150.163.131#53(207.150.163.131) ;; WHEN: Thu Oct 25 12:35:53 2007 ;; MSG SIZE rcvd: 87
DIG still doesn't resolve anything that I would say worthwhile. However, I changed a couple lines in the NAMED record and it seems to be working. I tried two emails and both came through... ;; QUESTION SECTION: ;uaphigam.com. IN MX NAMED change: www MX 10 www.inter5.org. mail MX 10 mail.uaphigam.com. -to- uaphigam.com. MX 10 mail.inter5.org.
If you create a MX record, you will have to leave the hostname field empty. Sorry, I did not recognized that in your first post that you had mail and www in the mx hostname field. If you put e.g. mail in the hostname field, the MX record will be for emails in the format [email protected] and not [email protected]
