Trouble with Remote Mail Exchanger and Mail Delivery
Hello,
I have added a new domain account to our server, but the A record is still pointing to the old/existing server because I am not ready to do the live transfer yet. I created a subdomain for testing and pointed it's A record to our server. In the MX entry settings for the new domain (not sub-domain) I have it set to use Remote Mail Exchanger and have entered the remote MX records.
My problem is that when I try to send an email from another local domain on our server to the new domain, it is failing immediately with the following message:
SMTP error from remote mail server after end of data: 550 permanent failure for one or more recipients
If I change the new domain to something else, then the emails to that domain go through successfully to the remote mail server... Do you know why this would happen or what in the world could possibly be going on?
I don't know if it affects anything or helps answer the question, but we are not running a DNS Server locally. I also checked the ect/localdomains and ect/remotedomains and the new domain is listed in the ect/remotedomains.
We also have other clients websites on the server with remote mail exchanger set, but have not experienced any issues with sending mail to them through a local account. They have been set up on the server for quite awhile though so I don't know if that makes a difference as to why emails to them work, but to the new domain don't....
Please help!
-
Hello :) Could you let us know the specific entry in /var/log/exim_mainlog when this happens? EX: exigrep user@domain /var/log/exim_mainlog
Thank you.0 -
Hello :) Could you let us know the specific entry in /var/log/exim_mainlog when this happens? EX:
exigrep user@domain /var/log/exim_mainlog
Thank you.
Is there something specific I should be looking for? Is there somewhere private I can send the log entry or should I just modify all references to IPs, e-mails, and domains?0 -
You are looking for the specific error message when the delivery attempt fails. You can post it here in CODE tags as long as you remove any identifying information about the domain name or server. Thank you. 0 -
I have more information regarding this issue (OP and I know each other). The issue is that Exim is sending mail from the wrong IP address under certain conditions, and an SPF record for the sending domain ending in "-all" will cause some hosts to reject the email. I've not systematically tested each condition to see which triggers this behavior, but these are the conditions that seem to be the logical causes: - ]
- Exim configured to "Send mail from account"s dedicated IP address"
- Sending account has dedicated IP address on server. (x.x.x.100)
- Sending account uses local mail exchanger.
- Receiving account is a reseller account with a "reseller's shared IP" (x.x.x.200)
- Receiving account uses a remote mail exchanger.
2016-03-23 22:09:23 1aiuiA-0007x0-Kz SMTP connection outbound 1458785363 1aiuiA-0007x0-Kz .com user@.com 2016-03-23 22:09:26 1aiuiA-0007x0-Kz ** user@.com R=dkim_lookuphost T=dkim_remote_smtp H=xxxxxxx.xxx.barracudanetworks.com [x.x.x.x] X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=yes: SMTP error from remote mail server after end of data: 550 permanent failure for one or more recipients (user@.com:blocked) 2016-03-23 22:09:26 cwd=/var/spool/exim 7 args: /usr/sbin/exim -t -oem -oi -f <> -E1aiuiA-0007x0-Kz 2016-03-23 22:09:27 1aiuiE-0007xZ-SC <= <> R=1aiuiA-0007x0-Kz U=mailnull P=local S=2405 T="Mail delivery failed: returning message to sender" for user@.com 2016-03-23 22:09:27 1aiuiA-0007x0-Kz Completed0 -
Could you verify the version of cPanel installed on this server? We've had a few cases that address the /etc/mailhelo and /etc/mailips files published in the past few weeks. Thank you. 0 -
We are on 54.0 (build 21) 0 -
Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you. 0 -
Sorry about the delay. Ticket #7512403 0
Please sign in to leave a comment.
Comments
8 comments