From: Ketanu <ketanu@wanadoo.fr>
Subject: Re: posting to a specific backend [POSTING][BACKEND]
Date: 13 May 2002 19:33:36 +0200 [thread overview]
Message-ID: <87r8kgx89b.fsf@ketanu.dyndns.org> (raw)
In-Reply-To: <vafit6ytazz.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Ketanu <ketanu@wanadoo.fr> writes:
>
> > Following what is done by gnus for article archiving
> > [(Gnus)Article Archiving::], i guessed a method after the Gcc header line that
> > may say "Gcc: nnfolder+sent:sent-misc", thus i tried to post with
> > "Newsgroups: nnfolder+notes:todays-notes" that failed.
>
> I have augmented nnml such that it groks Newsgroups headers. This
> can be done very easily for nnfolder, too.
>
> Would you like to try it and compare with the Gcc solution to see
> which one you like better?
>
> After you have allowed Newsgroups headers for nnfolder, you'd use
> this header: Newsgroups: todays-notes
How can i do this « allowing » ?
> And then you hit C-u 0 C-c C-c and choose the nnfolder:notes server
> for sending.
>
> If gnus-post-method is `current' (which is the default), you can also
> do `C-u a' over the nnfolder+notes:todays-notes group in the *Group*
> buffer, and then you just hit `C-c C-c' for sending.
>
> Here is the nnml.el modification:
>
> (deffoo nnml-request-post (&optional server)
> (nnmail-do-request-post 'nnml-request-accept-article server))
Alas, i did not find this modification to work along with
gnus 5.9.0 because the nnmail-do-request-post is empty variable,
and replacing (that's dumb, but i tried) it by nnmail-request-post
do not work much more (wrong number of arguments), and i have no idea for a
fix.
--
Ketanu
parent reply other threads:[~2002-05-13 17:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <vafit6ytazz.fsf@lucy.cs.uni-dortmund.de>]
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=87r8kgx89b.fsf@ketanu.dyndns.org \
--to=ketanu@wanadoo.fr \
/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).