CRM-15934: added a trickier Invalid pattern
authorJaka Kranjc <lynxlynxlynx@sourcemage.org>
Sat, 7 Feb 2015 14:12:44 +0000 (15:12 +0100)
committerjitendrapurohit <jitendra.purohit@webaccessglobal.com>
Mon, 23 Feb 2015 10:29:32 +0000 (15:59 +0530)
lots of responses start with "Recipient address rejected" and then provide
a concrete error on which we can categorize. A bunch of them only provide the
email's domain instead of the error, eg.:
Recipient address rejected: planet.si

CRM/Upgrade/Incremental/sql/4.6.alpha6.mysql.tpl
xml/templates/civicrm_data.tpl

index 8d685ac2224d4daf2cc39ed11d15af013783baf5..807c404094a735bf97cd5ac43bcf54b22a813c6c 100644 (file)
@@ -60,7 +60,8 @@ INSERT INTO civicrm_mailing_bounce_pattern (bounce_type_id, pattern)
       (@bounceTypeID, 'no one at this address'),
       (@bounceTypeID, 'misconfigured forwarding address'),
       (@bounceTypeID, 'account is not allowed'),
-      (@bounceTypeID, 'Address .<[^>]*>. not known here');
+      (@bounceTypeID, 'Address .<[^>]*>. not known here'),
+      (@bounceTypeID, 'Recipient address rejected: ([a-zA-Z0-9-]+\.)+[a-zA-Z]{2,}');
 
 UPDATE `civicrm_mailing_bounce_pattern` SET `pattern` = 'address(es)?( you (entered|specified))? (could|was)( not|n.t)( be)? found' WHERE `id` = 44;
 UPDATE `civicrm_mailing_bounce_pattern` SET `pattern` = 'address(ee)? (unknown|invalid)' WHERE `id` = 45;
index cc966a3fdb24012ba77d99ce7deb2920cf9e3024..7e1ffe1ede7df400d58dbc2bee9ad3d2651c4eec 100644 (file)
@@ -1280,7 +1280,8 @@ INSERT INTO civicrm_mailing_bounce_pattern
     (@bounceTypeID, 'no one at this address'),
     (@bounceTypeID, 'misconfigured forwarding address'),
     (@bounceTypeID, 'account is not allowed'),
-    (@bounceTypeID, 'Address .<[^>]*>. not known here');
+    (@bounceTypeID, 'Address .<[^>]*>. not known here'),
+    (@bounceTypeID, 'Recipient address rejected: ([a-zA-Z0-9-]+\.)+[a-zA-Z]{2,}');
 
 INSERT INTO civicrm_mailing_bounce_type
         (name, description, hold_threshold)