Domain MX on different server problem

P

pavelas

New member
Joined
Sep 8, 2009
Messages
4
Hi

My customers are experiencing problems. Lets say at the beginning everything of the domain (web project, MX) was on the server #1. Then they decides to have a dedicated MX (server #2), and asks me to change their MX record to point to their new MX IP.

Then the problem begins: emails generated and sent from their project on server #1 (e.g. contact form, forum, guestbook, orders etc) do not pass to server #2, instead, they are looking for locally defined mailboxes. And, if none defined (all mailboxes are defined on server #2 now), mail just does not reach their new mailboxes.

Same is for mail from users, which are using server #1 as SMTP server (users from another domain on server #1). They get DSN smth like: no such mailbox.

Question is: how to overcome this situation, keeping in mind that on server #1 there must be no mailboxes defined, and DNS control should be on server #1. All mailboxes are defined on server #2 which is not in my control

Thanks in advance!
 
Modifying the MX record is not enough; the MTA on server #1 must not think that the domain is a local one.
Open DA's administration interface, login as the user and select the correct domain, click on "MX Records", remove the check from "Use this server to handle my emails." and save.
 
Hi.

1. Thanks, I found it, we will try the differences. Does this check affect also exim`s conf?
2. Normally we do not give users DNS management rights - I think this check should also be made available from reseller/admin level DNS management section! Never imagined this setting exists ONLY in user level :S

Thanks again. If problem will continue - I will be back :)
 
1. Not directly, but it changes the /etc/virtual virtual mail hosting config.
2. It's an user setting, related only to that particular user; it has been already discussed in this forum a lot, user settings that can be changed by the user itself should only be found in the user's interface, not in the reseller or admin interface, for organisational reasons. It's way simpler like that.

Glad to be of help.
 
Hi

Agreed, except (2):
I believe this should be defined as:
- being in only user interface IF this user IS allowed to control DNS (he dont see this setting otherwise)
- being only available by admin (or reseller of that user) if this user NOT allowed to control DNS.

Opinion? And, thanks, works well now ;)

I start to like DA :)
 
1) Turn on DNS for user

2) Make the change in MX Records

3) Turn off DNS for user

As tillo points out, user-level settings belong in the user-level unless there's a security issue involved.

Certainly you can turn off DNS access; we do for some of our users. But then you bear the burden of managing it.

Jeff
 
You must log in or register to reply here.
Back
Top