Re: Setting up gnus: read on local, store remote (but not on mailserver)

[W. Greenhouse]

Hi Martin,

supermiri123@gmail.com writes:

> OK, I've *almost* got it working.  I did the following via customize:
>
> (gnus-home-directory "/scpc:YYY@XXX.ZZ:~")
> (message-directory "/scpc:YYY@XXX.ZZ:~/Mail/")
> (gnus-secondary-select-methods (quote ((nnml "" (nnml-marks-is-evil t)))))
>
> This let me read my old mail which is stored with nnml.  I had to set
> nnml-marks-is-evil because otherwise tramp would encode and decode
> every .marks file, which was annoying.
>
> However, the above does not let me read the archived mail stored with
> nnfolder. For these, the path is explicitely in my .newsrc.eld file.
> I tried to do
>
> (setq gnus-message-archive-method
>       '(nnfolder "archive"
>                (nnfolder-directory   "/scpc:YYY@XXX.ZZ:~/Mail/archive")
>                (nnfolder-active-file "/scpc:YYY@XXX.ZZ:~/Mail/archive/active")
>                (nnfolder-get-new-mail nil)
>                (nnfolder-inhibit-expiry t)
>                (nnfolder-marks-is-evil t)))
>
> but this had no effect (I guess it will only affect newly created
> archive folders).

I would say (despite the warnings in the ~/.newsrc.eld file) that you can
safely delete the line in your ~/.newsrc.eld where the nnfolder group is
defined.  For me it is a (setq gnus-server-alist ...) cell.  The new
nnfolder hierarchy should be detected from your settings.

Also, you might want to make sure that those old archive folders aren't
present but inactive.  Enter A A to see your entire list of available
groups from all backends (including nnfolder).  You might want to do
that to check before you try my idea above.

> In fact, I'd rather have no explicit paths in .newsrc.eld at all,
> because I do want to be able to use gnus by just taking the .emacs
> with me.
>
> Any ideas?

The mail-type backends including nnml and nnmaildir are *reasonably*
portable in that the NOV and marks are always included within the folder
itself, so that's all you really need to back up when changing systems.
But you can't eliminate .newsrc.eld completely, AFAIK, as it holds both
your group subscriptions and your marks for news-type backends
(including some mail systems that Gnus implements in a net-news-esque
way, like nnimap).  One idea you might think about is that all Gnus
directory variables inherit the `gnus-home-directory' variables, and
most backends inherit `gnus-directory'.  By setting these, you could
just move everything to the rsync/scpc address and hopefully everything
would just work.

I'm excited to here that remote nnml is mostly workable, though. :)  Is
the performance acceptable?

--
Regards,
WGG