Gnus development mailing list
 help / color / mirror / Atom feed
From: jason@mastaler.com (Jason R. Mastaler)
Cc: ding@gnus.org
Subject: Re: Splitting of ding@ifi
Date: 03 Apr 1997 12:51:16 -0500	[thread overview]
Message-ID: <x7encsm1uz.fsf@mastaler.com> (raw)
In-Reply-To: Hrvoje Niksic's message of 03 Apr 1997 18:45:56 +0200

Hrvoje Niksic <hniksic@srce.hr> writes:

> This isn't really relevant to the list (well, partially), but how do
> you people split the messages meant for this list?  I mean, it doesn't
> seem to come with a handy header like `X-Mailing-List', and it leaves
> the `Sender' intact.
> 
> Currently, my fancy mail splitting entry for ding list looks like
> this:
> 
>      ("received" "ding@ifi" "ding.discuss")

In any case the above isn't a good idea since list submissions can now
be made to 'ding@gnus.org'.


  parent reply	other threads:[~1997-04-03 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-03 16:45 Hrvoje Niksic
1997-04-03 17:10 ` Per Abrahamsen
1997-04-03 17:26   ` Hrvoje Niksic
1997-04-03 17:44     ` Per Abrahamsen
1997-04-03 17:51 ` Jason R. Mastaler [this message]
1997-04-03 18:48 ` Dewey M. Sasser
1997-04-03 18:55 ` David Moore

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=x7encsm1uz.fsf@mastaler.com \
    --to=jason@mastaler.com \
    --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).