Stephen J. Turnbull wrote: > Charles Buckley writes: > > I saw a report of this behaviour on this mailing list from the year > > 2000. > If you have an URL for this post, or a timestamp, or even a precise > date, it might be helpful. I can't find it.
It's https://mail.python.org/pipermail/mailman-users/2000-May/004782.html aka https://mail.python.org/pipermail/mailman-users/2000-May/004782.html > > It is still going on now in 2023. One would think that some > > information on how to workaround this bug would have been found > > between now and back then. > I rather doubt it's the same bug (but it's worth comparing). Mailman > 2.0 was in beta in 2000, and pretty much anything from mail composed > by badly written Japanese MUAs to mail composed by the even less > conformant Windows 2000 Outlook betas could crash it. Mailman 2.1 was > released in 2006 with a *lot* of attention to input validation and > exception handling, although more on the email side than the web UI > side. Actually, the first 2.1 release was in December, 2002. See https://wiki.list.org/DOC/7%20Mailman%20history ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
