Going to put in my 2 cents here as I don't see it anywhere else.
I just went through this to migrate out our exchange for alerts, and we ended up with Axigen.
Its pretty awesome in my experience so far.
Download link: https://www.axigen.com/mail-server/download/
I currently use the free version of Axigen. The setup was a breeze. I use the Docker version, however they also have various installers for Windows, Debian, and Linux RPM distros.
The UI server admin is what sold me. It was easy to configure.
> there is plenty of open source software which will do what yours does and some
Agreed! As there are plenty of other commercial software as well.
The initial question did not mention he was looking exclusively for an open-source solution. I would have not said anything if that has been stated.
And by the way, Axigen has also a Free Edition version (for up to 5 mailboxes): https://www.axigen.com/mail-server/free/. For which we do not charge ;).
You may wish to take a look at Axigen. It's a little bit of work to set up, but I think the webui makes it worth the effort. It is one of the few free, self hosted mail servers that has push for mobile and for webmail.
Axigen is not a bad choice. https://www.axigen.com/. Antispam and antivirus out in the box. 5 user and 5 domain it’s free - https://www.axigen.com/mail-server/free/. Simple admin UI and user UI + outlook connector included. Supported Microsoft ActiveSync
There is also icewarp, but it is already paid. It has a nice interface and more command collaboration features, but is administered under Windows snap-in https://www.icewarp.com
How do you communicate through a DMZ server?
I am creating an application that will be internet accessible, and this application will need access to local (behind my firewall) resources. I will use a single firewall in a "3 leg" system.
How should my web server connect with my local databases? SSH all the servers together and relay database queries? Create 3 API servers (local, dmz, web) to relay requests over VPN or SSH?
Some other communication method I haven't thought of?
Really good guide with incredibly useful graphics.
We've also got this useful resource on creating a mail server with Kubernetes on Google cloud we've updated recently (it's quite extensive)
Planning on expanding our list of cloud deployment articles with 2 more: one on Azure and one on AWS. If anyone here would be interested let me know and I'll hit reply once we publish.
We also prefer Docker.
For anyone looking for a how-to here, we've also put together a thorough guide for cearting a mail server environment in Docker.
If you’re a veteran Kubernetes user, this article may not add much value to your know-how.
However, the main objective is to bring together the typical steps that a user needs to follow when deploying a Dockerized mail server application to a Kubernetes cluster.
You can think of this article as a reference that you can get back to whenever you need a quick refresher about the most common resources used when deploying mail server applications with Docker and Kubernetes.
Through our discussion, we visit the conversion of the RPM to a Docker image, publishing to Docker Hub, creating and clustering in Google Cloud Platform, and deploying our image.
Read it and save it below
>! https://www.axigen.com/articles/cloud-native-applications-mail-server-docker\_69.html!<
​
What matters most to you? To have a cloud-native solution? To be able to scale quickly and easily? To be secure? To customize your interfaces? To be able to manage everything from a dashboard instead of using command line? To have great Support you can count on?
Here's a case study where you can see how the decision process should look like when choosing or switching mail server providers, depending on what your business needs.
Many organizations think that their application is cloud-native simply because it runs in the cloud. That’s not the case.
A truly cloud-native application takes advantage of all the modern techniques such as PaaS, multi-cloud, microservices, containers, or DevOps.
Other common misconceptions I've seens are thinking that cloud-native is only about running applications in containers, running a container orchestrator, or about infrastructure as a code. That's also not quite accurate.
Axigen currently has 4 licensing models: - Free Edition - up to 5 mailboxes; free yearly license renewal; no technical support - only community forum; no 3rd party addons (EAS, Premium AntiSpam and AntiVirus) - Business Edition - starts at 10 mailboxes; Perpetual + Optional Yearly support subscription renewal; fits a CAPEX + smaller OPEX finance models - Managed Services Provider - starts at 150 mbx; https://www.axigen.com/mail-server/msp/ (scroll for pricing) - Larger Hosting Providers (ISP) - starts at 1500 mbx; clustering available; tiered pricing
I hear you. Currently we have no plans on changing the current licensing models (stability in this regard is important for our customers - we’ve changed this model once in the last 8 years).
Maybe get back to Andreea and have a constructive chat with her about what are your needs. She’ll be more than happy to hear from you, I’m sure!
For anyone interested, I looked up his links. https://www.emclient.com/?lang=en
Maybe I'll do the trial and see what it's like. Nice that it runs in docker.
As the CEO, do you foresee any innovation for email in the next 5 years?
There definitely are. One thing I should mention is that this series actually started as an experiment with a friend who’s also a Software Engineer. We were going over the process of converting a standard RPM package to a cloud application with a friend, he’d already read a lot of what’s out there about containerization and was ready to try to do it himself and we thought Axigen might make an interesting case study for the both of us.
We found the entire process quite interesting so we decided to share this real-time experiment with the Axigen community in an article <strong>here</strong>.
About deploying mail serves: Axigen bundles all the components of a complete email hosting platform: MTA, IMAP & POP3 functionalities, one of the best WebMail interfaces out there, CalDAV and CardDAV, Optional Exchange ActiveSync connectivity, Premium AntiVirus and AntiSpam and many others. So it's more than just an MTA that relays messages outbound for which there are indeed many API driven SaaS services but also valid special use cases, like /u/omers mentioned.
And like u/jedieaston said*,* Axigen can be used as a single vendor supported server software for mailbox hosting providers since you get a multi tenant, scalable, on-premise (or your favorite cloud) solution for all the above.
TL;DR Axigen is fully built and supported. It doesn't include pre-made open-source components that are simply integrated.
Hi! Part 2 of this series is now up, you can see the thread here and read the article on the blog.
That's a great question! I should start by saying that this is only the first part of a series, so I'll be diving into GCP and Kubernetes in the next parts.
About Axigen - it's a complete email platform that also includes WebMail, IMAP, POP3, CalDAV and CardDAV access, as well as the separately licensed Exchange ActiveSync connectivity. It also features a powerful WebAdmin, so these are a few of the features that set it apart from Postfix.
What's also great about Axigen is that it has an extremely flexible per-domain storage configuration which honors one of the 'cloud native' domain separation principles: separating compute from storage.
I've also found it to be one of the most automatable email platforms out there, since it allows virtually everything to be scripted: you could provision a new domain via our provisioning API, with some users in it, and trigger the generation of a Let's Encrypt cert.
Last but not least, Axigen has a built-in clustering module which can group multiple Axigen instances to form a homogeneous multi node/multi tenant email platform.
Here are a few links that go into detail about this feature:
In a future article, I'll dive into the Axigen Helm Chart which spins up in a Kubernetes cluster multiple Axigen Pods (Front Ends and Back Ends) which leverage the clustering functionality I described above.
Hope that answers your question, let me know if I can help with anything else.
Important: To use Activesync in Axigen you will require an Axigen license with support for Exchange ActiveSync.
https://www.axigen.com/knowledgebase/How-to-enable-ActiveSync-in-Axigen_277.html
The Axigen Outlook Connector supported Outlook versions, as documented here https://www.axigen.com/mail-server/platforms are: - 2016 - 2013 - 2010 SP2
The download link for the Axigen Outlook Connector is https://www.axigen.com/mail-server/outlook-connector.php
For backup via FUSE use this link: https://www.axigen.com/documentation/backup-and-restore-p1410262 Scroll down to the FUSE section
As a free edition license holder please note that you should direct Axigen related question to the Axigen Forum.
If you own a commercial license open a ticket to our 24/7 support team.
>52.124.3.12:25
OK, right now this works for you since you disabled STARTTLS as well, which is not recommended since all emails will be delivered to your smarthost via cleartext.
Now, I've done a dump of an ssl connection to this IP and this server knows at most TLSv1:
SSL-Session:
Protocol : TLSv1
Cipher : ECDHE-RSA-AES256-SHA
Session-ID: 90100000921853625B8AE55C436895EF8118D371086D1CA6E662DFA26310C9EF
Session-ID-ctx:
Master-Key: F71310CE62407E1D9814FA76E76B938AAF5AD138355C5F37B0B71E6F3A937135E48F99B927548855B0FC3E277AF550D2
Start Time: 1552054863
Timeout : 7200 (sec)
Verify return code: 0 (ok)
This means that in Axigen Routing Basic Settings you should have checked the TLSv1 as well because that is not checked by default.
This is described in this article:
If you want to give this recommended setting a try please feedback here...
The ‘unable to perform starttls’ error seems to be the one addressed in our documentation here https://www.axigen.com/knowkledgebase/How-to-configure-the-TLS-settings-for-SMTP-incoming-and-outgoing-in-Axigen-iX-9-0-and-X-10-0-for-compatibility-with-older-mail-servers_342.html
Make sure you implement the second part of it about outgoing.
If this still does not work, please pair the logs with what your actual configuration is at the time the logs are captured: a screenshot, a description. Otherwise we are pretty blind here.
Thanks for the detailed investigation.
I think that the following article on our knowledge base might be of help: https://www.axigen.com/knowledgebase/How-to-configure-the-TLS-settings-for-SMTP-incoming-and-outgoing-in-Axigen-iX-9-0-and-X-10-0-for-compatibility-with-older-mail-servers_342.html
Let me know if, after implementing these recommendations, you managed to solve your issue.
Hi,
I think that you should check and make sure that the DNS Server's IP address is correctly configured in WebAdmin -> Services -> DNR. See this link to our documentation: https://www.axigen.com/documentation/setting-up-the-dnr-domain-name-resolver-p1410289
Next, the session timeout suggests that the Axigen process cannot make an outbound connection via port 25 to the remote mail server. If you are on a residential provider you may need to request the unblocking of port 25 from your internet provider.
Hope this helps.
Axigen. Free for up to 5 mailboxes, commercial licenses for more.
WebMail (both desktop and mobile) can be demo-ed here: https://www.axigen.com/mail-server/business/#product=webmail
WebAdmin can be demo-ed here: https://www.axigen.com/mail-server/business/#product=webadmin
The product is not open-source and I’m the CEO of the company.
Support for the free license is via the community forum. Support for commercial licenses is via email 24/7 unlimited cases.
Take a look at Axigen
How-to for Axigen Docker deployment: https://www.axigen.com/documentation/deploying-running-axigen-in-docker-p12222471
Getting a 5 user free license: https://www.axigen.com/mail-server/register.php - select Free
Further docs: https://www.axigen.com/documentation/
For Axigen, we have a detailed documentation that describes step-by-step exactly how to achieve this, including management by pacemaker. It would require adaptation for Zimbra, or, obviously, use of Axigen
Here are the links: - https://www.axigen.com/documentation/high-availability-general-architecture-p589854 - https://www.axigen.com/documentation/high-availability-cluster-deployment-with-drbd-p589853
The second one is the detailed guide.
Good luck with adapting it for Zimbra or, if you choose to try Axigen instead, feel free to reach out if something is unclear.