This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
reference:pop3_collection [2011/10/20 15:59] – paul | reference:pop3_collection [2018/11/14 10:45] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 30: | Line 30: | ||
===Notes: | ===Notes: | ||
- | - If the maximum message size is exceeded, VPOP3 will send a message to the intended recipient(s) asking if they want to download the message. If they reply to that message, VPOP3 will download the message at the next scheduled connection as long as the message was not first seen over 14 days ago | + | ==(1) Maximum Message Size== |
- | | + | If the maximum message size is exceeded, VPOP3 will send a message to the intended recipient(s) asking if they want to download the message. If they reply to that message, VPOP3 will download the message at the next scheduled connection as long as the message was not first seen over 14 days ago |
+ | |||
+ | ==(2) Leave Messages On Server== | ||
+ | If '' | ||
+ | |||
+ | Like other mail software, VPOP3 uses the '' | ||
+ | |||
+ | There are two situations where this can cause problems: | ||
+ | - if the remote server reuses '' | ||
+ | - if the remote server gives new '' | ||
Line 44: | Line 53: | ||
* [[Attempt to work with a single email address]] | * [[Attempt to work with a single email address]] | ||
* [[Search subject lines for a marker]] | * [[Search subject lines for a marker]] | ||
+ | |||
+ | =====Routing Errors===== | ||
+ | The **Routing Errors** tab is only visible if the **POP3 Routing** option is set to **Route by parsing message headers**. | ||
+ | |||
+ | The **Routing Errors** tab settings tell VPOP3 what it should do if it receives a message and, after parsing the message headers, it cannot work out who the message is for. Common reasons for routing errors are if the recipient address is misspelled, so that VPOP3 does not recognise it, or if the message was sent using a [[how to: | ||
+ | |||
+ | The main choice is what to do with the incoming message which it can't handle automatically | ||
+ | * **Send an Error Message to Main Administrator** - this sends a message to the [[admin_settings# | ||
+ | * **Send the Incoming Message to Main Administrator** - this sends the original message to the main administrator, | ||
+ | * **Send an Error Message to < | ||
+ | * **Send the Incoming Message to < | ||
+ | * **Bounce to sender and don't keep local copy** - this sends a message back to the original sender, and discards the message | ||
+ | * **Ignore** - the problem message is simply ignored. This can be useful if you expect there to be messages for unrecognised recipients - eg if all your domain' | ||
+ | |||
+ | There are a couple of extra options | ||
+ | * **Send a bounce message to the sender** - if this is checked, then a bounce message will be sent to the original sender as well as the main action above (if the main action is ' | ||
+ | * **Customise Bounce Message** - this lets you customise the bounce message which is generated | ||
+ | * **Don' | ||
+ | |||
+ | Note that sending a bounce message to the sender can cause [[howto: | ||
+ | |||
+ | =====Messages===== | ||
+ | The **Messages** tab lists all the messages which VPOP3 has seen on the ISP's POP3 mailbox. | ||
+ | |||
+ | Using this list you can tell VPOP3 to re-download or delete some messages, or during its normal download connection. |