From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: follow-up for usenet and email
Date: Thu, 14 Aug 2003 22:20:40 +0200 [thread overview]
Message-ID: <m3r83o2dpj.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <86he4kov09.fsf@doze.rijnh.nl>
Jochen Küpper <usenet@jochen-kuepper.de> writes:
> Assuming you got my question right:) Anyway: What I wanted to achieve
> is that my message was posted to the newsgroup gnu.Emacs.gnus and the
> mailing list bbdb-info@lists.sourceforge.net *and* replies
> automagically being send only to bbdb-info@lists.sourceforge.net.
There's really no way of saying to newsreaders "if you want to follow
up to this message, send a mail to this address" in the headers...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-08-14 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86r83s8kgd.fsf@doze.rijnh.nl>
2003-08-14 18:25 ` Lars Magne Ingebrigtsen
[not found] ` <86he4kov09.fsf@doze.rijnh.nl>
2003-08-14 20:20 ` Lars Magne Ingebrigtsen [this message]
[not found] ` <iMeowbot-71DA98.16271814082003@news.verizon.net>
2003-08-14 20:30 ` Lars Magne Ingebrigtsen
2003-08-14 20:43 ` Jochen Küpper
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=m3r83o2dpj.fsf@quimbies.gnus.org \
--to=larsi@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).