CiviCRM Community Forums (archive)

I think I have just about everything configured properly. CiviMail sends emails, they bounce to the proper email address, and there are no problems connecting to the IMAP folder on Google Apps.

However, whenever the bounce processor runs and actually processes a bounced email, I get an error message like this:

Failed Processing: Delivery Status Notification (Failure), Action: b, Job ID: 17, Queue ID: 16, Hash: 207824e628fccb21. Reason: DB Error: unknown error

The email is still moved to the /processed folder but CiviCRM does not give any indication that an email bounced.

What troubleshooting/debugging steps can I use to get to the bottom of this?

There is no error in that log file.

It's a new install.

Is there some sort of logging/debugging I can turn on?

So I enabled backtrace and, critically, DAO debugging. Here's the relevant part (I have more if we need it, but I think this gets to the bottom of the issue):

CRM_Mailing_Event_BAO_Bounce   : QUERY       : INSERT INTO civicrm_mailing_event_bounce (event_queue_id , bounce_type_id , bounce_reason , time_stamp ) VALUES ( 3 ,  6 , 'Delivery to the following recipient failed permanently: bounceemail@***********.com Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 Requested action not taken: mailbox unavailable (state 13). ----- Original message ----- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=***************.org; s=google; h=mime-version:content-type:reply-to:from:subject:list-unsubscribe :message-id:to:precedence:x-civimail-bounce:date; bh=ti5hWFb/dV43v841Da1O81Jr60nOiEfsxGhcbwtmefU=; b=7/N0r0FBXE3JoJfE6bdGdYUbEMqc6ZS/ectwvgawL+nn6DkyfgHAnHVkDphrg4ONes 2Es+ls/fPs0i8pLS1N1iPqbxqSEflQ1Ba1yN4bohSigJDOT3KnNaU8ezM4AJt0DkDBH/ LGIWXWbkLp3TGce4Or//tL3ecca5H5k4LQqZk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:content-type:reply-to:from:subject:list-unsubscribe :message-id:to:precedence:x-civimail-bounce:date:x-gm-message-state; bh=ti5hWFb/dV43v841Da1O81Jr60nOiEfsxGhcbwtmefU=; b=DT08bS/RZwYqeT5og2+kLnM51TLQ5LmikqMsM+8iCGWn35iy/wiB9UUziV3hSpfSJ5 ts/SagdEVU9qnCH+3xNZPmpa7stGvd7OcXzDOFJQ8xJGFLlC87qDKmpu3RTXQeXcI7I8 ZB9GulR3UXXZ8wzL5Pe2yk5Z0PlZXFgz55z19My0n1Kf5oI6nku9dbiTDSUcbtTCmQfD H8J9tBPMZSiU5AExxiHtd+EzmCo7fvftxQuKxYs5DNfzlrHYDym31fELkbRTJOPZsRuS MxCN2SkKHbE96kAFge2gGJAS4KFM3Wy5tGMKupuFpq3GO6P/Kl0fJ3bS+DtD8+B+V1/T JhPQ== Received: by **.***.***.*** with SMTP id bh2mr17814432igc.70.1354083406865; Tue, 27 Nov 2012 22:16:46 -0800 (PST) Return-Path: <delivery@***************.org> Received: from ***.***************.org (***************pc.org. [***.***.***.***]) by mx.google.com with ESMTPS id az6sm3568911igb.11.2012.11.27.22.16.46 (version=SSLv3 cipher=OTHER); Tue, 27 Nov 2012 22:16:46 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=\"=_0f6aeb9d9c7a6ab948195656512f56c4\" Reply-To: \"test\" <******@***************.org> Return-Path: delivery+b.4.3.e9de94bdb9dbfdf2@***************.org From: test <delivery@***************.org> Subject: Another Test Email Message List-Unsubscribe: <mailto:delivery+u.4.3.e9de94bdb9dbfdf2@***************.org> Message-ID: <delivery+m.4.3.e9de94bdb9dbfdf2@***************.org> To: ************ <bounceemail@***************.com> Precedence: bulk X-CiviMail-Bounce: delivery+b.4.3.e9de94bdb9dbfdf2@***************.org Date: Wed, 28 Nov 2012 06:16:49 +0000 X-Gm-Message-State: ALoCoQkKZCSh+Qg3wFvrZ5lgYbsv1oEZu0d3pMb96yxB0Lpznd3nTXaaWBrhRmXLk4gq/tVwhS03 Sample Header for HTML formatted content. [1] T [2]est 2 Email! Greetings **************, Your 2 Team News and Events Sunday October 20 HELPFUL TIPS Tokens Click \"Insert Tokens\" to dynamically insert names, addresses, and other contact data of your recipients. Plain Text Version Some people refuse HTML emails altogether. We recommend sending a plain-text version of your important communications to accommodate them. Luckily, CiviCRM accommodates for this! Just click \"Plain Text\" and copy and paste in some text. Line breaks (carriage returns) and fully qualified URLs like http://***.***************.org/wp-content/plugins/civicrm/civicrm/extern/url.php?u=4&qid=3 are all you get, no HTML here! Play by the Rules The address of the sender is required by the Can Spam Act law. This is an available token called domain.address. An unsubscribe or opt-out link is also required. There are several available tokens for this. _http://***.***************.org/?page=CiviCRM&q=civicrm/mailing/optout&reset=1&jid=4&qid=3&h=e9de94bdb9dbfdf2_ creates a link for recipients to click if they want to opt out of receiving emails from your organization. _http://***.***************.org/?page=CiviCRM&q=civicrm/mailing/unsubscribe&reset=1&jid=4&qid=3&h=e9de94bdb9dbfdf2_ creates a link to unsubscribe from the specific mailing list used to send this message. Click on \"Insert Tokens\" to find these and look for tokens named \"Domain\" or \"Unsubscribe\". This sample template includes both required tokens at the bottom of the message. You can also configure a default Mailing Footer containing these tokens. Composing Offline If you prefer to compose an HTML email offline in your own text editor, you can upload this HTML content into CiviMail or simply click \"Source\" and then copy and paste the HTML in. Images Most email clients these days (Outlook, Gmail, etc) block image loading by default. This is to protect their users from annoying or' ,  20121128061730 )
CRM_Core_DAO   : QUERY       : COMMIT
Failed Processing: Delivery Status Notification (Failure), Action: b, Job ID: 4, Queue ID: 3, Hash: e9de94bdb9dbfdf2. Reason: DB Error: unknown error

I believe the query fails because bounce_reason in the query exceeds the 255 character limit set in the database table--bounce_reason is VARCHAR(255).

What's the best way to fix this? Is there some sort of built in trim function that should be called and isn't?

Call for Proposals: Implementing CiviCRM at Médecins Sans Frontières / Doctors Without Borders (MSF) South Africa
1.0   MSF Background
Médecins Sans Frontières / Doctors Without Borders (MSF) is an international humanitarian aid organisation that provides emergency medical assistance to populations in distress in more than 60 countries. MSF was founded in 1971 to provide emergency medical assistance and to speak out about the plight of its patients. In 1999, in recognition of its work to alleviate human suffering, MSF was awarded the Nobel Peace Prize
Located in Johannesburg, MSF South Africa was established in 2006. The office now conducts communication and fundraising activities, and supports MSF programmes worldwide by providing medical expertise and recruiting fieldworkers.

2.0   Current software and number of users
MSF South Africa is currently using software that was originally designed to manage regular, monthly debit order donations but that has subsequently been modified to capture cash donors.
However problems remain, for example, in the software’s ability to segment donors, to generate automatic thank you notes and tax receipts, and to fulfil marketing and stewardship needs.
A total of four fundraising officers use the software to manage a growing database of nearly 20,000 donors.

3.0   Technical functionalities required from CiviCRM
MSF South Africa is in need of an effective tool to manage its relationship with its growing donor base. We have selected CiviCRM, and would now like to commission a consultant to customise the database to our requirements and assist with the transition.
Successful proposals will cater for MSF South Africa’s specific requirements, as well as compelling, additional requirements that prospective consultants may consider necessary given previous experience implementing such systems.
4.0   Summary of CiviCRM requirements
Should you be interested in submitting a proposal for this job, please contact the MSF Data Supervisor Mthulisi Ncube to obtain the detailed MSF requirements   on 0800 000331.

What follows is a summary of MSF South Africa’s CiviCRM requirements:
•   Register and centralise all relationships between MSF SA and our donors;
•   Provide a set of tools that will facilitate the donor categorisation;
•   Develop a powerful tool for data analysis and report generation based on templates;
•   Manage different kinds of relationships between contacts, companies and organisations;
•   Provide a flexible system that will facilitate the introduction of information or MSF contacts, including donors, service providers and volunteers;
•   Promote and facilitate fundraising actions with the management of campaigns and mailings;
•   Integrate a tool to manage financial data;
•   Migrate data from the old database to the new system.

5.0   Your proposal must detail:
•   How you will implement CiviCRM to meet our listed needs and yet guarantee its adaptability to possible future needs;
•   Examples of three implementations of CiviCRM you have completed in the past 24 months, including your approach and lessons learned;
•   The level of support you are willing to offer and the associated cost;
•   The level of training, expected outcomes, requirements and cost;
•   Itemised project details.

6.0   Contacts and deadline
•   Should you have any questions, please contact Mthulisi Ncube on 0800 000331
•   All proposals must be submitted on or before the 31st of December 2012.
•   Only shortlisted consultants will be contacted.