From: egallego@babel.ls.fi.upm.es (Emilio Jesús Gallego Arias)
To: ding@gnus.org
Subject: Re: Incoming IMAP split problem
Date: Thu, 17 Feb 2011 21:53:33 +0100 [thread overview]
Message-ID: <87vd0i1iya.fsf@babel.ls.fi.upm.es> (raw)
In-Reply-To: <87d3mqhbh0.fsf@hati.baby-gnu.org>
Daniel Dehennin <daniel.dehennin@baby-gnu.org> writes:
> Another case of nnimap split problem: copy but not deleted.
>
> I set imap-log to t and found something interessting:
>
> #v+
> 08:10:00 128662 LIST "" "*"
> [snip]
> 08:15:00 128761 EXAMINE "baby-gnu.org.cf" (QRESYNC (1236917076 2))
> #v-
That's exactly what I was seeing but it is difficult to duplicate. Lars
suggested stepping through the function, but I've modified it in order
to log the interesting values:
diff --git a/lisp/nnimap.el b/lisp/nnimap.el
index 74ef756..1ffe5ad 100644
--- a/lisp/nnimap.el
+++ b/lisp/nnimap.el
@@ -1794,6 +1794,7 @@ textual parts.")
(nnimap-wait-for-response (caar sequences))
;; And then mark the successful copy actions as deleted,
;; and possibly expunge them.
+ (message "NNIMAP SPLIT DEBUG %s %s" (nnimap-parse-copied-articles sequences) sequences)
(nnimap-mark-and-expunge-incoming
(nnimap-parse-copied-articles sequences)))
(nnimap-mark-and-expunge-incoming junk-articles)))))))
Could you apply the patch and post the message when splitting goes wrong?
I guess posting also the contents of the response for the COPY command
would be useful.
Regards,
Emilio
next prev parent reply other threads:[~2011-02-17 20:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 16:23 Michael Welsh Duggan
2011-02-16 16:31 ` Michael Welsh Duggan
2011-02-16 21:42 ` Lars Ingebrigtsen
2011-02-16 22:14 ` Emilio Jesús Gallego Arias
2011-02-16 22:21 ` Lars Ingebrigtsen
2011-02-16 22:28 ` Lars Ingebrigtsen
2011-02-18 20:23 ` Michael Welsh Duggan
2011-02-17 16:28 ` Daniel Dehennin
2011-02-17 20:53 ` Emilio Jesús Gallego Arias [this message]
2011-02-18 16:53 ` Daniel Dehennin
2011-02-18 17:19 ` Emilio Jesús Gallego Arias
2011-02-18 23:13 ` Lars Ingebrigtsen
2011-02-18 23:52 ` Michael Welsh Duggan
2011-02-19 9:40 ` Lars Ingebrigtsen
2011-02-19 17:48 ` Michael Welsh Duggan
2011-02-19 18:29 ` Daniel Dehennin
2011-02-19 22:36 ` Daniel Dehennin
2011-02-20 1:06 ` Lars Ingebrigtsen
2011-02-21 6:30 ` Daniel Dehennin
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=87vd0i1iya.fsf@babel.ls.fi.upm.es \
--to=egallego@babel.ls.fi.upm.es \
--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).