From: Mariano Mara <mariano.mara@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] RMail chokes on broken headers
Date: Thu, 29 Oct 2009 20:02:46 -0300 [thread overview]
Message-ID: <c1d7c48b0910291602t551ee26ek198e558e6e70b7b8@mail.gmail.com> (raw)
In-Reply-To: <1255612194-sup-3880@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 4213 bytes --]
2009/10/15 William Morgan <wmorgan-sup@masanjin.net>
> Reformatted excerpts from Tero Tilus's message of 2009-10-12:
> > RMail looks abandoned. Development is pretty much stalled. No
> > functional changes since 2004-04-27. None of the reported bugs have
> > been fixed. Might it be worth to think about switching to another
> > mail lib? TMail author's http://github.com/mikel/mail/ looks
> > promising.
>
> Yeah, this is certainly an option. But it seems like a lot of work. And
> every day our set of rmail workarounds grows more robust. :)
>
> Not to say I wouldn't accept a patch that magically did this all for me,
> of course.
> --
Hi there, I'm facing the same error as reported by Tero. I applied the
modifications he sent, however it's failing in another place and my total
ignorance of Ruby prevents me from fixing it. Would anyone be so kind to
suggest a workaround?
Below is the complete exception recorded.
TIA,
Mariano
--- NoMethodError from thread: poll after loading inbox
undefined method `downcase' for nil:NilClass
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:502:in
`message_to_chunks'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:435:in
`message_to_chunks'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:435:in `map'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:435:in
`message_to_chunks'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:239:in
`load_from_source!'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:335:in
`build_from_source'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:145:in
`each_message_from'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/maildir.rb:160:in `each'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/maildir.rb:157:in `upto'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/maildir.rb:157:in `each'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:560:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:560:in `__pass'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:547:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:139:in
`each_message_from'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:93:in `do_poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:81:in `each'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:81:in `do_poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:80:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:80:in `do_poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:520:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:520:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/poll-mode.rb:15:in `poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:48:in `poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:520:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:520:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/bin/sup:196
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:77:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `initialize'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `new'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/bin/sup:196
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:669:in
`call'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:669:in
`__unprotected_load_threads'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:610:in
`call'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:610:in
`load_n_threads_background'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:77:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `initialize'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `new'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:608:in
`load_n_threads_background'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:679:in
`__unprotected_load_threads'
(eval):12:in `load_threads'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/bin/sup:196
/usr/bin/sup:19:in `load'
/usr/bin/sup:19
[-- Attachment #1.2: Type: text/html, Size: 5074 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-29 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 23:22 Tero Tilus
2009-10-15 13:11 ` William Morgan
2009-10-29 23:02 ` Mariano Mara [this message]
2009-10-30 21:50 ` William Morgan
2009-10-31 20:18 ` Mariano Mara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1d7c48b0910291602t551ee26ek198e558e6e70b7b8@mail.gmail.com \
--to=mariano.mara@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox