Best way of moving E-Mail Accounts and one custom DNS entry from MyW to Namecrane?

Ympker · April 2

It's finally time. I'll make use of my Namecrane Email Package So, I've had this xyz domain over at MyW which I use mainly to create various "throwaway" email accounts I can retain access to incase ever needed again (for newsletters, freebies, trials..). So various blabla@domainxyz accounts. If I want to "move" them to Namecrane (I don't need to retain any of the previous inboxes just the email accounts need to continue functioning to receive mails when needed), can I just update my DNS records on Namecheap DNS Manager and then on Namecrane re-create those email accounts with new credentials? I always used One-Click sign in from DA for the throwaways so I never wrote down the pw anyway. Can I just re-create blabla@domainxyz on Namecrane and from there on continue receiving mails there? I haven't dealt much with email before and usually just had them as part of my shared hosting so moving them to Namecrane I'd wanted to double check I don't forget anything.

The custom DNS entry I need from MyW is just for my personal self-hosted Snikket/XMPP instance, so I'd probably just set that in Namecheap and be done with it.

Cheers

Decicus · April 2

Since you don't need to keep the emails from your old inboxes, it's enough to just edit the MX DNS records and update to the MX record(s) that Namecrane gives you. Make sure to remove any extra MX DNS records that still point towards MyW.

If you plan on sending emails (e.g. for support reasons) from those inboxes, you need to update/add the TXT record with SPF (the one with the contents of v=spf1...), as well as add the DKIM (another TXT record with the content starting with v=DKIM1...) from Namecrane.

For your Snikket/XMPP instance it's just to point the (sub-)domain's A (IPv4) or AAAA (IPv6) record to the right IP where you're hosting the service.

edip · April 2

Do you need inboxes for throwaway emails? How about creating just 1 inbox and make aliases for others?

dgc1980 · April 2

just create the domain on namecrane, setup the verifcation and MX records as per the setup

have a single email address on there, and add aliases as you need them, delete them when you no longer need them.

Ympker · April 2

@edip said:
Do you need inboxes for throwaway emails? How about creating just 1 inbox and make aliases for others?

Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

dgc1980 · April 2

@Ympker said: Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

can do both, you can setup an alias for a@domain b@domain etc and only accept emails on them, or setup a catch all that will get anything and everything without being able to disable them

Ympker · April 2

@dgc1980 said:

@Ympker said: Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

can do both, you can setup an alias for a@domain b@domain etc and only accept emails on them, or setup a catch all that will get anything and everything without being able to disable them

Catchall sounds even easier, but could also be abused if some bots were to spam random [email protected] on some forms online since there is no validity check if the email exists right? If I understand correctly, alias requires the alias to exist to have the mail delivered.

MichaelCee · April 2

@Ympker said:

@dgc1980 said:

@Ympker said: Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

can do both, you can setup an alias for a@domain b@domain etc and only accept emails on them, or setup a catch all that will get anything and everything without being able to disable them

Catchall sounds even easier, but could also be abused if some bots were to spam random [email protected] on some forms online since there is no validity check if the email exists right? If I understand correctly, alias requires the alias to exist to have the mail delivered.

Yep, I get the occasional bot trying random things but not very often.

root · April 2

@MichaelCee said:

@Ympker said:

@dgc1980 said:

@Ympker said: Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

can do both, you can setup an alias for a@domain b@domain etc and only accept emails on them, or setup a catch all that will get anything and everything without being able to disable them

Catchall sounds even easier, but could also be abused if some bots were to spam random [email protected] on some forms online since there is no validity check if the email exists right? If I understand correctly, alias requires the alias to exist to have the mail delivered.

Yep, I get the occasional bot trying random things but not very often.

Same with me. I use catch-all on a domain.

Ympker · April 2

@root said:

@MichaelCee said:

@Ympker said:

@dgc1980 said:

@Ympker said: Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

can do both, you can setup an alias for a@domain b@domain etc and only accept emails on them, or setup a catch all that will get anything and everything without being able to disable them

Catchall sounds even easier, but could also be abused if some bots were to spam random [email protected] on some forms online since there is no validity check if the email exists right? If I understand correctly, alias requires the alias to exist to have the mail delivered.

Yep, I get the occasional bot trying random things but not very often.

Same with me. I use catch-all on a domain.

Might just try that then lol.
So, do I understand correctly that with catch-all it is one inbox in DirectAdmin/Webmail and when I need a new throwaway mail I just signup somewhere using randomatring@mydomainxyz and it will be delivered?

What happens if I need to reach out to support or actually send an email with catchall? Since it's only one inbox what will the receiver see as email sender?

root · April 2

@Ympker said:

@root said:

@MichaelCee said:

@Ympker said:

@dgc1980 said:

@Ympker said: Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

can do both, you can setup an alias for a@domain b@domain etc and only accept emails on them, or setup a catch all that will get anything and everything without being able to disable them

Catchall sounds even easier, but could also be abused if some bots were to spam random [email protected] on some forms online since there is no validity check if the email exists right? If I understand correctly, alias requires the alias to exist to have the mail delivered.

Yep, I get the occasional bot trying random things but not very often.

Same with me. I use catch-all on a domain.

Might just try that then lol.
So, do I understand correctly that with catch-all it is one inbox in DirectAdmin/Webmail and when I need a new throwaway mail I just signup somewhere using randomatring@mydomainxyz and it will be delivered?

What happens if I need to reach out to support or actually send an email with catchall? Since it's only one inbox what will the receiver see as email sender?

Catch-all is like having a forward of *@example.org towards [email protected]. This excludes the email addresses which are already created, or the forwarders which are already created. It simply forwards messages of every other possible address which does not exist (not defined) to a specific email address of your choice.

Catch-all could be handy for creating addresses easily, on the spot when you signup somewhere, without creating the email addresses as separate accounts or separate forwarders. The downside is obviously possible bots attacking you. The upside is having different accounts along with different passwords in your password manager.

If however you wish to send an email from an email address used through catch-all (not created), you simply create that address in DirectAdmin and send messages from it. This happens if for example a company needs to speak with you through email (but we all know we like to use tickets for that).

edip · April 2

@Ympker said:

@edip said:
Do you need inboxes for throwaway emails? How about creating just 1 inbox and make aliases for others?

Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

Not catch-all because it will become a spam inbox . For example I have an inbox for private trackers "[email protected]". All my account emails, like "[email protected]", "[email protected]" reaches to [email protected]" not anything else. Everytime when I need to add alias, I add it through the dashboard with just 1 line.

Ympker · April 2

@root said:

@Ympker said:

@root said:

@MichaelCee said:

@Ympker said:

@dgc1980 said:

@Ympker said: Is that the catchall function? Does that mean all emails [email protected] will go to the same inbox?

can do both, you can setup an alias for a@domain b@domain etc and only accept emails on them, or setup a catch all that will get anything and everything without being able to disable them

Catchall sounds even easier, but could also be abused if some bots were to spam random [email protected] on some forms online since there is no validity check if the email exists right? If I understand correctly, alias requires the alias to exist to have the mail delivered.

Yep, I get the occasional bot trying random things but not very often.

Same with me. I use catch-all on a domain.

Might just try that then lol.
So, do I understand correctly that with catch-all it is one inbox in DirectAdmin/Webmail and when I need a new throwaway mail I just signup somewhere using randomatring@mydomainxyz and it will be delivered?

What happens if I need to reach out to support or actually send an email with catchall? Since it's only one inbox what will the receiver see as email sender?

Catch-all is like having a forward of *@example.org towards [email protected]. This excludes the email addresses which are already created, or the forwarders which are already created. It simply forwards messages of every other possible address which does not exist (not defined) to a specific email address of your choice.

Catch-all could be handy for creating addresses easily, on the spot when you signup somewhere, without creating the email addresses as separate accounts or separate forwarders. The downside is obviously possible bots attacking you. The upside is having different accounts along with different passwords in your password manager.

If however you wish to send an email from an email address used through catch-all (not created), you simply create that address in DirectAdmin and send messages from it. This happens if for example a company needs to speak with you through email (but we all know we like to use tickets for that).

Will try that! Thanks for bearing with me, mate

poppz · April 2

Catch-all is definitely the go-to route here. I use it on all of my domains though, not sure if that's a good idea or not, but makes it easier for my family to signup for things.

bikegremlin · April 2

I block + and alias emails whenever possible (often used by spammers LOL).
Then again - I don't send spam (or "newsletters") or sell user data.

Ympker · April 3

Any idea why my CNAME mail entry and MX entry still show as missing on Namecrane?

Namecheap config:

Namecrane:

COLBYLICIOUS · April 3

@Ympker said:
Any idea why my CNAME mail entry and MX entry still show as missing on Namecrane?

Namecheap config:

Namecrane:

Why not using Cloudflare DNS? Is more faster.

NameCrane · April 3

@Ympker said:
Any idea why my CNAME mail entry and MX entry still show as missing on Namecrane?

We may've cached the incorrect records for a bit too long, did it clear up or still not verifying?

Re: catch-all, you lose some features like automated scout reports with SpamExperts - and also you will get random junk showing up when people start blasting abcxyz@yourdomain. I prefer to just create an alias for each new site I sign up for.

On the migration side of things, with CraneMail you can create the account(s) you need and then in that account go to Settings -> Connectivity -> Mailbox Migration - and you can kick off an imapsync job from your old server to us.

Ympker · April 4

@NameCrane said:

@Ympker said:
Any idea why my CNAME mail entry and MX entry still show as missing on Namecrane?

We may've cached the incorrect records for a bit too long, did it clear up or still not verifying?

Re: catch-all, you lose some features like automated scout reports with SpamExperts - and also you will get random junk showing up when people start blasting abcxyz@yourdomain. I prefer to just create an alias for each new site I sign up for.

On the migration side of things, with CraneMail you can create the account(s) you need and then in that account go to Settings -> Connectivity -> Mailbox Migration - and you can kick off an imapsync job from your old server to us.

Thanks for chiming in The MX record shows as active now, after I used "@" instead of my domain in Host field. CNAME mail.mydomain.xyz still shows as missing (I've entered it like shown above in the screenshots).

I also feared that I might get too much junk with catch-all. I'll explore the alias option and see how that works out. I don't need hundreds of alias mails either. I think I had like 10 [email protected] mail accounts before. Alias would then be one inbox and 10 alias that are accepted by the inbox (but not all strings are accepted like catch-all) if I understand correctly, but I'll have a look.

NameCrane · April 4

@Ympker said:

@NameCrane said:

@Ympker said:
Any idea why my CNAME mail entry and MX entry still show as missing on Namecrane?

We may've cached the incorrect records for a bit too long, did it clear up or still not verifying?

Re: catch-all, you lose some features like automated scout reports with SpamExperts - and also you will get random junk showing up when people start blasting abcxyz@yourdomain. I prefer to just create an alias for each new site I sign up for.

On the migration side of things, with CraneMail you can create the account(s) you need and then in that account go to Settings -> Connectivity -> Mailbox Migration - and you can kick off an imapsync job from your old server to us.

Thanks for chiming in The MX record shows as active now, after I used "@" instead of my domain in Host field. CNAME mail.mydomain.xyz still shows as missing (I've entered it like shown above in the screenshots).

I also feared that I might get too much junk with catch-all. I'll explore the alias option and see how that works out. I don't need hundreds of alias mails either. I think I had like 10 [email protected] mail accounts before. Alias would then be one inbox and 10 alias that are accepted by the inbox (but not all strings are accepted like catch-all) if I understand correctly, but I'll have a look.

If I'm looking at the right domain, it looks like you're missing that first verification TXT record. Need that in place before the system will create/etc to make sure you control the domain.

Ympker · April 4

@NameCrane said:

@Ympker said:

@NameCrane said:

@Ympker said:
Any idea why my CNAME mail entry and MX entry still show as missing on Namecrane?

We may've cached the incorrect records for a bit too long, did it clear up or still not verifying?

Re: catch-all, you lose some features like automated scout reports with SpamExperts - and also you will get random junk showing up when people start blasting abcxyz@yourdomain. I prefer to just create an alias for each new site I sign up for.

On the migration side of things, with CraneMail you can create the account(s) you need and then in that account go to Settings -> Connectivity -> Mailbox Migration - and you can kick off an imapsync job from your old server to us.

Thanks for chiming in The MX record shows as active now, after I used "@" instead of my domain in Host field. CNAME mail.mydomain.xyz still shows as missing (I've entered it like shown above in the screenshots).

I also feared that I might get too much junk with catch-all. I'll explore the alias option and see how that works out. I don't need hundreds of alias mails either. I think I had like 10 [email protected] mail accounts before. Alias would then be one inbox and 10 alias that are accepted by the inbox (but not all strings are accepted like catch-all) if I understand correctly, but I'll have a look.

If I'm looking at the right domain, it looks like you're missing that first verification TXT record. Need that in place before the system will create/etc to make sure you control the domain.

Thanks for the pointer! I've added that one as the very first entry yesterday, but somehow saw that I put "workspace-verification.mydomain" in Host field, while it should only be "workspace-verification". Let's see if that does the trick then

NameCrane · April 4

@Ympker said:

@NameCrane said:

@Ympker said:

@NameCrane said:

@Ympker said:
Any idea why my CNAME mail entry and MX entry still show as missing on Namecrane?

We may've cached the incorrect records for a bit too long, did it clear up or still not verifying?

Re: catch-all, you lose some features like automated scout reports with SpamExperts - and also you will get random junk showing up when people start blasting abcxyz@yourdomain. I prefer to just create an alias for each new site I sign up for.

On the migration side of things, with CraneMail you can create the account(s) you need and then in that account go to Settings -> Connectivity -> Mailbox Migration - and you can kick off an imapsync job from your old server to us.

Thanks for chiming in The MX record shows as active now, after I used "@" instead of my domain in Host field. CNAME mail.mydomain.xyz still shows as missing (I've entered it like shown above in the screenshots).

I also feared that I might get too much junk with catch-all. I'll explore the alias option and see how that works out. I don't need hundreds of alias mails either. I think I had like 10 [email protected] mail accounts before. Alias would then be one inbox and 10 alias that are accepted by the inbox (but not all strings are accepted like catch-all) if I understand correctly, but I'll have a look.

If I'm looking at the right domain, it looks like you're missing that first verification TXT record. Need that in place before the system will create/etc to make sure you control the domain.

Thanks for the pointer! I've added that one as the very first entry yesterday, but somehow saw that I put "workspace-verification.mydomain" in Host field, while it should only be "workspace-verification". Let's see if that does the trick then

Should be good now

COLBYLICIOUS · April 4

@Ympker you got the lifetime plan?

Ympker · April 4

@COLBYLICIOUS said:
@Ympker you got the lifetime plan?

Yes.

@NameCrane said:
Should be good now

Shows as Active now. Awesome! Thanks for the help! Didn't wanna pop a ticket but happy to have this solved anyway. Human-error as always Gonna try setting everything up the next days

Best way of moving E-Mail Accounts and one custom DNS entry from MyW to Namecrane?

Comments