31
Jul
What is DNS? How does it work? How to use the ‘NSlookup’ tool
A long time ago in a galaxy far away....well....ok, just a long time ago, I learnt that in order to diagnose the email delivery problems of our customers, understanding the role of DNS would be absolutely fundamental.
Not only that, but I quickly realised the value of the 'NSlookup' DNS tool which is included within Windows.
You've probably picked up in the IT press that the developers of TrueCrypt, currently integrated within BackupAssist, are no longer actively developing the software.
If you've ever needed to recreate your Outlook profile, or have migrated to a new PC, you may have noticed you'll lose your auto-complete information that Outlook keeps when you send a message to a recipient email address.
In most deployments of MailStore we recommend your journalling job is configured to archive a selection of journalled or 'copied' emails for all your users.
This type of job is designed to interrogate each message that it archives and look for headers that it can match to decide which user's archive it should store the message under.
In a perfect installation where all of your MailStore users have been setup correctly, every journalled message should find the correct corresponding users archive. But it is common to overlook some addresses and you may find email appearing in the general 'Unknown e-mail archive' instead.
If you're not already familiar with Rsync, it's the method (or 'protocol' to be posh about it) that BackupAssist uses to send data off-site to locations such as NAS boxes or to other servers.
QNAP make a NAS device that's popular with our customers and this week I came across an issue with backing up via Rsync to it that I've seen before...
...cue helpful (hopefully) blog post!
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.
Something I get asked for by MailStore customers on a regular basis is an easy way for one user to search for messages within another's archive.
One approach to this would simply be to log into the MailStore client as an Administrator, which would give you full rights over all the user archives but this is only really useful for one-off access - there is a much more elegant way to tackle this...
I recently found myself working on a project where I needed to calculate how much bandwidth the average MDaemon server uses - I'm hoping if you're an MDaemon user, you'll be able to help me out here.
Every server's usage is different of course - bandwidth will vary depending upon the number of users and the type and the number of emails, but I knew if I could arrive at an average across a handful of customer sites I'd be able to get close enough for my needs.
As Office365 and other hosted Exchange platforms continue to attract more users, we're starting to see more demand from customers looking for a way to keep an offline copy of their data 'just in case' the unthinkable should happen.