Skip to content
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

Background sent notifications repeatedly (on 14th July 2017) #51

Open
alanbarrett opened this issue Jul 20, 2017 · 1 comment
Open

Background sent notifications repeatedly (on 14th July 2017) #51

alanbarrett opened this issue Jul 20, 2017 · 1 comment

Comments

@alanbarrett
Copy link
Member

a) Some project creation notifications were sent 3 times spaced about 2 minutes apart.

b) Some task stream notifications were sent every hour (instead of once a day).

(a) could have been caused by RabbitMQ messages not been deleted and reconsumed.

(b) could have been caused by failure to update the database with the fact that the tasks stream had been sent.

But these seem to have nothing in common, so I think there was some sort of resource problem. Restarting the backend cleared the problem.

At the next monthly maintenance, I will restart RabbitMQ. It has ben running for close to two years without stopping.

Here are some related emails:-

Alan...
Yes, you should reach out to the translator saying that we seem to have had a problem, which seems to have been resolved, and to let us know if not. This is different to the normal response which should say that Microsoft has told us that they have marked the email as Spam and tell them how to unsubscribe or asking if they want us to do it for them (actually quite often we are told they do not wish to unsubscribe).

We do have an unsubscribe header "List-Unsubscribe: mailto:info@trommons.org?subject=Unsubscribe%20from%20Trommons%3A%20alanabarrett0%40gmail.com"
which some mailers will allow the user to click on which will send an email to us that we can act on.

After much investigation I cannot see why this problem occurred, maybe the C++ "background" application had a resource issue of some kind. It does seem to be resolved now (hopefully).

Marina...
Thank you, Alan. We will reach out to the translator mnazeef786@hotmail.com

Ambra says we've gotten more unsubscribe requests over the weekend than usual.

What would you say about adding a line at the bottom of the Trommons emails: "If you would like to unsubscribe from all emails, please click here." or something to that effect, with the link triggering an unsubscribe email (or, ideally, an automated unsubscribe action)?

Alan...
I checked what ways we have of unsubscribing.

  • As I said before there is an email unsubscribe header which causes the mailer (e.g. Gmail) to put up an unsubscribe option which will send us an email.

  • Nearly all our emails also have instructions on how to unsubscribe in a footer. Here is the text of the email footer...
    "
    Trommons is maintained by The Rosetta Foundation, a non-profit organisation promoting equal access to information and knowledge across the languages of the world.

We need your help to make this happen! Support Trommons.

If you no longer wish to receive tasks stream notification emails, please visit your Profile page to edit your email notification settings.

To unsubscribe from Trommons, visit your Profile page and delete your account or email info@trommons.org
"
The email address is a clickable link which will bring them into a new email to "info@trommons.org".

However, the project email in question, for some reason is missing the footer. I will add it. I will add a github issue to address this.

@alanbarrett
Copy link
Member Author

A few comments...
(Copying @mirko33 & @mari-na because not sure they are subscribed to C++ background)

I have learned that "Project Created" can be generated by editing a project, so it is unlikely that we have a RabbitMQ problem. I will not need to restart at next maintenance.

It is not necessary to add unsubscribe information to "Project Created" as it only goes to Site Admins.

Alan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant