From: Pieter Wenk <pwenk@urbanet.ch>
Subject: Re: nnspool: Reference header too long (article not posted)
Date: Fri, 31 Dec 1999 00:47:58 +0100 [thread overview]
Message-ID: <19991231004758.B3075@sre-4-139.urbanet.ch> (raw)
In-Reply-To: <m3wvpwm8a9.fsf@acm.org>
On jeu, 30 déc 1999, Alan Shutko wrote:
>Pieter Wenk <pwenk@urbanet.ch> writes:
>
>> This nifty "great" feature: Reference header too long (article not posted),
>> is really able motivating to some frank, harsh well known words.
>
>Well, it seems the consensus is it's not Gnus's fault, it's your
>newsserver's fault. You could always try complaining there. It
>probably wouldn't help. 8^)
>
>It seems Gnus already tries to keep Reference headers below some
>limits. Those aren't currently configurable, but you could change
>message-shorten-references in message.el to have a lower maxcount.
>Someone with more time might change that to be configurable...
I am using leafnode, latest version which is 1.9.7...
Strange..with my older gnus version, I had "NOT" these
problems...perhaps somebody is able to tell me why,
this upgraded 5.8.2 Version is behaving like this ?
Regards
--
/ / (_)____ __ ____ __
Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland
/____/_/_//_/\_,_/ /_/\_\
next prev parent reply other threads:[~1999-12-30 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-30 20:44 Pieter Wenk
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 [this message]
-- 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=19991231004758.B3075@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).