Options

Account is private

MDaemon automatically creates and maintains an "everyone@" mailing list for each domain, which can be used to send a message to everyone at once. By default MDaemon will include all accounts when it constructs this list. Check this box if you wish to exclude this account from that list. This will also hide the account from shared calendars and VRFY results. The account's address book entry, however, will not be hidden from a global address book lookup performed on a BlackBerry device that is activated on your MDaemon's BlackBerry Enterprise Server.

Account can modify the public address book

Click this option if you want the account to be able to add and delete entries from the WorldClient or LDAP-based public address books.

If the Account is synchronizing folders with ComAgent then modifications could be propagated to all users. Exercise caution when enabling this feature.

Account automatically processes meeting and cancellation requests

Click this checkbox if you wish to cause automatic processing of meeting requests, changes, and cancellations for this account. When the account receives a message that contains a meeting request, the account’s calendar will be updated automatically. This option is disabled for all accounts by default.

Automatically decline requests that conflict with an existing event

If automatic processing of meeting requests and cancellations is enabled for this account, those meeting requests will be automatically declined by default when they conflict with an existing event. Clear this checkbox if you wish to allow the conflicting event to be created.

Automatically decline recurring meeting requests

Click this box if automatic processing of meeting requests and cancellations is enabled for this account but you wish to decline those requests when they are for recurring meetings.

Account can use subaddressing to route incoming mail into folders

Click this checkbox if you wish to permit subaddressing for this account.

Apply domain signature to all messages from this account

When there is a Domain Signature for the domain to which this account belongs, this option causes it to be added to all emails sent by the account. It is enabled by default.

Account is exempt from the "Authentication credentials must match those of the email sender" requirement

Use this option if you wish to exempt the account from the "Authentication credentials must match those of the email sender" global option located on the SMTP Authentication screen. This option is disabled by default.

White Listing

Spam Filter uses personal contacts, white list, and black list files

The Spam Filter's White List (automatic) screen contains a global option that can be used to cause the Spam Filter to white list a message automatically when the sender of the message is found in the local recipient's personal contacts or white list files. It will also automatically black list a message when the sender is found in the user's black list file. If you have enabled the Spam Filter's global option but do not wish to apply it to this account, clear this check box to override the global setting. If the global option is disabled then this option will not be available.

Keeping your contacts updated and synchronized with WorldClient, the Windows Address Book, and other MAPI mail clients that use the Windows Address Book can be easily done using ComAgent.

Update white listed contacts with mail recipients

Click this option if you wish to update this account's white list folder each time it sends an outgoing message to a non-local email addresses. When used in conjunction with the above option, Spam Filter uses personal contacts, white list, and black list files, the number of Spam Filter false positives can be drastically reduced. The Automatically update white listed contacts option located on the White List (automatic) screen must be enabled before you can use this feature.

This option is disabled when the account is using an autoresponder.

Remove contacts which are missing name or phone data

Click this button if you wish to remove every contact that contains only an email address from the account's default Contacts folder. If a contact doesn't have at least a name or phone data it will be removed. The option is primarily to help those who were using MDaemon's automatic white listing option prior to version 11 purge contacts that were added purely as a function of the white list feature. In previous versions of MDaemon the addresses were added to the main contacts instead of to a dedicated white list folder. This could result in the account having many entries in the contacts folder that the user would rather not have there.

Consider this option carefully before using it, because contacts containing only an email address could still be legitimate.

Show me all mailing lists that have this account as a member

Click this button to open a list of all Mailing Lists that have this account as a member.

Subaddressing

Subaddressing is a system for including a folder name in the mailbox portion of an account's email address. Using this system, messages addressed to the mailbox+folder name combination will be routed automatically to the account's folder included in the address (assuming that folder actually exists), without the need to create specific filtering rules to make that happen.

For example, if bill.farmer@example.com has an IMAP mail folder called "stuff," then mail arriving addressed to "bill.farmer+stuff@example.com" would be routed automatically to that folder. Subfolders can be designated by including the folder and subfolder names separated by an additional "+" character, and underscores are used to replace spaces in folder names. So, using the example above, if Bill's "stuff" folder had a subfolder called "my older stuff," then messages addressed to "bill.farmer+stuff+my_older_stuff@example.com" would be routed automatically to Bill's "\stuff\my older stuff\" mail folder.

Since subaddressing requires the use of the "+" character, mailboxes that contain "+" cannot be subaddressed. So, in the example above, if the actual address were "bill+farmer@example.com" instead of "bill.farmer@example.com" then it could not be subaddressed. Further, you cannot use an address alias in a subaddress. You can, however, create an alias that refers to an entire subaddressed form. So, even though "alias+stuff@example.com" is not permitted, using "alias@example.com" to point to "bill.farmer+stuff@example.com" would be fine.

To prevent exploits or abuse, the IMAP folder included in the subaddress must be valid. If a subaddressed message arrives for an account that does not have a folder matching the name of the folder defined in the subaddress, then the subaddress will be treated as an unknown email address and handled accordingly, based on your other MDaemon settings. For example, if bill.farmer@example.com does not have a folder named "stuff" and yet a message arrives for "bill.farmer+stuff@example.com" then that message will be treated as if were addressed to an unknown user, and it will most likely be rejected.

By default, each account has the subaddressing feature disabled. You can, however, disable this feature globally via the Disable subaddressing feature for all accounts option located on the Miscellaneous screen of the Preferences dialog. If Subaddressing is disabled via that option, it will not be permitted for any account, regardless of the individual account settings.

See:

White List (automatic)

WebAdmin

Template Manager