You may have picked up in the IT press recently that we’re starting to see an industry-wide movement to a new, and importantly more secure, standard of SSL certificate.
Alt-N Technologies, developer of the Exchange alternative MDaemon Messaging Server have just announced they too are following this trend and stating they’ll be replacing all end-point and intermediate server certificates with those based on the new SHA-2 algorithm.
Important note: Alt-N will be moving to SHA-2 SSL certificates on January 20, 2015.
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.
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.
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.
Alt-N Technologies (the developers of MDaemon and SecurityGateway) and MailStore have both confirmed the security flaw to OpenSSL, known as Heartbleed, does not impact any of their products.
However as IT professionals you may well be using other Open SSL internet facing services on your network so if you have any concerns, we recommend you take the time to run a quick scan by entering the site details using one of the following websites.
As a side note If you are interested in knowing even more detail about the SSL cipher versions your server supports this search is particularly detailed.
It’s a bit of a niche technical one this but as I’ve had several reports of it recently I wanted to share this one with you in case it helps.
If you’re an MDaemon customer you may have started to see the following errors in the SMTP (Out) logs when trying to send email to some specific external hosts…
“SSL negotiation failed*,*error code 0x80090326”
What this boils down to is an issue where MDaemon and the remote SMTP server cannot find a common set of SSL ciphers that they both have available to use.
We have recently been dealing with a range of customers who are using the SecurityMetrics PCI compliance check on their network and are in the process of working through the highlighted security vulnerabilities the report has brought to their attention. Continue reading
One of the most notable changes visually in Windows 8 is the range of new apps that now appear on the “Start” page. In a similar vein to mobile devices, there are email and calendar apps which now integrate tightly, offering handy features such as notifications.
It’s easy to see why some users will end up switching to this as their preferred method of access, so in this post I’ll show you how to configure MDaemon to synchronise with these two key apps.