This page discusses a method of BCCing every message going through Xeams to a different recipient. This method is useful if you're using a third-party journaling or email archiving service that needs a copy of the message.
Since this is not a very common feature, this setting cannot be done using the web interface. Instead, add a file called BccRecipients.xml in the $INSTALL_DIR\config folder. A sample XML file is displayed below with comments on how to set it up.
<?xml version="1.0" encoding="UTF-8"?>
<BccRules>
<!-- There can be multiple BccRecipients nodes -->
<BccRecipients>
<!-- Represents the email address where BCC messages are sent. -->
<Recipient>bcc.recipient@example.com</Recipient>
<!-- Conditions have two attributes: field and value. Possible values for fields are:
sender - containing either a full email address or a domain.
recipient - containing either a full email address or a domain.
senderIP - containing either a full IP address or a CIDR notation
-->
<Conditions>
<!--Multiple conditions are ORed together. For example, the following means that the
BCC recipient will be added if the sender IP is either 192.168.4.10 or 192.168.4.5. -->
<Condition field="senderIP" value="192.168.4.10" />
<Condition field="senderIP" value="192.168.4.5" />
</Conditions>
</BccRecipients>
<BccRecipients>
<Recipient>bcc1.recipient@example.com</Recipient>
<Conditions>
<Condition field="sender" value="sales@myorg.com" />
</Conditions>
</BccRecipients>
<BccRecipients>
<Recipient>bcc2.recipient@example.com</Recipient>
<Conditions>
<Condition field="recipient" value="support@myorg.com" />
</Conditions>
</BccRecipients>
<BccRecipients>
<Recipient>bcc3.recipient@example.com</Recipient>
<Conditions>
<Condition field="senderIP" value="10.0.0.0/24" />
</Conditions>
</BccRecipients>
<!-- No conditions mean it will always pass, and a BCC will be added to every message. -->
<BccRecipients>
<Recipient>alwayson@example.com</Recipient>
</BccRecipients>
</BccRules>