With the prevalence of data-destroying malware, more businesses are using an archiving solution such as MailStore to create backup copies of all email communications. Archiving is crucial for recovery when the unexpected disaster strikes, and useful for e-discovery and meeting legal requirements & regulations. I’ve written this article to help explain the value of archiving and why it’s so important:
For end-users, it’s important to have easy access to your archived messages, with the ability to search through your archives based on key words. With the addition of a custom button in the WorldClient toolbar that points to the MailStore login screen (performed by the MDaemon administrator), users can access their archive and perform a search in three easy steps. I’ll show you how in the following video:
MailStore works with virtually all email platforms and clients, and is the recommended choice for small-to-medium businesses worldwide. If you have questions or would like a personal demo, leave a comment below & let me know!
Remember – there are two components to Outlook Connector – one for the server, and one for the client. There is a link to the latest Outlook Connector client on the above link. We recommend installing this update on the server as well as on all clients.
If you have questions, feel free to leave a comment below!
Note: July 27 – A fix to Outlook that was caused by the Windows Creators Update is now available by upgrading to most current version of OutlookConnector – version 4.5.1. Click here to download the update.
The Creators Update for Microsoft Windows 10 has introduced various technical issues. One of the issues is that it may cause Outlook to become unstable when Outlook Connector is used. The issues with Outlook are not isolated to Alt-N products.
Our technical team is working to find a solution to address the issues as soon as possible.
Who is affected?
Customers using Outlook Connector with the Windows 10 Creators Update are affected.
What is the issue?
After installing the Creators Update, Outlook may, under some circumstances, crash or stop working. We have also had reports of searches not returning results.
How do I fix it?
There are a number of workarounds available but the only solution at this time is to uninstall the Windows Creators Update and install the Windows 10 Anniversary Update (version 1607). Using older versions of the Windows operating system can put your system at risk; please use caution.
How do I install the Microsoft update – version 1607?
As I was coaxing myself awake this morning with my usual jolt of strong coffee, I checked my favorite news sites & was informed of yet another ransomware attack. This one, which is believed to have originated from Ukraine, was first thought to be a variation of last year’s Petya ransomware outbreak, but upon further investigation, it appears that today’s malware is a new type – a worm that some computer experts are referring to as “NotPetya“. This attack demands a smaller ransom (in comparison to other attacks) of approximately $300, and then begins to serve its primary purpose – to wipe files on the computer. According to researchers at Symantec, this attack used the same National Security Agency hacking tool, Eternal Blue, that was used in the WannaCry outbreak, as well as two other methods to spread the attack. According to information provided by this article on CNN, if you’ve installed all of the latest Windows patches, you should be safe from this particular strain of malware, however, by no means is this a reason to be complacent. Administrators and end users must still be mindful of safety precautions.
Due to the proliferation of Malware as a Service (MaaS), just about anyone with the desire and the funds can initiate a malware attack, making new & emerging threats a real concern for the foreseeable future. This presents a good opportunity to review best practices for avoiding ransomware – for end users, and for administrators via the tools available in MDaemon and SecurityGateway.
How can end users protect themselves from ransomware?
End users should be aware of the following 18 email safety tips, which originally appeared in this post.
Change your password often.
Use strong passwords. Never use a password that contains “password” or “letmein”.
Use a different password for each of your accounts. If you use the same password for your bank account as you do for your email account, you become much more vulnerable to data theft.
Don’t open an attachment unless you know who it is from & are expecting it. Many of today’s social engineering tactics rely on the ability to trick users into opening attachments.
Use anti-virus software on your local machine, and make sure it’s kept up-to-date with the latest virus definitions.
If you receive an attachment from someone you don’t know, don’t open it. Delete it immediately.
Learn how to recognize phishing
– Messages that contain threats to shut your account down
– Requests for personal information such as passwords or Social Security numbers
– Words like “Urgent” – false sense of urgency
– Forged email addresses
– Poor writing or bad grammar
Hover your mouse over links before you click on them to see if the URL looks legitimate.
Instead of clicking on links, open a new browser and manually type in the address.
Don’t give your email address to sites you don’t trust.
Don’t post your email address to public websites or forums. Spammers often scan these sites for email addresses.
Don’t click the “Unsubscribe” link in a spam email. It would only let the spammer know your address is legitimate, which could lead to you receiving more spam.
Understand that reputable businesses will never ask for personal information via email.
Don’t send personal information in an email message.
Don’t reply to spam. Be aware that if you reply to a spam email, your reply most-likely will not go back to the original spammer because the FROM header in the spam message will most-likely be forged.
Don’t share passwords.
Be sure to log out.
How can administrators protect their systems from ransomware?
The battle against ransomware cannot be fought by users alone. Administrators must also take steps to lock down their email infrastructure. These best practices will help protect your network and users.
Best Practices for MDaemon Administrators
Enable account hijack detection. This feature will automatically disable an account if a designated number of messages are sent from it via an authenticated session in a given period of time. When the account is disabled, the administrator receives a notification so that corrective action can be taken. Instructions for configuring account hijack detection can be found in this knowledge base article.
Enable dynamic screening. Dynamic screening is a feature that blocks future connections from a connecting server or client based on its behavior. Instructions for configuring dynamic screening can be found here.
Configure the IP Shield. The IP Shielding feature allows administrators to assign an IP address (or IP address range) to email messages from a given domain. Messages claiming to come from a specific domain must originate from one of the approved IP addresses. Exceptions can be made for users connecting from outside of the network who are using SMTP authentication. Click here for instructions.
Require SMTP Authentication. This helps ensure that the user authenticates with a valid username and password. Instructions can be found here.
Use DKIM & SPF to detect spoofing. DKIM uses a private/public key pair to authenticate a message. When an incoming message is signed with DKIM, a DNS record lookup is performed on the domain taken from the signature and the private key taken from the signature is compared with the public key in the domain’s DNS records. SPF uses a DNS record that lists hosts that are allowed to send mail on behalf of a domain.
Enable DMARC & configure your DMARC record. DMARC (Domain-Based Message Authentication, Reporting & Conformance) allows domain owners to instruct receiving servers on how to handle messages claiming to come from their domain that did not pass DKIM and SPF lookups. Learn more here.
Ensure that all connections (SMTP, POP, IMAP), are using SSL. SSL (Secure Sockets Layer) is a method for encrypting the connection between a client and server, as well as between to servers. Learn more here.
Have a backup strategy. If by chance malware still manages to infect your network, your last resort is to have a reliable backup strategy. Ideally, you should have your systems backed up off-site and, for added safety, secondary backup data should be saved to media that is not connected to the network.
More information on these settings can be found in the following guide on best practices for protecting your users:
SecurityGateway provides an extra layer of anti-spam, anti-spoofing and anti-malware security, in addition to your mail server’s built-in security settings. These best practices will help keep ransomware and other malicious content from reaching your mail server. Each item includes a link with more information.
Don’t whitelist local addresses. If a spam messages was spoofed with one of your local addresses, this could allow the spam message to bypass various security features. This why it is recommended that no local addresses be added to your whitelist.
Of course, no system is 100% fool-proof, which is why user education is so important. Remember – your network and email infrastructure are only as secure as their weakest link. It is the responsibility of all parties involved – administrators and end users, to help ensure a secure messaging and collaboration environment.
For many small-to-medium businesses, hosting an in-house Microsoft Exchange Server requires dedicated staff and deep pockets. In the mid-90’s, MDaemon was created as an affordable alternative to Exchange that wouldn’t break your IT budget & required no dedicated staff to administer it. With every installation of MDaemon comes the free Exchange migration utility – MDMigrator. MDMigrator will import all user accounts, email messages, public folders and other settings from Exchange to MDaemon. You can find step-by-step instructions in this knowledge base article:
Has this happened to you? Let’s say you’re the MDaemon administrator for your company, and you’ve noticed that somewhere, somehow, spam messages are being sent from within your network. Perhaps one of your PCs has been compromised. What do you do? Here are some tips to help you track the issue down.
First, make sure you have the option “Authentication is always required when mail is from local accounts” enabled (Security | Security Settings | SMTP Authentication). Also enable “Credentials used must match those of the return-path address” and “Credentials used must match those of the From header address.” Then, make sure “…unless message is sent to a local account” is unchecked to prevent intra-domain spam (between local domain users).
Next, find out if the spam messages are coming in from an authenticated session. To do this, locate one of the spam messages & open it up in Notepad to view its headers (or you can open it in Queue & Statistics Manager). Does the message have an X-Authenticated-Sender header? It will look something like this:
If this header is present, then that is the user who authenticated to send the message. The first thing you should do in this case is to change the account’s password via the Accounts menu in MDaemon. Even if the spamming is going through the user’s mail client, until you give the user the new password and they update their mail client the authentication credentials will be rejected and the spamming will be temporarily stopped.
In newer versions of MDaemon, we’ve added Account Hijack Detection, which will automatically disable an account if it sends a specified number of outbound messages via an authenticated session in a given period of time. We recommend enabling this feature. In MDaemon, it’s located under Security | Security Settings | Screening | Hijack Detection.
The next step is to look at the Received headers. Find the one where the message was received by your server. Here is an example of what this header would look like:
Received from computer1 (email@example.com (188.8.131.52) by example.com (MDaemon PRO v17) with ESMTP id md50000000001.msg for <UserWhoWasSpammed@example.com >, Fri, 13 Sep 2016 21:00:00 -0800
Find the connecting IP (184.108.40.206) in the above example. This is the machine that is sending out spam. Locate that machine to deal directly with the spambot on that machine.
If the message wasn’t authenticated or wasn’t sent from your local network, locate the Message-ID header and copy that value.
Then open the MDaemon SMTP-IN log that covers the time when that message was received by MDaemon (based on the timestamp in the received header) and search for that Message-ID in the log (in the 250 response line when the message is accepted):
When disaster strikes, is your business able to recover from data loss with minimal downtime?
How does your business handle legal requests for discovery and compliance audits?
Are you protected against data loss when employees leave the company?
Businesses of all sizes worldwide rely on email for their day-to-day communication needs. With the prevalence of malware, ransomware, and malicious actors hell-bent on wreaking havoc for personal profit, and with increasingly strict guidelines for HIPAA, FERPA and other regulations, it is more important than ever to have backup copies of all email communications for your business.
MailStore is a complete, secure archiving solution that can grow with your business. A robust archiving solution such as MailStore can meet your company’s needs in these key areas:
Compliance & eDiscovery – Businesses in the education, legal and healthcare industries have a growing list of regulations and eDiscovery requirements that must be met.
Disaster Recovery – When disaster strikes, in addition to easily getting data into your archive, you want it to be just as easy to get data back out of your archive. MailStore supports multiple archive & export methods, providing the flexibility businesses need to get their data into and back out of MailStore regardless of what email platform or mail client is used.
Reduced Server Workload – An archive solution helps reduce the workload of the mail server, freeing up resources for more important business communications.
Storage Space – MailStore can be configured to delete messages after a given period of time once they have been archived. This helps reduce storage requirements on the server.
Easy Backup & Restore – MailStore makes it easy to make backup copies of your important email messages – from any mail server, mail client, or even a PST file. The restore process is just as easy!
Avoidance of PST Nightmares – PST files can be archived and accessed from the MailStore client. Businesses whose users use PST files will benefit from being able to consolidate these PST files in a single archive location.
Elimination of Mailbox Quotas – Archived messages can be removed from the mail server after a period of time, reducing the need for mailbox quotas.
Prevent Users from Deleting Emails – A journaling mailbox can be configured on the mail server to collect copies of all inbound and outbound mail. You can then create a journaling archive profile in MailStore to capture all inbound and outbound messages as they pass through the mail server. This allows all messages to be archived even when the sender or recipient deletes the message from his Inbox or Sent Items folder.
Increased Productivity – Archived messages and attachments are fully indexed, making it easy to perform complex searches in a matter of seconds.
We’ve created the following video to help you get started with MailStore.
In MDaemon 17, we added support for DropBox integration for WorldClient, MDaemon’s web-based email client. Now, users can easily save attachments in inbound messages to their DropBox account, or insert links to their DropBox files in outbound attachments. Because files are stored in DropBox and not on the mail server, disk space and bandwidth are reduced.
We’ve put together the following tutorial video to help you get started with WorldClient’s DropBox file sharing features.
Step-by-step instructions can be found in the following knowledge base article:
I’m happy to announce the release of SecurityGateway 4.5.1. Though this is only considered a point (.1) release, it packs a big punch with the newly-added RMail features from RPost. With RMail, you can:
Track your important emails and know precisely when they’re delivered and opened.
Receive Proof of Delivery, Time, and Exact Content.
Easily encrypt sensitive emails and attachments for security or legal compliance.
RMail™ makes it easy for all parties to e-sign and complete a transaction, as well as to determine when a message has been delivered and opened.
For more information on the latest features and enhancements, or to download the latest SecurityGateway with RMail support, visit our downloads page.
As always, you can leave a comment if you have questions!
In today’s connected society, users demand instant access to open channels of communication. For years, MDaemon has offered instant messaging via WorldClient Instant Messenger. Formerly known as ComAgent, WorldClient Instant Messenger has evolved to support open protocol (XMPP/Jabber) for instant messaging, giving users more choices over what instant messaging client to use.
What exactly is XMPP & why should I care?
XMPP is a communication protocol based on XML that powers a wide range of applications. It is based on open standards and offers greater flexibility and choice for its users. XMPP supports secure communications via SSL, and a wide variety of XMPP clients for Windows, MacOS, Linux, iOS, Android, BlackBerry, and Nokia devices. There’s even a DOS/Command-line client for die-hard DOS purists. A complete list of XMPP clients can be found at xmpp.org.
Why is this important for MDaemon users and administrators?
In addition to greater choice for end users, other features that we’ve come to appreciate from the ComAgent years remain, including file transfer for end users and message logging for administrators.
How do I connect to MDaemon’s XMPP service with third-party chat clients?
The steps for each instant messaging client will vary, but the concepts for each are the same. You’ll need your email address, password, and the host name or IP address of your MDaemon server. I’ve created a tutorial video showing the configuration process for both MDaemon administrators and end users.
Want to learn more? We have some valuable resources in the following knowledge base article.