Redmine - Issue creation based on emails - UID COPY failed
Added by Cédric HATEM about 6 years ago
Hello All,
We are using Redmine as an Heldesk/Ticketing system.
I'm trying to configure the creation of issues based on email. But It does not working yet.
My env :
A bitnami stack
RAILS_ENV=production bin/about sh: 1: darcs: not found sh: 1: hg: not found sh: 1: bzr: not found Environment: Redmine version 3.4.5.stable Ruby version 2.3.7-p456 (2018-03-28) [x86_64-linux] Rails version 4.2.8 Environment production Database adapter Mysql2 SCM: Subversion 1.9.7 Cvs 1.12.13 Git 2.14.1 Filesystem Redmine plugins: redmine_mail_reminder 3.0.0.0001
And when I try below command I receive an error.
sudo rake redmine:email:receive_imap RAILS_ENV="production" host=myhostname.mysuperdomain.fr username=testredmine@mysuperdomain.fr password=testredmine ssl=1 port=993 move_on_success=read move_on_failure=failed --trace
Output :
** Invoke redmine:email:receive_imap (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute redmine:email:receive_imap rake aborted! Net::IMAP::NoResponseError: UID COPY failed /opt/bitnami/ruby/lib/ruby/2.3.0/net/imap.rb:1196:in `get_tagged_response' /opt/bitnami/ruby/lib/ruby/2.3.0/net/imap.rb:1250:in `block in send_command' /opt/bitnami/ruby/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize' /opt/bitnami/ruby/lib/ruby/2.3.0/net/imap.rb:1232:in `send_command' /opt/bitnami/ruby/lib/ruby/2.3.0/net/imap.rb:1418:in `copy_internal' /opt/bitnami/ruby/lib/ruby/2.3.0/net/imap.rb:854:in `uid_copy' /opt/bitnami/apps/redmine/htdocs/lib/redmine/imap.rb:49:in `block in check' /opt/bitnami/apps/redmine/htdocs/lib/redmine/imap.rb:36:in `each' /opt/bitnami/apps/redmine/htdocs/lib/redmine/imap.rb:36:in `check' /opt/bitnami/apps/redmine/htdocs/lib/tasks/email.rake:117:in `block (4 levels) in <top (required)>' /opt/bitnami/apps/redmine/htdocs/app/models/mailer.rb:438:in `with_synched_deliveries' /opt/bitnami/apps/redmine/htdocs/lib/tasks/email.rake:116:in `block (3 levels) in <top (required)>' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/task.rb:271:in `block in execute' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/task.rb:271:in `each' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/task.rb:271:in `execute' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/task.rb:213:in `block in invoke_with_call_chain' /opt/bitnami/ruby/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/task.rb:193:in `invoke_with_call_chain' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/task.rb:182:in `invoke' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:160:in `invoke_task' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:116:in `block (2 levels) in top_level' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:116:in `each' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:116:in `block in top_level' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:125:in `run_with_threads' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:110:in `top_level' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:83:in `block in run' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:186:in `standard_exception_handling' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/lib/rake/application.rb:80:in `run' /opt/bitnami/ruby/lib/ruby/gems/2.3.0/gems/rake-12.3.1/exe/rake:27:in `<top (required)>' /opt/bitnami/ruby/bin/rake:23:in `load' /opt/bitnami/ruby/bin/rake:23:in `<main>' Tasks: TOP => redmine:email:receive_imap
Do you have any ideas ?
Thanks in advance,
Cédric
Replies (1)
RE: Redmine - Issue creation based on emails - UID COPY failed - Added by Cédric HATEM about 6 years ago
I've focus the problem.
It is due to below options :
move_on_success=read move_on_failure=failed
So issue is partialy solved as I can import the issues received per email.
Cédric