Defect #26515: Email not being sent for NEW issues using async_smtp AND non-standard emission address - Redmine

Actions

Copy link

Defect #26515

closed

Email not being sent for NEW issues using async_smtp AND non-standard emission address

Added by Matthew Paul over 7 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Email notifications

Target version:

Start date:

Due date:

% Done:

Estimated time:

Resolution:

Invalid

Affected version:

3.3.0

Description

This is similar to an old issue about async_smtp mail. To reproduce -

Project A - setup with inbound/outbound email the same like tracker@example.com
Project B - setup with inbound email like test@example.com but outbound the same tracker@example.com

On project A, new issues will cause emails to be sent fine
On Project B, new issues will cause emails to NOT be sent for NEW issues. UPDATES however will work fine.

So this is like similar issues I see. I fixed it by returning to smtp emails, but this is not as good, obviously. It looks like when you fixed the original issue from a few years back, you fixed it for email UPDATES but not for NEW emails with an email address different from the inbound email address.

Actions

Copy link

Updated by Toshi MARUYAMA over 7 years ago

Status changed from New to Needs feedback

What difference with #8157?

Actions

Copy link

Updated by Matthew Paul over 7 years ago

#8157 relates to sending emails if one of the recipient emails is wrong. This is different and very specific. It only occurs if you have two projects with 2 inbound emails, 1 where the standard redmine emission email is the same as the inbound email, one where the inbound email is DIFFERENT fro the emission email.

In the first case - inbound and emission emails are the same - add task to a project, notifies ok about that new issue.

In the second case, inbound and emission emails are not the same - add task to a project, does not notify ok about new issue. BUT does notify ok about any subsequent updates, strangely.

I do have plugins, but I do not think it is anything to do with that. Why? Because, if I do nothing else except change configuration.yml from async_smtp to smtp, it fixes itself. i.e. no changes whatsoever to redmine, only to the smtp protocol, and it starts working. Which is fine, not a big problem. But async is definitely better.

Actions

Copy link