Redmine do not send notification emails if a recipients email address is not valid
|Assignee:||Jean-Philippe Lang||% Done:|
- Add a user with the name "TestUser" and a misconfigured email address (at my side it was something like UserTest@OurCompanyName.de).
- Let the "TestUser" create a ticket.
- Redmine needs very long to respond (~2 min.).
- Nobody receives a notification email (e.g. the ticket creator, watchers, everyone with the "For any event on all my projects" email setting).
- MySQL 5.1.41-3ubuntu12.6
- Ruby 1.8.6
- Rails 2.3.5
- Redmine 1.1.0
- SVN 1.6.12-1406.49 hosted via CollabNet Subversion Edge 1.2.1-1406.49
- Our email server is Microsoft Exchange 2003
Fatal side effect of this bug
We do a lot of subtasking. Sometimes when the user with the misconfigured email address adds a ticket into a deep subtask structure this structure will be corrupted!
After a little database analysis I figured out, that the issues.lft and issues.rgt become inconsistent...
Redmine is pretty cool! We use it since some years and this is the first real problem with it.
Keep on moving ;-)
#1 Updated by Евгений Золотин over 7 years ago
I have the same problem. Today I've noticed, that notifications from forum were not send. Looking through production.log file I've found the reason: 550 error - unknown accaunt. One of user's account has wrong e-mail, and other users can't recieve e-mail notifications. I've tried to send e-mail to this wrong adress with other good adresess from MS Outlook, and I've recieved the same bug from automatic admin's e-mail: 550 unknown account. But other users with good adresses got my test e-mail. When Redmine do send it's notifications and one of the e-mail adresses is wrong, nobody can recieve notifications. Seems that problem with Redmine.
#2 Updated by Fabien Crespel over 6 years ago
This issue still occurs with Redmine 1.3.3.
When one project member with an invalid email address fails to receive a notification (e.g.
550 Recipient address rejected: User unknown in local recipient table), subsequent notifications are not sent to any other member involved in the issue/project.
As the account involved is a generic account in my case, I disabled all notifications for it. But if for a reason or another a previously valid email address becomes invalid (employee leaving a company...), it will block notifications for everyone else - which I think is a major issue.
#14 Updated by Dariusz Kowalski over 3 years ago
I have the same issue.
In our RM , we are connected do Ldap - there is many separated teams were people go in and go out even often. It is impossible to manage of that and disable each account manually. This is a big problem.
Anybody has solution for that issue?
#15 Updated by James H over 3 years ago
if you are connected to LDAP, why dont you just let LDAP handle the email addresses so you never have an invalid email address?
but still +1 to this issue. It also can still appear when using LDAP if the information in your LDAP is not correct. But that is a different underlying issue.
#21 Updated by John Simmons over 2 years ago
I know this is getting pretty old, but I'm having this issue as well. I have all of my users set through LDAP, so there's no defective email addresses, but we added some people who have external email addresses, and they login through non-LDAP, and it breaks any project they are added to. So, 99% of my users are @companyA.com, and 1% are @companyB.com, and any project where someone from company B is added, stops sending emails all together.
#32 Updated by Ken Zalewski about 1 month ago
This issue has persisted for years, and is now in the current version, 3.4.6.
It has affected us here at the Senate on multiple occasions when an employee leaves the Senate. That employee's email address is disabled/deleted, so any mail sent to that address returns a 550 SMTP error.
This has the end result of preventing ANY notifications from going out on a project where the terminated employee might be a member. This is bad behavior, and it's been reported multiple times by many Redmine users.
I am asking that this issue be prioritized. We depend on email notifications working properly, and we don't want project notifications to stop working just because one member on that project/group has a bad email address.