E-mail archiving is an indispensable tool in the armoury of any company looking for a secure but accessible way of storing email. It’s also an excellent way to tick a number of the boxes of the General Data Protection Regulation (GDPR).
I touched on this topic in a recent YouTube video and today the German vendor MailStore have released a new whitepaper detailing exactly how to fully support your GDPR compliance customers, available here.
Last week we let you know about the release of MailStore v10.1, the centrepiece of which was a simple but useful feature we’ve been asked for quite a bit – scheduled email reporting.
You may be thinking, MailStore is German so there won’t be any issues to report on!? Well, not everything about your email is under MailStore’s control, so as an administrator, it’s still nice to see confirmation that your ‘Enten in einer Reihe’ occasionally.
In this blog post, I’ll show you how to enable the delightful HTML report email, and let you know how to get the most from it.
A popular feature of MDaemon is its ability to let administrators quickly pinpoint message activity and session information using detailed logs. Sometimes, however, what’s required is more an overview of server usage such as how load is being shared across users or mailboxes for example.
In this post I take a look at how you can use Microsoft Excel to query data you may not even be aware is available in MDaemon!
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.
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.
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…