Answers.Body: <p>Unfortunately, the bounce messages aren't standardized, so pretty much every mail server has their own text to say that the account doesn't exist, or that the mailbox is full or any of the bounce reason.</p>
  
  <p>So what civimail has to do is to look at these emails and parse them to find keywords "INVALID MAILBOX", "DNS error" and if that specific keywords are found, flag the bounce accordingly.</p>
  
  <p>Unfortunately for you, "quota" is one of these keywords, and to add insult to injury, your mail server puts a "this is a permanent error", but clearly is is not the case, as it would go through.</p>
  
  <p>You could try to look at these rules in civi and try to come up with a new one for your "quota" email and flag it as a temporary bounce, but it means going into the database directly to update and create these rules.</p>
  
  <p>I would suggest you that your time is too valuable for that and it would be cheaper to move to an hosting provider that doesn't have quota, or use an external mailing provider (eg mailjet, sendgrid...) to handle pushing your emails.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-29T14:17:34.853Z
Answers.LastActivityDate: 2016-03-29T14:17:34.853Z
Answers.UserDisplayName: Xavier
Body: <p>I have a confounding challenge.</p>
  
  <p>Email addresses are placed on <strong>hold</strong> after having bounced (where bounce type is Quota).</p>
  
  <p>I looked at the actual bounce messages (see an example attached below) for some of the email addresses which bounced with bounce type=quota and the messages indicate that the email job exceeded the outgoing email sending quota on the sending server  (this is an issue I plan to look into and resolve later). </p>
  
  <p>However, What is strange is that email addresses to which email could not be 'sent' because sending server quota for outgoing email has been exceeded is now marked as onHold.</p>
  
  <p>Another strange but related observation, is that there is an actual bounce email message - which should not be the case if the original email never left the outgoing server.</p>
  
  <p>My questions:</p>
  
  <ol>
  <li>Could the bounce email message be wrong and the email was actually sent but the receiving inbox is full?</li>
  <li>If not, what am I missing?</li>
  </ol>
  
  <p>Thanks a lot in advance!</p>
  
  <p><a href="https://i.sstatic.net/llyen.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/llyen.png" alt="One of the Bounce email messages"></a></p>
  
Tags: <bounce>
Title: Bounce type = Quota
ThreadText: # Bounce type = Quota
  
  (Asked by: username_0 on 2016-03-26)
  
  I have a confounding challenge.
  
  Email addresses are placed on **hold** after having bounced (where bounce type is Quota).
  
  I looked at the actual bounce messages (see an example attached below) for some of the email addresses which bounced with bounce type=quota and the messages indicate that the email job exceeded the outgoing email sending quota on the sending server (this is an issue I plan to look into and resolve later).
  
  However, What is strange is that email addresses to which email could not be 'sent' because sending server quota for outgoing email has been exceeded is now marked as onHold.
  
  Another strange but related observation, is that there is an actual bounce email message - which should not be the case if the original email never left the outgoing server.
  
  My questions:
  
  1. Could the bounce email message be wrong and the email was actually sent but the receiving inbox is full?
  2. If not, what am I missing?
  
  Thanks a lot in advance!
  
  [![One of the Bounce email messages](https://i.sstatic.net/llyen.png)](https://i.sstatic.net/llyen.png)
  
  **Tags:** bounce
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-03-29. Score: 1
  
  Unfortunately, the bounce messages aren't standardized, so pretty much every mail server has their own text to say that the account doesn't exist, or that the mailbox is full or any of the bounce reason.
  
  So what civimail has to do is to look at these emails and parse them to find keywords "INVALID MAILBOX", "DNS error" and if that specific keywords are found, flag the bounce accordingly.
  
  Unfortunately for you, "quota" is one of these keywords, and to add insult to injury, your mail server puts a "this is a permanent error", but clearly is is not the case, as it would go through.
  
  You could try to look at these rules in civi and try to come up with a new one for your "quota" email and flag it as a temporary bounce, but it means going into the database directly to update and create these rules.
  
  I would suggest you that your time is too valuable for that and it would be cheaper to move to an hosting provider that doesn't have quota, or use an external mailing provider (eg mailjet, sendgrid...) to handle pushing your emails.
  
  
  ---
  
  