Defect #7791
closed
No New Issue is created via email (SMTP fetching)
50%
Description
- complete the steps described in Fetching emails from an IMAP server
- if you reply to received issue notification email your comment is assigned well
- if you try to create new issue by appropriate Issue attributes, import fails (I know about failure by move_on_failure parameter, but I can't find any corresponding error log :-( )
Updated by Anonymous over 13 years ago
Same thing for me. Sinde a few days and i do not know why, i can not create new issue from an email.
No trace, no log, no error message...
Updated by Anonymous over 13 years ago
I think i have a track... I have added a mandatory custom_field while an issue is creeated. I think i have to set a value for thit mandatory field while a call receaive_imap task...
Do you know how i cam fix a value ?
Updated by Ladislav Nesnera over 13 years ago
Patrice Bonhomme wrote:
... I have added a mandatory custom_field while an issue is creeated...
We have no cusgtom fields :-(
Updated by Anonymous over 13 years ago
i confirm, my problem was coming from those custom fields.
I think that your problem is coming from a bad parameter of the rake task receive_imap. You have to provide some parameters. Here is a copy of the BASH script i am currently using and that is call by cron :
#!/bin/bash cd /services/redmine rake -v --trace -f /services/redmine/Rakefile redmine:email:receive_imap \ RAILS_ENV="production" \ host=imap.everest \ username=support@mydomain.com \ password=secret \ project=dsi-support \ tracker=Assistance \ unknown_user=create \ allow_override=tracker,priority,project # EOF
Updated by Ladislav Nesnera over 13 years ago
- % Done changed from 0 to 50
Patrice Bonhomme wrote:
I think that your problem is coming from a bad parameter of the rake task receive_imap..
Thanks for your hint. You inspired me to rewrite my cron command to the script. My parameters was almost the same expect for project and tracker. As seems they aren't optional, as I thought, but required. Import works well now. Thanks again.
It reminds me of note about custom fields from Receiving emails - "Make sure that the target project doesn't use required custom fields with no default value.."
My problem is resolved. What about your?
Updated by Etienne Massip over 13 years ago
- Status changed from New to Closed
- Resolution set to Invalid