MDaemon Priority Mail Features

In order to let you understand the MDaemon mail server more functions, to facilitate your network management colleagues use MDaemon Mail server, today to introduce a MDaemon function of priority Mail. As the name suggests, it is the priority of the message that meets certain conditions.

This feature can be entered from the MDaemon main menu: Set Default domain/server Priority mail. You can adjust the Priority mail condition according to your company's situation. Below with everybody take an experiment to explain, the following figure is the detailed setting of the priority Mail, the condition "1" means the recipient, CC, dark copy, etc., as long as contains 11@huns.com this mailbox, priority treatment. The condition "2" indicates that the message from 11@huns.com is treated as a priority. Of course, these two header conditions are the most commonly used Oh!

The following is a routing log that does not have priority settings. Because it is a newly built mail test server, so the mail is relatively few, in order to be able to experiment results, in the mail before the local queue frozen, we can see that a total of two mail, a 22 group to 11 and 332 people, into the stack time is 11:17:25. Another email was sent 11 to 22, and the stack time was 11:17:55. When I thaw the local queue, the order of processing is 22 to 11, then 33, and finally 11 to 22. Therefore, when the message is not prioritized, it is processed in a first-in, first-out order.

Sun 2011-07-24 11:17:25:routing Message (inbound queue): c:\mdaemon\queues\inbound\md50000000003.msg
Sun 2011-07-24 11:17:25: * from:22@huns.com; recipient:11@huns.com; size:1379; Message:c:\mdaemon\queues\local\md35000000009.msg
Sun 2011-07-24 11:17:25: * from:22@huns.com; recipient:33@huns.com; size:1379; Message:c:\mdaemon\queues\local\md35000000010.msg
Sun 2011-07-24 11:17:25: * Subject: =?gb2312? b?sulk1dm=?=
Sun 2011-07-24 11:17:25: * message-id:wc20110724031721.500003@huns.com
Sun 2011-07-24 11:17:25:----------
Sun 2011-07-24 11:17:55:routing Message (inbound queue): c:\mdaemon\queues\inbound\md50000000004.msg
Sun 2011-07-24 11:17:55: * from:11@huns.com; recipient:22@huns.com; size:1360; Message:c:\mdaemon\queues\local\md35000000011.msg
Sun 2011-07-24 11:17:55: * Subject: =?gb2312? b?sulk1dq=?=
Sun 2011-07-24 11:17:55: * message-id:wc20110724031754.370004@huns.com
Sun 2011-07-24 11:17:55:----------
Sun 2011-07-24 11:18:07:routing message (local queue): C:\mdaemon\queues\local\pd35000000009.msg
Sun 2011-07-24 11:18:07: * from:22@huns.com; Recipient:11@huns.com
Sun 2011-07-24 11:18:07: * Subject: =?gb2312? b?sulk1dm=?=
Sun 2011-07-24 11:18:07: * Message-id: <WC20110724031721.500003@huns.com>
Sun 2011-07-24 11:18:07: * Size: 1379; Mail: c:\mdaemon\users\huns.com\11\md50000000003.msg
Sun 2011-07-24 11:18:07:----------
Sun 2011-07-24 11:18:07:routing message (local queue): C:\mdaemon\queues\local\pd35000000010.msg
Sun 2011-07-24 11:18:07: * from:22@huns.com; Recipient:33@huns.com
Sun 2011-07-24 11:18:07: * Subject: =?gb2312? b?sulk1dm=?=
Sun 2011-07-24 11:18:07: * Message-id: <WC20110724031721.500003@huns.com>
Sun 2011-07-24 11:18:07: * Size: 1379; Mail: c:\mdaemon\users\huns.com\33\md50000000003.msg
Sun 2011-07-24 11:18:07:----------
Sun 2011-07-24 11:18:07:routing message (local queue): C:\mdaemon\queues\local\pd35000000011.msg
Sun 2011-07-24 11:18:07: * from:11@huns.com; Recipient:22@huns.com
Sun 2011-07-24 11:18:07: * Subject: =?gb2312? b?sulk1dq=?=
Sun 2011-07-24 11:18:07: * Message-id: <WC20110724031754.370004@huns.com>
Sun 2011-07-24 11:18:07: * Size: 1360; Mail: c:\mdaemon\users\huns.com\22\md50000000003.msg
Sun 2011-07-24 11:18:07:----------