Defect #10910

Mail not sent when issue status updated after a repository commit

Added by Rui Pires over 10 years ago. Updated over 10 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Category:Email notifications
Target version:-
Resolution: Affected version:1.4.1


Posted earlier on Fora Help and Open Discussion without further feedback.

The subject summarises my issue. I am having redmine retrieve the changesets through a post-commit hook in a subversion repository ("ruby /usr/share/redmine/script/runner "Repository.fetch_changesets" -e production > /dev/null 2>&1 &"). This is working perfectly.

I typically use keywords which trigger the update of an issue status (Fixes,Closes), such as changing from "In progress" to "Resolved". The status is indeed changing automatically with the commit operation.

However, whereas a manual status update triggers an e-mail notification (I've configured redmine to behave so), a status update through an SCM commit is not sending this notification.

Note that the log file production.log DOES shows that such notifications ARE sent. However, my SMTP server does not receive any requests in this case. Here's an excerpt of the log file.

Processing [filtered]
Sending email notification to: [mail address filtered]
Redirected to http://[filtered]

I wonder where this is an intended behaviour or it should be considered a defect.

Thanks for your feedback.

Ruby version 1.8.7 (i686-linux)
RubyGems version 1.6.2
Rack version 1.1.3
Rails version 2.3.14
Database adapter mysql
Database schema version 20120301153455


#1 Updated by Etienne Massip over 10 years ago

What does your email configuration look like?

#2 Updated by Rui Pires over 10 years ago

Here's a sample. Note that we use async_smtp as delivery method.

delivery_method: :async_smtp
tls: true
enable_starttls_auto: true
address: ""
port: '587'
domain: ""
authentication: :login
user_name: ""
password: "xxxxxxx"

Also available in: Atom PDF