Re: (no subject)
Peter Occil <[email protected]> Tue, 24 Jul 2018 00:25:38 -0400
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Message-ID | <[email protected]> |
--===============5578793158611390200== Content-Type: multipart/alternative; boundary="_EB6EF9AE-B63D-4D61-8FF3-1618C927DCFB_" --_EB6EF9AE-B63D-4D61-8FF3-1618C927DCFB_ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" I mean from the point of view of a software developer creating a library to= generate email messages. This software developer is not the one who comes= up with values for header fields (such as URLs for List-Unsubscribe header= fields). If the developer's software library is passed a List-Unsubscribe= header field value greater than 998 characters in length (e.g., when a thi= rd-party user uses that library to generate a blank message, then to set th= e List-Unsubscribe header field to such a value, then to generate a finishe= d message), the software developer would then have to make a choice whether= to program that library-- - to reject the user-provided value,=20 - to accept the value and later be required to generate a message with a l= ine exceeding 998 characters or to fold lines to fit that character limit, = or=20 - to take some other error-handling action. --Peter Occil From: John Levine Sent: Tuesday, July 24, 2018 12:13 AM To: [email protected] Cc: [email protected] Subject: Re: [ietf-822] (no subject) In article <[email protected]> you write: >> Plan B: figure out how to make your URLs short enough that your List-Uns= ubscribe >headers are under 998 characters. ... >Plan B is only feasible if the same person provides the URL _and_ writes t= he code to generate the >List-Unsubscribe header field (or any other list header field) for the cor= responding message; not so if a >software library generates a message containing the value of a List-Unsubs= cribe (or other) header field >provided by a (third-party) user that, while otherwise syntactically valid= , could exceed 998 characters in >length. .... You lost me here. Is there some force that requires you to pass giant URLs to List-Unsubscribe? If you want to interoperate, use reasonably short URLs. This should not be rocket science. R's, John --_EB6EF9AE-B63D-4D61-8FF3-1618C927DCFB_ 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>I mean from the point of view of a s= oftware developer creating a library to generate email messages.=C2=A0 This= software developer is not the one who comes up with values for header fiel= ds (such as URLs for List-Unsubscribe header fields).=C2=A0 If the develope= r's software library is passed a List-Unsubscribe header field value greate= r than 998 characters in length (e.g., when a third-party user uses that li= brary to generate a blank message, then to set the List-Unsubscribe header = field to such a value, then to generate a finished message), the software d= eveloper would then have to make a choice whether to program that library--= </p><p class=3DMsoNormal> - to reject the user-provided value, </p><p class= =3DMsoNormal>=C2=A0- to accept the value and later be required to generate = a message with a line exceeding 998 characters or to fold lines to fit that= character limit, or </p><p class=3DMsoNormal>=C2=A0- to take some other er= ror-handling action.</p><p class=3DMsoNormal><o:p> </o:p></p><p class= =3DMsoNormal>--Peter Occil</p><p class=3DMsoNormal><o:p> </o:p></p><di= v 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'border:none= ;padding:0in'><b>From: </b><a href=3D"mailto:[email protected]">John Levine</= a><br><b>Sent: </b>Tuesday, July 24, 2018 12:13 AM<br><b>To: </b><a href=3D= "mailto:[email protected]">[email protected]</a><br><b>Cc: </b><a href=3D"m= ailto:[email protected]">[email protected]</a><br><b>Subject: </b>Re: [ie= tf-822] (no subject)</p></div><p class=3DMsoNormal><o:p> </o:p></p><p = class=3DMsoNormal>In article <[email protected]= > you write:</p><p class=3DMsoNormal><o:p> </o:p></p><p class=3DMso= Normal>>> Plan B: figure out how to make your URLs short enough that = your List-Unsubscribe</p><p class=3DMsoNormal>>headers are under 998 cha= racters. ...</p><p class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNor= mal>>Plan B is only feasible if the same person provides the URL _and_ w= rites the code to generate the</p><p class=3DMsoNormal>>List-Unsubscribe= header field (or any other list header field) for the corresponding messag= e; not so if a</p><p class=3DMsoNormal>>software library generates a mes= sage containing the value of a List-Unsubscribe (or other) header field</p>= <p class=3DMsoNormal>>provided by a (third-party) user that, while other= wise syntactically valid, could exceed 998 characters in</p><p class=3DMsoN= ormal>>length. ....</p><p class=3DMsoNormal><o:p> </o:p></p><p clas= s=3DMsoNormal>You lost me here.=C2=A0 Is there some force that requires you= to pass giant</p><p class=3DMsoNormal>URLs to List-Unsubscribe?=C2=A0 If y= ou want to interoperate, use reasonably</p><p class=3DMsoNormal>short URLs.= =C2=A0 This should not be rocket science.</p><p class=3DMsoNormal><o:p>&nbs= p;</o:p></p><p class=3DMsoNormal>R's,</p><p class=3DMsoNormal>John</p><p cl= ass=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal><o:p> </o:p>= </p><p class=3DMsoNormal><o:p> </o:p></p></div></body></html>= --_EB6EF9AE-B63D-4D61-8FF3-1618C927DCFB_-- --===============5578793158611390200== 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 --===============5578793158611390200==--