Email stopped working after upgrade from 1.0.3 to 1.0.4

Added by Toni Mueller over 9 years ago

Suddenly, my setting of "authentication: :plain" is no longer honoured, and Redmine instead insists on using "AUTH LOGIN" (as seen by tcpdump, just to confirm the mail server's logs).

Restarting Redmine had no effect.

Replies (9)

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Toni Mueller over 9 years ago

I thought that you might want to see the email config:

production:
delivery_method: :smtp
smtp_settings:
address: 127.0.0.1
port: 25
domain: example.com
authentication: :plain
user_name:
password: secretpassword

Domain, user_name and password are of course not the real values.

Please...

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Jean-Philippe Lang over 9 years ago

AFAIK, there was no change in 1.0.4 on email notifications.

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Toni Mueller over 9 years ago

Thanks - it may be something related to the general environment (a library?), but how can I debug such a problem? I tried to look at

ii libactionmailer-ruby 2.3.5-1~bpo50+1 and
ii libactionmailer-ruby1.8 2.3.5-1~bpo50+1

but these are well beyond my Ruby skills (I'm making my way through some books, but slowly). I should probably also look at Redmine's source code, but found that not all tags are yet in git.

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Toni Mueller over 9 years ago

In the meantime, I made some progress. I can now send test emails after reconfiguring my mail server to accept "login" type authentication, but notifications from eg. issues are not being sent, even when I specifically "watch" those issues.

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Adam DeJardine over 9 years ago

I'm having the same problem in 1.1.0 (r4702)

It seems that no emails are being sent to issue watchers. The test email sends fine.

I have my email notification preferences set to "Only for things I watch or I'm involved in" and "I don't want to be notified of changes that I make myself" is unchecked. I'm watching Issue 18, and I've tested this by adding comments and changing its status, both as myself and as my admin account.

This is what gets logged to production.log when I update a comment:

(I'd put the logs, but the server thinks this is spam... the main takeaway is that there's nothing in there about trying to send an email)

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Adam DeJardine over 9 years ago

OK WOW I feel stupid now...

Under (Administration > Settings > Email Notifications) I had nothing checked for what to send emails about...

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Toni Mueller over 9 years ago

Toni Mueller wrote:

In the meantime, I made some progress. I can now send test emails after reconfiguring my mail server to accept "login" type authentication, but notifications from eg. issues are not being sent, even when I specifically "watch" those issues.

I have now "solved" the problem. Due to another problem, namely wrecking "My Page" by adding a non-working "EasyAgile" piece to it, I globally disabled "EasyAgile" and resurrected my database entry using plain SQL, and suddenly, email start to flow again.

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Chris Martin over 9 years ago

I've just noticed that i'm having this same issue too. I checked Admin>Settings>Email notifications, and i have that configured okay. Test emails work. Emails will be sent to people who are watching tickets. Emails are NOT being sent to anyone who is assigned or owns the ticket. Also new ticket notifications are not working anymore. I'm on version 1.1.0.devel

I also noticed that the default notification option is: "Only for things i watch, or I'm involved in". But when i goto "My Account" i see my notification option is: "For any event on all my projects". When i try to change this to "Only for things I watch, or I'm involved in" I get the green "Account successfully updated" but the drop down resets to "For any event on all my projects".

RE: Email stopped working after upgrade from 1.0.3 to 1.0.4 - Added by Chris Martin over 9 years ago

And i upgrade to 1.1.1 and things are working. While going through the upgrade process i noted while i was going the db migration, that i don't remember doing those steps the last time blush. So i'm not sure if it's the upgrade to 1.1.1 or the db migrate that ultimately solved my problem.

Cheers

(1-9/9)