From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Subject: Re: OT Length of Header-Lines?
Date: 30 Oct 1998 10:44:50 -0600 [thread overview]
Message-ID: <ufak91i2e4d.fsf@sina.hpc.uh.edu> (raw)
In-Reply-To: Karl Kleinpaste's message of "29 Oct 1998 16:06:39 -500"
>>>>> "KK" == Karl Kleinpaste <karl@jprc.com> writes:
KK> On the one hand, this is an utterly stupid question to have to
KK> answer. Any "new" mail-serving program which imposes such severe line
KK> length limits of that sort has, in the very first analysis, violated
KK> the Robustness Principle.
I'll add for funnies that, as the owner of this list, I see bunches of fun
bounces due to this. Folks at cs.cmu.edu, what crappy mailer are you
running there that _bounces_ mail if a header is over 510 characters?
It's off topic, but I'll also add that I get a lot of bounces doe to
non-ASCII characters in the headers. Yes, my mailing list manager should
encode them as it sees them (though what character set to use is a mystery)
but whatever is generating them (which is probably Gnus) shouldn't be doing
so. The incidence of this has gone up with the advent of pgnus.
- J<
next prev parent reply other threads:[~1998-10-30 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-29 20:13 Robert Epprecht
1998-10-29 21:06 ` Karl Kleinpaste
1998-10-30 8:24 ` Robert Epprecht
1998-10-30 16:44 ` Jason L Tibbitts III [this message]
1998-10-30 18:20 ` Michael Welsh Duggan
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=ufak91i2e4d.fsf@sina.hpc.uh.edu \
--to=tibbs@hpc.uh.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).