Answers.Body: <p>I think this might be related to the <code>CSS</code> brackets <code>{}</code> in the <code>&lt;style&gt;&lt;/style&gt;</code> tag a the top of your email source code, and/or Smarty enabled in CiviMail.</p>
  
  <p>Removing entirely the <code>style</code> tag should fix the issue.</p>
  
  <p>I think BeeFree already does inline styling, so it should not affect the formatting of the email.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-03T20:16:32.667Z
Answers.LastActivityDate: 2016-10-03T20:16:32.667Z
Answers.UserDisplayName: Andrei
Body: <p>Interesting situation... we use BeeFree to compose responsive emails, however they are failing to send, resulting in a scheduled/sent email as "running". We use EasyCron to trigger the scheduled jobs, however when using a BeeFree template, only the starting job is visible in the log, hence we see:</p>
  
  <blockquote>
    <p>Entity: Job Action: process_mailing Summary Starting execution of
    Mailings scheduler Details Parameters parsed (and passed to API
    method):  a:1:{s:7:"version";i:3;} Full message:  Starting execution
    of Mailings scheduler</p>
  </blockquote>
  
  <p>But we never see the "finished execution" message. I suspect this is why the status of the emailing is perpetually set to "running". If we try to then trigger the cron via the URL, the result is an internal server error 500.</p>
  
  <p>Here's where it's interesting... if we compose a new HTML email and just drop some text in there, along with the require tokens, everything works perfectly. If we review the cron logs provided by EasyCron we see that the only difference between the successful and failed jobs (in the logs) is that the successful job log has this additional line:</p>
  
  <blockquote>
    <p>X-Proxy-Cache: BYPASS</p>
  </blockquote>
  
  <p>The log of the failed job does not have this line. I know this is probably way out there as far as an issue, however any insight into this would be great. We're running CiviCRM 4.7.11</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-10-03T20:04:25.790Z
Comments.Text: I think this might be related to the `CSS` brackets `{}` in the `<style></style>` tag a the top of your email source code, and/or Smarty enabled in CiviMail, can you try removing entirely the `style` tag? I think BeeFree already does inline styling, so it should not affect the formatting of the email.
Comments.UserDisplayName: Andrei
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-10-03T20:12:42.823Z
Comments.Text: Andrei, you nailed it. We did recently enable smarty. Removing the style tags (and everything in between) corrected the issue. Thank you.
Comments.UserDisplayName: user3742
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-10-03T20:14:00.630Z
Comments.Text: Glad it helped, I'll add it as answer so we keep SE happy.
Comments.UserDisplayName: Andrei
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-11-02T20:57:44.777Z
Comments.Text: would be good if Second Chance accepted the answer
Comments.UserDisplayName: petednz - fuzion
Tags: <civimail>
Title: CiviMail/Cron Fails using BeeFree template
ThreadText: # CiviMail/Cron Fails using BeeFree template
  
  (Asked by: username_0 on 2016-10-03)
  
  Interesting situation... we use BeeFree to compose responsive emails, however they are failing to send, resulting in a scheduled/sent email as "running". We use EasyCron to trigger the scheduled jobs, however when using a BeeFree template, only the starting job is visible in the log, hence we see:
  
  > Entity: Job Action: process\_mailing Summary Starting execution of
  > Mailings scheduler Details Parameters parsed (and passed to API
  > method): a:1:{s:7:"version";i:3;} Full message: Starting execution
  > of Mailings scheduler
  
  But we never see the "finished execution" message. I suspect this is why the status of the emailing is perpetually set to "running". If we try to then trigger the cron via the URL, the result is an internal server error 500.
  
  Here's where it's interesting... if we compose a new HTML email and just drop some text in there, along with the require tokens, everything works perfectly. If we review the cron logs provided by EasyCron we see that the only difference between the successful and failed jobs (in the logs) is that the successful job log has this additional line:
  
  > X-Proxy-Cache: BYPASS
  
  The log of the failed job does not have this line. I know this is probably way out there as far as an issue, however any insight into this would be great. We're running CiviCRM 4.7.11
  
  **Tags:** civimail
  
  > **Comments:**
  > **username_1**: I think this might be related to the `CSS` brackets `{}` in the `<style></style>` tag a the top of your email source code, and/or Smarty enabled in CiviMail, can you try removing entirely the `style` tag? I think BeeFree already does inline styling, so it should not affect the formatting of the email.  
  > **username_0**: username_1, you nailed it. We did recently enable smarty. Removing the style tags (and everything in between) corrected the issue. Thank you.  
  > **username_1**: Glad it helped, I'll add it as answer so we keep SE happy.  
  > **username_2**: would be good if Second Chance accepted the answer  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-10-03. Score: 2
  
  I think this might be related to the `CSS` brackets `{}` in the `<style></style>` tag a the top of your email source code, and/or Smarty enabled in CiviMail.
  
  Removing entirely the `style` tag should fix the issue.
  
  I think BeeFree already does inline styling, so it should not affect the formatting of the email.
  
  
  ---
  
  