On Wed, Dec 6, 2017, at 08:25 AM, Simon Hanna wrote:
On 12/06/2017 11:40 AM, Thor Atle Rustad wrote:
If I make changes here: https://example.com/postorius/lists/test2.example.com/settings/message_accep..., I get a warning that the Maximum Message Size field at the bottom is mandatory. However, if I put a number in that field and save, I get "Unknown attribute: max_message_size". That makes sense, since Mark states in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... that max_messages_size is not exposed in REST. It is. https://gitlab.com/mailman/mailman/merge_requests/329
I have added a backport-candidate tag to the MR and will get it out in 3.1.2 release, if that happens.
What to do?
I understand that it might not be the best answer, but rolling tags
for images do have this problem fixed, they are based on Git-heads.
I have Maxking mailman-docker but can easily copy files into the image if necessary.
Are you sure you have up to date images?
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in