Cisco Cisco Email Security Appliance C160 Betriebsanweisung

The expiration time of the signature, in seconds.

A vertical bar-separated (i.e., 

|

) list of header fields present when the message was signed.

The tags you want to include in the signature (DKIM only).

A list of Profile Users (addresses allowed to use the domain profile for signing).

The domain in the addresses specified in the profile users must match the domain specified in the 
Domain field.

You can search through all of your existing domain profiles for a specific term. See 

 for more information.

You can also choose whether to sign system-generated messages with DKIM signatures. See 

 for more information.

You can export your existing domain profiles to a text file on the Cisco IronPort appliance. When you 
export the domain profiles, all of the profiles existing on the appliance are put into a single text file. See 

.

You can import domain profiles that you have previously exported. Importing domain profiles causes all 
of the current domain profiles on the machine to be replaced. See 

.

DomainKeys and DKIM signing is enabled on mail flow policies for outbound mail. For more 
information, see the “Configuring the Gateway to Receive Mail” chapter in the Cisco IronPort AsyncOS 
for Email Configuration Guide.

To enable signing on an outgoing mail flow policy:

On the Mail Flow Policies page (from the Mail Policies menu), click on the RELAYED mail flow policy 
(outgoing).

From the Security Features section, enable DomainKeys/DKIM Signing by selecting On.

Submit and commit your changes.

In addition to signing outbound messages, you may want to sign bounce and delay messages. You may 
want to do this to alert recipients that the bounce and delay messages they receive from your company 
are legitimate. To enable DomainKeys and DKIM signing for bounce and delay messages, you enable 
DomainKeys/DKIM signing for the bounce profile associated with the public listener.

To enable signing for bounce and delay messages: