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

[supermiri123@gmail.com]

Thanks for the quick response!

> A maildir might be a good choice.  The `nnmaildir' backend (info "(gnus)
> Maildir") can use a remote filesystem, e.g.
> 
> (setq gnus-select-method
>       '(nnmaildir "mail"
>         (directory "/rsyncc:user@remotehost.org:/path/to/maildir/")
>         (get-new-mail t)))
> 
> The above would use Gnus to incorporate mail using whatever methods you
> picked in `mail-sources', and store them in a remote maildir accessed
> with rsync (you can use any TRAMP filename, e.g. ssh:, scpc:, etc.).

Reading this, it appears to me that I was confused about what gnus-select-method does :-) I now checked my .emacs and learn that I use the customized variable mail-sources to tell gnus where to get my mail from, gnus-select-method to tell gnus where to get my news from, and gnus-secondary-select-method to tell gnus where to store my mail.  The last currently just reads ((nnml "")).

In the documentation I see that nnml allows a parameter nnml-directory.  Could I set this to a tramp path also?  This would have the advantage that I do not have to respool my old mail.  Also, the doc says that nnmaildir uses many many inodes (while nnml only uses many).  Should I worry about this?

Is there a particular reason to prefer nnmaildir over nnml in my setting?  (I was happy with nnml for some 10 years now, but of course, the setting is slightly different now.)


Many many thanks,

Martin