Companies around the world are faced with the need to manage email access after hours to reduce overtime pay and promote a stronger work/life balance for their employees. MDaemon makes this goal attainable using its Do Not Disturb feature. Do Not Disturb allows administrators to designate a time during which selected users are not allowed to check their email. During the Do Not Disturb period, accounts can still receive email on the mail server, but users cannot send or check for mail using SMTP, IMAP, POP, WorldClient or ActiveSync.
In MDaemon, you can access the Do Not Disturb feature via the Group Manager screen under the Accounts menu. Follow these steps to configure Do Not Disturb.
Select Groups & Templates.
Select Group Manager.
Select New Group or click on an existing group to select it. Enter a Group Name and Description for your new group.
Click on Add or remove accounts from the selected group.
Check the box for each account you wish to add to this group, and then click OK.
Select the group name under the Group Manager list.
Check Enable Do Not Disturb.
Click on Define Do Not Disturb Schedule to configure when you would like this feature to take effect.
Select your desired Do-Not-Disturb schedule, including dates, times, and days of the week, and then click OK.
Click OK to close the Groups & Templates window.
Once these settings are enabled, users who try to access or send email during Do Not Disturb hours will be denied access.
The following video demonstrates how to configure Do Not Disturb.
Do Not Disturb gives administrators and management teams greater control over who has after-hours access to the email system. This feature was added in MDaemon 15.5. If you’re using an older version of MDaemon and would like to upgrade, then visit our Downloads page to download the latest version of MDaemon.
For spammers, the barriers to entry are very low and the potential payoffs are very high relative to the small amounts of effort required to send out lots of spam. Spammers typically look for the “low hanging fruit” of an email system, such as mail servers that are not configured to prevent relaying, or accounts with weak passwords. If a hacker manages to guess an account’s password, he can use that account to send out large amounts of unsolicited spam email messages. This can result in your server winding up on a blacklist. Additionally, if large amounts of spam are sent out before the issue is corrected, your business can suffer lost trust and a reduction in revenue.
MDaemon’s Account Hijack Detection feature can be used to disable the account once a specified number of messages have been sent from an authenticated session within a given period of time. But it would be better to not even let a hacker get that far. Having strong passwords that are difficult to guess would help prevent an account from being hijacked in the first place.
Today, we focus on the issue of weak passwords and how to thwart hackers by implementing strong password policies. These settings are located in MDaemon under the Accounts | Account Settings configuration screen. In today’s video tutorial, we demonstrate how to require strong passwords, how to force accounts with a weak password to change their password, and how to send a Weak Passwords report to a designated email address.
Email is one of the most valuable intellectual property assets a company can have. Protect your email by enacting strong security and password policies & keep the hackers out.
MDaemon 15.5.3 has been released. With this latest release, we’ve added support for one of the most popularly-requested features – the ability for the content filter to check for restricted files inside of RAR and ZIP attachments.
We recently released MDaemon 15, with new features such as IPv6 support, email encryption, improved account hijack detection, 64-bit support, dynamic screening improvements, and much more. To learn more about what’s new, watch the following brief webinar.