From: Steven L Baur <steve@miranova.com>
Subject: Re: Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch))
Date: 15 May 1996 15:25:59 -0700 [thread overview]
Message-ID: <m2pw853760.fsf@deanna.miranova.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 14 May 1996 19:07:23 -0700
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
Lars> "Sudish Joseph" <sudish@VNET.IBM.COM> writes:
>> Per Abrahamsen <abraham@dina.kvl.dk> writes:
>> > I'd say massage the subject as much as you want for presentation
>> > purposes in the article and subject buffers, but when you generate a
>> > reply or followup, make the default subject line be in strict
>> > compliance with The Seal and with Son-of-RFC1036.
>>
>> Amen.
Lars> Indeedy. Just because we feel it's totally neat-o-keano to rewrite
Lars> "Re[145]: re^4: WORD TOTALLY RO=?ISO-X-666?ABNSAGHS?=OOLZ!!!!!!!!! -reply"
Lars> to "Re: Word totally sucks!", that doesn't mean that everybody will
Lars> agree.
That's more rewriting than I really had in mind:
Subject: Re: WORD TOTALLY RO=?ISO-X-666?ABNSAGHS?=OOLZ!!!!!!!!!
X-Original-Subject: Re[145]: re^4: WORD TOTALLY RO=?ISO-X-666?ABNSAGHS?=OOLZ!!!!!!!!! -reply
X-Gnus-GNKSA-Warning: You've got a bogus mailer, dude. Fix it!
Lars> By sticking totally to The Seal and RFC1036 we give those
Lars> standards greater legitimacy and have a greater chance of
Lars> getting writers of non-compliant software to get their acts
Lars> together. They will then not be able to say "Oh, but that thing
Lars> also rewrites Subject headers, so we can do to." No. We comply
Lars> with the standards.
Lars> If users decide to rewrite Subject headers manually -- that's up to
Lars> them.
At some point we're going to need an adjunct to Gnus with
user-contributed neat-o-keano, but unofficial software.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
next prev parent reply other threads:[~1996-05-15 22:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-09 18:21 [sgnus v0.83] Followup Subject: typos in message.el (patch) Steven L Baur
1996-05-09 21:58 ` Lars Magne Ingebrigtsen
1996-05-10 1:50 ` Raja R Harinath
1996-05-10 3:29 ` Steven L Baur
1996-05-11 0:37 ` Lars Magne Ingebrigtsen
1996-05-14 4:41 ` Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch)) Jason L Tibbitts III
1996-05-14 12:25 ` Per Abrahamsen
1996-05-14 14:32 ` Richard Pieri
1996-05-14 15:25 ` Per Abrahamsen
1996-05-14 17:28 ` Richard Pieri
1996-05-14 18:44 ` Sudish Joseph
1996-05-15 2:07 ` Lars Magne Ingebrigtsen
1996-05-15 4:31 ` Greg Stark
1996-05-15 14:10 ` Sudish Joseph
1996-05-15 21:53 ` Edward J. Sabol
1996-05-15 22:25 ` Steven L Baur [this message]
1996-05-15 3:15 ` Greg Stark
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=m2pw853760.fsf@deanna.miranova.com \
--to=steve@miranova.com \
/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).