Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
Subject: Re: nnspool: Reference header too long (article not posted)
Date: 30 Dec 1999 13:22:46 -0800	[thread overview]
Message-ID: <ylso0k3yzd.fsf@windlord.stanford.edu> (raw)
In-Reply-To: dsg@mitre.org's message of "30 Dec 1999 16:01:12 -0500"

David S Goldberg <dsg@mitre.org> writes:

> As others have already pointed out, that message appears to be coming
> from your news software, not gnus itself.  It seems the easiest thing
> would be to pare down the references header when you edit your message.
> You could probably write a hook to do so, or maybe modify/advise
> message-shorten-references with a smaller limit.  Or get better news
> software.

If the problem is that the References header is over 1024 characters on a
single line, you definitely don't want "better" news software where better
is defined as news software that will post that, since your article would
end up getting dropped at other sites.

A better solution would be to set message-cater-to-broken-inn to nil so
that Gnus will fold the References header.  Anyone running that old of a
version of INN should upgrade anyway.

-- 
Russ Allbery (rra@stanford.edu)         <URL:http://www.eyrie.org/~eagle/>



  reply	other threads:[~1999-12-30 21:22 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 [this message]
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=ylso0k3yzd.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    /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).