Re: Switching to IMAP

[Simon Josefsson <jas@pdc.kth.se>]

"Chris D.Halverson" <cdh@CompleteIS.com> writes:

> I've got about 20 nnml groups that I'd like to have available to
> nnimap.

Um, do you mean you want to move them to nnimap groups?  nnimap is a
client, not a server.  This means you can't "export" existing nnml
groups via nnimap to other imap clients.

> I'm looking over the manual and see that I should setup nnimap
> as a secondary-select-method. I currently have:
> 
> (setq gnus-secondary-select-methods   '((nnml "")))
> 
> I'd like to use SSL for my local connection, openssl is already
> installed and running as is my imaps server. I'm also using procmail
> to split my mail and would like to continue to do so. I'm guessing
> I'll just set it up to deliver to the "real" mailboxes instead of to
> the spool files I am doing now assuming I want them available to
> nnimap (or any other imap client). I also have the following vars set:
> 
>       nnmail-use-procmail t
>       mail-source-delete-incoming t
> 
> I can't seem to find it, but currently my nnml groups expire after 7
> days if marked w/ 'E', ie. I can go back and see "deleted" messages
> which is very helpful at times. It doesn't appear that this is
> possible w/ nnimap, correct?

No, nnimap do expiring.

But I'm confused, do you want to access your mail remotely, via
(nn)imap or fetching the mail via IMAP to a local nnml spool?

If you want to access your mail remotely via (nn)imap, the variables
you mention are not used at all.  The variables only have semantics
only if the backend download mail locally to split them.  nnimap
access mail remotely (such as nntp), so any procmail-splitting would
have to take place on the server.  (Or with the nnimap splitter.)