This page covers the settings that will be applied to the SmartPop accounts.
These options control the general connection handling..
|
Property |
Description |
|
When online, check every |
This option specifies the period between successive checks, while the mail server is online.
Note: This is the best way to control SmartPop access if you use a LAN connection. |
|
Inactivity timeout
|
Defines the time the connection will wait with no data transfer before failing. |
|
Max size to download
|
Defines the maximum size of message to retrieve from the ISP's server. |
|
Leave on server for
|
Defines how long to 'leave mail on server'. Zero (0) deletes all messages after successful retrieval. |
|
Log all transactions
|
Writes additional SmartPop activity to the debug log. This option will be required to debug SmartPop problems.
|
These options control how the messages are processed to deliver them to their final destination.
SmartPop is able to examine the headers of messages to determine who the final recipient should be, the following options define which methods are used to determine who the messages are for.
|
Property |
Description | ||||||||||
|
Deliver messages to |
In the event of options below being disabled or no address being found from the analysis of the header, the mail messages will be delivered to this address. | ||||||||||
|
Unless a recipient is found that is a member of the following domain |
This sets the domain that SmartPop will use when looking for addresses to deliver to. | ||||||||||
|
Use Inbox rules |
FTGate will deliver incoming mail using the defined delivery rules - on the Rules page. | ||||||||||
|
If no match found use special header fields |
This option allows SmartPop to scan additional fields used by some ISP's to tag the actual intended recipient of the message. You can specify an additional tag in the "(include this field)" box . SmartPop recognises the following special header fields :
| ||||||||||
|
If no match found use standard header fields |
FTGate will deliver incoming mail using standard header tags, e.g. To:, cc: etc | ||||||||||
|
If no match found use 'Received for' header field |
FTGate will deliver incoming mail using the Received for: field if one is present | ||||||||||
|
If several messages have the same ID, only deliver the first |
Delete messages with matching message IDs. |
Unless your ISP supports the use of special header tags it is unlikely that all messages can be correctly delivered. The reason for this that the POP3 protocol does not permit the original envelope information for the message to be included. Thus if a message is sent to a user from a blind list or a BCC message, the actual recipient is not available to SmartPop and the final recipient cannot be determined.
In this case you should ask you ISP if they can include the additional information.
For a longer discussion of the problem see our online knowledgebase article
http://www.ftgate.com/knwldgbs/kb/article-view.asp?id=47