Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Green <cmg@dok.org>
Subject: Re: Losing tickmarks in nnimap groups
Date: Wed, 07 Apr 2004 14:40:23 -0400	[thread overview]
Message-ID: <m21xmztyw8.fsf@catbert.dok.org> (raw)
In-Reply-To: <ilu65ch89dc.fsf@latte.josefsson.org>

[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]

Simon Josefsson <jas@extundo.com> writes:

> I always run with `imap-log' enabled, so I can look at what happened
> if something weird happens.  It might not help reproduce the problem,
> but could give some hints to help pin point a pattern or something.

I'm using Oort 5.10.6.  This message isn't flagged because I can't get
gnus to display it no matter the value I pass to the group open
function. I have a plugged agent doing imap over openssl and I think
that's about the only notable gnus config.

I've not included the output from the * 477 fetch commands.  If they
are important to you, I can send them in private, I just don't want to
sign up all my friends for spam :).

I'm willing to try most commands and I can atleast plod at lisp but
debugging this problem (it's not the first message to have that happen
to ) is close to impossible for me without guidance. If I do an nnir
search for flight, it does display.

Maildir/cur/1081245048.27012_3.lilly:2,S

Maildir/courierimapuiddb has

2173 1081245048.27012_3.lilly

(2188 is the highest number I have right now so C-u 30 should pull
that out )

0:nnimap+csoft:INBOX 
C-u 30 Enter

This mail is flight information from my wife on where to pick up my
mother in law... a really bad mail to have had problem with :)

I have the imap.log for this from the C-u 30 Enter 

The only time I see 2173 as a UID in this log is on the initial search
seen command.

Here's the output from reentering the INBOX. I originally had this
posted inline but nntp.gmane.org said my article only had headers.

Sorry if I've sent multiple copies of this message.


[-- Attachment #2: imap-to-gnus.txt.gz --]
[-- Type: application/octet-stream, Size: 2483 bytes --]

[-- Attachment #3: Type: text/plain, Size: 61 bytes --]


-- 
Chris Green <cmg@dok.org>
A good pun is its own reword.

      parent reply	other threads:[~2004-04-07 18:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02  6:22 Steinar Bang
2004-04-02  6:49 ` Wes Hardaker
2004-04-02 11:18 ` Simon Josefsson
2004-04-02 15:42   ` Wes Hardaker
2004-04-03 10:21     ` Steinar Bang
2004-04-03 10:27       ` Steinar Bang
2004-04-16  5:49         ` Steinar Bang
2004-04-16 16:14           ` Wes Hardaker
2004-04-16 10:47         ` Steinar Bang
2004-04-03 10:22   ` Steinar Bang
2004-04-03 13:43     ` Simon Josefsson
2004-04-07 18:37       ` Chris Green
2004-04-07 21:01         ` Simon Josefsson
2004-04-08 12:53           ` Chris Green
2004-04-08 21:26             ` Invisible articles (was: Re: Losing tickmarks in nnimap groups) Simon Josefsson
2004-04-09 13:12               ` Invisible articles Chris Green
2004-04-09 13:28                 ` Simon Josefsson
2004-04-07 18:38       ` Losing tickmarks in nnimap groups Chris Green
2004-04-07 18:40       ` Chris Green [this message]

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=m21xmztyw8.fsf@catbert.dok.org \
    --to=cmg@dok.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).