Actions
Defect #10971
closed1.4.3 Email receiving (IMAP) fails on Swedish date format
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Email receiving
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Invalid
Affected version:
Description
Hi all,
I tried reading (imap) mails on a gmail account (from a Swedish Windows 7 machine as well as from a reagular Gamil account, but I keep getting errors on the date format (which I am not explicitly specifying in my mail).
The command reporting the below was:
{server}:/my prompt$ rake -f /path/to/apps/redmine/Rakefile redmine:email:receive_imap \ RAILS_ENV="production" \ host=imap.googlemail.com port=993 ssl=1 username=first.last@gmail.com password=whatever \ project=projectname tracker=Deviation status=New \ allow_override=project,tracker,status,priority \ folder=INBOX move_on_success=issues_received move_on_failure=issues_ignored
Invalid gemspec in [/usr/share/ruby-rvm/gems/ruby-1.9.2-p180/specifications/mime-types-1.18.gemspec]: invalid date format in specification: "2012-03-21 00:00:00.000000000Z" Invalid gemspec in [/usr/share/ruby-rvm/gems/ruby-1.9.2-p180/specifications/tilt-1.3.3.gemspec]: invalid date format in specification: "2011-08-25 00:00:00.000000000Z" Invalid gemspec in [/usr/share/ruby-rvm/gems/ruby-1.9.2-p180/specifications/mail-2.4.4.gemspec]: invalid date format in specification: "2012-03-14 00:00:00.000000000Z" Invalid gemspec in [/usr/share/ruby-rvm/gems/ruby-1.9.2-p180/specifications/mime-types-1.18.gemspec]: invalid date format in specification: "2012-03-21 00:00:00.000000000Z" Invalid gemspec in [/usr/share/ruby-rvm/gems/ruby-1.9.2-p180/specifications/tilt-1.3.3.gemspec]: invalid date format in specification: "2011-08-25 00:00:00.000000000Z" Invalid gemspec in [/usr/share/ruby-rvm/gems/ruby-1.9.2-p180/specifications/mail-2.4.4.gemspec]: invalid date format in specification: "2012-03-14 00:00:00.000000000Z"
Is there anything more I try to narrow in on what I'm experiencing?
// Rolf Lampa
Updated by Jean-Philippe Lang over 12 years ago
- Status changed from New to Closed
- Resolution set to Invalid
This is a rubygems issue and it was fixed (commit). You should upgrade rubygems.
Actions