Unroutable Address (Forwards)

[jldurham6]

I have an interesting problem. All of my existing forwards work but when I create a new one I get a mailer daemon back that says unroutable address (Pasted below). If I create it as a pop account the email works. I've tested this on 5 of the domains on my server and just noticed this within the last couple of days. I haven't made any changes to the server other than the DA update to the latest version a few weeks ago.

I've already gone through the forum for this specific error and checked DNS settings and folder and file permissions. I've even reinstalled Exim using the script and also following the instruction to replace the .conf file and .pl file. Everything looks good so I don't know what to do next. I'll post whatever anyone needs.

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

XXX@proitsolutions.us
(ultimately generated from YYY@proitsolutions.us)
Unrouteable address
XXX@proitsoloutions.us
(ultimately generated from YYY@proitsolutions.us)
Unrouteable address




Thanks
Jared Durham
Professional IT Solutions

[nobaloney]

Do you have working forwards for proitsolutions.us?

Check from your shell login to see what you get for:

$ dig proitsolutions.us mx
Jeff

[jldurham6]

Here's what I get, thanks for the quick reply. I think it's wierd that regular pop addresses work fine just not forwarded boxes..


[root@da ~]# dig proitsolutions.us mx

; <<>> DiG 9.2.5 <<>> proitsolutions.us mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1645
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

;; QUESTION SECTION:
;proitsolutions.us. IN MX

;; ANSWER SECTION:
proitsolutions.us. 14400 IN MX 10 mail.proitsolutions.us.

;; AUTHORITY SECTION:
proitsolutions.us. 14400 IN NS ns2.ciruspc.com.
proitsolutions.us. 14400 IN NS ns1.ciruspc.com.

;; ADDITIONAL SECTION:
mail.proitsolutions.us. 14400 IN A 208.39.218.230
ns1.ciruspc.com. 14400 IN A 208.39.218.230
ns2.ciruspc.com. 14400 IN A 208.39.218.231

;; Query time: 1 msec
;; SERVER: 208.39.218.230#53(208.39.218.230)
;; WHEN: Sat Mar 24 14:29:33 2007
;; MSG SIZE rcvd: 151

[jldurham6]

[root@da ~]# dig ciruspc.com mx

; <<>> DiG 9.2.5 <<>> ciruspc.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21396
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

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

;; ANSWER SECTION:
ciruspc.com. 14400 IN MX 10 mail.ciruspc.com.

;; AUTHORITY SECTION:
ciruspc.com. 14400 IN NS ns2.ciruspc.com.
ciruspc.com. 14400 IN NS ns1.ciruspc.com.

;; ADDITIONAL SECTION:
mail.ciruspc.com. 14400 IN A 208.39.218.230
ns1.ciruspc.com. 14400 IN A 208.39.218.230
ns2.ciruspc.com. 14400 IN A 208.39.218.231

;; Query time: 1 msec
;; SERVER: 208.39.218.230#53(208.39.218.230)
;; WHEN: Sat Mar 24 14:33:24 2007
;; MSG SIZE rcvd: 134

[root@da ~]#

[jldurham6]

[root@da ~]# dig dredsdomain.com mx

; <<>> DiG 9.2.5 <<>> dredsdomain.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2465
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

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

;; ANSWER SECTION:
dredsdomain.com. 14400 IN MX 10 mail.dredsdomain.com.

;; AUTHORITY SECTION:
dredsdomain.com. 14400 IN NS ns2.ciruspc.com.
dredsdomain.com. 14400 IN NS ns1.ciruspc.com.

;; ADDITIONAL SECTION:
mail.dredsdomain.com. 14400 IN A 208.39.218.230
ns1.ciruspc.com. 14400 IN A 208.39.218.230
ns2.ciruspc.com. 14400 IN A 208.39.218.231

;; Query time: 2 msec
;; SERVER: 208.39.218.230#53(208.39.218.230)
;; WHEN: Sat Mar 24 14:33:53 2007
;; MSG SIZE rcvd: 146

[root@da ~]

[nobaloney]

These all look fine.

Good, but bad because now we don't know why you're having the problem.

Are you using an original exim.conf file or have you made changes?

Can you post the top ten lines from your exim.conf file?

Jeff

[jldurham6]

Well it's the default one, I did a reinstall of Exim so it should be the one DA generated. Let me know if this helps. I appreciate you helping me out.

Jared

######################################################################
# SpamBlocker.exim.conf.2.0-release #
# Runtime configuration file for DirectAdmin/Exim 4.24 and above #
######### IMPORTANT ########## IMPORTANT ########## IMPORTANT ########
# WARNING! Be sure to back up your previous exim.conf file before #
# attempting to use this exim.conf file. #
# #
# Do may not use this exim.conf Exim configuration file unless you #
# make the required modifications to your Exim configuration #
# following the instructions in the README file included in this #
# distribution.

[nobaloney]

If you've installed this file and exim is running and not failing, then I can't see any reason why this is happening; you'll need to have someone look inside your server.

Jeff