bounce_classifier_override – Override/Augment Bounce Classifications

datasource "my_sqlite" {
  uri = ( "sqlite:/path/to/db" )
}

bounce_classifier_override {
  user_smtp_classification_override =
    ":datasource:my_sqlite:SELECT domain, bounce_code, rule FROM overrrides;"
  refresh = 900
  custom_classes = [
    99 = "profanity"
  ]
}

custom_classes

Map of user-defined bounce_codes that have a numeric value less than 100 and a user-defined description string. Registering new bounce codes in this manner will allow you to setup user_smtp_classification_override and user_mdn_classification_override rules to assign to that bounce code. This description string is currently available via the custom_logger or other internal calls.

enable_system_updates

Load unclassified bounce reasons into memory. This option must be enabled if you use the Live Bounce Updates service provided by Message Systems. Default value is 1.

refresh

Frequency (in seconds) for refreshing the bounce classifications lists. Default value is 300 seconds.

system_smtp_classification_override

Default value is /opt/msys/ecelerity/etc/updates/smtp_classification.ovr. Do not change this option without consulting support.

system_mdn_classification_override

Default value is /opt/msys/ecelerity/etc/updates/mdn_classification.ovr. Do not change this option without consulting support.

user_smtp_classification_override

SMTP classification override file. Default name of this file is user_smtp_classification.ovr.

This file is found in the /opt/msys/ecelerity/etc/ directory. The file format for SMTP overrides is: domain,bounce_code,rule, where

• domain can be the empty string, in which case the rule is considered to be global. Otherwise, the rule will only apply to responses given when talking to the specified domain.

• bounce_code is the numeric bounce classification code you want to assign. This must either be an internal code or one registered via the custom_classes directive. For more information about the internal codes, see “Bounce Classification Codes”. When adding new codes be careful not to use existing internal code numbers.

• rule can take one of two forms. If the ‘|’ character appears anywhere in the string, it will act as a globbing character in a wildcard. Otherwise, the string will be considered a simple static pattern. In both cases, the rule will return true if the pattern matches any substring of the classification text.

If you use a datasource instead of a flat-file, the datasource query must return 3 fields: domain, bounce_code, rule.

Use the prefix :datasource:ds_name:query when assigning a datasource as the value for user_smtp_classification_override. Select the fields that contain the domain name, the bounce code and the rule, in that order. When querying a flat file instead of a datasource, simply specify the path to the file.

user_mdn_classification_override

Default name of this file is user_mdn_classification.ovr.

It is found in the /opt/msys/ecelerity/etc/ directory. The file format for MDN overrides is: bounce_code,rule, where

• bounce_code is the numeric bounce classification code you want to assign. This must either be an internal code or one registered via the custom_classes directive. For more information about the internal codes, see “Bounce Classification Codes”. When adding new codes be careful not to use existing internal code numbers.

• rule can be of one of two forms. If the ‘|’ character appears anywhere in the string, it will act as a globbing character in a wildcard. Otherwise, the string will be considered a simple static pattern. In both cases, the rule will return true if the pattern matches any substring of the classification text.

Use the prefix :datasource:ds_name:query when assigning a datasource as the value for user_mdn_classification_override. Select the fields that contain the bounce code and the rule, in that order. When querying a flat file instead of a datasource, simply specify the path to the file.

bounce_classifier_override reload

Use this command to trigger a manual reload of the bounce classification overrides at runtime.

bounce_classifier_override test *``*

Use this command to determine how a specific SMTP reply is classified. This command reports the classification followed by the rule.