Jason L Tibbitts III writes:
> [If this IS a Majordomo problem, please remove list-managers from the To:
> and CC: headers. Please.]
Done...
> I think the
> problem happens when the message starts with an indented line. Majordomo
> seems to lose all of the lines that are indented. I have one list member
> whose mailer is so broken that it sends _all_ lines indented; messages from
> this person always come out blank even though they get to resend just
> fine.
This sounds similar to a problem I had with messages losing lines
(and getting all messed up with text defined in message_headers).
Not only was the original message indented in the body, but the
supposedly empty line seperating headers from text actually
contained a space. I made the appended fix to resend to deal with
this. (Line numbers may be off by a few.) It's possible this *may*
fix your problem too.
1 - ensure we always emit a newline at the end of message_headers
2 - though we recognise a line with only whitespace as end of
headers, force it to be an *empty* line on output.
Hope this helps
Scott Larnach
---- cut here --------------------------------------------------
*** resend.old Thu Mar 28 11:37:40 1996
--- resend Thu Mar 28 11:37:47 1996
***************
*** 169,180 ****
if ( $config_opts{$opt_l,"message_headers"} ne '' ) {
local($headers) = &config'substitute_values (
$config_opts{$opt_l,"message_headers"}, $opt_l);
! $headers =~ s/\001/\n/g;
print OUT $headers;
}
$in_hdr = 0;
! print OUT $_;
# print out front matter
if ( $config_opts{$opt_l,"message_fronter"} ne '' ) {
--- 169,180 ----
if ( $config_opts{$opt_l,"message_headers"} ne '' ) {
local($headers) = &config'substitute_values (
$config_opts{$opt_l,"message_headers"}, $opt_l);
! $headers =~ s/\001|$/\n/g;
print OUT $headers;
}
$in_hdr = 0;
! print OUT "\n";
# print out front matter
if ( $config_opts{$opt_l,"message_fronter"} ne '' ) {
---- cut here --------------------------------------------------
|
|
