Gnus development mailing list
 help / color / mirror / Atom feed
From: david@adboyd.com (J. David Boyd)
Subject: Re: backing up read messages, and subscribed lists.
Date: Fri, 15 Jul 2005 14:33:29 -0400	[thread overview]
Message-ID: <81mzonj4w6.fsf@adboyd.com> (raw)
In-Reply-To: <q94wtnslzxj.fsf@xenon.gnostech.com>

"Steven E. Harris" <seh@panix.com> writes:

> david@adboyd.com (J. David Boyd) writes:
>
>> It's no problem at all to set up a script that sends over my
>> newsrc.eld right at the end of the work day, and retrieves it from
>> home at the beginning of the work day.
>
> But that's not enough, and won't work properly if you use the agent
> for your IMAP groups. We've been over this a few times over the last
> couple of years.
>
> At present I use unison (rsync works fine too) to synchronize
> everything under ~/doc/news, excluding ~/doc/news/agent. I used to
> synchronize ~/.newsrc and ~/.newsrc.eld, but was advised against
> it. Supposedly the per-backend marks files take care of whatever state
> is represented in .newsrc.eld.
>
> However, you'll find that your IMAP groups don't behave properly after
> this kind of syncing. New messages appear as expected, but Gnus loses
> track of which read messages are on the server and which ones are
> marked for expiry.
>
> For example, if at work you received and read three new messages, then
> go home and synchronize your Gnus files, you'll find that Gnus at home
> won't realize that those three messages you read at work are present
> on the server. You can kick it into doing so by manually running
> `gnus-agent-expire-group', but this also has the unfortunate
> side-effect of losing your expiry marks previously set at home.¹
>
> Note that I'm not syncing the agent files. My take on it is that the
> agent is good for local caching; I don't want to synchronize the
> cached copies of messages I've read in one location to another. But
> cached articles aside, apparently some extra files conveying some
> agent-related state must be necessary to prevent the lossy behavior
> I'm describing.
>
>
> Footnotes: 
> ¹ Note that this is still the case even with an IMAP server that
>   supports user-defined flags such as "gnus-expire" and
>   "gnus-dormant".
>


Thanks for the caveat.

I'm not using IMAP for mail with Gnus, just reading newsgroups, so I'm going
to try and synch up the .newrc, .newsrc.eld, and files in ~/News, and see how
it goes.

Thanks for the lucid explanation!

Dave




  reply	other threads:[~2005-07-15 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 14:52 J. David Boyd
2005-07-15 15:37 ` Ted Zlatanov
2005-07-15 15:47   ` J. David Boyd
2005-07-15 16:34     ` Ted Zlatanov
2005-07-15 16:44       ` J. David Boyd
2005-07-15 17:52         ` Steven E. Harris
2005-07-15 18:33           ` J. David Boyd [this message]
2005-07-15 19:01           ` Ted Zlatanov

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=81mzonj4w6.fsf@adboyd.com \
    --to=david@adboyd.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).