*sigh* looks like some SPAM in my inbox caused sup some serious heart burn: --- RuntimeError from thread: poll after loading inbox just added message "20080502075530.7980.qmail@\343\340\353\377" but couldn''t find it in a search /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:204:in `sync_message'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:497:in `send'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:497:in `method_missing'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:160:in `add_messages_from'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/imap.rb:167:in `each'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/imap.rb:155:in `upto'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/imap.rb:155:in `each'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:534:in `send'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:534:in `__pass'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:523:in `method_missing'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:141:in `add_messages_from'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:98:in `do_poll'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:86:in `each'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:86:in `do_poll'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:85:in `synchronize'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:85:in `do_poll'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:497:in `send'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:497:in `method_missing'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/poll-mode.rb:17:in `poll'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:53:in `poll'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:497:in `send'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:497:in `method_missing'' /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup:200 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:60:in `reporting_thread'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:58:in `initialize'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:58:in `new'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:58:in `reporting_thread'' /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup:200 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:536:in `call'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:536:in `__unprotected_load_threads'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:478:in `call'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:478:in `load_n_threads_background'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:60:in `reporting_thread'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:58:in `initialize'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:58:in `new'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:58:in `reporting_thread'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:476:in `load_n_threads_background'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:546:in `__unprotected_load_threads'' (eval):12:in `load_threads'' /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup:200 /usr/bin/sup:16:in `load'' /usr/bin/sup:16 --- SystemExit from thread: main just added message "20080502075530.7980.qmail@\343\340\353\377" but couldn''t find it in a search /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:64:in `select'' /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/buffer.rb:31:in `nonblocking_getch'' /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup:217 /usr/bin/sup:16:in `load'' /usr/bin/sup:16 -- Jon M. Dugan <jdugan at es.net> | GTalk: jdugan.esnet ESnet Network Engineering Group | http://www.es.net Lawrence Berkeley National Laboratory | http://www.lbl.gov/
Reformatted excerpts from Jon Dugan''s message of 2008-05-02:> looks like some SPAM in my inbox caused sup some serious heart burn: > > --- RuntimeError from thread: poll after loading inbox > just added message "20080502075530.7980.qmail@\343\340\353\377" but couldn''t > find it in a searchInteresting. Non-ASCII characters in a message id. Haven''t seen that one before. Maybe I should SHA1 all message ids anyways. -- William <wmorgan-sup at masanjin.net>
Excerpts from William Morgan''s message of Mon May 05 17:59:55 -0700 2008:> Interesting. Non-ASCII characters in a message id. Haven''t seen that one > before. Maybe I should SHA1 all message ids anyways.Ayup, that made me do a double take too. I used mutt to delete it and ran a sup-sync -c to get back to business. I kept a copy of the message if you want to take a look, but the salient point was the wide chars in the message id. Cheers, Jon -- Jon M. Dugan <jdugan at es.net> | GTalk: jdugan.esnet ESnet Network Engineering Group | http://www.es.net Lawrence Berkeley National Laboratory | http://www.lbl.gov/
Reformatted excerpts from Jon Dugan''s message of 2008-05-07:> Ayup, that made me do a double take too. I used mutt to delete it and > ran a sup-sync -c to get back to business. I kept a copy of the > message if you want to take a look, but the salient point was the wide > chars in the message id.I''ve stripped out non-ascii characters in a patch to next. Try it out if you want! -- William <wmorgan-sup at masanjin.net>