Siebel Marketing Installation and Administration Guide > Installing and Configuring Email Marketing > Process of Configuring the Bounce Handler Daemon >

Configuring How the Bounce Handler Daemon Classifies Bounce Messages

You can configure how the Bounce Handler Daemon classifies bounce messages by defining custom classification rules. This topic describes how to perform this configuration task. For information about the files used to define custom classification rules, see About Creating Classification Rules for Bounce Messages.

This task is a step in Process of Configuring the Bounce Handler Daemon.

The following procedure describes how to create custom rules for classifying bounce messages.

NOTE:  The Bounce Handler Daemon processes classification rules in the order in which they appear in a customxxBounceConfig file and, when it encounters a match for a bounce, it does not evaluate rules defined further down in the file. Therefore, enter classification rules in a customxxBounceConfig file in order of importance.

To define classification rules for bounce messages

1. Navigate to the bhd_install_home/config directory.
2. Using a text editor, edit the appropriate customxxBounceConfig file.

   The file you edit will vary according to whether you want to create a classification rule by matching values in the Diagnostic Code entry, or the From header, or the Subject header of the delivery status notification message for the undelivered email. For additional information about the customxxBounceConfig files, see About Creating Classification Rules for Bounce Messages.

3. To create a classification rule by matching string values in the Diagnostic Code entry of the delivery status notification message, add the entries shown in the following table to the customDCBounceConfig file.

   Parameter	Value
   DIAGNOSTICCODEDATA=	The diagnostic code you want to match. Either enter the exact string you want to match, or enter the value in the form of a regular expression. For information on regular expression notation, see the Java 2 Platform Standard Edition 5.0 API Specification at http://docs.oracle.com/javase/1.5.0/docs/api/java/util/regex/Pattern.html#sum Information on regular expressions is also available at http://www.vogella.com/articles/JavaRegularExpressions/article.html
   CODE=	The value you want to assign bounce messages that contain the diagnostic code specified in the DIAGNOSTICCODEDATA parameter.
   HARD=	Enter either Yes or No to indicate whether or not bounce messages that include the diagnostic code specified in the DIAGNOSTICCODEDATA parameter are to be classified as hard bounces. A hard bounce refers to an email that cannot ever be delivered. A soft bounce refers to an email that cannot be delivered at present, but that can possibly be delivered in the future.

   For example, you might want to classify bounce messages that include the following diagnostic code:

   Diagnostic-Code: smtp; 5.4.7 - Delivery expired (message too old) 421-'4.7.0 [TS01] Messages from 155.91.38.221 temporarily deferred due to user complaints - 4.16.55.1; see http://postmaster.yahoo.com/421-ts01.html' (delivery attempts: 1)

   To assign these bounce messages a code of MAILBOX_CUSTOMSTATE, and to classify them as soft bounces, enter the following values:

   DIAGNOSTICCODEDATA=.*5\\.4\\.7.*
   CODE=MAILBOX_CUSTOMSTATE
   HARD=no

4. To create a classification rule by matching string values in the From header of the delivery status notification message, add the entries shown in the following table to the customFromBounceConfig file.

   Parameter	Value
   FROMDATA=	The string value in the From header that you want to match. Either enter the exact string to match, or enter the value in the form of a regular expression. See Step 3 for information on regular expressions.
   CODE=	The code you want to assign bounce messages that contain the specified string in the From header.
   HARD=	Enter either Yes or No to indicate whether or not bounce messages that include the specified string are to be classified as hard bounces.

   For example, to classify bounce messages returned from a specific Mail Transfer Agent as hard bounces, and to assign them a code of BAD_ADDRESS, enter the following values:

   FROMDATA=.*name_of_mailer.*
   CODE=BAD_ADDRESS
   HARD=yes

5. To create a classification rule by matching string values in the Subject header of the delivery status notification, add the entries in the following table to the customSubjectBounceConfig file.

   Parameter	Value
   SUBJECTDATA=	The string value in the Subject header that you want to match. Either enter the exact string to match, or enter the value in the form of a regular expression. See Step 3 for information on regular expressions.
   CODE=	The code you want to assign bounce messages that contain the specified string in the Subject header.
   HARD=	Enter either Yes or No to indicate whether or not bounce messages that include the specified string are to be classified as hard bounces.

   For example, to classify bounce messages that contain the string VACATION in the Subject header as soft bounces, and to assign them a code of AUTO_REPLY, enter the following values:

   SUBJECTDATA= (?i).*VACATION.*
   CODE=AUTO_REPLY
   HARD=no

   NOTE:  In the SUBJECTDATA field, the values (?i) indicate that the match is case-insensitive.

6. If you create custom bounce codes for the CODE parameter, you must also add the new code value to the Siebel BOUNCE_REASON_CODE Lists of Values (LOV).

   For information about customizing Siebel CRM LOVs, see Siebel Applications Administration Guide.

7. After creating a custom rule, stop and restart the Bounce Handler Daemon for the rule to take effect.