On Tue, 29 Sep 1998 18:16:48 +0300, Liviu Daia
<daia(_at_)stoilow(_dot_)imar(_dot_)ro>
wrote:
On 29 September 1998, Jari Aalto+list.procmail
<jari(_dot_)aalto(_at_)poboxes(_dot_)com>
wrote:
|Tue 1998-09-29 Liviu Daia <daia(_at_)stoilow(_dot_)imar(_dot_)ro>
list.procmail
| MIME-compliant don't have much use for it. Moreover, it should only
(Off the list, I think we agreed that Content-Length doesn't have
anything with MIME to do, and that this discussion doesn't belong on
the Procmail list anymore.)
| may confuse the [Content-Length]-_aware_ MUAs that (naively :-))
| use it as a hint for parsing mbox mailboxes into messages.
After I saw Jamie Zawinsky's Content-Lenth header discussion in
1996-05-17 comp.mail.headers (included in pm-tips.txt), I agreed
with him that it was utterly useless and too error prone. E.g. SUN's
mailtool uses C-L and it breaks if C-L is wrong.
Yes. Fortunately, it can be fixed with procmail:
:0 Bfh
* $ H ?? ^Content-Length:
* 1^1 .
* 1^1 ^.*$
* -1^0
| formail -I "Content-Length: $="
Actually, it's even simpler than that. Without the -Y flag, Procmail
will fix any wrong Content-Length headers. Just run any messages
through Procmail. If you want to force them to have a Content-Length
(which Procmail subsequently fixes), add one with formail:
:0fhw # yeah, note the w flag (or isn't it required here?)
* ! ^Content-Length:
| formail -I"Content-Length: 00000000"
The standard caveat here is to make the field wide enough to allow
Procmail to fix the number without making the physical line longer.
/* era */
--
Bot Bait: It shouldn't even matter whether (`') Just (`') http://www.iki
I am a resident of the State of Washington \/ Married! \/ .fi/~era/