email configurations in 1.1.1 and trunk (rev 5857) -- the latter does not work, why?
Added by Ivan Cenov over 13 years ago
Hello,
I have two installations of Redmine at my laptop:
1) Redmine 1.1.1 with rails 2.3.5
2) Redmine from trunk (the future 1.2.0), rev 5857 of trunk and rails 2.3.11.
The email configuration in Redmine 1.1.1 is OK and mails are sent when needed.
The email configuration in Redmine rev 5857 is NOT OK.
The working configuration in Redmine 1.1.1 is
production: delivery_method: :smtp smtp_settings: address: "mail.myisp.com" port: 25 domain: "mycompany.com"
The not-working configuration in Redmine trunk 5857 is
production: email_delivery: delivery_method: :smtp smtp_settings: address: "mail.myisp.com" port: 25 domain: "mycompany.com"As it may be seen, I copied the configuration from old Redmine to the new one. Of course, the old is in email.yml, and the new is in configuration.yml. I tried both Redmines one after other in five minutes. Where could be the problem? Some hits are welcome.
Ivan
Replies (3)
RE: email configurations in 1.1.1 and trunk (rev 5857) -- the latter does not work, why?
-
Added by Ivan Cenov over 13 years ago
Hm,
I created email.yml and copied the configuration from Redmine 1.1.1 and it worked. It seems that the intended variant in configuration.yml does not work yet in current trunk. On the other side, when Redmine is started the following message appears:
D:\biz\apps\redmine_trunk>ruby script\server -e production => Booting WEBrick => Rails 2.3.11 application starting on http://0.0.0.0:3000 Storing outgoing emails configuration in config/email.yml is deprecated. You should now store it in config/configuration.yml using the email_delivery setting. => Call with -d to detach => Ctrl-C to shutdown server [2011-05-20 11:18:24] INFO WEBrick 1.3.1 [2011-05-20 11:18:24] INFO ruby 1.8.7 (2010-08-16) [i386-mingw32] [2011-05-20 11:18:24] INFO WEBrick::HTTPServer#start: pid=10212 port=3000In fact, email.yml not deprecated yet.
RE: email configurations in 1.1.1 and trunk (rev 5857) -- the latter does not work, why?
-
Added by Ivan Cenov over 13 years ago
I opened an issue #8412