Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: References (was: Re: Brian May's `Re: Bugs in PGnus' article jams Gnus)
Date: 10 Dec 1999 10:24:35 +0100	[thread overview]
Message-ID: <rj1z8vkv1o.fsf_-_@zuse.dina.kvl.dk> (raw)
In-Reply-To: Jan Vroonhof's message of "09 Dec 1999 20:18:49 +0100"

Jan Vroonhof <vroonhof@math.ethz.ch> writes:

> Per Abrahamsen <abraham@dina.kvl.dk> writes:
> 
> > PS: What is breaking your references header?
> 
> Our mailserver. Or better the stupid program they have here to forward
> to the real one. I have asked our sysadmins to fix.

It is not the only such broken injection agent in existence.  Maybe
`maxsize' and `cut' below should be made a user options, in order to
allow workarounds?

(defun message-shorten-references (header references)
  "Trim REFERENCES to be less than 31 Message-ID long, and fold them.
If folding is disallowed, also check that the REFERENCES are less
than 988 characters long, and if they are not, trim them until they are."
  (let ((maxcount 31)
	(count 0)
	(cut 6)
	refs)
    ;; ...
    (when message-cater-to-broken-inn
      (let ((maxsize 988)
#


  parent reply	other threads:[~1999-12-10  9:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-07 13:38 Brian May's `Re: Bugs in PGnus' article jams Gnus Hannu Koivisto
1999-12-07 13:52 ` Gunnar Evermann
1999-12-07 14:06   ` Stein Arild Stromme
1999-12-07 14:21   ` Hannu Koivisto
1999-12-07 15:23     ` Laura Conrad
1999-12-07 16:01       ` Per Abrahamsen
1999-12-07 16:16         ` Hrvoje Niksic
1999-12-07 17:09 ` Shenghuo ZHU
1999-12-07 17:45   ` Shenghuo ZHU
1999-12-07 18:18     ` Hannu Koivisto
1999-12-07 18:22       ` Hrvoje Niksic
1999-12-07 18:57         ` Shenghuo ZHU
1999-12-07 19:21         ` Hannu Koivisto
1999-12-07 18:35     ` Toby Speight
1999-12-07 19:02       ` Shenghuo ZHU
1999-12-07 20:01         ` Jan Vroonhof
1999-12-08  9:18           ` Hrvoje Niksic
1999-12-09  0:46     ` Brian May
1999-12-09  1:11       ` Shenghuo ZHU
1999-12-09 13:37         ` Jan Vroonhof
1999-12-09 14:14           ` Per Abrahamsen
1999-12-09 15:46           ` Jan Vroonhof
     [not found]           ` <rj9034mcb2.fsf@zuse.dina.kvl.d <byr9gw2k2u.fsf@bolzano.math.ethz.ch>
1999-12-09 16:08             ` Per Abrahamsen
1999-12-09 19:18           ` Jan Vroonhof
1999-12-09 22:55             ` Shenghuo ZHU
1999-12-10  6:31               ` Lloyd Zusman
1999-12-10  6:42                 ` Shenghuo ZHU
     [not found]           ` <rj9034mcb2.fsf@zuse.dina.kvl.d <byr9gvrkh2.fsf@bolzano.math.ethz.ch>
1999-12-10  8:19             ` Hrvoje Niksic
1999-12-10  9:24             ` Per Abrahamsen [this message]
1999-12-10  9:59               ` References (was: Re: Brian May's `Re: Bugs in PGnus' article jams Gnus) Hrvoje Niksic
1999-12-10 11:52                 ` Per Abrahamsen
1999-12-10 10:24           ` Brian May's `Re: Bugs in PGnus' article jams Gnus Jan Vroonhof
1999-12-10 10:58             ` Broken References (was: Brian May's `Re: Bugs in PGnus' ...) Toby Speight
     [not found]           ` <rj9034mcb2.fsf@zuse.dina.kvl.d <byso1b14bp.fsf@bolzano.math.ethz.ch>
1999-12-10 12:06             ` Brian May's `Re: Bugs in PGnus' article jams Gnus Per Abrahamsen
1999-12-10 14:27           ` Jan Vroonhof
1999-12-10  0:46         ` Kai Großjohann
1999-12-10  3:55           ` Aaron M. Ucko

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=rj1z8vkv1o.fsf_-_@zuse.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).