I may make this into a patch later To: mailman-users@python.org Subject: max_message_size description suggested extension From: "Julian H. Stacey" Organization: http://www.berklix.com/jhs http://StolenVotes.uk User-agent: EXMH on FreeBSD http://www.berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ Fcc: sent Hi all, On my mailman server I have: General Options max_message_size 10K Content filtering collapse_alternatives Yes convert_html_to_plaintext Yes I posted OK to a list with Mime-version: 1.0 Content-type: text/plain; charset="us-ascii" size (stripped of all headers & list footer) 4087 bytes A reply was trapped by Mailman with admin page showing draft reply: Your message was too big; please trim it to less than 10 KB in size. The sender had used: User-Agent: Roundcube Webmail/1.3.7 Content-Type: multipart/alternative; Sender had only added maybe a K or so of text, but I presume her adding the bloater of HTML via multipart/alternative caused her to be caught. If that supposition is correct ? Moving the size checking to after stripping would be nice, ( I dont care how much discardable HTML the server receives from an individual, but I do care max size of messages server stores in archive, & sends to all on list) but moving the count would be work. An easy quick fix would be to extend the description of max_message_size to inform admins the effect of the limit can be variant, eg extend From Maximum length in kilobytes (KB) of a message body. To Maximum length in kilobytes (KB) of a message body, (counting all bulk in multipart/alternative [before that bulk may later be trimmed by collapse_alternatives &/or convert_html_to_plaintext]). Comments ? Cheers -- Julian H. Stacey, Consultant Systems Engineer, BSD Linux http://www.berklix.com/jhs/ ttp://www.berklix.org/corona/#masks Tie 2 handkerchiefs or 1 pillow case. Jobs & economy hit by Corona to be hit again by Crash Brexit 31st Dec. 2020