[DRE-maint] Bug#722670: feed2imap: feed-item causes crash

[Christoph Feenders]

Package: feed2imap
Version: 1.0-2
Severity: normal
Tags: upstream

I've been using feed2imap on a fixed set of feeds for some time without
problems, but suddenly, feed2imap started to crash on a particular feed. The
original address of the feed is
  http://iopscience.iop.org/1367-2630/?rss=1
but since the troublesome item might disappear soon, I copied the current
(2013-09-13) state to
  http://echti.de/feed2imap/trouble_feed

On this feed, feed2imap correctly extracts the oldest 3 items titled
* Entangled mechanical cat states via conditional single photon optomechanics
* Evolution of the electronic structure in Mo 1− x Re x alloys
* Spin–orbit-induced hole spin relaxation in InAs and GaAs quantum dots
but then crashes (presumably) processing the following item
* Search for excited electrons and muons in ##IMG##
[http://ej.iop.org/images/1367-2630/15/9/093011/toc_nj482877ieqn1.gif] {$\sqrt
{s}=8$} TeV proton–proton collisions with the ATLAS detector

Error messages in verbose-mode are as follows:

$ feed2imap -v
I, [2013-09-13T09:12:49.603471 #12979]  INFO -- : Feed2Imap V.1.0 started
I, [2013-09-13T09:12:49.603567 #12979]  INFO -- : Reading configuration file
....
I, [2013-09-13T09:12:49.609261 #12979]  INFO -- : Initializing cache ...
I, [2013-09-13T09:12:49.615230 #12979]  INFO -- : Connecting to IMAP accounts
....
I, [2013-09-13T09:12:49.971640 #12979]  INFO -- : Fetching and filtering feeds
....
I, [2013-09-13T09:12:53.796017 #12979]  INFO -- : Parsing and uploading ...
I, [2013-09-13T09:12:54.677351 #12979]  INFO -- : newJournalPhysics: 10 new
items, 0 updated items.
F, [2013-09-13T09:12:56.510144 #12979] FATAL -- : Exception caught while
uploading mail to eTocs2/New J Physics: Command Argument Error. 11
/usr/lib/ruby/vendor_ruby/feed2imap/rubyimap.rb:1095:in `get_tagged_response'
/usr/lib/ruby/vendor_ruby/feed2imap/rubyimap.rb:1147:in `send_command'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/lib/ruby/vendor_ruby/feed2imap/rubyimap.rb:1129:in `send_command'
/usr/lib/ruby/vendor_ruby/feed2imap/rubyimap.rb:649:in `append'
/usr/lib/ruby/vendor_ruby/feed2imap/imap.rb:107:in `putmail'
/usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:256:in `initialize'
/usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:253:in `each'
/usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:253:in `initialize'
/usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `each'
/usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `initialize'
/usr/bin/feed2imap:48:in `new'
/usr/bin/feed2imap:48
F, [2013-09-13T09:12:56.510530 #12979] FATAL -- : We can't recover from IMAP
errors, so we are exiting.

Hope this helps.
Christoph



-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages feed2imap depends on:
ii  librmail-ruby1.8                  1.0.0-1
ii  ruby-feedparser                   0.7-2
ii  ruby-rubymail [librmail-ruby1.8]  1.0.0-1
ii  ruby1.8                           1.8.7.358-7

feed2imap recommends no packages.

Versions of packages feed2imap suggests:
ii  evolution [imap-client]  3.4.4-3
pn  imap-server              <none>
ii  mutt [imap-client]       1.5.21-6.2

-- no debconf information