Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: Inews and long headers (Julien ?LIE)
2. Re: Inews and long headers (Kamil =?iso-8859-2?Q?Jo=F1ca?=)
3. Re: Inews and long headers (Julien ?LIE)
4. Re: Inews and long headers (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Sat, 8 Jul 2017 14:50:14 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Inews and long headers
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Kamil,
>> I suggest the following patch for inews. Do you happen to have
>> the possibility to test it and report if it solves your issue?
>
> It looks it is better now.
OK, thanks for having tested.
> Now I have problem with lines
>
> --8<---------------cut here---------------start------------->8---
> Header-name:
> aaaaa
> --8<---------------cut here---------------end--------------->8---
> but I am not sure if this is properly formatted line.
Header-name:\r\n aaaaa\r\n
is malformatted. A space is needed after the colon.
FYI, I quote Appendix C of RFC 5536:
This appendix lists the differences between the syntax allowed by the
Netnews article format (this document) as compared to the Internet
Message Format, as specified in [RFC5322].
The Netnews article format is a strict subset of the Internet Message
Format; all Netnews articles conform to the syntax of [RFC5322].
The following restrictions are important:
o A SP (space) is REQUIRED after the colon (':') following a header
field name.
o A slightly restricted syntax of <msg-id> (to be used by the
Message-ID, References, and Supersedes header fields) is defined.
o The length of a <msg-id> MUST NOT exceed 250 octets.
o Comments are not allowed in the Message-ID header field.
o The CFWS between <msg-id>s in the References header field is not
optional.
o It is legal for a parser to reject obsolete syntax, except that:
* The <obs-phrase> construct MUST be accepted.
* The obsolete <zone> "GMT" MUST be accepted within a
<date-time>.
o Every line of a header field body (including the first and any
that are subsequently folded) MUST contain at least one non-
whitespace character. This means that an empty header field body
is illegal.
--
Julien ?LIE
? O fortunatos nimium, sua si bona norint, agricolas. ? (Virgile)
------------------------------
Message: 2
Date: Sat, 08 Jul 2017 16:05:49 +0200
From: [email protected] (Kamil =?iso-8859-2?Q?Jo=F1ca?=)
To: [email protected]
Subject: Re: Inews and long headers
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-2
Julien ?LIE <[email protected]> writes:
> Hi Kamil,
>
>>> I suggest the following patch for inews. Do you happen to have
>>> the possibility to test it and report if it solves your issue?
>>
>> It looks it is better now.
>
> OK, thanks for having tested.
>
>
>> Now I have problem with lines
>>
>> --8<---------------cut here---------------start------------->8---
>> Header-name:
>> aaaaa
>> --8<---------------cut here---------------end--------------->8---
>> but I am not sure if this is properly formatted line.
>
> Header-name:\r\n aaaaa\r\n
> is malformatted. A space is needed after the colon.
>
Roma locuta, causa finita. :)
Thanks for clarification.
KJ
--
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Law stands mute in the midst of arms.
-- Marcus Tullius Cicero
------------------------------
Message: 3
Date: Sat, 8 Jul 2017 17:04:04 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Inews and long headers
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Kamil,
>>> Now I have problem with lines
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> Header-name:
>>> aaaaa
>>> --8<---------------cut here---------------end--------------->8---
>>> but I am not sure if this is properly formatted line.
>>
>> Header-name:\r\n aaaaa\r\n
>> is malformatted. A space is needed after the colon.
>
> Roma locuta, causa finita. :)
It is not a fatality :)
This format is not allowed at injection time (inews), which does not
mean it cannot be fixed at posting time (mailpost).
mailpost should convert mails to valid Netnews articles. It already
adds a space after the colon, so I believe the issue in your above
example is in fact an empty header line (the first line, without any
non-whitespace chars in header body).
Something like this could work. (Not tested.)
--- mailpost.in (r?vision 10159)
+++ mailpost.in (copie de travail)
@@ -224,6 +224,11 @@
next;
}
+ # Remove empty header lines within header body.
+ s/\n[ \t]+\n/\n/g; # middle
+ s/\n[ \t]+$//; # last line
+ s/^([^:]+):[ \t]+\n/$1/; # first line
+
if (/^($exclude):\s*/sio) {
$real_news_hdrs .= "$_\n";
next;
Of course, if you have a better patch, do not hesitate to share.
--
Julien ?LIE
? Je n'aime pas faire du char-stop ! ? (Ast?rix)
------------------------------
Message: 4
Date: Sat, 8 Jul 2017 17:21:45 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Inews and long headers
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
> + # Remove empty header lines within header body.
> + s/\n[ \t]+\n/\n/g; # middle
> + s/\n[ \t]+$//; # last line
> + s/^([^:]+):[ \t]+\n/$1/; # first line
s/^([^:]+:[ \t]+)\n/$1/;
with wider scope for $1 will be far better!
--
Julien ?LIE
? Je n'aime pas faire du char-stop ! ? (Ast?rix)
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 96, Issue 3
******************************************
