From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: possible imap.el bug
Date: 15 Oct 2004 11:04:51 -0400 [thread overview]
Message-ID: <4nfz4gc99o.fsf@lifelogs.com> (raw)
In-Reply-To: <ilud5zlxgu4.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu, 14 Oct 2004 21:03:31 +0200")
On Thu, 14 Oct 2004, jas@extundo.com wrote:
> "Ted Zlatanov" <tzz@lifelogs.com> writes:
>
>> I got this today while processing spam. I'm not sure what the problem
>> is, unfortunately, but it looks like some data may be missing from the
>> overview?
>>
>> Ted
>>
>>
>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>> string-to-number(nil)
>> imap-message-copyuid-1("train")
>> imap-message-copy("111169" "train" dontcreate nil " *nnimap* depot")
>
> Do (setq imap-log t) and get the last part from *imap-log*, it looks
> like a protocol problem.
The error may be due to something unusual in the message (a mail
bounce here), so I'm attaching the headers of the bounce. I've also
seen this error happen with spam, which may also have funny headers.
I edited the real address to nosuch@invalid.com.
The server is Courier IMAP.
Ted
10844 UID FETCH 32361 BODY.PEEK[].
* 9 FETCH (UID 32361 BODY[] {3247}.
Return-Path: <>.
Delivered-To: lifelogs-lifelogs:com-tzz@lifelogs.com.
X-Envelope-To: tzz@lifelogs.com.
Received: (qmail 56231 invoked from network); 15 Oct 2004 14:50:44 -0000.
Received: from sysblade0.bwh.harvard.edu (HELO mail.bwh.harvard.edu) (134.174.9.44).
by saghotta.pair.com with SMTP; 15 Oct 2004 14:50:44 -0000.
Received: (qmail 18054 invoked for bounce); 15 Oct 2004 14:40:53 -0000.
Date: 15 Oct 2004 14:40:53 -0000.
From: MAILER-DAEMON@mail.bwh.harvard.edu.
To: tzz@lifelogs.com.
Subject: failure notice.
X-Spam-Filtered: f9609c3ab574f6a5d7c7e6b6300efd2a.
X-Spam-Status: No, hits=-34.8 required=4.0 tests=NO_REAL_NAME,BAYES_00.
X-Spam-Flag: NO.
X-Spam-Level: .
.
Hi. This is the qmail-send program at mail.bwh.harvard.edu..
I'm afraid I wasn't able to deliver your message to the following addresses..
This is a permanent error; I've given up. Sorry it didn't work out..
.
<nosuch@invalid.com>:.
Sorry, I couldn't find any host named invalid.com. (#5.1.2).
.
--- Below this line is a copy of the message..
.
10844 OK UID FETCH completed.
10845 UID COPY 32361 "soccer".
10845 OK UID COPY completed.
next prev parent reply other threads:[~2004-10-15 15:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 18:48 Ted Zlatanov
2004-10-14 19:03 ` Simon Josefsson
2004-10-15 15:04 ` Ted Zlatanov [this message]
2004-10-15 16:39 ` Simon Josefsson
2004-10-15 16:53 ` Ted Zlatanov
2004-10-15 16:57 ` Simon Josefsson
2004-10-15 17:32 ` Ted Zlatanov
2004-10-15 17:37 ` Simon Josefsson
[not found] ` <4nsm8f956n.fsf@lifelogs.com>
[not found] ` <iluacunx0k6.fsf@latte.josefsson.org>
[not found] ` <4nsm8fcr00.fsf@bwh.harvard.edu>
[not found] ` <iluvfdbrsni.fsf@latte.josefsson.org>
[not found] ` <4nvfd7ubzv.fsf@lifelogs.com>
[not found] ` <ilulldvoplv.fsf@latte.josefsson.org>
2004-10-25 19:11 ` Ted Zlatanov
2004-10-25 19:29 ` Simon Josefsson
2004-10-26 15:06 ` Ted Zlatanov
2004-10-26 15:54 ` Simon Josefsson
2004-10-26 17:09 ` CHENG Gao
2004-10-26 17:59 ` Ted Zlatanov
2004-10-26 18:05 ` Ted Zlatanov
2004-10-26 20:07 ` Simon Josefsson
2004-10-26 15:51 ` Gerd Flaig
2004-10-26 16:01 ` Simon Josefsson
2004-10-26 16:30 ` Gerd Flaig
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=4nfz4gc99o.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).