Is it possible to have two working mail servers?

Question

Mail server

Hello!
We use Yandex.Connect as corporate mail. Several organizations and domains, respectively. From 5 to 110 boxes. We work on IMAP. OS for all Windows, from 7 to 10 and x86 and x64. The mail client for all MS Outlook is also x86 or x64 from 2010 to 2019 versions. In the last 3 weeks, some users (and the number is growing) have started having problems with mail. Emails are not received or sent until you restart Outlook. Moreover, the client for IOS and Android official work without problems, mail browser also works as it should. The problem is on different machines, different providers and all our mail domains.

I want to install MS Exchange and transfer all users to it, but problems with the Internet where the server will be located do not allow me to do this. Mail must be accessible by at least a browser 365/24/7. Is it possible to work Exchange and Yandex Mail at the same time? Transfer mail from Yandex to Exchange, make Exchange the main server and set up synchronization automatically with built-in tools, if any, or with third-party utilities in both directions? It is necessary that Exchange receive and send mail (I hope this will solve the current problem with the work of mail clients), and users can go to Yandex with a browser and work with mail there if necessary, and mobile applications so that they also work from Yandex servers.

Answer 1

"well, if you set up synchronization with third-party utilities" - then yes you can, but not, but do you need it?

Answer 2

and users could go to Yandex with a browser and work with mail there, if necessary, and mobile applications so that they also work from Yandex servers.

Nakua?
Exch is not cheap. And you need licenses to connect to it. And the SAN-ovsky certificate that OWA worked. Therefore, usually if they migrate to eksch, then they switch to it completely. It has its own webmord - Outlook Web Access (OWA). Reminds me of regular Outlook. It has mobile access - for example Maildroid works great with it.
Windows must die, of course, but eksch solves its problems if you bother, otherwise you shouldn't do it - it's expensive, long, difficult.

Answer 3

Nobody will give you 365/24/7. Exchange needs to be patched, Windows Server too, it's quite expensive to set up fault tolerance yourself, you need to raise the Database Availability Group, and these are at least two servers + file share witness. Ah, I forgot! You also need to raise Active Directory ... Well, licenses, respectively. If you want stability and a relatively quiet life, look towards G-Suite or Office 365.

Answer 4

The Exchange solution will add intermediaries to your mail, plus it's expensive.
Yandex has recently had flaws, which is also not the best option. I can offer two options for others (I also do not consider G Suite because of the cost).
Firstly, Mile Ru for business, it is easily transferred from Yandex with all the contents, it is also native applications, users have much less complaints about it. Also free and without restrictions on the size of the boxes. Plus much more prompt support, the average response time is less than a day. Yandex answered me like that in the fall for more than a month !!! I’ll clarify right away that when transferring the organization to Yandex Connect, it’s better to delete it, otherwise Yandex will continue sending letters from other Yandex mailboxes to itself, without looking at MX.
The second option is paid, and more exotic. Swiss Migadu. Without your own applications, you will have to use third-party, fairly simple web interface. But clearly working. All paid plans have an unlimited number of mailboxes, an unlimited number of domains, and no volume limits. Prices depend on the number of letters sent per day from all mailboxes. Up to 100 outgoing calls per day - 5 dollars a month, up to 500 - 17 dollars, up to 2000 - 60 dollars. Moreover, the restriction is not rigid, if you exceed it, you will receive a letter - do you want to change the tariff. If you choose this option, I can ask them for a promo code. Already given, but mine it ended.
Both options can be tried on separate domains with a small number of mails and compared.