Unknown attribute: max_message_size
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.
What to do?
I have Maxking mailman-docker but can easily copy files into the image if necessary.
Thor
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
What to do?
I have Maxking mailman-docker but can easily copy files into the image if necessary.
Are you sure you have up to date images?
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
Hi,
just encountering the same problem in postorious, how are the chances of a fix being released soon? Otherwise, we will try the workaround mentioned here: https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24f...
Regards, Alex
Am 06.12.17 um 20:03 schrieb Abhilash Raj:
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
rollingtags 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/
-- Mit freundlichen Grüßen, Alexander Klotz
(redaktion kulturserver)
mailto:alexk@kulturserver.de
Stiftung kulturserver.de gGmbH
Lothringerstraße 23 D-52062 Aachen http://ggmbh.kulturserver.de
Geschäftsführer: Wolfgang Knauff
Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 Umsatzsteuer-Identifikations-Nr.:DE DE 230868040
On 05/28/2018 08:05 AM, Alexander Klotz wrote:
Hi,
just encountering the same problem in postorious, how are the chances of a fix being released soon?
It is fixed in the current branch heads. We plan a new release very soon. There are still a few things we want to get in the release, so it's not quite ready yet, but we're working on it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
unfortunately we still have problems configuring a list so that it allows a message size larger than 40 KB. Neither the workaround described here: https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24f... (required was already set to false) nor this docker setup by yova https://gitlab.com/mailman/postorius/issues/246 worked. Are there any other options we could try?
Thanks!
Regards, Alex Klotz
(CultureBase editorial staff)
Am 28.05.18 um 17:16 schrieb Mark Sapiro:
On 05/28/2018 08:05 AM, Alexander Klotz wrote:
Hi,
just encountering the same problem in postorious, how are the chances of a fix being released soon?
It is fixed in the current branch heads. We plan a new release very soon. There are still a few things we want to get in the release, so it's not quite ready yet, but we're working on it.
On 06/21/2018 03:29 AM, Alexander Klotz wrote:
Hi,
unfortunately we still have problems configuring a list so that it allows a message size larger than 40 KB. Neither the workaround described here: https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24f... (required was already set to false) nor this docker setup by yova https://gitlab.com/mailman/postorius/issues/246 worked. Are there any other options we could try?
Use 'mailman shell'. I.e. 'mailman shell -l listname@domain' and set m.max_message_size = N where N is the number of KB you want.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Thor,
On Wed, Dec 6, 2017, at 02: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.
I have opened a new issue for this, turns out this was fixed but isn't a part of the 3.1.1 bugfix release of COre.
https://gitlab.com/mailman/postorius/issues/246
What to do?
I have Maxking mailman-docker but can easily copy files into the image if necessary.
Thor
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in
participants (5)
-
Abhilash Raj -
Alexander Klotz -
Mark Sapiro -
Simon Hanna -
Thor Atle Rustad