In order to maintain their excellent reputation for secure software, Alt-N Technologies, developer of Exchange alternative MDaemon Messaging Server, continually perform rigorous testing across their portfolio of products, including both current and historic releases.
With the recent Panda Antivirus signature problem still fresh in my mind, and as a fair few of our support calls continue to be antivirus related, I thought you might find it useful if I share some of the antivirus issues we see regularly tripping customers up.
Of course every software vendor professes their product incorporates the latest and greatest protection technology. When you're working out what to use as a Systems Administrator however, it's also important to think beyond that and specifically about how your proposed solution will interact with other applications in your network environment.
These are a handful of the areas we find usually end up resulting in a support call.
We recently needed to migrate our own internal MDaemon and SecurityGateway server to a new location. Luckily we often do this for customers and we have guides specifically written to help with this process.
Migrating MDaemon
Migrating SecurityGateway
However one of the areas which we felt we haven't documented before is how to also migrate an existing SSL certificate that was being used by multiple services in these products.
This year in particular, I've seen an increasing number of users' email account credentials become compromised, which has allowed spammers free reign to use their mail server to send spam out to the Internet.
The usual result is an overflowing outbound mail queue, thousands of bounce messages coming in and your server's IP address being blacklisted.
The first thing to note is that if your company has an email server, you should assume that spammers will always be trying to hijack users' accounts by guessing their passwords.
In this post I will run through a few simple pro-active settings checks that can reduce the chances of this happening and - in the unfortunate event that it does happen - can limit the resulting negative effects.
If you've recently made the move to MailStore version 9, it's entirely possible you'll be sat there wondering why on earth all of those archiving jobs you had set up can't be modified any more.
You'll hopefully be pleased when I tell you it's not a mistake and nothing's gone dramatically wrong, it's just that MailStore are now adopting a new and far more efficient way of automating jobs that no longer needs the old Windows task scheduler method.
Today's nugget of MDaemon wisdom comes from conversations I've had with a small number of customers reporting they're unable to send outbound email to specific recipients.
Upon closer inspection of the error in the SMTP (OUT) log, there's a message reading "SSL negotiation failed".
Configuring any Web service to work over HTTP using SSL is a good idea.
We certainly recommend it for BackupAssist's Multi-site Manager (BAMM) and in this post I'll show you how to create an SSL certificate you can then bind this kind of service to.
A new SSL vulnerability is doing the rounds this morning, known as POODLE, or Padding Oracle On Downgraded Legacy Encryption.
POODLE is a newly disclosed vulnerability in the legacy SSL 3.0 protocol that could be exposing users of newer Transport Layer Security (TLS) encryption protocols to risk.
If exploited, the POODLE flaw could potentially enable an attacker to access and read encrypted communications.
Just like a lot of our customers we use multiple ADSL broadband lines for our Internet access in the office and occasionally we have seen a line issue that effects our Draytek Vigor router and the only fix we have found is a quick controlled reboot.
If you have recently upgraded to MailStore version 9 you may not be aware that the new maximum number of messages that an archive can contain has now been increased from 500,000 to 5,000,000 messages.
If you are like me and you have found yourself with a collection of much smaller MailStore message archives it is now much easier to merge these together into a smaller number of larger archives.
