Miscellaneous

Do not send welcome message to new accounts

By default, MDaemon will generate a Welcome message based upon the NEWUSERHELP.DAT file and distribute it to new users when their account is created. Enable this control if you want to prevent the message from being generated.

Send response to invalid command messages

By default when someone sends an email to the system account that does not contain a valid command, MDaemon does not respond with a "No valid command found" email. Enable this option if you wish to send a response to those emails.

Create "Everyone" lists

Check this box if you wish MDaemon to create and maintain "Everyone" mailing lists for your domains (e.g. "everyone@example.com"). Maintaining mailing lists of every user on every MDaemon domain could be a potential waste of resources if the lists are never used, or if they are for very large numbers of users. This option is disabled by default.

Create "MasterEveryone" list

Enable this option if you want there to be a "MasterEveryone" mailing list. Everyone on all of your domain-specific "everyone" lists will be included on this list. This option is disabled by default.

System generated messages are sent through the Content Filter

By default, system generated messages are processed through the Content Filter. Clear this checkbox if you want them to be excluded from content filtering.

Apply content & spam filters to list mail before cracking individual copies

When the MDaemon will crack list mail option is chosen on the Routing screen of the mailing list editor, enabling this control will cause the content filter rules and spam filter to be applied to list messages before they are cracked and distributed to list members.

List pruner deletes messages that don't contain parsable addresses

When you have configured MDaemon to scan messages that are returned to a Mailing List in an attempt to delete list members that cannot be reached, this control will cause those messages to be deleted that do not contain a parsable address. For more information, see the Automatically remove dead addresses from list membership control on the Members screen of the Mailing List editor.

List pruner saves messages which result in list member removal

When MDaemon scans returned list messages in an attempt to remove member addresses that cannot be reached, this control will cause messages that result in a list member's removal to be saved.

Honor '<List>-subscribe' and '<List>-unsubscribe' addresses

Click this checkbox if you want MDaemon to recognize email addresses of this format as valid (as long as the list actually exists) in order to facilitate an easier method for users to join and leave your mailing lists. For example: suppose you have a list called MyList@example.com. People will be able to subscribe/unsubscribe to your list by sending an email message to MyList-Subscribe@example.com and MyList-Unsubscribe@example.com. The content of the subject and message body is irrelevant. Also, when this feature is active MDaemon will insert the following header into all list messages:

List-Unsubscribe: <mailto:<List>-Unsubscribe@example.com>

Some mail clients can pick up on this and make an UNSUBSCRIBE button available to users automatically.

You can override this option for individual lists by specifying a value for the List-Subscribe and List-Unsubscribe headers in the Mailing List URLs options located on the Mailing List Editor's Moderation screen.

Disable subaddressing feature for all accounts

Click this option if you wish to globally disable the Subaddressing feature. Subaddressing will not be permitted for any account, regardless of the individual account settings. For more on Subaddressing, see the IMAP Filters screen of the Account Editor.

Inform postmaster when new MDaemon updates are available

This option causes MDaemon to notify the postmaster whenever there is an MDaemon update available. This is enabled by default.

No spam allowed in mailing list public folders

By default, when a mailing list has an associated Public Folder, list messages will not be placed in that folder when their spam scores meet or exceed the value designated in the "A message is spam if its score is greater or equal to" option located on the Spam Filter screen. Clear this checkbox if you wish to allow spam to be placed in the public folder.

Send stats report to postmaster at midnight

By default a statistics report will be sent to the postmaster each night at midnight. Clear this checkbox if you do not want the report to be sent. This option corresponds to the Statistics tab located on MDaemon's main display.

Account export includes disk usage stats (this could greatly slow export)

By default, account exports do not include disk file counts and space consumed. If you wish to include this information in exports, enable this checkbox. This may, however, significantly slow export speeds.

Messages forwarded to specific hosts do not go to the smart hosts on errors

Using the "Advanced Forwarding Options" on the Account Editor's Forwarding screen, accounts can be set to forward messages to a specific smart host rather than using MDaemon's standard delivery process. By default, when MDaemon encounters a delivery error when attempting to forward one of those messages, it will be placed in the bad message queue. Enable this option if you instead want MDaemon to place the message into the Retry Queue for further delivery attempts using MDaemon's normal delivery process.

Delete messages sent from blacklisted senders (otherwise put in bad queue)

Enable this option if you want MDaemon to delete incoming messages from senders who are in the recipient's personal Blacklist IMAP folder. When this option is disabled, the message will be placed into the Bad Message Queue instead of being deleted. This option is disabled by default.

Remove duplicate list recipients when single message submitted to multiple lists

When this option is enabled and a single message is addressed to multiple mailing lists, MDaemon will deliver only one copy of the message to any recipient who is a member of more than one of the lists. For example, if frank@example.net is a member of List-A@example.com and List-B@example.com and an incoming message is addressed to both lists, Frank will receive only one copy of the message rather than two. This option only applies to lists, therefore in the above example if the message were addressed to Frank directly, plus the two lists, then Frank would receive two copies of the message rather than three. This option is disabled by default.

Using this option is not generally recommended. Mailing lists can be used and organized many different ways by users, and there is no way of knowing which list will receive the message when limiting duplicates in this way. Therefore using this option could cause unnecessary difficulties for some users, due to message threading preferences, using IMAP filters to sort messages to specific folders, and so on.