Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: converting archive group to different format without losing marks
Date: Fri, 28 Sep 2001 16:33:06 +0200	[thread overview]
Message-ID: <vaf1ykr75ct.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m37kuje8xk.fsf@localhost.localdomain> (Joe Wells's message of "28 Sep 2001 14:33:59 +0100")

Joe Wells <jbw@izanami.cee.hw.ac.uk> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> I presume that nnml is your primary mail backend, and that you are
>> satisfied with a single nnml:outgoing group, which is on the same
>> server as your other nnml mail.
>
> Does it cause a problem if I am not already using nnml?  I would also
> like to move my incoming e-mail from nnbabyl to nnml.

No problem, I just wanted to simply my instructions.  If you want to
put your outgoing group into a new backend, you'll have to create that
server.  For example:

(add-to-list 'gnus-secondary-select-methods
             '(nnml "archive"
               (nnml-directory "~/Mail-archive")))

Then, you can use the group nnml+archive:outgoing.  Maybe you need to
add more parameters, in addition to nnml-directory.  nnml-active-file
comes to mind.

But if you want to move from nnbabyl to nnml anyway...

>> Change your setting for gnus-message-archive-group from "misc-mail"
>> to "nnml:outgoing" (with "nnml:").  The value for
>> gnus-message-archive-method does not really matter -- just leave it
>> as it is.
>
> Am I correct in understanding that the prefix "nnml:" effectively
> overrides the value of gnus-message-archive-method?

That's right.

kai
-- 
Abort this operation?   [OK]  [Cancel]



      reply	other threads:[~2001-09-28 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28 11:09 Joe Wells
2001-09-28 13:00 ` Kai Großjohann
2001-09-28 13:33   ` Joe Wells
2001-09-28 14:33     ` Kai Großjohann [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=vaf1ykr75ct.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).