From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Sending via smtp-mail slow
Date: Tue, 09 Jul 2002 10:15:38 +0200 [thread overview]
Message-ID: <vaf65zp8ggl.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3sn2u7xtu.fsf@lugabout.jhcloos.org> ("James H. Cloos Jr."'s message of "08 Jul 2002 16:45:49 -0400")
"James H. Cloos Jr." <cloos@jhcloos.com> writes:
> Any tips on converting that to an nnml group?
If you want Gnus to copy to a group instead of writing to a file, you
have to use the Gcc header instead of the Fcc header. In a nutshell,
"Fcc: /some/file" writes to a file whereas "Gcc: nnml:some.group"
writes to a group.
If you have an nnml backend already, it's as simple as using `G m' to
create a group there and to change the Fcc header into a Gcc header.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
prev parent reply other threads:[~2002-07-09 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-28 10:06 Frank Schmitt
2002-07-08 16:37 ` Jesper Harder
2002-07-08 17:59 ` Josh Huber
2002-07-08 20:45 ` James H. Cloos Jr.
2002-07-09 8:15 ` 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=vaf65zp8ggl.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).