Remote Accounts are used to fetch mail from user accounts on external POP3 servers. You can assign Merak to check for waiting mails on a remote server. It can either be done for one account only or for the whole domain using the Domain POP feature and other related options.
Domain POP is a very powerful feature where Merak parses all messages received from the remote servers and places them in proper mailboxes based on the message headers and other information. All basic Merak features also work for remote accounts such as the Antivirus, Instant Anti Spam, Content Filters and others.
All Remote Accounts send a message to the Forward to addresses if they are not Domain POP.
C
H A P T E R9
Field Description
Name The name of this remote account. It is used purely for informational and display purposes.
Server Specifies the POP3 host name server (incoming mail server). This is the server the mailbox resides on.
Example:
pop3.demon.com
Username This is the username which is used for the authentication on the remote server. Password The password to the remote mailbox.
Forward to You are required to specify an email address (or email addresses) where all the received messages should be sent to. This will be mostly a local account.
When used with the Domain POP option you are still required to specify a special email address for cases when the recipient on the local server could not be found. APOP Check this to ensure that Merak uses the secure APOP authentication command.
The remote server must support this. APOP is a secure login using md5 encryption. Dedupe
collected mail
Merak will read the messages' Message-ID header field and if some messages have the same ID the message will be processed only once and no message duplicates will be done. This procedure works only in one session.
Leave messages on server
Merak will leave messages on the remote server after retrieving them. In other words, it will not erase them. It keeps a local logs of downloaded messages and their IDs.
Delete message if older than
This option is related to the Leave messages on server option. If the message on the remote server is older than the specified number of days it will be deleted.
Delete messages if more than
This option is related to the Leave messages on server option. If there is the specified number of messages or more on the remote server, messages will be deleted.
Schedule Specifies the schedule tasks for this remote account that need to be entered. This is the standard schedule dialog.
You can also set a global schedule account that will let you leave all of your remote account schedule properties empty.
Chapter 9 Server Windows Administration 69
In This Chapter
Remote Account - Domain POP ... 69 Remote Account - Special ... 71
Remote Account - Domain POP
Field Description
Domain POP Specifies that this remote account will be used to collect mail for the entire domain from a catch all account (also known as Domain POP). The account contains mail for the whole domain.
The messages will be resolved by parsing the headers "To: ", "Cc: " or other methods.
Example:
If a message received has the header "To: John Doe <john @doe.com>", the doe.com domain must exist on Merak and the message will be delivered to john in the doe.com domain.
If the domain does not exist or the user, the Forward to option will be used and the message will be delivered to the specified email address.
Sometimes all messages are delivered to the Forward to account. This might be caused by several reasons. If such thing happens make sure the domain in the To header matches the domain defined on Merak else use the special option Domain conversions. You can also use direct Email address routing which has the same syntax as the Merak redirect option.
Do not process received header
Specifies that the Domain POP procedure should not use the "Received: " header and the "for" item. Some remote mail servers set this field to a different email address then the one in the To header. This can cause nothing but problems.
Stop parsing if received yeilds a local address
If processing the received headers Merak will always use the first received header created in the message. When this option checked Merak will read all of the received headers and will check to find if some of them contains a local email address. If found the processing will be stopped and the address will be used.
Parse these headers By default Merak parses some given headers like To, Cc etc. This option when used lets you specify other MIME header fields for Merak to use. The window lets you specify additional header items. One per each line.
Real name address matching
Specifies that when using Domain POP Merak should try to search through actual names in the header and only lookup based on the name. Example for "John Doe <[email protected]>" Merak will look for "John Doe" on the server and if found it will deliver the message to that account. The name of the account has to be the same as the one in the email messgage.
If email You can also limit the feature above only when the email address matches the given email address.
Chapter 9 Server Windows Administration 71