How to know which IPs send emails

This document details all the steps needed to add publicID in Campaign Classic delivery logs

This document's purpose is how to define which IP sent each email in a delivery.

Note:

This modification is different if you are using a single instance or mid-sourcing instance. Before doing the modification ensure you're connected to email sending instance.

To add publicID in your delivery logs you need to extend the schema first. You can proceed as follow.

Create a schema extension, under Administration > Configuration > Data Schemas > New.

For more information about schema extensions, refer to this page.
Select broadLogRcp to extend the Recipient delivery logs (nms) and define a custom Namespace. In this case it will be cus:

Note:
If your instance is in Mid-sourcing, you need to work with broadLogMid schema.

Add the new field in your extension. In this sample, you need to replace:

<element img="nms:broadLog.png" label="Recipient delivery logs" 
labelSingular="Recipient delivery log" name="broadLogRcp"/>

by:

<element img="nms:broadLog.png" label="Recipient delivery logs" 
labelSingular="Recipient delivery log" name="broadLogRcp">
   <attribute desc="Outbound IP identifier" label="IP identifier" 
name="publicId" type="long"/>
</element>

Once modifications are done, you need to update database structure so that it is aligned with its logical description.

To do this, follow the steps below:

Click the Tools > Advanced > Update database structure... menu.
In the Edit tables window, the NmsBroadLogRcp table is checked (or the broadLogMid table if your are in a Mid-sourcing environment), as below:

Caution:
Always ensure there is no other modification, except the NmsBroadLoGRcp table (or the broadLogMid table if your are in a Mid-sourcing environment). If so, uncheck other tables.
Click Next to validate. The following screen is displayed:
Click Next, and Start to start updating database structure. Index building is starting. This step can be long, depending on the number of rows in the NmsBroadLogRcp table.

Note:
Once update of the physical structure of the database is sucessfully completed, you need to disconnect and reconnect so that your modifications are taken into account.