Redmine

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.

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.

Same problem on our server (Redmine 1.4.2). Also tried to change the Blind carbon copy recipients (bcc) option on the 'Redmine'.'Settings'.'Email notifications' page as a potential workaround, but it has no effect.

The issue is still present

Does anybody know some quick fix solution for this in source code ?
For instance parallel sending of mails to each user and so on ?

is this still like this?

+1

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?

Dariusz Tanner
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.

It seems Redmine.org has this problem, too.
I watch some forum messages on Redmine.org and I don't get notification.
Issue form have watchers list, but forum message form does not have.

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.

+1

Just by looking at the list of related issues, this problem apparently has affected many redmine users. Is there any chance that there will be a solution anytime soon?

Any updates on this?

Hello, does anyone have a solution for this currently?

This would be solved by #26791.

+1

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.

I can confirm this is causing me problems too. If one person leaves the company then no-one receives emails.

Richard Holyoak wrote:

I can confirm this is causing me problems too. If one person leaves the company then no-one receives emails.

This issue will be resolved in upcoming Redmine 4.0.0. The patch #26791 has already been committed to the repository.