-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing the description of the DSN used for list moderated notification emails #1688
Comments
The DSN Sympa itself returns is as below. It includes human-readable description.
Somehow, the M365 server seems to have seen this message returned by Sympa and reported that a "persistent error" (554 5.4.0) had occurred. The Diagnostic-Code seems to be preserved, so I'll try to improve this. |
@fusenuk , please check the PR above.. |
Those new DSN descriptions look good thanks. |
Holy Crap this is causing unimaginable pain for us. How the hell is "X-Sympa; Other or undefined mail system status" human readable? Seriously. To an engineer, sure. To the average Sympa user, oh hell no. Beginning to really regret doing a point release update to Sympa right before the Fall semester. I'm used to point releases not being major pain points. However, this one sure hasn't proven to be so far based on the number of support calls we're getting. |
Expected Behavior
When sending an email to a list that is moderated, the sender should receive a easily understandable notice that the message has not been distributed due to awaiting moderator approval.
Current Behavior
The recent change via #1508 means that you no longer send out an easily understandable notice but instead respond with a SMTP status code of 4.3.0 but with the default description of "Other or undefined mail system status".
Possible Solution
Change the description to be something like "Your email is awaiting approval from the owner of the mailing list"
Context
Previously Sympa sent out the plain English email notifying of awaiting modification. Now it ends up with the sending mail server sending a random unexplained bounce message.
And example of this is from Office365 -
I don't think that is very helpful for end users.
The text was updated successfully, but these errors were encountered: