Re: (no subject)
Peter Occil <[email protected]> Tue, 24 Jul 2018 00:33:12 -0400
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Message-ID | <[email protected]> |
--===============1997004559810581869== Content-Type: multipart/alternative; boundary="_B81BD1BB-4E6F-46B8-A16A-0ECC25297C57_" --_B81BD1BB-4E6F-46B8-A16A-0ECC25297C57_ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" So in that case, would a reasonable update to RFC 2369 be to impose a chara= cter limit of 998 characters on list header fields, including the List-Unsu= bscribe header field? --Peter Occil From: John R Levine Sent: Tuesday, July 24, 2018 12:28 AM To: Peter Occil Cc: [email protected] Subject: RE: [ietf-822] (no subject) [=E2=80=A6] If it were my library I'd=20 throw an error if the list-unsubscribe header didn't fit in 998 characters= =20 so the person calling it would know to fix whatever was generating giant=20 URL strings. Regards, John Levine, [email protected], Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly --_B81BD1BB-4E6F-46B8-A16A-0ECC25297C57_ Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc= hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of= fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta ht= tp-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta name= =3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;} ..MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style></head><body lang=3DEN-US link=3Dblue vlink=3D"#954F72"><div cla= ss=3DWordSection1><p class=3DMsoNormal>So in that case, would a reasonable = update to RFC 2369 be to impose a character limit of 998 characters on list= header fields, including the List-Unsubscribe header field?</p><p class=3D= MsoNormal><o:p> </o:p></p><p class=3DMsoNormal>--Peter Occil</p><p cla= ss=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal><o:p> </o:p><= /p><div style=3D'mso-element:para-border-div;border:none;border-top:solid #= E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'borde= r:none;padding:0in'><b>From: </b><a href=3D"mailto:[email protected]">John R = Levine</a><br><b>Sent: </b>Tuesday, July 24, 2018 12:28 AM<br><b>To: </b><a= href=3D"mailto:[email protected]">Peter Occil</a><br><b>Cc: </b><a href= =3D"mailto:[email protected]">[email protected]</a><br><b>Subject: </b>RE: = [ietf-822] (no subject)</p></div><p class=3DMsoNormal><o:p> </o:p></p>= <p class=3DMsoNormal>[=E2=80=A6]=C2=A0 If it were my library I'd </p><p cla= ss=3DMsoNormal>throw an error if the list-unsubscribe header didn't fit in = 998 characters </p><p class=3DMsoNormal>so the person calling it would know= to fix whatever was generating giant </p><p class=3DMsoNormal>URL strings.= </p><p class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>Regards,= </p><p class=3DMsoNormal>John Levine, [email protected], Taughannock Networks= , Trumansburg NY</p><p class=3DMsoNormal>Please consider the environment be= fore reading this e-mail. https://jl.ly</p><p class=3DMsoNormal><o:p> = </o:p></p></div></body></html>= --_B81BD1BB-4E6F-46B8-A16A-0ECC25297C57_-- --===============1997004559810581869== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ietf-822 mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-822 --===============1997004559810581869==--