From: Pieter Wenk <pwenk@urbanet.ch>
Subject: Re: nnspool: Reference header too long (article not posted)
Date: Thu, 30 Dec 1999 21:44:04 +0100 [thread overview]
Message-ID: <19991230214404.A2041@sre-4-139.urbanet.ch> (raw)
On jeu, 30 déc 1999, Kai Großjohann wrote:
Hello to all
This nifty "great" feature: Reference header too long (article not posted),
is really able motivating to some frank, harsh well known words.
Every third message (follow ups), I get the above
absolute unpleasant message. Really, that thing can
really go on your ner
How is this to correct....
--
/ / (_)____ __ ____ __
Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland
/____/_/_//_/\_,_/ /_/\_\
next reply other threads:[~1999-12-30 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-30 20:44 Pieter Wenk [this message]
1999-12-30 21:01 ` David S. Goldberg
1999-12-30 21:22 ` Russ Allbery
1999-12-30 23:40 ` Pieter Wenk
1999-12-30 21:24 ` Alan Shutko
1999-12-30 23:47 ` Pieter Wenk
-- strict thread matches above, loose matches on Subject: below --
1999-12-29 19:20 What does this error message mean ? Pieter Wenk
1999-12-29 20:48 ` Kai Großjohann
1999-12-30 6:30 ` Pieter Wenk
1999-12-30 7:50 ` nnspool: Reference header too long (article not posted) Pieter Wenk
1999-12-30 13:08 ` Kai Großjohann
1999-12-30 17:22 ` Pieter Wenk
2000-01-03 10:20 ` Kai Großjohann
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=19991230214404.A2041@sre-4-139.urbanet.ch \
--to=pwenk@urbanet.ch \
/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).