From: manish@gslab.com (Manish Sapariya)
Subject: [sup-talk] lots of fake messages in my mailbox
Date: Fri, 14 Dec 2007 10:14:29 +0530 [thread overview]
Message-ID: <47620A2D.6080602@gslab.com> (raw)
Hi All,
I just wanted to confirm if this is the problem due to special character
set used by mail?
I used to get crash 2 weeks before, but after upgrading to 0.3 that
problem seems to be
gone away, but I see lots of fake messages with null body.
Does this mean that the mail contents were not understood by RubyMail?
[Fri Dec 14 10:12:29 +0530 2007] faking date header for
sup-faked-89e4ed8175efd30de99101ed93a51869
[Fri Dec 14 10:12:29 +0530 2007] warning: error
(Redwood::MessageFormatError) decoding message body from : RubyMail
decode returned a null body
Thanks and Regards,
Manish
reply other threads:[~2007-12-14 4:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47620A2D.6080602@gslab.com \
--to=manish@gslab.com \
/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