CiviCRM Community Forums (archive)

I am using the latest version of civi 4.2.8, just upgraded last week. I started using the mailer this week and I was getting the dreaded "DB Error: unknown error".  I enabled the back trace and found that the bounce_reason was longer than the bounce_reason defined in MySQL.  The bounce reason in MySQL is a varchar of 255 but the actual reason code returned by a server can be any length.  The problem is if the length of the actual server bounce code is longer than the database field you get an error, at least is MySQL is running in strict mode.  The solution is simple either increase the field length or only store the first 255 characters in the database.  I solved it by adding a line to file /CRM/Mailing/Event/BAO/Bounce.php on line 77

if (empty($params['bounce_type_id'])) {
      $params['bounce_type_id'] = 11;
      if (empty($params['bounce_reason'])) {
        $params['bounce_reason'] = ts('Unknown bounce type: Could not parse bounce email');
      }
    }
   +++ $params['bounce_reason'] = substr($params['bounce_reason'], 0, 254);
    $bounce->copyValues($params);
    $bounce->save();
    $success = TRUE;

I am not sure if I should file a bug report for this or not.  I dont even know if this is the best place to make the change but it solves the length problem right before persisting to the database.  What is everyone else doing to prevent errors when you have a bounce_reason larger than 255 characters?  Do you not run MySQL is strict mode so it silently truncates the string?  I saw a couple of posts on this problem but none listed a final answer. 

Submitted.  Thanks for the quick response!

its fairly easy for you to go check that file and see it it made it into 4.3, the file and line is mentioned in the initial postings

lobo