Permanent error sending to specific email address
Have latest Thunderbird (60.??) installed on Sierra MAC. Have configured to IMAP usage. There is a specific email address that I attempt to send that gives me a permanent error message to my Inbox. Sometimes the email actually does arrive at the destination even though I get the error message. Seems to occur with or without sending an attachment, but most consistently attempting to send an Excel spreadsheet; size is modest, so I don't think that is the issue.
1. Is there some email address format that is forbidden or that could cause a problem? 2. Are any of these problems possibly caused by some antivirus filtering? 3. My ISP has not been able to resolve this issue (Comcast) or tell me why I am getting this error. 4. Is there any potential problem with the setup of my router that would be a problem with a specific email?
Thanks for your kindness and suggestions.
Chosen solution
re : There is a specific email address that I attempt to send that gives me a permanent error message to my Inbox.
That means the email was sent successfully and you have received a message from the server. So nothing is wrong at your end.
Sometimes the wording in that Mailor Daemon reply offers some insight into the issue.
One of the most common reasons is that the recipient has allowed their server quota to become full, so new emails cannot be accepted by the server. When they delete a few it allows a few new emails to be received, but is full again very quickly. The only remedy would be for the recipient to check their server quota and if full, remove/delete some emails to create sufficient space.
Read this answer in context 👍 0All Replies (5)
Chosen Solution
re : There is a specific email address that I attempt to send that gives me a permanent error message to my Inbox.
That means the email was sent successfully and you have received a message from the server. So nothing is wrong at your end.
Sometimes the wording in that Mailor Daemon reply offers some insight into the issue.
One of the most common reasons is that the recipient has allowed their server quota to become full, so new emails cannot be accepted by the server. When they delete a few it allows a few new emails to be received, but is full again very quickly. The only remedy would be for the recipient to check their server quota and if full, remove/delete some emails to create sufficient space.
Thanks for your kind and quick response. This may be as much as we can determine since I did not provide the complete wording from the Daemon. If (and when) this occurs with this address again, I will capture and provide the full wording; I believe they would like to fix their issue (if known in detail).
Here is the most recent and expanded response from an attempt to try the correspondence again:
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed permanently:
* coindan@q.com
Reason: Permanent Error
Reporting-MTA: dns; resqmta-po-08v.sys.comcast.net [96.114.154.167]
Received-From-MTA: dns; resomta-po-15v.sys.comcast.net [96.114.154.239]
Arrival-Date: Fri, 21 Dec 2018 15:41:23 +0000
Final-recipient: rfc822; coindan@q.com
Diagnostic-Code: smtp; 554 5.7.1 [P4] Message blocked due to spam content in the message.
Last-attempt-Date: Fri, 21 Dec 2018 15:41:23 +0000
Received: from resomta-po-15v.sys.comcast.net ([96.114.154.239]) by resqmta-po-08v.sys.comcast.net with ESMTP id aMEhgOaD5jyENaMvTgMX5Y; Fri, 21 Dec 2018 15:41:23 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1545406883; bh=7yUu7JJDHmLTejC4xoxDIR429QyLnCe+F6Nl+MTMvYU=; h=Received:Received:To:From:Subject:Message-ID:Date:MIME-Version: Content-Type; b=W22nvXyIc/mLKqApqtZ/WzBOv9cUNtlu5sqzYrVKsHIWbjx687x8nhZdW49MD/oIb sA987rbft4/vxdWyCpXohqIlvJMJxp2poxhvlEB62GzA1ptGZtKd/0MlU8Ur3rjugd qEPwtsZLW6hOdFogoJdA6lPicapFZKn0GrjzAmoy/XtfFcWkw+e0pudNEGt320y/9e UnLt2sDOdGxoQSflGTxvWLEQAU9d8c/mEeqS6xknPbH4IrCz35yHX4igG4bnTZo9JP 4rJw/LOpU8Sva1CTm16REqBw5cE0Mt0YR/jpENrrx9WLSr+m1lml1YR+GgkIugp2zO AWcV4boIvRF5g== Received: from Johns-Sierra.local ([67.190.43.143]) by resomta-po-15v.sys.comcast.net with ESMTPSA id aMvTgusyJS0fxaMvTgHrc9; Fri, 21 Dec 2018 15:41:23 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedtkedrudejhedgjeelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvnecuuegrihhlohhuthemuceftddtnecunecujfgurhepvffhuffkffgfgggtgfesthekredttdefjeenucfhrhhomheplfhohhhnucfouhhrrhgrhicuoehjhhdrmhhurhhrrgihsegtohhmtggrshhtrdhnvghtqeenucfkphepieejrdduledtrdegfedrudegfeenucfrrghrrghmpehhvghloheplfhohhhnshdqufhivghrrhgrrdhlohgtrghlpdhinhgvthepieejrdduledtrdegfedrudegfedpmhgrihhlfhhrohhmpehjhhdrmhhurhhrrgihsegtohhmtggrshhtrdhnvghtpdhrtghpthhtoheptghoihhnuggrnhesqhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-Xfinity-VMeta: sc=??;st=legit To: Dan <coindan@q.com> From: John Murray <jh.murray@comcast.net> Subject: Anticipated meeting on Jan 25, 26 in SLC Message-ID: <23f6cfc0-d59a-f94f-e477-1048eacf8a33@comcast.net> Date: Fri, 21 Dec 2018 08:41:23 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0)
Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US
I'm getting the same response from Comcast's mailer-daemon as above. Can receive emails, but recipients are not receiving emails that I send, even though Comcast's outgoing server tells me they've been sent. A few minutes later the mailer-daemon message above arrives. Have checked all my port settings and they are what Comcast is currently requiring. Don't know what to do next.
I'm getting the same response from Comcast's mailer-daemon as above. Can receive emails, but recipients are not receiving emails that I send, even though Comcast's outgoing server tells me they've been sent. A few minutes later the mailer-daemon message above arrives. Have checked all my port settings and they are what Comcast is currently requiring. Don't know what to do next.