Defect #41463
closed
Email not woking in the latest release 5.1.3 (2024-06-12)
0%
Description
Email not woking in the latest release 5.1.3 (2024-06-12) and the details as below
Environment:
Redmine version 5.1.3.stable
Ruby version 3.2.5-p208 (2024-07-26) [x86_64-linux]
Rails version 6.1.7.8
Environment production
Database adapter Mysql2
Mailer queue ActiveJob::QueueAdapters::AsyncAdapter
Mailer delivery smtp
Redmine settings:
Redmine theme Purplemine2 (includes JavaScript)
SCM:
Subversion 1.14.2
Mercurial 6.3.2
Bazaar 3.3.2
Git 2.39.2
Filesystem
Redmine plugins:
redmine_wktime 4.7.4
Files
Related issues
Updated by Holger Just 5 months ago
- Status changed from New to Needs feedback
What exactly is not working? Please describe in detail what you are trying to do, what you would expect to happen and what you observe instead. Please be specific.
Updated by Krish Gopalakrishnan 5 months ago
All the configurations were made perfectly, but email notifications not generating from the redmine to the users .
Updated by Krish Gopalakrishnan 4 months ago
Please help the error is An error occurred while sending mail (Net::ReadTimeout with #<Socket:(closed)>)
Updated by Krish Gopalakrishnan 4 months ago
- File Email Error Snapshot.png Email Error Snapshot.png added
Please help the error is An error occurred while sending mail (Net::ReadTimeout with #<Socket:(closed)>)
Updated by Krish Gopalakrishnan 4 months ago
Had deployed Redmine version 5.1.3 on CentOS 9.2 . Could you please provide the docker-compose.yml and configuration.yml files for this version. Just to cross check with the existing files please..
Updated by Holger Just 4 months ago
- Has duplicate Defect #41490: Request for docker-compose.yml and configuration.yml added
Updated by Holger Just 4 months ago
Redmine does not ship with a docker configuration. There are several third-party projects who provide a docker image though. If you are using one of those images, please contact the maintainers of this image.
As for your apparent issue: it seems that Redmine is not able to contact the mailserver you have configured in your configuration.yml. This may have several causes, including firewall or routing issues, DNS resolution issues, and others.
Check that you can reach the configured mailserver from your Redmine server. If this does not work, you may have to use a different mailserver or change your server's configuration so that it can reach your mailserver.
Updated by Go MAEDA about 2 months ago
- Status changed from Needs feedback to Closed
- Resolution set to Invalid