Adding rules to Bounce Handler?

[JohnA]

I've got a load of bounces which when looking at the logs include this line: -

Code: Select all

std_reason :  user_unknown

I'd class that as a hard bounce but Bounce Handler is only giving it a soft bounce score.

How do I add this to the rules so that it's classes as a hard bounce? I'm pretty sure it's an edit to DADA/App/BounceHandler/Rules.pm but there's a lot in there including some regex etc. and so I could do with a little help!

[justin]

Check out the bounce handler docs that go over how to add new rules, and use the existing rules as a guide. There may already by a rule named, "user_unknown"

[JohnA]

The only documentation I can find on adding rules to Bounce Handler is for Mystery Girl back in Dada Mail 3.0.4: -

http://dadamailproject.com/support/docu ... les__rule_

Is this still relevant? Or have I missed the updated docs?

[JohnA]

As far as I can tell a lot of my bounces which got a soft bounce score meet this rule (around line 908 in DADA/App/BounceHandler/Rules.pm): -

Code: Select all

        {
            postfix_5dot0dot0_error => {
                Examine => {
                    Message_Fields => {

                        Status      => [qw(5.0.0)],
                        Guessed_MTA => [qw(Postfix)],
                        Action      => [qw(failed)],

                       #said_regex              => [(qr/550\-Mailbox unknown/)],
                    },
                    Data => {
                        Email => 'is_valid',
                        List  => 'is_valid',
                    }
                },
                Action => {

                    #unsubscribe_bounced_email => 'from_list',
                    add_to_score => 'hardbounce_score',
                },
            }
        },


in that they have a status=5.0.0, Guessed_MTA=Postfix, a Action=failed, with a valid email & list.

How can they have scored only a soft bounce score if they meet this rule?

Also, if a bounce meets more than one rule, is the order in that file important (i.e. the first match is taken)? For example I'm thinking of a broad matching: -

Code: Select all

        {
            my_wide_net => {
                Examine => {
                    Message_Fields => {

                        Action                  => [qw(failed)],
                        std_reason              => [qw(user_unknown)],
                    },
                    Data => {
                        Email => 'is_valid',
                        List  => 'is_valid',
                    },
                },
                Action => {

                    add_to_score => 'hardbounce_score',
                },
            }
        },

would this be best placed before or after all the other rules if I want it to take priority?

I think it would help for trouble-shooting if in the bounce handler report (after clicking on an email in the scorecard) gave the label for the matching rule (e.g. postfix_5dot0dot0_error or my_wide_net for the above examples).

[justin]

Also, if a bounce meets more than one rule, is the order in that file important (i.e. the first match is taken)? -

Yeah, the first rule found will be used.

[JohnA]

Yeah, the first rule found will be used.

Thanks Justin :)

I saw another thread (Hard Bounces Incrementing By 1) which might be a related issue. I am sure my hard bounces were being missed by the default rules. I'll try putting my "catch all" at the top of the rules list for now...

Hope you enjoyed your holiday :)