Message320905
| Author | r.david.murray |
|---|---|
| Recipients | Douglas Thor, barry, r.david.murray |
| Date | 2018-07-02.18:18:12 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1530555492.16.0.56676864532.issue34025@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The default maximum line length is indeed supposed to be 78 (characters..and I can't now remember whether I implemented it in terms of characters or octets), that's per RFC 5322. What is wrong is that content encoded text is supposed to use a max line length of 76. A "simple" fix would be to hardcode the maximum line length at 76 when doing content encoding. An arguably better fix would be a separate policy control for the encoded text line length. The former can be the bug fix, but it would be nice to have the latter as an enhancement. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-07-02 18:18:12 | r.david.murray | set | recipients: + r.david.murray, barry, Douglas Thor |
| 2018-07-02 18:18:12 | r.david.murray | set | messageid: <1530555492.16.0.56676864532.issue34025@psf.upfronthosting.co.za> |
| 2018-07-02 18:18:12 | r.david.murray | link | issue34025 messages |
| 2018-07-02 18:18:12 | r.david.murray | create | |