Weak passwords are the most common method by which email accounts and servers can become compromised by spammers.
The great news is that Exchange alternative MDaemon Messaging Server, now offers an easy way to identify when somebody’s using one that isn’t secure via a simple but effective new reporting feature.
Whether you then decide to name and shame, or just to give them a friendly nudge is entirely up to your discretion! :).
If you’ve used Achab’s Archive Server (ASM) software in the past and upgraded to MailStore, it’s highly likely you’ll be wanting to bring across that historic archived data to the new platform. There are two ways you can go about importing an external ASM archive to MailStore – either directly as files, or, via your MDaemon email server.
One of the limitations of importing directly into MailStore is that mail can’t be sorted on a per-user basis and instead the archive will have to reside under a single MailStore user account which you delegate access to via MailStore’s permissions system. It’s for this reason that we tend to recommend the second option and utilise the MDaemon server as an intermediary for MailStore to collect the old archive data from.
If you’ve configured the archiving feature in MDaemon but have since upgraded to MailStore Server, it makes sense to move the historic stuff across so you’ve got a single unified archive store.Let’s have a look at how you go about it…
One of the more common customers support calls i get relates to MDaemon suddenly sending vast amounts of spam email. This floods the outbound Internet connection and everything crawls to a halt.
Secondary to this the server’s public IP address can get listed on various external SMTP blacklists which the customer then has to request removal from.