From mboxrd@z Thu Jan  1 00:00:00 1970
From: manish@gslab.com (Manish Sapariya)
Date: Thu, 08 Nov 2007 10:45:09 +0530
Subject: [sup-talk] 'undefined method `longname' for
 nil:NilClass'	(error type NoMethodError)
In-Reply-To: <1194467915-sup-5870@south>
References: <473186CB.8090307@gslab.com> <1194467915-sup-5870@south>
Message-ID: <47329B5D.4090907@gslab.com>

Hi Williams,
Thanks for the fix. However looks like I have some weird mail in my box.
The body and the charset both are nil. Is there any way I can backtrack the
offending message and find out whats the character set and encoding used
for that message?
Thanks,
Manish

(rdb:1) list
[372, 381] in /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/message.rb
   372    def self.convert_from body, charset
   373      begin
   374        raise MessageFormatError, "RubyMail decode returned a null 
body" unless body
   375        return body unless charset
   376        Iconv.iconv($encoding, charset, body).join
   377      rescue Errno::EINVAL, Iconv::InvalidEncoding, 
Iconv::IllegalSequence, MessageFormatError => e
   378        Redwood::log "warning: error (#{e.class.name}) decoding 
message body from #{charset}: #{e.message}"
   379        File.open("sup-unable-to-decode.txt", "w") { |f| f.write 
body }
   380        body
   381      end
(rdb:1) p m.charset
nil
(rdb:1) p m.body
nil



William Morgan wrote:
> Excerpts from Manish Sapariya's message of Wed Nov 07 01:35:07 -0800 2007:
>   
>> The problem was: 'undefined method `longname' for nil:NilClass' (error 
>> type NoMethodError)
>> A backtrace follows:
>> /usr/lib/ruby/gems/1.8/gems/sup-0.2/lib/sup/poll.rb:102:in `do_poll': undefined method `longname' for nil:NilClass (NoMethodError)
>>     
>
> This should be fixed in SVN now. You may have to re-index the offending
> source (sup-sync --all <source uri>).
>
>