Fresh install, new mail won't login at all (migrating from Plesk to HestiaCP)

Community Support Mail
1

Good evening! I was trying to migrate emails from a Plesk server using imapsync.
However, I’m struggling with a newly created email in HestiaCP. They won’t login or work anywhere, not even on Thunderbird or through Webmail.

So far, the stack and setup are:

  • Plesk server: origin_mail@mywebsitecom. Not needed to solve this problem?
  • imapsync: using their online tool, I can confirm that my mail, and some other providers, login and sync together.
  • Thunderbird will green light using ports 993, 465 and mail.mywebsite.com, destiny_mail@mywebsitecom as credentials, but won’t connect.

Now, on HestiaCP proper:

  • HestiaCP: Proxmox container running Debian 12, regular install, then login as Admin, then creating a new user, hestiauser, and login again.
  • Creating a web domain with the same name as Plesk, mywebsite.com. Yes to DNS and Mail Support.
  • Add Mail Domain, yes to DKIM Support, no SMTP Relay. Then, Add Mail Account, destiny_mail, with my password.

I suspect DNS records being messy here, I covered up for the attached picture my public IP, myselfhosting (.es), and mywebsite(.com). There’s a WireGuard VPN in place to connect to both Plesk and the server running HestiaCP, which seem to run just fine.

Any input is greatly appreciated.

HesitaCP mail
HesitaCP mail1094×980 71.2 KB

2

Hi @sysmin,

Reading your post seems like mywebsite.com is being used at the same time in your Plesk and Hestia servers. Could you please clarify if that is the case?

3

Yes, I’d like to migrate some WordPress websites from Plesk to my new HestiaCP server, which have some mail accounts too. The newer mail acounts should keep the same name and password, then imapsync logs in and transfers all messages. Or so I thought :sweat_smile:

4

But if your domain points to your Plesk server, if you try to login to the mail account created on Hestia it will try to login on Plesk server because the domain is pointing there.

Maybe I’m missing something…

1 Like
5

That’s how it goes for Thunderbird, I know. Domain names are kept the same, but DNS config and IPs are about to be upgraded to a new server.

6

Solved! Thanks for your support @sahsanu .

For this specific migration, it turns out creating new emails with the same hostname was ok. However, upon connecting, using mywebsite.com wouldn’t work. Instead, using the local IP of the second server solved it (like 192.168.XX.YY). nginx wan’t running on HestiaCP panel > Admin > services list, so I turned it on.

Thunderbird needs that IP too, and ports 143 (IMAP), 25 (SMTP). It may be buggy upon checking data once with default settings, so make sure to manually edit before the check, and restart the program if necessary.

No certificates and no password security is going to show a lot of warnings, so stay away from production :wink:

Last, imapsync only needs an IP at --host2, like:
./imapsync
–host1 mydomain com
–user1 original_mail@mydomain
–password1 ‘pass’
–host2 192.168.XX.YY
–user2 target@mydomain
–password2 ‘pass’

1 Like
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.