Differences

This shows you the differences between two versions of the page.

--- how_to:bccs [2010/02/08 10:56] – created paul
+++ how_to:bccs [2015/09/23 13:46] – external edit 127.0.0.1
@@ Line 4: / Line 4: @@
 In most cases this will work fine. However, if the message has been BCCd to you, the recipient address will not be in the message header at all (that is the whole point of BCCd mail). The message reaches your ISP mailbox because the actual recipient is listed in the **SMTP Envelope** but most ISPs will throw that information away when they deliver the message into a POP3 mailbox. Because of this there is no automatic way that VPOP3 can work out the message's recipient(s). Instead it will deliver the message to the failed recipient address specified in the **Mail Collector -> Routing Errors** settings in VPOP3.
-Some ISP will copy the SMTP Envelope recipient information into custom header fields in the message, such as **X-RCPT-TO** or **Delivered-To**. In this case, you can tell VPOP3 to use this header information.
+=====Possible Solutions=====
+Some ISP will copy the SMTP Envelope recipient information into custom header fields in the message, such as **X-RCPT-TO** or **Delivered-To**. In this case, you can tell VPOP3 to use this header information (see the **Custom Headers** section below).
 If your ISP does not copy the SMTP Envelope information into the header your options are limited:
   * Manually. An administrator can go through the messages which were not delivered, and forward them to the appropriate person.
-  * Mappings. Many BCCd messages are actually from mailing lists. In this case the **To** header will often have the address of the mailing list in it. In this case you can create a **Mapping** of type **POP3** from the mailing list address to the user(s) who want to receive the message.
+  * [[reference:mappings|Mappings]]. Many BCCd messages are actually from mailing lists. In this case the **To** header will often have the address of the mailing list in it. In this case you can create a **Mapping** of type **POP3** from the mailing list address to the user(s) who want to receive the message.
-  * SMTP Feed. If you can switch to an incoming SMTP Feed for your mail (instead of POP3 collection), then that will allow the SMTP Envelope information to be given directly to VPOP3, so the problem will vanish.
+  * [[Incoming SMTP Feed|SMTP Feed]]. If you can switch to an incoming SMTP Feed for your mail (instead of POP3 collection), then that will allow the SMTP Envelope information to be given directly to VPOP3, so the problem will vanish. This is the recommended option if it is possible for you.
+  * Individual POP3 mailboxes. If your ISP uses its SMTP feed to sort the messages into individual POP3 mailboxes at the ISP, then VPOP3 can download the messages from those and use which mailbox the message was in to determine which local user should get the message. The BCC problem only applies to //shared// POP3 mailboxes, not to individual POP3 mailboxes.
-=====Custom Headers=====
+====Custom Headers====
 If your ISP adds custom header information, then, to tell VPOP3 about this, go to **Mail Collectors -> POP3 Routing -> Configure Routing Options** in the VPOP3 settings. In the **Special Header Fields** box put information defining the header field(s) which you want VPOP3 to look at. Some examples are:

PSCS Wiki

User Tools

Site Tools

Differences

Page Tools