Forum archive
Create issues from mail not working.
Hello everyone,
I have a little issue with my new redmine server when I am trying to create a issue from a mail.
I have a OTRS server, that send the details of every new ticket created in OTRS to one pop3 email account.
I am following this old guide, that is working in my old redmine server,
https://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails
The following cron job works fine in my old redmine server, but doesnt't work in my new server.
Private data have been change by XXX
/var/www/redmine/bin/rake -f /var/www/redmine/Rakefile redmine:email:receive_pop3 RAILS_ENV="production" project=XXXX tracker=support priority=normal allow_override=project host=mail.xxxx.com username=xxxx@xxxx.com password=XXXX
All the data was migrated from the old server to the newest, for this reason I think that this cronjob should work fine in the new server, without configure anything more.
As after run the job, the console not show any error message I don´t know wich is the problem here,
Some of you hade a similar issue ?
It's posible that this task not run in the latest version of redmine ?
There are another solutions to create issues from a mail ?
Somebody knows a plugin that do the same work?
My servers info:
Newest:
Environment: Redmine version 4.0.3.stable Ruby version 2.3.5-p376 (2017-09-14) [x86_64-linux] Rails version 5.2.2.1 Environment production Database adapter Mysql2 Mailer queue ActiveJob::QueueAdapters::AsyncAdapter Mailer delivery sendmail SCM: Subversion 1.9.5 Git 2.11.0 Filesystem Redmine plugins: no plugin installed
OLD:
Environment: Redmine version 3.2.0.stable Ruby version 2.1.5-p273 (2014-11-13) [x86_64-linux-gnu] Rails version 4.2.5 Environment production Database adapter Mysql2 SCM: Subversion 1.8.10 Mercurial 3.1.2 Bazaar 2.7.0 Git 2.1.4 Filesystem Redmine plugins: no plugin installed
Many thanks to all for read my issue.
Will be much apreciatted if anybody could helps to me with this.
Regards.
We've changed our Ruby install method during v15.x, so I suspect that the issue is caused by the cron job being incompatible with the newer install method.
Could you please share the full contents of the cron job?