Let’s face it. We all make mistakes. At one time or another, most of us have gotten a little hasty with the Send button when composing an email, and sent it to the wrong Frank Thomas, accidentally CC’d the customer in an inter-office communication, or realized the email was probably not such a good idea in the first place. These examples can be quite embarrassing, but other mistakes can result in legal trouble for you or your company. For example, healthcare providers can violate HIPAA regulations by sending an email containing protected health information (PHI) to the wrong person. Penalties for these HIPAA violations can be steep, ranging from $50,000 to $1.5 million.
To avoid these situations, your email solution should have a feature that lets you delay delivery of a message. With MDaemon Webmail, message scheduling options are just a mouse click away.
“This is all great, but why would I want to delay delivery of an important email message?”
There are many reasons why one might want to defer delivery of an email message.
- Delaying message delivery for an hour or even a few minutes gives you time to take a break from it and review it with a refreshed perspective – providing another opportunity to catch errors you might have missed before.
- Some email conversations go back and forth too quickly, so you might respond before you have all the information or ask questions that are already answered in the next message. Deferred delivery allows you to slow the process down so you’re not having to play email tag.
- Deferred delivery can help prevent you from sending an angry email response during heated discussions. Allowing yourself a little extra time to re-think your message or to cancel the message altogether can help prevent a great deal of workplace conflict.
- For companies that operate globally, deferred delivery allows users to schedule messages for delivery during peak business hours in the recipient’s country, increasing the likelihood that it will be seen.
We demonstrate how to defer delivery of an email message in MDaemon Webmail in this week’s tutorial video.
Would you like to learn more about this and other MDaemon features? Click here to schedule a personal demo of MDaemon. Deferred Delivery is explained further here in the MDaemon Help file. Here’s a handy list of features, or you can download your free trial of MDaemon and see for yourself how easy it is to use!
On our next post, we’ll discuss MDaemon’s message recall feature and demonstrate three ways to recall a message, so check back soon for more tips & tricks!
While it’s true that hard drives are continuing to grow exponentially in storage capacity, many mail server administrators are still finding the need for greater control over disk space usage. An easy way to automate the process of limiting disk space used per-user while still retaining business-related data transmitted via email is to set message and disk space quotas while implement an archiving solution such as MailStore.
In today’s tutorial video, we show you how to assign message and disk space quotas to an account via MDaemon Remote Administration.
By default, MDaemon Remote Administration is accessed via port 1000 at your server’s host name, so if your host name is mail.example.com, then you’d enter http://mail.example.com:1000 to access Remote Administration. You can also use a secure URL – for example: https://mail.example.com. The URL you would use depends on the settings you have configured in MDaemon under Setup | Web & IM Services | Remote Administration | Web Server (and SSL & HTTPS).
I hope you find these tutorials useful. If you have questions or comments, please click on Leave a Comment (up there under the title of this post) and let us know!
For more tutorial videos, visit us on YouTube!
Most of our customers are small-to-medium businesses with limited IT budgets across a variety of industries – including healthcare, education, manufacturing, and government. Having a limited IT budget often means having limited staff available for troubleshooting email or tracking down messages, so when considering which email gateway/spam filter you want for your business, one of the main criteria to consider is how easy it is to find messages for your users. Users who are expecting business-critical messages need to know ASAP what happened if that message is not delivered. With SecurityGateway, it’s easy to find out if a message was rejected, quarantined or delivered. If it was rejected or quarantined, color-coded transcripts make it easy to determine exactly why the message was not delivered.
At-a-Glance: The Message Log Window
Let’s have a look at the message log and its layout.
Use the buttons across the top to:
- Refresh the message list
- Search for messages. Advanced search options are provided, allowing you to find messages based on a variety of criteria, such as message contents, delivery date, the result of the message delivery attempt, keywords in a message header, and others.
- View message details (providing the same information as double-clicking the message)
- Redeliver the message. Note that if the issue that made a message undeliverable still exists then the message will return to the message log with the same status.
- Whitelist the sender or sender’s domain
- Blacklist the sender or sender’s domain
Press the blue buttons to enable or disable specific columns.
The right-facing blue arrows indicate outbound messages, and the left-facing green arrows indicate inbound messages.
The remaining columns from left-to-right include:
- Date (notice the arrow indicating sort order)
- The message sender (From)
- The message recipient
- The message subject
- The result of the message delivery attempt (Delivered, Quarantined, Rejected, etc.)
- The reason the message was quarantined or rejected (for those that meet these criteria)
- The message size
- The final message score based on the total score accumulated by all security tests performed
Viewing message transcripts to determine a message’s fate
Now that we’re familiar with the layout of the message listing, let’s review how to troubleshoot email delivery issues.
Key events in a message’s transcript are color-coded for easy identification. In the following example, the message was scanned by SpamAssassin. During this process, it accumulated 1.7 points. It was then scanned by Outbreak Protection, during which it accumulated an additional 5.5 points. Finally, the total message score was tallied with a final score of 12.2 points and was rejected.
We’ve created the following video to help you become more familiar with message tracking in SecurityGateway.
Would you like to learn more about how SecurityGateway can protect your business from spam, phishing attempts and malware? Click here to download your free trial!
If you work in IT or manage a mail server, then you probably know that the vast majority of global email traffic consists of spam. However, if you’re an end user working for a small business in healthcare, manufacturing or education, the following statistic might surprise you:
In June 2018, spam made up a staggering 85.32% of all global email traffic.
A good spam filter & email gateway will filter out most of these malicious email messages circling the globe so that users and administrators can spend more time focusing on their business.
SecurityGateway for Email Servers was designed to make it easy for small-to-medium businesses to manage their inbound and outbound email security needs without taking up too much time that could be spent on more business-related tasks. It reduces the workload on administrators by providing automated user & domain creation and periodic quarantine report emails for end users. The focus on today’s “30-Second Email Tips” video is to demonstrate the quarantine report emails which allow users to manage their own quarantines so you can spend more time focusing on your business.
Many of SecurityGateway’s security settings (including heuristic and Bayesian analysis by the spam filter, DNS blacklists, SPF verification, DKIM verification, DMARC, and others) can be configured to perform one of three options for messages that fail a given security check:
- Accept the message (and optionally place a tag in the message subject and add points to the message’s spam score)
- Refuse the message
- Quarantine the message
For messages that are placed in the quarantine, reports can be sent out to users so that they can decide what to do with these messages. Options provided are:
- Release the message from quarantine
- Always allow (whitelist) messages from the sender
- Blacklist messages from the sender
We’ve created the following video to demonstrate these features.
SecurityGateway helps meet the needs of businesses that want an additional layer of security for their existing email server and businesses running Microsoft Exchange or another mail server that has cumbersome controls or a confusing interface – helping simplify the process of scanning inbound and outbound email for malicious content. Click here to learn more about SecurityGateway, or click here to download your free trial!
I’ve heard various opinions on what to do with an MDaemon account belonging to someone who has left a company. In a recent post on our community forums, an MDaemon administrator had set a former employee’s account to Frozen, and then configured an auto-responder for the account. Frozen accounts cannot send outbound email, and the user of a frozen account cannot check for new email.
Account is FROZEN (can receive but cannot send or check email)
Select this option if you wish to allow the account to receive incoming messages but prevent it from being able to check or send messages. This is useful when, for example, you suspect the account has been hijacked. Freezing the account would prevent the malicious user from accessing its messages or using the account to send messages, but it would still be able to receive its incoming email.
The result of this is that auto-response messages from frozen accounts to external (non-local) addresses are sent to the Holding queue (more information on the Holding queue can be found here).
Let’s take a closer look at what happens.
Let’s say an employee has left the company. As the MDaemon administrator, I don’t want that employee’s account to be used, so I place it in Frozen status via the main Account Details screen of the account editor, as shown here.
Now let’s say I’ve enabled an auto-responder for the account, as shown here.
In the following example, I’ve created the account email@example.com, and have configured the auto-responder.
When I send a test to firstname.lastname@example.org from email@example.com, the MDaemon server hosting the @brad.ssllock.com domain places the message in the frozen account’s mailbox, but the user is unable to log into webmail or access the inbox via another email client. When MDaemon then tries to send the auto-responder that we enabled for the frozen account, the message is moved to the Holding queue and the following is written to the MDaemon logs:
Mon 2018-06-18 11:18:33.406: Session 042192; child 0001
Mon 2018-06-18 11:18:33.406: Parsing message <c:\mdaemon\queues\remote\pd50000000056.msg>
Mon 2018-06-18 11:18:33.406: * From: firstname.lastname@example.org
Mon 2018-06-18 11:18:33.406: * To: Training@mdaemon.com
Mon 2018-06-18 11:18:33.406: * Subject: RE: Test to Frozen Account with Auto-Responder
Mon 2018-06-18 11:18:33.406: * Size (bytes): 3822
Mon 2018-06-18 11:18:33.406: * Message-ID: MDAEMON0005201806181118.AA1812640@mail.brad.ssllock.com
Mon 2018-06-18 11:18:33.421: Message moved to holding queue because sending account is disabled
Mon 2018-06-18 11:18:33.421: SMTP session terminated (Bytes in/out: 0/0)
Mon 2018-06-18 11:18:33.421: ———-
The result is that the auto-response never gets sent because the account is frozen.
Rather than freezing the account, you could simply change the account’s password so that it can still accept mail and send auto-response messages. This can be done via the main Account Details screen, as shown here.
If you prefer to freeze the account instead of changing its password, another option would be to create a content filter rule that would send your desired response to the original message sender instead of using the auto-responder. That content filter rule would look something like this:
In this example, I created a rule that sends a reply to the sender of messages addressed to email@example.com using the “Send a NOTE 1” action. I then entered the $SENDER$ macro and the desired response. This message will be sent back to the message sender in response to a message originally sent to the frozen account.
You can get pretty creative with MDaemon’s content filter to perform a variety of tasks, so hopefully you found this helpful!
Most of us don’t wake up thinking about email, but without it, business communications would be set back at least 20 years. We rely on email for many basic business functions, so we want email management features that simplify communications & make collaboration easier and more efficient.
With MDaemon Webmail, users can perform a variety of tasks via the Options menu. But, following the theme of making things easier, did you know you can perform many of these same tasks with the click of the right mouse button without leaving your Inbox?
In our latest tutorial video, we show you how to:
- Create and Share Folders
- Convert an Email to a Task
- Import and Export Calendar Events
- Rearrange Columns
- Add Categories and Attachments to Notes
Many businesses are responsible for maintaining large amounts of confidential data, including customer records, medical records, financial reports, legal documents, and much more. It’s very common for these types of information to be transmitted via email. So how can you ensure confidential data transmitted via email is kept private? How can you ensure the integrity of transmitted data and that a message actually came from its purported sender?
Businesses need to ensure confidentiality, data integrity, message authentication (proof of origin), and non-repudiation (proof of content and its origin). These goals can be accomplished using MDaemon’s OpenPGP message encryption and signing services. Read on to learn more about the differences between encrypting and signing, and when each is used.
The Need for Encryption
Businesses need to protect sensitive data and preserve confidentiality and privacy. Whether you work in healthcare, finance, legal, HR or education, chances are you’re familiar with the terms GDPR, HIPAA or FERPA (among others). Businesses that fail to meet these regulations risk data breaches that can lead to lost revenue or legal action, as well as steep fines. To address these issues, businesses can use encryption to make their sensitive data unreadable to unauthorized parties.
The Need for Signing
In addition to data privacy, businesses may need to ensure that a message was not altered during transit, and that it actually came from the purported sender. These tasks are accomplished with message signing (adding a digital signature) using OpenPGP. Much like your handwritten signature, a digital signature can be used for authentication purposes, but also cannot be forged.
Signing a message helps ensure the following:
- Data Integrity – That the message was not altered from its original form.
- Message Authentication (Proof of Origin) – That the message actually came from the purported sender.
- Non-repudiation – That the sender cannot deny the authenticity of the message they sent and signed with OpenPGP.
Encrypting vs. Signing – What’s the Difference?
So what are the differences between encrypting & signing? Let’s discuss each.
What is Encryption?
Encryption is the act of converting plain text to cipher text. Cipher text is basically text that has been scrambled into non-readable format using an algorithm – called a cipher. MDaemon’s implementation of OpenPGP encryption uses public key encryption (also known as asymmetric key encryption) to encrypt email messages and attachments.
So How Does Public Key Encryption Work?
Public key encryption uses public/private key pairs. If you want me to send you an encrypted message, you send me your public key, which I import into my encryption software (using the OpenPGP configuration screen in MDaemon, in this case). I encrypt the message with your public key. When you receive the message, you decrypt it with your private key. Even though your public key can be freely distributed and used to encrypt messages addressed to you, these encrypted messages can only be decrypted with your own private key. This private key must always be kept secret. Data encrypted with the public key can only be decrypted with its corresponding private key; conversely, data encrypted with the private key can only be decrypted with its corresponding public key. We’ll talk about why you would encrypt a message with your own private key in the next section when we discuss message signing.
In our latest release of MDaemon, we’ve added the ability for MDaemon Webmail users to encrypt messages from within the message compose window. This procedure is explained in this blog post.
Check out the following video to see this process in action!
Encrypting a message helps ensure that the message is kept confidential. The message remains in its encrypted format until it is decrypted with the recipient’s private key.
What is Message Signing with OpenPGP?
As I mentioned above, messages are encrypted with the message recipient’s public key and decrypted with the corresponding private key. Message signing, on the other hand, uses the sender’s private key to sign (encrypt) the message, and his public key is used to read the signature (decrypt). Message signing binds the identity of the message source to the message. This helps ensure data integrity, message authentication, and non-repudiation.
For example, if John wants to digitally sign a message to Michelle, he uses his private key to encrypt the message, and sends it (along with his public key if it hasn’t already been sent) to Michelle. Since John’s public key is the only key that can decrypt the message, the digital signature is verified by simply decrypting the message with John’s public key.
Signing a message with OpenPGP ensures that the message was not altered in transit, that it did in fact come from the purported sender, and that the sender cannot deny the authenticity of the message they sent and signed with OpenPGP.
More information on using MDaemon’s PGP encryption & signing features can be found in the following knowledge base article:
How to enable MDaemon PGP, configure who can use MDPGP, and create keys for specific users
Do you have questions? Let us know in the Comments section below!
Whether you work in healthcare, finance, education, or another highly regulated industry, it’s likely that you’re required to meet increasingly stringent regulations on email security and privacy, such as the General Data Protection Regulation (GDPR). But even if these strict requirements do not apply to your industry, you still want to maintain customer trust by ensuring their confidential data is safe.
To address these concerns, MDaemon offers email encryption using OpenPGP.
In the past, implementations of OpenPGP have been cumbersome, requiring users to manually exchange encryption keys or to take complex steps to send encrypted messages. With MDaemon, in addition to providing various ways to automate the encryption key exchange and server-side encryption processes, MDaemon Webmail users can easily enable per-message encryption right from within the message compose window.
Here’s a quick video to demonstrate how easy it is to encrypt messages in MDaemon Webmail.
A more comprehensive overview of MDaemon’s OpenPGP settings and how to configure them can be found in this knowledge base article.
Upgrade MDaemon to Take Advantage of the Latest Features!
Are you running an older version of MDaemon? Check out our Features by Version chart to see what you may be missing out on! Server-side email encryption with OpenPGP was introduced in MDaemon 15.5. Click here for upgrade & renewal instructions.