- allura still supports python 3.6 so `from __future__ import annotations` won't work ([added in 3.7](https://docs.python.org/3/library/__future__.html)). I believe the Apache jenkins build uses 3.6 and will error on that. - that said, `email.message` is available in 3.6 so can be imported & used without any `__future__` stuff - can we keep MAX_MAIL_LINE_OCTETS at 990. that seems more conservative and safe since http://www.jebriggs.com/blog/2010/07/smtp-maximum-line-lengths/ indicates some email servers have a limit of 990 - would be nice to have the commit message start with this ticket number: `[#8404] ...`
--- ** [tickets:#8404] SMTP maximum allowed line length (part 2)** **Status:** open **Milestone:** unreleased **Created:** Thu Dec 16, 2021 05:30 PM UTC by Dillon Walls **Last Updated:** Thu Dec 16, 2021 05:30 PM UTC **Owner:** nobody There is a [previous ticket](https://forge-allura.apache.org/p/allura/tickets/8241/) which addressed this, but apparently the problem lingers... A sourceforge user noticed the problem. I dug into it, and the problem lies with the email headers, not the body. Due to our reply-thread emails, the References email header can be quite long. This was tripping SMTP's line length limit. I have pushed some fixes to `dw/smtp_line_length` --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
