From: Simon Josefsson <jas@extundo.com>
Subject: Re: nnimap problem solved by removing .agentview and .overview
Date: Thu, 12 Aug 2004 22:35:43 +0200 [thread overview]
Message-ID: <ilu7js42ixs.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87llgkp269.fsf@mail.contactor.se>
Mats Lidell <matsl@contactor.se> writes:
>>>>>> Simon wrote:
>
> Simon> Is there a simple recipe for reproducing this?
>
> My recipe is like this.
>
> 1. Send myself a letter. (I have splitting configured so gnus will
> automatically place mail form INBOX in the folder 'incoming')
> 2. Get new mail by pressing 'g'. See that there is one new letter in
> 'incoming'.
> 3. Enter the summary for 'incoming' and see that it is the letter I
> sent myself. (Don't read it.)
> 4. Send myself another letter.
> 5. Save and exit gnus and exit (X)Emacs.
> 6. Read mail with squirrelmail using the same source (imap and same
> server).
> 7. See the new mail (the second sent above) in INBOX. (There is no
> splitting activated in squirrelmail so the mail stays in INBOX.)
> 8. Use squirrelmail to move the new mail to the folder 'incoming'
> (simulating the fancy splitting in gnus ;-)
> 9. Go to 'incoming' in squirrelmail and look at the two new letters
> there. (The two I just sent myself.) (Don't read them.)
> 10. Exit squirrelmail.
> 11. Start (X)Emacs and go back into gnus.
> 12. See that the *Group* says there are two new mails in incoming.
> 13. Enter the summary and find only one new letter. The first.
This suggest a bug, somewhere; the above should work fine.
Could you get *imap-log* dumps from the first and second part of
running Gnus? (setq imap-log t)
Could you also collect *imap-log* for:
14. Quit summary buffer.
15. rm -rf ~/News/agent/nnimap/SERVER/GROUP
16. C-u RET the summary buffer.
Can you see the article in the summary buffer?
next prev parent reply other threads:[~2004-08-12 20:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 21:36 Mats Lidell
2004-08-11 22:05 ` Steven E. Harris
2004-08-12 2:11 ` Kevin Greiner
2004-08-12 15:13 ` Steven E. Harris
2004-08-12 15:46 ` Simon Josefsson
2004-08-12 16:08 ` Steven E. Harris
2004-08-12 16:48 ` Simon Josefsson
2004-08-12 17:26 ` Steven E. Harris
2004-08-12 19:31 ` Simon Josefsson
2004-08-16 15:02 ` Steven E. Harris
2004-08-16 15:11 ` Steven E. Harris
2004-08-16 15:31 ` Simon Josefsson
2004-08-16 16:45 ` Steven E. Harris
2004-08-16 16:59 ` Simon Josefsson
2004-08-16 17:50 ` gnus-parameters remodeled for Topics (was: nnimap problem solved by removing .agentview and .overview) Ted Zlatanov
2004-08-16 20:03 ` gnus-parameters remodeled for Topics Steven E. Harris
2004-08-17 3:13 ` nnimap problem solved by removing .agentview and .overview Steven E. Harris
2004-08-17 8:23 ` Simon Josefsson
[not found] ` <ilupt5q2mwv.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2004-08-17 11:59 ` Jochen Küpper
2004-08-17 15:50 ` Steven E. Harris
2004-08-17 16:40 ` Simon Josefsson
2004-08-12 19:49 ` Mats Lidell
2004-08-12 20:35 ` Simon Josefsson [this message]
2004-08-20 22:09 ` Mats Lidell
2004-08-12 21:30 ` Kevin Greiner
2004-08-12 22:28 ` Simon Josefsson
2004-08-16 17:45 ` Ted Zlatanov
2004-08-16 18:34 ` Chris Green
2004-08-16 19:43 ` Steven E. Harris
2004-08-16 19:54 ` Steven E. Harris
2004-08-17 11:39 ` Steinar Bang
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=ilu7js42ixs.fsf@latte.josefsson.org \
--to=jas@extundo.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;
as well as URLs for NNTP newsgroup(s).