TOPIC:

Here's the message I get. A couple of other members of my exec tried from different locations/servers and get a similar problem. Help please: I need to email my members about the exec elections!

I believe the agenda mail function on the website still works though; I just can seem to input the group addresses into my Outlook; or Gmail, etc.

From: Mail Delivery Subsystem <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Tue, Apr 5, 2016 at 11:36 AM
Subject: Returned mail: see transcript for details
To:

---

@gmail.com


The original message was received at Tue, 5 Apr 2016 15:36:07 GMT
from mail-yw0-f177.google.com [209.85.161.177]

---

The following addresses had permanent fatal errors

---

|/etc/tcmail.pl
(reason: 255)
(expanded from: <This email address is being protected from spambots. You need JavaScript enabled to view it.>)

---

Transcript of session follows

---

Status: 500
Content-type: text/html

<h1>Software error:</h1>
<pre>Can't locate object method "message" via package "Wide character in subroutine entry at /usr/local/share/perl5/Email/Sender/Transport/SMTP.pm line 218.
" (perhaps you forgot to load "Wide character in subroutine entry at /usr/local/share/perl5/Email/Sender/Transport/SMTP.pm line 218.
"?) at /etc/smrsh/tcmail.pl line 856.
</pre>
<p>
For help, please send mail to this site's webmaster, giving this error message
and the time and date of the error.

</p>
[Tue Apr 5 15:36:20 2016] tcmail.pl: Can't locate object method "message" via package "Wide character in subroutine entry at /usr/local/share/perl5/Email/Sender/Transport/SMTP.pm line 218.
[Tue Apr 5 15:36:20 2016] tcmail.pl: " (perhaps you forgot to load "Wide character in subroutine entry at /usr/local/share/perl5/Email/Sender/Transport/SMTP.pm line 218.
[Tue Apr 5 15:36:20 2016] tcmail.pl: "?) at /etc/smrsh/tcmail.pl line 856.
554 5.3.0 unknown mailer error 255

Final-Recipient: RFC822; This email address is being protected from spambots. You need JavaScript enabled to view it.
X-Actual-Recipient: X-Unix; |/etc/tcmail.pl
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Unix; 255
Last-Attempt-Date: Tue, 5 Apr 2016 15:36:20 GMT

---

Forwarded message

---

From: "

---

" <

---

@gmail.com>
To: This email address is being protected from spambots. You need JavaScript enabled to view it.
Cc:
Date: Tue, 5 Apr 2016 11:36:06 -0400
Subject: ODYSSEA - Élection du comité exécutif 2016–17 // Election of the 2016–17 Executive Committee
Envoyé de la part de Stefan Wesche / Sent on behalf of Stefan Wesche

try now

Thank you Steve for taking this on.

I'm happy to say that I no longer get the same error message, so you've clearly made some difference, but nobody got the message, and now I get a different error message (a .bin file was also attached, but I can't open it.):

Your message to (---@----.com in This email address is being protected from spambots. You need JavaScript enabled to view it.) had the following error and was not delivered (11 retries):
[]
NOTE: This may be due to an invalid recipient address or high email volume at this time--try again later.

Stefan wrote:

Your message to (---@----.com in This email address is being protected from spambots. You need JavaScript enabled to view it.) had the following error and was not delivered (11 retries):
[]
NOTE: This may be due to an invalid recipient address or high email volume at this time--try again later.

Was that the whole bounce message?... I think I likely just need to up the number of retries. Probably high email volume issue.

Yes, that was the entire message. It mentioned only one email in the whole list - I'm not sure if it just tried with the first email address and never proceeded to the second. I was able to verify with at least one other member who didn't receive it, and I also am on that list but didn't receive it.

Have you tried emailing the email address that it is choking on? (sending to it directly)

Update: I just got the same bounce message again with reference to a second email address on the list.

Ok, well l will have to come back to this later this evening... I am at my day job now... have to take care of that.

OK, thanks for your efforts so far!

One further update: I forwarded the bounce message to the two addresses that had bounced, and one of them has already confirmed reception, so the problem can't be on her end.

Cheers

Stefan: so I did a few tweaks, and did a couple of test emails to my test member group and a test agenda send... No issues.

I am still thinking there was either an email volume overload or something else yesterday... I am seeing a number of SMTP send errors for the last few of days.


>>> Message to Brian: Brian, can you check out the SMTP workings on the server and maybe reset the email system? The SMTP errors looked a bit unusual to me.

Thank you Steve (and Brian?) for all your help. The members list works again

Cheers,

Stefan

I spoke too soon. The first message went through, but I had the wrong subject line and tried to resend, and the second one is now bouncing back. I've never had this problem before with these lists...

I note that our club's chair for this week's meeting was still able to send out the meeting agenda using the function on our FTH website.

Cheers,

Stefan

Can you send a test message with a simple subject. like "Test" or similar... Might be a problem with characters in the subject.

Thanks Steve,
I think you may have diagnosed the issue.

I very much appreciate all your help.

Cheers,

Stefan

Well, let me know what you find... we should not be having any issues with special characters.

If you confirm that is the case, I would very much appreciate any assistance you could contribute to helping me get rid of the issue.

Workarounds are fine, but much better to fix a problem if we can.

I believe it's the "en dash" "–", created with the following ALT code: ALT 0150
It is technically correct to use for ranges, including date ranges, but some programs have difficulty with it, so the workaround is to use the less-technically correct hyphen instead. I suspect the same problem would probably occur with the "em dash" "—", produced with ALT 0151.

I took out the two "–" from my subject line and poof – the message sent

Good luck with the fix!

Hmmm Interesting.

I will look into this... Do you mind if I contact you in the future regarding fixes?

Sure, I don't mind at all.