English
Chinese (Simplified)
French
German
Italian
Japanese
Russian
Spanish
Vietnamese
Can Mdeamon (on-premises) co-exist with 365 as hybrid system using same domain?
-
Hi there,
Is it possible Mdeamon (on-premises) co-exist with 365 as hybrid?
-
Arron Staff
Yes.
https://knowledge.mdaemon.com/configure-mdaemon-microsoft-365-to-use-the-same-domain-name
-
HI there,
Can Mdeamon on-premises cluster with hosted cloud Mdeamon?
-
Arron Staff
We reccomend that all nodes of a cluster are on the same network. The main reason for this is that it is difficult to synchronize the mailbox and public folder data between multiple locations quickly enough to not cause issues.
We also offer a feature called domain sharing that may be helpful for you. Domain sharing can be used to split a domain between multiple servers. Some users exist on server 1 and some users exist on server 2. There are some draw backs to this system as it doesn't synchornize public folder data.
-
Hi! I’ve read the Knowledge Base article and I’m sorry to resurrect an old topic, but I was left wondering what needs to be set on the MDaemon part if one wants to use Microsoft 365 as an upstream server (with MX records pointing at Microsoft 365)? We ran into some difficulties with incoming mail being rejected due to errors such as „550 5.1.1 Too many IPs seen in too short a time frame“ and, sometimes, „550 5.7.0 Message rejected per SPF policy“. I understand that some of the MDaemon's security settings need to be relaxed but I'm not sure which ones are causing problems.
Many thanks,
Marko
-
Arron Staff
I was left wondering what needs to be set on the MDaemon part if one wants to use Microsoft 365 as an upstream server (with MX records pointing at Microsoft 365)?
If you are wanting to share a domain between Microsoft 365 and MDaemon but have the MX records point to Microsoft 365, you'll probably want all accounts to exist in Microsoft 365, which probably defeats the purpose of sharing the domain. If you don't have all accounts in Microsoft 365 then you'll need to configure it to accept mail for all users and forward unknown mail to MDaemon, which will cause a lot of unnecesary mail to be accepted. Another option would be to put SecurityGateway in front of both MDaemon and Office 365. Allow it to choose where to route mail to.
550 5.1.1 Too many IPs seen in too short a time frame
This could be caused by a couple of different settings, spambot detection or account hijacking. The log should give more details that will help figure out which. (Security / Security Settings / Screening / Spambot Detection or Security / Security Settings / Screening / Account HiJack Detection)
550 5.7.0 Message rejected per SPF policy
Was this occurring on inbound mail or outbound mail? If its inbound mail, you simply need to change the policy in MDaemon to not reject based on the SPF result. (Security / Security Settings / Sender Authentication / SPF Verification)
If you are getting this error when sending mail, then your SPF policy probably needs to be updated in DNS.
If you can provide more details including the version of MDaemon you are running, and an SMTP transcript that shows the issue occurring, we can provide reccomendations.
-
Hi! Many thanks for your quick reply! Our MDaemon is v23.5.3. Spambot Detection was the culprit and we managed to override it by adding the following addresses to the trusted IP list:
40.92.0.0/15
40.107.0.0/16
52.100.0.0/14
52.238.78.88/32
104.47.0.0/17
2a01:111:f400::/48
2a01:111:f403::/48Additionally, we disabled the SPF check for the incoming mail. Now everything works as expected.
All the best,
Marko
