Date
1 - 5 of 5
moderated Wrong error/bounce message when member tries to reply to a topic with a "tag only moderators can use" #bug
|
Andy
Some of our Hashtags are set so that only Moderators can reply. ("Only moderators can reply to topics tagged with this hashtag.")
When a regular member tries to reply to it by email, Groups.io does not send an appropriate bounce message. Apparently this results in the sender's email server re-trying over and over (38 times over 6 hours), and eventually gives up. Here is the message the member received from his email server (6 hours after replying): ----------------- Subject: Failure Notice
Sorry, we were unable to deliver your message to the following address.
<xxxxxx@groups.io>:
Unable to deliver message after multiple retries, giving up.
--- Below this line is a copy of the message.
Sorry, we were unable to deliver your message to the following address.
<xxxxxx@groups.io>:
Unable to deliver message after multiple retries, giving up.
----------------- At the least, the bounce message from Groups.io ought to tell the sender WHY the message could not be delivered to that topic. It should also tell his email server not to keep trying. Regards, Andy
|
|
|
|
Starchild <sfdreamer@...>
+1 to this suggestion from Andy as well! Receiving mail delivery failure notices that don't explain why a message was not delivered is annoying and non-helpful. Namaste, ((( starchild )))
-----Original Message-----
|
|
|
|
On Thu, Jan 28, 2021 at 09:30 PM, Andy wrote:
Some of our Hashtags are set so that only Moderators can reply. ("Only moderators can reply to topics tagged with this hashtag.")Andy -- Yep. Just sent a post with a moderator-reserved hashtag and nothing back 10 minutes later. Different from the "only moderators can reply" thing, but similar. Both should have promptly bounced with a 500-level error of some kind. See https://beta.groups.io/g/main/message/27632 Regards, Bruce
|
|
|
|
On Thu, Jan 28, 2021 at 09:30 PM, Andy wrote:
At the least, the bounce message from Groups.io ought to tell the sender WHY the message could not be delivered to that topic.Andy -- Using GMail, I got this back: So it does...eventually...tell you why the failure occurred. The main problem is that the failure is not 500-level, so your provider (and mine) keeps trying to deliver the message. Hope this helps, Bruce
|
|
|
|
Hello, On Sat, Jan 30, 2021 at 9:24 AM Bruce Bowman <bruce.bowman@...> wrote:
This should be fixed now. Thanks, Mark
|
|
|