Solved Partly migration between 2 DA boxes mail problem between those 2

ikkeben

Verified User
Joined
May 22, 2014
Messages
1,489
Location
Netherlands Germany
Ressel backup , restored on other da box.
External DNS service

So want to use only few domains from that account with websites on the new da box, but mail and mx records to stay on old box

Then it is not possible to send mails from a other account on the new DA box to mailadres that because of changed mx records in dns ( external and on both boxes pointing to old DA box) to old da box mailaccount

Gives 500 unroutable mailadres

Also mailing from new mail account domain moved to new box and new emailadres on this new da box , but still having domain on old DA box with settings ip and mx to new box , you can send mails to any adress on old DA BOX, you have to delete totally the domain then on old DA box it works.

For readers, here and support sometimes you have to migrate only partly and not all, this is not easy to do, while you have then problems communicating between the 2 boxes per mail for ...

Also wen only moving domains / or mailaccount but not all under a reseller / user there is not a kind of backup restore option in DA GUI i guess?

Ok this is not so normal, but more info in DOCS could be very handy.

And some extra backup restore / mail boxes (imap) synch and such in GUI also.
 
If You move only website to NEWDA - you need to change A-records for www/domain, and keep old MXs and A-records for MXs.
Than in NEWDA at DNS settings you can remove all email related records and UNSELECT (use this server) in MX settings, or modify A-records for MX in NEWDA DNS management to point it to old server and also UNSELECT (use this server) in MX settings.
---
than check your firewall to allow outoging connections from NEWDA to OLDDA through SMTP (25,465,587 ports or what you use).
also you can permanently add NEWDA server IP to AllowList in firewall at OLDDA to prevent blocking when you will configure smtp etc.
 
r and also UNSELECT (use this server) in MX settings.
---
ONly this forgotten urggha :( (EVO TEMPLATE hard to find things when used to. old enhanced. )

EDIT that:
THIS is a UX failure of EVO template the green save button for other function where this function saves itself with green message

BUt then after doing that i get error!

Error setting MX Template​

Template does not exist



This is not solved:
For domains that are restored by backup restore , but not when creating new domains on that new DA box

And error unroutable adress stays.
 
Last edited:
ONly this forgotten urggha :( (EVO TEMPLATE hard to find things when used to. old enhanced. )

BUt then after doing that i get error!


For domains that are restored by backup restore , but not when creating new domains on that new DA box

And error unroutable adress stays.
if you removed MXs - you can try to add it again at DNS settings on NEWDA but point them to OLDDA IP
 
if you removed MXs - you can try to add it again at DNS settings on NEWDA but point them to OLDDA IP
No not removed they are and where set to the old DA ip , the first thing i did.

I didn't found the mx option before, that was what i did but no change and get that error no template.

That error is my fault, but user experience here not ok if you tick the box then a saved green is shown in the right , but thinking i have to push save there is giving the error while that green save button has a other function and is not for the mx option switch on or of.

Error is REPORTING MTA dns (the new DABOX hostname)

final recipient status 5.0.0 unroutable address.

But for domains that are deleted on old DA box i can send mails from those domain on new DABOX from new to old da box to other mailaccount on that BOX
 
Last edited:
DNS need some time to update, check all records if they all ok - then wait 1-2h
 
DNS need some time to update, check all records if they all ok - then wait 1-2h
but dns TTL times was set on 5 Minutes long time before the changes.

But ok

Strange is sending from that unreachable mail acount from new to old DA box, if i do it the other way arround

So sending to a mail account from the old DA box ( same mailadres that is unreachable the other way)) ( same where domain website is on new DA box) that mail is going ok

So it is strange for me.
 
Last edited:
Check your logs. maybe it's the setting which causes the "imporsonating domain name" in the helo which causes mail from the other server to be blocked.
Or DNS is not synched yet indeed.
 
Check your logs. maybe it's the setting which causes the "imporsonating domain name" in the helo which causes mail from the other server to be blocked.
Or DNS is not synched yet indeed.
So for all who reading or find with a search looks like solved.

Strange only one direction was taking so long before the mx settings or whatever.

The other pointed @Zhenyapan me that i did forgot to switch off local mx in checkbox ( did the dns mx only changed) , if you are used to enhanced skin, then is this in EVO hard to find , and there a little UX problem for saving the checked box in green automaticly where you also have a green save button beneath that is for the other input there. ;)

Thank you all for the support
 
Parental NS may needs longer. Mostly in 2hours. Check propagation:
 
Parental NS may needs longer. Mostly in 2hours. Check propagation:
I did tested some, also this ns switched https://www.dns.computer/ Letsencrypt was long time there also , so yup somewhere , but i think the forgotten mx checkbox only the time between those the restored domain.

Manuel domains created and migrated where in 123 ok , only the via backup restore.

O to mention one direction was working the other direction not . Same hoster and datacenter
 
Last edited:
Back
Top