Before administration functions can be accessed, it is necessary to login. The user ID used to login determines what administration capabilities will be available. Once logged in, if more than fifteen minutes elapse without a button click, it will be necessary to login again.
To access administration functions, enter your login ID.
If you accessed the administration page through the URL for your own domain, you only need to enter the user name part of the ID, without the "@" sign and domain. Otherwise, the full user ID with domain must be entered, and can be entered even if not needed.
You can tell if you are on your own domain's page because the domain name will appear in the main title at the top of the page (not in the browser's title bar).
After entering your user ID, enter your password and click the Login button to proceed.
This field shows the user currently logged in. This determines which account is being edited.
The logoff button will end the session and return to the login page.
This setting allows a new password to be entered if desired:
Keep same password will cause the password for the account to remain unchanged, even if other settings are changed and applied.
Set new password will allow a new password to be entered for this account, which will take effect when the Apply button is pressed.
Passwords may also be set for accounts by the administrator for a domain. If you have problems with your password, you should contact your administrator.
This field is only visible when Set new password is selected.
Passwords may be any length, although it is a good idea to limit then to no more than fifteen characters or so, as some client software may not deal well with longer passwords.
This setting controls how messages sent to this account are handled -- whether they are delivered locally, remotely, or not at all:
Deliver to mailbox will cause a mailbox to be created on the system for the account. Any messages received will be delivered to this mailbox. This is the "normal" mail setting.
Deliver and forward will create a mailbox, as above, for delivery of messages, and will also forward a copy of all messages received to one or more additional addresses.
Forward to address will cause all messages received to be forwarded to one or more other addresses. No mailbox will be created.
Accept but discard will cause all messages sent to this account to be silently discarded. The sender will be unaware that the message was not delivered.
Return to sender will cause all messages received for this account to be returned to the sender as undeliverable.
Use domain default will make this account "invisible" for email purposes by using the default settings for the domain for any mail received.
If either Deliver to mailbox or Deliver and forward are used, mail will be stored on the system and can be read using a POP3 or IMAP mail client, or using web mail. These are the only options that result in local delivery.
The Deliver and forward option may be useful to provide notification of mail delivery on a cell phone, pager, or other device that can receive text messages through email.
If you only want the new account to be an alias for another account where all mail will actually be read, use Forward to address. Because more than one address may be entered, this can also be user to create simple mailing lists or "mail exploders".
If you need an account for FTP or FrontPage access but do not want email, choosing Use domain default will disable any email capability for the account.
When the Deliver and forward or Forward to address options are selected for incoming mail, this field contains the list of addresses forwarded to.
Addresses should be in standard format and multiple addresses can be entered either on separate lines, or separated by commas.
This setting controls whether and how the system checks incoming mail to identify "spam", "junk mail", or unsolicited commercial email. All received messages can be automatically scanned for certain identifying phrases, formatting peculiarities, and other characteristics that can determine that a message is probably spam.
Because this automated identification is not foolproof, occasionally messages that are not spam will be incorrectly classified as spam ("false positives"), and sometimes messages that are in fact spam will not be caught ("false negatives"). To adjust for individual users preferences, it is possible to control how agressively the system tries to block spam:
Disabled does not filter any messages at all. Both spam and legitimate messages will be delivered.
Very conservative will adjust the filter to minimize the risk of false positives at the expense of more false negatives. This setting makes it unlikely that legitimate email will be blocked, but will allow more spam messages to pass through undetected.
Slightly relaxed reduces the chance for false positives on mail received from systems that are incorrectly configured, but are otherwise probably legitimate. Only a small amount of spam should pass though undetected with this setting.
Normal detection is the best setting for most users. False positives will be infrequent with this setting and only one or two percent of spam messages are likely to go undetected.
Very agressive will minimize the chance of receiving any spam at all at the expense of some messages probably being misidentified as spam. This setting should only be used when almost any spam at all is absolutely unwanted. Expect some legitimate messages, such as from opt-in mailing lists, to possibly be filtered.
The Normal detection setting is recommended for most users, especially initially. After some experience with spam filtering, you may wish to adjust the setting up or down. If messages from certain legitimate senders are consistenly misclassified, changing to Slightly relaxed will probably solve the problem.
This setting determines what action is taken for messages that the system determines are likely to be spam:
Notify of attempt will discard the spam email and deliver a notice in its place to the recipient identifying the message that was blocked.
File in spam folder will deliver the spam message to a special folder defined by the user instead of to the inbox. This option is only available when mail is configured for local delivery and not exclusively forwarded to another account. Note that POP3 mail clients will not be able to see this folder; IMAP or web mail are recommended.
Forward to address will forward the spam message to another email address. This setting should only be used for advanced configurations, and only if you have a good understanding of how the mail system operates. One possible use for this setting is to aggregate spam messages from several different accounts under one account so that they may be reviewed together for false positive messages.
Accept but discard will silently delete all messages identified as spam without any notification or confirmation.
Return to sender will discard the spam email and deliver an error message back to the original sender notifying them that their email was not delivered, but only if the sender address can be verified as being a valid address and not faked (by means of SPF, Domainkeys, or DKIM).
It is recommended that the File in spam folder setting be used at least until you have confidence that the system is classifying your mail correctly and not falsely identifying legitimate email as spam. Once you are sure the system is filtering messages to your satisfaction, it may be more convenient to simply discard all spam message by changing the setting to Accept but discard.
If the Spam action is set to File in spam folder, this field determines the name of the folder spam messages will be placed in.
If the Spam action is set to Forward to address, this field determines the email address that spam messages will be forwarded to.
If spam filtering is enabled, this setting enables filtering by the sender address of each email message. There are two possible lists than can be used for sender address filtering, one is a list of addresses to always accept (even if they would otherwise be counted as spam), and the other is a list of addresses to always reject (even if they do not appear to be spam).
If both lists are used together, any addresses that match both lists will be accepted; that is, entries in the "accept from" list override entries in the "reject from" list. See the entries for Accept mail from and Reject mail from for more information.
If spam filtering is enabled, this field may contain a list of email addresses, and patterns that match email addresses, that mail should always be allowed from, even if the spam filter classifies them as spam. This can be used to prevent mailing lists and other messages that look like spam from being blocked.
This list may contain actual email addresses, or patterns to match email addresses. Patterns are formed by using the "*" character to match any artitrary sequence of characters in an email address. For example, "*@yahoo.com" would accept all messages claiming to be from yahoo.com email addresses, "*.gov" would accept mail cliaming to be from any address at any domain under the gov top-level domain, and "david@*" would accept email from any account named "david" in any domain.
Settings in the Accept mail from list override those in the Reject mail from list (see below). This allows exceptions to be made to reject rules. For example, if the reject list contained "*@yahoo.com" and the accept list contained "david@yahoo.com", then all email claiming to be from yahoo.com would be rejected except mail from "david@yahoo.com".
If spam filtering is enabled, this field may contain a list of email address, and patterns that match email addresses, that email should not be accepted from, even if it doesn't otherwise look like spam. This can be used to prevent mail from being received from unwanted senders.
Please see the examples under the Accept mail from setting for details on how to use patterns, and information on how the Reject mail from and Accept mail from settings interact.
If spam filtering is enabled, this setting enables filtering by matching the subject line of each email message. There are two possible lists than can be used for subject line filtering, one if a list of subjects to always accept (even if they would otherwise be counted as spam), and the other is a list of subjects to always reject (even if they do not appear to be spam).
If both lists are used together, any subjects that match both lists will be accepted; that is, entries in the "accept from" list override entries in the "reject from" list. See the entries for Accept subject and Reject subject for more information.
If spam filtering is enabled, this field may contain a list of subjects, and patterns that match subjects, that if they match a message, will cause it to be allowed, even if the spam filter classifies it as spam. This can be used to prevent mailing lists and other messages that look like spam from being blocked.
This list may contain exact dubject lines to match, or patterns to match subject lines. Patterns are formed by using the "*" character to match any artitrary sequence of characters in a subject line. For example, "Re:*" would match all subjects beginning with "Re:", with the case being unimportant. Likewise, "*secret*" would match any subject that contains "secret" anywhere. If wildcards are not used, only subjects that match exactly will be accepted. The case of letters is not significant in the pattern.
Settings in the Accept subject list override those in the Reject subject list (see below). This allows exceptions to be made to reject rules. For example, if the reject list contained "*virus*" and the accept list contained "*virus*warning*", then all emails with a subject containing "virus" would be rejected unless it is followed somewhere with "warning".
If spam filtering is enabled, this field may contain a list of subjects, and patterns that match subjects, that if they match a message, will cause it to be rejectd, even if the spam filter does not classify it as spam. This can be used to block spam mail that is not blocked automatically.
Please see the examples under the Accept subject setting for details on how to use patterns, and information on how the Reject subject and Accept subject settings interact.
This setting enables email to be further classified for processing as spam based on the languages contained in the message. Unlike sender rules, the language rules do not act absolutely, rather, they change the weighting of the spam scoring algorithm.
Automated language detection is an inexact process, therefore the mechanism is designed to be conservative in deciding what languages might be present in a message and tends to generate false positive detection of languages fairly frequently, especially for languages that are very similar or have similar roots. For this reason, including languages on the Prefer languages list is not likely to increase false positive rates of spam detection, but including languages on the Avoid languages list may do so.
Language detection does not work at all on very short messages.
If language filtering is enabled, this provides a list of languages that are desired. If a message if received that is in a language that is not included in this list, that message is more likely to be classified as spam, although the language alone will not cause that.
To select multiple languages, use you normal browser convention for multiple selections (for example, control-click).
Please see the information under Language rules for more information.
If language filtering is enabled, this provides a list of languages that are unwanted. If a message is received that is in a language that is included in this list, that message is more likely to be classified as spam, although the language alone will not cause that.
To select multiple languages, use you normal browser convention for multiple selections (for example, control-click).
Please see the information under Language rules for more information.
This setting controls the scanning of incoming mail messages for viruses, trojan horses, and other types of malicious software, or "malware". Messages are checked for signatures of known viruses, and also for formatting irregularities that are typical of viruses or likely to cause security issues with email clients.
While scanning for known viruses is essentially foolproof, with little or no chance of false positives, scanning for formatting problems is a little more subject to error. For this reason, it is possible to adjust how agressively the system checks messages:
Normal detection checks for known viruses and also the most serious formatting problems, that is, ones that are known to exploit vulnerabilities in certain email client software.
Extra cautious checks for known viruses, potentially dangerous attachment types, and less serious formatting problems that have the potential to exploit vulnerabilities in certain email client software. This does not mean that all messages with these irregularies are contain viruses, however, and occasionally malformed, but harmless, messages will be blocked by this setting.
Extra paranoid checks for known viruses, potentially dangerous attachment types, and also any formatting problems at all, no matter how minor. These include problems, that while technically incorrect, are not known to represent any security risk at this time. This will cause some messages that are malformed but harmless to be blocked.
For most users, Normal detection should provide adequate security against malicious messages. If you wish to reduce the risk from possible future viruses, the Extra cautious or Extra paranoid settings might provide additional protection at the risk of falsely blocking messages that are not actually virus-infected, but are malformed or have certain attachment types.
When using the Extra cautious or Extra paranoid settings, the following are the file types that are blocked by default:
ADE, ADP, ASP, APP, BAS, BAT, CER, CHM, COM, CMD, CPL, CRT, CSH, KSH, EXE, FXP, HLP, HTA, INF, INS, ISP, ITS, JS, JSE, LNK, MAD, MAF, MAG, MAM, MAQ, MAR, MAS, MAT, MAU, MAV, MAW, MDA, MDB, MDE, MDT, MDW, MDZ, MSC, MSI, MSP, MST, OPS, PCD, PIF, PRF, PRG, PST, REG, SCF, SCR, SCT, SHB, SHS, TMP, URL, VBE, SBE, VSMACROS, VSS, VST, VSW, WS, WSC, SWF, WSH
In any case, you should not rely solely on email scanning for virus protection, but should also employ a local virus detection package.
This setting determines what action is taken for messages that the system determines are likely to be viruses:
Notify of attempt will discard the infected email and deliver a notice in its place to the recipient identifying the message that was blocked.
File in virus folder will deliver the virus message to a special folder defined by the user instead of to the inbox. This option is only available when mail is configured for local delivery and not exclusively forwarded to another account. Note that POP3 mail clients will not be able to see this folder; IMAP or web mail are recommended.
Forward to address will forward virus infected messages to another email address. This setting is almost never a good idea. It is only provided for use in very advanced configuration by users who understand exactly what they are doing and the implications of this option.
Accept but discard will silently delete all messages identified as being infected without any notification or confirmation.
Return to sender will discard the infected email and deliver an error message back to the original sender notifying them that their email was not delivered, but only if the sender address can be verified as being a valid address and not faked (by means of SPF, Domainkeys, or DKIM).
It is recommended that the Accept but discard setting be used in most cases. Unless you are particularly interested in capturing samples of viruses, it is not recommended to use File in virus folder as the risk of infection is high, since some mail clients can be infected without even opening an email.
If you wish to know when an infected message is blocked, you can use the Notify of attempt setting, but this may result in hundreds of extra messages in your inbox during a major virus outbreak. Likewise, it is not recommended to use the Return to sender option as it will only cause increased email traffic during an outbreak.
If the Virus action is set to File in virus folder, this field determines the name of the folder infected messages will be placed in.
If the Virus action is set to Forward to address, this field determines the email address that infected messages will be forwarded to.
This setting enables the automatic sending of a reply message back to the sender of any email messages received. These messages will be returned in response to personal emails (not from mailing lists) received. There are three settings that determine how frequently replies are sent:
Disabled causes no automatic responses to sent at all. If you have previously defined an auto-reply message, however, that messages is still retained for possible future use.
N Days between repeat replies limits how frequently the automatic reply is sent to any particular sender. Each time a response is sent, the date and time and sender are remembered; that particular sender will not be send another automatic reply until the specified number of days has passed. This setting is ideal for use on normal accounts while the user is out of the office; it avoids annoying senders by sending them out-of-office notifications too frequently.
Reply to every message sends an automatic response to each and every email that is received. This setting is useful for generating automatic confirmation messages to assure the sender that his message was received.
When automatic responses are enabled, this field defines the subject line of the reply message. When used for out-of-office messages, a subject similar to "John Doe is out of the office" is typically used. Even when the auto reply feature is disabled, the last value of this field is retained.
When automatic responses are enabled, this field defines the body of the reply message that is sent. When used for out-of-office messages, the body typically indicates the specific date that the recipient will be away. Even when the auto reply feature is disabled, the last value of this field is retained.
This enables the automatic addition of "signature" text to the end of messages sent sent from the account being edited. Many email clients also support the ability to add a signature and may be easier to use than enabling this setting in the server.
Note that messages that are cryptographically signed will not have the signature appended, nor will any messages that are not sent through the mail server. If you have your own server or use your ISP's server for outgoing mail, this option will probably not work.
Email messages can contain two different representations of each message, one in plain text with no formatting, and one formatted in HTML. You can specify a different signature for each part of the message if desired, this will allow the use of fonts, colors, and other formatting when the sender and recipient support it, and plain text otherwise.
Enter the signature that should be appended to messages or message parts that are plain text only, when a separate HTML signature is defined. If no HTML signature is defined, this will be used for HTML messages also.
It may be easier to first compose your signature in your email client or a word-processing program and then copy and paste it into the control panel field.
Enter the signature that will be applied only to HTML messages or message parts. If this is not defined, the plain text signature will be used for HTML messages.
It may be easier to first compose your signature in your email client or a word-processing program and then copy and paste it into the control panel field. Note that the actual HTML code must be pasted, not just the formatted representation of it's output. Try the "View source" or similar option if needed.
The server is able to verify that delivery status notifications received from other systems are legitimate responses to email that was sent by the server. This works by tagging the (normally hidden) envelope sender field with a 'cookie' that is unique for each sender on each day. When a delivery status notification is received, it is not accepted unless it contains the correct 'cookie'.
To enable tagging of outgoing message envelope sender fields, set this field to Tag outgoing messages only. With this setting, incoming message will be accepted whether they are tagged or not.
To enable both tagging of outgoing messages and filtering of incoming messages, set this field to Tag and filter status messages. With this setting, only correctly tagged status notifications will be accepted.
This option will only work if your outgoing mail is sent though Omd3.com's servers. If you use your own server or an ISP server, it is not possible to add the correct tags to outgoing messages and all incoming status notifications will be rejected. This is an advanced option; please obtain advice before enabling it if you are not sure of what you are doing.