Answers.Body: <p>The solution for me was to set up a Bounce Processing email account in <strong>Administer menu > CiviMail > Mail Accounts</strong>.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-04-29T15:56:06.413Z
Answers.Text: Yes this worked for me too. Would love to know how and why....
Answers.UserDisplayName: Tony Horrocks
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-31T09:56:44.677Z
Answers.LastActivityDate: 2017-09-01T04:56:38.517Z
Answers.LastEditDate: 2017-09-01T04:56:38.517Z
Answers.UserDisplayName: Slingshot Design
Answers.Body: <p>We're using Drupal 7.56 and CiviCRM 4.7.25 and we also have this problem. None of the above solutions worked.</p>
  
  <p>This seems to be a very general type of error that can be inadvertently triggered by a great many causes. For us, we eventually discovered that our SMTP gateway had ceased authorizing payment on our account and was declining our traffic from CiviSMTP.</p>
  
  <p>So if you're receiving this error, it might be a good idea to double check that your expected mail path actually works as you expect it to before you go digging through code. :-)</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-12-13T17:07:02.460Z
Answers.Text: Similar here. With a 4.7.22 CiviCRM version in our case we exceed quota asigned to our SMTP gateway. Filling again our SMTP gateway with more credit the error disappears.
Answers.UserDisplayName: Francesc Bassas i Bullich
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-12-15T18:31:55.377Z
Answers.Text: Thanks, this was a good clue. In my case, it was due to an oversized attachment being rejected by the mail system. It was only the server logs that diagnosed the details of why the mail() call failed.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-13T00:05:02.073Z
Answers.LastActivityDate: 2017-10-19T21:12:40.770Z
Answers.LastEditDate: 2017-10-19T21:12:40.770Z
Answers.UserDisplayName: DMCoding
Answers.Body: <p>For me (CiviCRM 4.7.8) the problem was related to some changes introduced in 4.7.8. regarding permission checks (see <a href="https://github.com/civicrm/civicrm-core/pull/8415" rel="nofollow">GitHub PR #8415</a>, <a href="https://issues.civicrm.org/jira/browse/CRM-18159" rel="nofollow">Jira issue CRM-18159</a>).</p>
  
  <p>Reverting those changes fixed the problem:</p>
  
  <p>Remove the acl clauses by replacing </p>
  
  <pre><code>list($aclJoin, $aclWhere) = CRM_ACL_BAO_ACL::buildAcl($senderId);
  </code></pre>
  
  <p>with</p>
  
  <pre><code>$aclJoin = ""; $aclWhere = "";
  </code></pre>
  
  <ol>
  <li>in <code>CRM/Mailing/BAO/Mailing.php</code> in function <code>getTestRecipients</code> (line 926)</li>
  <li>and in <code>CRM/Mailing/BAO/MailingJob.php</code> in function <code>deliver</code> (line 502)</li>
  </ol>
  
  <hr>
  
  <h2>Some details from Debugging</h2>
  
  <p>While CiviCRM works fine on another installation with 4.7.8 in our live system there seems to be some issue with ACL (access control) related to mailings, causing CiviCRM to block the user trying to send a mailing to address any contact.</p>
  
  <p>It seems like the database table <code>group_contact_cache</code> is not filled with the necessary entries in the affected system. However, I don't know why that could be the case.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-05T13:30:31.080Z
Answers.Text: As @Cibes have mentioned in a comment, the related issue is issues.civicrm.org/jira/browse/CRM-19036 and CiviCRM 4.7.12 is now released. I can confirm that the update solves this problem.
Answers.UserDisplayName: samuelsov
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-05T09:20:02.130Z
Answers.LastActivityDate: 2016-09-17T08:17:12.943Z
Answers.LastEditDate: 2016-09-17T08:17:12.943Z
Answers.UserDisplayName: sleidig
Answers.Body: <p>I was having same problem on Drupal 7.43 / Civi 4.76 and managed to fix it. Unfortunately I'm not sure which action I took achieved the fix - perhaps one of the following will help you.</p>
  
  <ul>
  <li>cleared all Drupal and Civi caches via the frontend</li>
  <li>emptied Civi Cache tables via phpMyAdmin</li>
  <li>deleted the contents of the templates_c folder</li>
  <li>deleted the contents of the ConfigAndLog folder</li>
  <li>deleted the cache folder in my extensions directory</li>
  <li>I disabled and uninstalled the Cividesk Sparkpost extension</li>
  <li>installed the Proexchange extension github.com/proexchange/com.pesc.sparkpost.</li>
  </ul>
  
  <p>In case this unfairly maligns the Cividesk Sparkpost extension note that I have it working on another of our sites that uses Drupal 6 / Civi 4.76. I am not sure whether it was the problem but I did keep getting errors which may have to do with something else in my installation.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-13T21:13:11.580Z
Answers.Text: For me, clearing civi and drupal caches and emptying cache table in database didn't help. Neither did deleting templates_c, ConfigAndLog or extensions/cache folder. also I don't have the sparkpost extension
Answers.UserDisplayName: sleidig
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-14T19:28:56.883Z
Answers.Text: I am having the same problem.  I am also having an issue with multiple emails being sent when an email is accepted - such as the email for the administration account.  By multiple I mean dozens until the draft mailing is deleted.
Answers.UserDisplayName: Dave T
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-21T15:15:56.187Z
Answers.LastActivityDate: 2016-04-21T15:15:56.187Z
Answers.UserDisplayName: Davy Ivins
Answers.Body: <p>I know this is an old thread but on the off chance, someone else finds this helpful. I came across this error when I had an unclosed token in an email. I'd use the checksum token but inadvertently removed the final bracket - the email had "www.mysite.org?cid1={contact.contact_id}&amp;{contact.checksum/"</p>
  
  <p>Once I added back in the final '}' all was back to working order!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-07-09T18:16:13.520Z
Answers.LastActivityDate: 2019-07-09T18:16:13.520Z
Answers.UserDisplayName: RayWright
Answers.Body: <p>If you are using Amazon SES for sending email, Check Return-Path email domain verified by Amazon SES (it return with error message "554 Message rejected")</p>
  
  <p>More Details here : <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html" rel="nofollow noreferrer">http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html</a></p>
  
  <p>Same might be applicable for other provider, Check CiviCRM log for more details.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-07T09:10:27.470Z
Answers.LastActivityDate: 2017-03-07T09:10:27.470Z
Answers.UserDisplayName: Sunil Pawar
Answers.Body: <p>We also had this problem. Following this other issue <a href="https://issues.civicrm.org/jira/browse/CRM-19685" rel="nofollow noreferrer">CRM-19685</a> and solving it applying the following SQL script fixes the 'Send test' problem.</p>
  
  <p><code>UPDATE `civicrm_contact` SET `preferred_mail_format` = 'Both' WHERE `preferred_mail_format` IS NULL;</code></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-25T11:16:23.117Z
Answers.LastActivityDate: 2016-11-25T11:16:23.117Z
Answers.UserDisplayName: Francesc Bassas i Bullich
Answers.Body: <p>We noticed this issue recently on 4.7.15 but forgot to follow <a href="https://civicrm.stackexchange.com/questions/10964/smtp-connection-failing-problem/10966#10966">this fix</a> post upgrade. Once we applied it, the error cited above disappeared. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-19T07:36:51.407Z
Answers.LastActivityDate: 2017-01-19T07:36:51.407Z
Answers.LastEditDate: 2017-04-13T12:53:13.207Z
Answers.UserDisplayName: user3742
Answers.Body: <p>I think perhpas you are confused about what "send test" does.</p>
  
  <p>The number near the recipients field is the number who will receive the finished email. It has nothing to do with the <strong>send test</strong> buttons. (Possibly it would be better if they were labelled Send Draft)  </p>
  
  <p><strong>Send test</strong> either sends one email to the email address in the box if you use the <strong>Send test email to:</strong> panel (the middle panel in the image below), or it sends a test email to the group you have chosen in the right panel (below <strong>Sent test email to group:</strong> . In the image below, the test email would be sent to the Case resouces group if the <strong>send test</strong> button directly below that name was clicked.<a href="https://i.sstatic.net/DR68N.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/DR68N.png" alt="test email image"></a> </p>
  
  <p>The idea of sending a test email to one or a few people before sending the actual email is so that you can check links and formating or perhaps so that others can proofread or approve the email, before you sent it out.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-23T13:51:22.510Z
Answers.Text: Thanks for your feedback.
  
  Unfortunately I'm not confused, if I use the Send test button on either "Send test email to:" or "Send test email to group:" the error message I receive is the same "Could not identify any recipients. Perhaps the group is empty?".
  
  Is seems that before sending the test it checks that you have valid recipients on your mailing, but I do have indeed valid recipients so I guess this check is bogus somewhere
Answers.UserDisplayName: Stefano
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-24T06:37:54.900Z
Answers.Text: Sorry, I was confused by your reference ot the number of people in the mailing group which should have nothing to do with the test. Do you get the same error message using either Send test button?
Answers.UserDisplayName: JoAnne
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-24T17:03:15.747Z
Answers.Text: Yes, same error using both buttons
Answers.UserDisplayName: Stefano
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-21T07:38:47.417Z
Answers.Text: I'm having the same problem on Drupal 7.43  Civi 4.7.6.
Answers.UserDisplayName: Davy Ivins
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-11-07T09:13:19.633Z
Answers.Text: I having the same problem. How it will be solve?
Answers.UserDisplayName: Md Maidul Islam
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-23T13:35:38.163Z
Answers.LastActivityDate: 2016-03-23T13:35:38.163Z
Answers.UserDisplayName: JoAnne
Answers.Body: <p>These suggestions have not worked for me (now on 4.7.11). The workaround for this has been to reuse &amp; edit old successful mailings, which seem unaffected.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-09-11T03:02:01.407Z
Answers.LastActivityDate: 2016-09-11T03:02:01.407Z
Answers.UserDisplayName: Bryan
Answers.Body: <p>I had the exact same problem, but it was being caused by an incorrect password in the SMTP Outbound Mail Settings (someone had changed the password and not updated CiviCRM!). </p>
  
  <p>More generally it is probably worth testing the Outbound Mail Settings as a problem here could be causing this issue.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-29T08:51:13.673Z
Answers.LastActivityDate: 2018-03-29T08:51:13.673Z
Answers.UserDisplayName: Ben
Answers.Body: <p>The message identifies one possible cause, but many other problems lead to the same message.  A more verbose version might read:</p>
  
  <p>"No mails were successfully sent.  This could be caused by many
  different issues.  Known causes include:</p>
  
  <ul>
  <li>could not identify any recipients</li>
  <li>errors relating to the SMTP service, including authentication or network problems</li>
  <li>invalid tokens in your mail  </li>
  <li>no Bounce Processing account configured"</li>
  </ul>
  
  <p>Check <a href="https://civicrm.org/extensions/civicrm-log-viewer" rel="nofollow noreferrer">the CiviCRM log file</a> - some causes are logged there.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-02T16:41:30.840Z
Answers.LastActivityDate: 2019-09-02T16:41:30.840Z
Answers.UserDisplayName: Aidan
Answers.Body: <p>I use CiviSMTP</p>
  
  <p>Actually, it is a known issue : there is a patch there :
  <a href="https://forum.civicrm.org/index.php?topic=37194.0" rel="nofollow noreferrer">https://forum.civicrm.org/index.php?topic=37194.0</a></p>
  
  <p>But why isn't it finally fixed in the standard CiviCRM ?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-26T08:28:25.740Z
Answers.LastActivityDate: 2017-03-26T08:28:25.740Z
Answers.UserDisplayName: Jacques-Marie Moranne
Answers.Body: <p>Same problem :</p>
  
  <p>I have just upgraded to Civi 4.7.16 (Drupal 7.54) :</p>
  
  <ul>
  <li>"Send Test" issues the same message (Could not Identify ...)</li>
  <li>If I overpass the test and send the mailing, the mailing fails :
  Intended recipients 206
  Successful deliveries 0
  Bounces 21 (all for "syntax" reason)</li>
  </ul>
  
  <p>CRON Mail Report says :</p>
  
  <p>*Parameters raw (from db settings): 
  instanceId=[ID of report instance] required
  format=[csv or print] optional-output CSV or print-friendly HTML, else PDF</p>
  
  <p>Parameters parsed (and passed to API method): 
  a:3:{s:7:"version";i:3;s:10:"instanceId";s:32:"[ID of report instance] required";s:6:"format";s:67:"[csv or print] optional-output CSV or print-friendly HTML, else PDF";}</p>
  
  <p>Full message: 
  Finished execution of Mail Reports with result: Echec, Error message: A fatal error was triggered:  is not of type String*</p>
  
  <p>I have no ACL defined</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-22T08:54:59.810Z
Answers.LastActivityDate: 2017-03-22T08:54:59.810Z
Answers.UserDisplayName: Jacques-Marie Moranne
Answers.Body: <p>Check that every contact on the list is not 'on hold'.</p>
  <p>I deleted the mail server and since this group was used as the first test, all  contacts on the list were set to 'on hold'.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-11-27T06:15:32.787Z
Answers.LastActivityDate: 2021-11-27T06:15:32.787Z
Answers.UserDisplayName: Interlated
Body: <p>I am experiencing a weird issue on my CiviCRM 4.7.3 on Joomla 3.5.0 (also happening on some 4.7.8 on Drupal 7)</p>
  
  <p>When I try to send or schedule a mailing and I hit "Send test" I receive an error saying <code>Could not identify any recipients. Perhaps the group is empty?</code>. However I have selected a group with valid recipients inside (I can see the yellow text near the recipients field saying "~81 recipients").</p>
  
  <p>If I ignore the test and try to send the mailing, it does not give me any errors, but no emails are sent and if I check the report it says:</p>
  
  <pre><code>Intended Recipients     1
  Successful Deliveries   0 (0.00%)
  </code></pre>
  
  <p>The Mail module works - I can send mail through CiviCRM to a contact directly, only through CiviMail there is a problem.</p>
  
  <h1>Further debugging information</h1>
  
  <p>After a lot of debugging I can narrow the problem down to an ACL issue:</p>
  
  <p>In <code>CRM/Mailing/BAO/MailingJob.php</code> the <code>deliver()</code> function is reached but the query (<code>$eq-&gt;query</code>, <code>$eq-&gt;fetch</code>) doesn't return any results.</p>
  
  <p>This is due to the condition from <code>$aclWhere</code>, for me it is:</p>
  
  <pre><code>( ( `civicrm_group_contact_cache-ACL`.group_id IN (8) ) )
  </code></pre>
  
  <p>which is joined in the full query by</p>
  
  <pre><code>LEFT JOIN civicrm_group_contact_cache `civicrm_group_contact_cache-ACL` ON contact_a.id = `civicrm_group_contact_cache-ACL`.contact_id
  </code></pre>
  
  <p>while I do get a contact joined in the query, an entry in <code>civicrm_group_contact_cache</code> seems to be missing. What is that table for, anyway?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-04T21:52:07.243Z
Comments.Text: I have the same problem on CiviCRM 4.7.8. for Drupal 7.
Comments.UserDisplayName: sleidig
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-04T22:15:17.000Z
Comments.Text: edited the question so my further findings from debugging are visible to narrow down the problem. Unfortunately I still don't see a fix yet ...
Comments.UserDisplayName: sleidig
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-05T07:29:41.417Z
Comments.Text: see also this bug ticket: https://issues.civicrm.org/jira/browse/CRM-19036
Comments.UserDisplayName: sleidig
Tags: <civimail><mailing>
Title: Mailing issue. Could not identify any recipients. Perhaps the group is empty?
ThreadText: # Mailing issue. Could not identify any recipients. Perhaps the group is empty?
  
  (Asked by: username_0 on 2016-03-23)
  
  I am experiencing a weird issue on my CiviCRM 4.7.3 on Joomla 3.5.0 (also happening on some 4.7.8 on Drupal 7)
  
  When I try to send or schedule a mailing and I hit "Send test" I receive an error saying `Could not identify any recipients. Perhaps the group is empty?`. However I have selected a group with valid recipients inside (I can see the yellow text near the recipients field saying "~81 recipients").
  
  If I ignore the test and try to send the mailing, it does not give me any errors, but no emails are sent and if I check the report it says:
  
  ```
  Intended Recipients     1
  Successful Deliveries   0 (0.00%)
  
  ```
  
  The Mail module works - I can send mail through CiviCRM to a contact directly, only through CiviMail there is a problem.
  
  # Further debugging information
  
  After a lot of debugging I can narrow the problem down to an ACL issue:
  
  In `CRM/Mailing/BAO/MailingJob.php` the `deliver()` function is reached but the query (`$eq->query`, `$eq->fetch`) doesn't return any results.
  
  This is due to the condition from `$aclWhere`, for me it is:
  
  ```
  ( ( `civicrm_group_contact_cache-ACL`.group_id IN (8) ) )
  
  ```
  
  which is joined in the full query by
  
  ```
  LEFT JOIN civicrm_group_contact_cache `civicrm_group_contact_cache-ACL` ON contact_a.id = `civicrm_group_contact_cache-ACL`.contact_id
  
  ```
  
  while I do get a contact joined in the query, an entry in `civicrm_group_contact_cache` seems to be missing. What is that table for, anyway?
  
  **Tags:** civimail, mailing
  
  > **Comments:**
  > **username_1**: I have the same problem on CiviCRM 4.7.8. for Drupal 7.  
  > **username_1**: edited the question so my further findings from debugging are visible to narrow down the problem. Unfortunately I still don't see a fix yet ...  
  > **username_1**: see also this bug ticket: https://issues.civicrm.org/jira/browse/CRM-19036  
  
  ---
  
  ## 15 answers
  
  ### Answer by username_2 on 2017-08-31. Score: 6
  
  The solution for me was to set up a Bounce Processing email account in **Administer menu > CiviMail > Mail Accounts**.
  
  > **Comments:**
  > **username_3**: Yes this worked for me too. Would love to know how and why....  
  
  ---
  
  ### Answer by username_4 on 2017-10-13. Score: 4
  
  We're using Drupal 7.56 and CiviCRM 4.7.25 and we also have this problem. None of the above solutions worked.
  
  This seems to be a very general type of error that can be inadvertently triggered by a great many causes. For us, we eventually discovered that our SMTP gateway had ceased authorizing payment on our account and was declining our traffic from CiviSMTP.
  
  So if you're receiving this error, it might be a good idea to double check that your expected mail path actually works as you expect it to before you go digging through code. :-)
  
  > **Comments:**
  > **username_5**: Similar here. With a 4.7.22 CiviCRM version in our case we exceed quota asigned to our SMTP gateway. Filling again our SMTP gateway with more credit the error disappears.  
  > **username_6**: Thanks, this was a good clue. In my case, it was due to an oversized attachment being rejected by the mail system. It was only the server logs that diagnosed the details of why the mail() call failed.  
  
  ---
  
  ### Answer by username_1 on 2016-07-05. Score: 3
  
  For me (CiviCRM 4.7.8) the problem was related to some changes introduced in 4.7.8. regarding permission checks (see [GitHub PR #8415](https://github.com/civicrm/civicrm-core/pull/8415), [Jira issue CRM-18159](https://issues.civicrm.org/jira/browse/CRM-18159)).
  
  Reverting those changes fixed the problem:
  
  Remove the acl clauses by replacing
  
  ```
  list($aclJoin, $aclWhere) = CRM_ACL_BAO_ACL::buildAcl($senderId);
  
  ```
  
  with
  
  ```
  $aclJoin = ""; $aclWhere = "";
  
  ```
  
  1. in `CRM/Mailing/BAO/Mailing.php` in function `getTestRecipients` (line 926)
  2. and in `CRM/Mailing/BAO/MailingJob.php` in function `deliver` (line 502)
  
  ---
  
  ## Some details from Debugging
  
  While CiviCRM works fine on another installation with 4.7.8 in our live system there seems to be some issue with ACL (access control) related to mailings, causing CiviCRM to block the user trying to send a mailing to address any contact.
  
  It seems like the database table `group_contact_cache` is not filled with the necessary entries in the affected system. However, I don't know why that could be the case.
  
  > **Comments:**
  > **username_7**: As @Cibes have mentioned in a comment, the related issue is issues.civicrm.org/jira/browse/CRM-19036 and CiviCRM 4.7.12 is now released. I can confirm that the update solves this problem.  
  
  ---
  
  ### Answer by username_8 on 2016-04-21. Score: 2
  
  I was having same problem on Drupal 7.43 / Civi 4.76 and managed to fix it. Unfortunately I'm not sure which action I took achieved the fix - perhaps one of the following will help you.
  
  * cleared all Drupal and Civi caches via the frontend
  * emptied Civi Cache tables via phpMyAdmin
  * deleted the contents of the templates\_c folder
  * deleted the contents of the ConfigAndLog folder
  * deleted the cache folder in my extensions directory
  * I disabled and uninstalled the Cividesk Sparkpost extension
  * installed the Proexchange extension github.com/proexchange/com.pesc.sparkpost.
  
  In case this unfairly maligns the Cividesk Sparkpost extension note that I have it working on another of our sites that uses Drupal 6 / Civi 4.76. I am not sure whether it was the problem but I did keep getting errors which may have to do with something else in my installation.
  
  > **Comments:**
  > **username_1**: For me, clearing civi and drupal caches and emptying cache table in database didn't help. Neither did deleting templates_c, ConfigAndLog or extensions/cache folder. also I don't have the sparkpost extension  
  > **username_9**: I am having the same problem.  I am also having an issue with multiple emails being sent when an email is accepted - such as the email for the administration account.  By multiple I mean dozens until the draft mailing is deleted.  
  
  ---
  
  ### Answer by username_10 on 2019-07-09. Score: 2
  
  I know this is an old thread but on the off chance, someone else finds this helpful. I came across this error when I had an unclosed token in an email. I'd use the checksum token but inadvertently removed the final bracket - the email had "www.mysite.org?cid1={contact.contact\_id}&{contact.checksum/"
  
  Once I added back in the final '}' all was back to working order!
  
  
  ---
  
  ### Answer by username_11 on 2017-03-07. Score: 2
  
  If you are using Amazon SES for sending email, Check Return-Path email domain verified by Amazon SES (it return with error message "554 Message rejected")
  
  More Details here : <http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html>
  
  Same might be applicable for other provider, Check CiviCRM log for more details.
  
  
  ---
  
  ### Answer by username_5 on 2016-11-25. Score: 2
  
  We also had this problem. Following this other issue [CRM-19685](https://issues.civicrm.org/jira/browse/CRM-19685) and solving it applying the following SQL script fixes the 'Send test' problem.
  
  `UPDATE `civicrm_contact` SET `preferred_mail_format` = 'Both' WHERE `preferred_mail_format` IS NULL;`
  
  
  ---
  
  ### Answer by username_12 on 2017-01-19. Score: 2
  
  We noticed this issue recently on 4.7.15 but forgot to follow [this fix](https://civicrm.stackexchange.com/questions/10964/smtp-connection-failing-problem/10966#10966) post upgrade. Once we applied it, the error cited above disappeared.
  
  
  ---
  
  ### Answer by username_13 on 2016-03-23. Score: 1
  
  I think perhpas you are confused about what "send test" does.
  
  The number near the recipients field is the number who will receive the finished email. It has nothing to do with the **send test** buttons. (Possibly it would be better if they were labelled Send Draft)
  
  **Send test** either sends one email to the email address in the box if you use the **Send test email to:** panel (the middle panel in the image below), or it sends a test email to the group you have chosen in the right panel (below **Sent test email to group:** . In the image below, the test email would be sent to the Case resouces group if the **send test** button directly below that name was clicked.[![test email image](https://i.sstatic.net/DR68N.png)](https://i.sstatic.net/DR68N.png)
  
  The idea of sending a test email to one or a few people before sending the actual email is so that you can check links and formating or perhaps so that others can proofread or approve the email, before you sent it out.
  
  > **Comments:**
  > **username_0**: Thanks for your feedback.  Unfortunately I'm not confused, if I use the Send test button on either "Send test email to:" or "Send test email to group:" the error message I receive is the same "Could not identify any recipients. Perhaps the group is empty?".  Is seems that before sending the test it checks that you have valid recipients on your mailing, but I do have indeed valid recipients so I guess this check is bogus somewhere  
  > **username_13**: Sorry, I was confused by your reference ot the number of people in the mailing group which should have nothing to do with the test. Do you get the same error message using either Send test button?  
  > **username_0**: Yes, same error using both buttons  
  > **username_8**: I'm having the same problem on Drupal 7.43  Civi 4.7.6.  
  > **username_14**: I having the same problem. How it will be solve?  
  
  ---
  
  ### Answer by username_15 on 2016-09-11. Score: 1
  
  These suggestions have not worked for me (now on 4.7.11). The workaround for this has been to reuse & edit old successful mailings, which seem unaffected.
  
  
  ---
  
  ### Answer by username_16 on 2018-03-29. Score: 1
  
  I had the exact same problem, but it was being caused by an incorrect password in the SMTP Outbound Mail Settings (someone had changed the password and not updated CiviCRM!).
  
  More generally it is probably worth testing the Outbound Mail Settings as a problem here could be causing this issue.
  
  
  ---
  
  ### Answer by username_17 on 2019-09-02. Score: 0
  
  The message identifies one possible cause, but many other problems lead to the same message. A more verbose version might read:
  
  "No mails were successfully sent. This could be caused by many
  different issues. Known causes include:
  
  * could not identify any recipients
  * errors relating to the SMTP service, including authentication or network problems
  * invalid tokens in your mail
  * no Bounce Processing account configured"
  
  Check [the CiviCRM log file](https://civicrm.org/extensions/civicrm-log-viewer) - some causes are logged there.
  
  
  ---
  
  ### Answer by username_18 on 2017-03-26. Score: 0
  
  I use CiviSMTP
  
  Actually, it is a known issue : there is a patch there :
  <https://forum.civicrm.org/index.php?topic=37194.0>
  
  But why isn't it finally fixed in the standard CiviCRM ?
  
  
  ---
  
  ### Answer by username_18 on 2017-03-22. Score: 0
  
  Same problem :
  
  I have just upgraded to Civi 4.7.16 (Drupal 7.54) :
  
  * "Send Test" issues the same message (Could not Identify ...)
  * If I overpass the test and send the mailing, the mailing fails :
    Intended recipients 206
    Successful deliveries 0
    Bounces 21 (all for "syntax" reason)
  
  CRON Mail Report says :
  
  \*Parameters raw (from db settings):
  instanceId=[ID of report instance] required
  format=[csv or print] optional-output CSV or print-friendly HTML, else PDF
  
  Parameters parsed (and passed to API method):
  a:3:{s:7:"version";i:3;s:10:"instanceId";s:32:"[ID of report instance] required";s:6:"format";s:67:"[csv or print] optional-output CSV or print-friendly HTML, else PDF";}
  
  Full message:
  Finished execution of Mail Reports with result: Echec, Error message: A fatal error was triggered: is not of type String\*
  
  I have no ACL defined
  
  
  ---
  
  ### Answer by username_19 on 2021-11-27. Score: 0
  
  Check that every contact on the list is not 'on hold'.
  
  I deleted the mail server and since this group was used as the first test, all contacts on the list were set to 'on hold'.
  
  
  ---
  
  