I'm working on an app that updates the site's MX records to redirect mail for the site to our servers. I'd like to be able to remove the MX records we add when the site is uninstalled, since at that point we'll stop accepting mail for the domain. It seems like other record types, such as TXT, are removed on uninstall, but MX records are not. Is there a way I can remove them?
MX records should be removed with an uninstall as well. Did the zone you test on have the mx record prior to installing the app? Have you tested with multiple zones? I recommend creating a test zone (doesn't have to be active) and not adding any mx records then see what happens.
This was a bug, which has since been fixed. MX records are now correctly removed when the app is uninstalled.
Related
The current mailprovider has had technical issues for more than 14 days now until last night when their servers came offline.
They are insisting that the issue will be solved, but I've gone ahead and prepared to move to gsuite.
I started the mail migration tool several days ago but it fails after migrating a few mails due to the old providers tech issues.
My question is:
If I move the MX records to gsuite, I will receive emails again, but would it then be possible to migrate old mails at a later time? (In case the my old provider fixes their issues?)
My concern is, that when I move the domain name, I will no longer have access to my old emails on the old server.
I've moved the MX records so, that new mails will appear in gsuite.
This means, that the old mails won't migrate, since the MX records has changed.
When the old host, hopehully works again, I'll switch the records temporarily, move the mails and change the MX back to gsuite again.
I have a postfix server (Linux) hosting a large amount of emails (120GB for 70 accounts) to be migrated into Google Apps. Only 30 accounts remain active and the remainder are archives.
What is an efficient way to migrate active accounts into Google Apps and minimize disruption? Are there scripts to read direct from the server disk then upload? What about folders and email statuses (read/flagged)?
Depending on the needs of your users, it's usually easier to cut over the MX records first and send your users to Apps for all new mail. Then, migrate over their old data. In this case, the downtime is very limited and they can always access the old server should they need something there.
The alternative would be to do multiple waves of migration that look something like:
Migrate all data from data X - Y
Change MX records for all users and send them to Apps
Run a second migration from date Y - Z to pick up any of the missed data (there won't be duplicates in emails if there's some overlap)
Regarding your last point, I'm guessing your users are using at least IMAP to access the mail server as I believe Postfix is not a mail server on its own. If this is the case, you'll want to use an IMAP migration for which Google provides a tool for (GAMME). An IMAP migration will bring over folder structure as well as read/unread status but I don't believe any 'flagged' status will translate.
After my Zarafa (Small Business) update to version 7.1.7 all emails were lost. The accounts are still there.
What can I do to solve the problem quickly?
From which version did you upgrade? What do the Zarafa logs say, specifically /var/log/zarafa/server.log (or if you configured syslog instead, what does that log say)?
On github I have made the CNAME record of my domain name. My domain is registered with crazy domains. I went to crazy domains and entered the ip address for the name server, "204.232.175.78". But it keeps asking for a "hostname". It will not allow me to leave the hostname area blank. In the past I have been told to use a hostname like "ns1.host.com" but I can't seem to find anything like this for github pages.
I tried "pages.github.com" but it refuses that, saying it is not a valid hostname.
What should I use as the hostname?
I believe the issue is that you're updating your nameserver registration, when in fact you should be editing your DNS Zone File. Those are two separate records. The nameserver registration determines who's copy of the DNS Zone File acts as master on the domain. The DNS Zone File is what actually controls A, CNAME, MX, and SRV records (and many more). You should try looking through your domain management system (I'm not familiar with Crazy Domains) to see if you can find a section called "All Host Records" or "DNS Zone Editor".
F#$k crazy domains. They changed their interface to try to get everyone to upgrade to premium. On the hamburger on the right side of DNS settings you can add a record there (not forward) and then the CNAME stuff appears.
Seriously considering changing because of this.
StackMob allows you to setup a custom domain. All you have to do is add a CNAME record for a wildcard '*' pointing to stackmobapp.com
I set it up on my domain registrar 24 hours ago, but it still doesn't resolve. It is going to my web hosting providers server instead of stackmob's server when I type dev.mydomain.com
I kept my nameservers the same (ns1.myisp.com and ns2.myisp.com).
Do I have to change these to something else?
update: its been over a week and my dev.domain.com dont' go to stackmob.
You don't have to change your nameservers. Likely the dns changes hadn't propagated to your nameservers yet. It's been known to take up to 72 hours.
I figured out I have to use my registrars name servers, not my own in order to add A/CNAME records to it.
There is one problem with stackmob though, http://example.com doesn't forward to stackmob, only www.example.com and dev.example.com