This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
how_to:bccs [2013/07/22 12:05] – [BCCd mail not being delivered] paul | how_to:bccs [2013/07/22 12:07] – [Possible Solutions] paul | ||
---|---|---|---|
Line 6: | Line 6: | ||
=====Possible Solutions===== | =====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. | + | 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 |
If your ISP does not copy the SMTP Envelope information into the header your options are limited: | 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. | * 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: |
- | * [[Incoming SMTP Feed|SMTP Feed]]. If you can switch to an incoming SMTP Feed for your mail (instead of POP3 collection), | + | * [[Incoming SMTP Feed|SMTP Feed]]. If you can switch to an incoming SMTP Feed for your mail (instead of POP3 collection), |
- | =====Custom Headers===== | + | ====Custom Headers==== |
If your ISP adds custom header information, | If your ISP adds custom header information, | ||