From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: Re: arg???!!! losing expiry marks (nnimap)
Date: Fri, 28 Mar 2008 12:55:41 -0700 [thread overview]
Message-ID: <sd8x02y66a.fsf@wes.hardakers.net> (raw)
In-Reply-To: <sdmyoiy7ks.fsf@wes.hardakers.net> (Wes Hardaker's message of "Fri, 28 Mar 2008 12:25:23 -0700")
>>>>> "WH" == Wes Hardaker <wes@hardakers.net> writes:
WH> So, I took the plunge and converted my mail server to dovecot thinking
WH> it'd be better. I did the complete plunge and went to maildir on the
WH> backend as well. So far so good... Until gnus looses my gnus-expire
WH> marks when something else accesses the directory? This is really really
WH> bad since I tend to keep old mail around for a month before it gets
WH> "actually expired".
Well... the flag still exists in the file in the X-Keyword header. It
turns out that the Mail::Box perl class modifies the file name and
strips the 'a' off the end. I don't know what flag the 'a' associates
with since I don't see it in maildir docs anywhere.
So... How can I rebuild gnus' internal list of what's expired from
headers? Because this:
(display . [not expire])
Still shows expired messages.
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
prev parent reply other threads:[~2008-03-28 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 19:25 Wes Hardaker
2008-03-28 19:55 ` Wes Hardaker [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=sd8x02y66a.fsf@wes.hardakers.net \
--to=wes@hardakers.net \
--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).