From: Simon Josefsson <jas@extundo.com>
Subject: Re: Bad interaction between nnimap + agent + expiry (bug?)
Date: Wed, 14 Dec 2005 23:11:13 +0100 [thread overview]
Message-ID: <iluhd9bcose.fsf@latte.josefsson.org> (raw)
In-Reply-To: <q94bqzjea5i.fsf@chlorine.gnostech.com> (Steven E. Harris's message of "Wed, 14 Dec 2005 11:44:26 -0800")
"Steven E. Harris" <seh@panix.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Yes. The E mark should be visible in the Summary buffer on the
>> second Gnus if the first Gnus had set the mark.
>
> I've noticed messages marked as expirable in one instance not be
> recognized as expirable in another. (Mark message while at work, go
> home, connect, and find the same message unmarked.) The server does
> appear to support client flags:
>
> ,----
> | 252 SELECT "INBOX"
> | * FLAGS (gnus-expire gnus-forward gnus-dormant \Draft \Answered \Flagged \Deleted \Seen \Recent)
> | * OK [PERMANENTFLAGS (gnus-expire gnus-forward gnus-dormant \* \Draft \Answered \Flagged \Deleted \Seen)] Limited
> | * 148 EXISTS
> | * 0 RECENT
> | * OK [UIDVALIDITY 1067275254] Ok
> | * OK [MYRIGHTS "acdilrsw"] ACL
> | 252 OK [READ-WRITE] Ok
> `----
>
> I'll have to try some debugging and see if I can reproduce the
> problem.
Following how flags are set on a particular message in *imap-log* in
both Gnus may help.
prev parent reply other threads:[~2005-12-14 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 23:08 Gregory Novak
2005-12-14 14:29 ` Simon Josefsson
2005-12-14 16:04 ` Steven E. Harris
2005-12-14 19:08 ` Simon Josefsson
2005-12-14 19:44 ` Steven E. Harris
2005-12-14 22:11 ` Simon Josefsson [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=iluhd9bcose.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).