The message is larger than the 40 KB maximum size
Hi,
I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped.
Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087
On 2020-09-18 15:32, Mohsen Masoudfar wrote:
Hi,
I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped.
Assuming that this works roughly the same in mm3 as it does in mm2, you can set max_message_size in your list configuration. It defaults to 40; units are KB.
-- Phil Stracchino Babylon Communications phils@caerllewys.net phil@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
On 9/18/20 12:48 PM, Phil Stracchino wrote:
On 2020-09-18 15:32, Mohsen Masoudfar wrote:
Hi,
I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped.
Assuming that this works roughly the same in mm3 as it does in mm2, you can set max_message_size in your list configuration. It defaults to 40; units are KB.
Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear".
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
Thank you Mark and Phil for your help.
It seems I got stuck!
1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size"
2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40
I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size
3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works.
4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/
Thanks Mohsen
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Friday, September 18, 2020 4:00 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size
[EXTERNAL EMAIL]
On 9/18/20 12:48 PM, Phil Stracchino wrote:
On 2020-09-18 15:32, Mohsen Masoudfar wrote:
Hi,
I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped.
Assuming that this works roughly the same in mm3 as it does in mm2, you can set max_message_size in your list configuration. It defaults to 40; units are KB.
Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear".
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
It seems something is fundamentally wrong with Hyperkitty:
From /var/log/mailman3/mailman.log
49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 50 <h1>Authorization Required</h1></body></html> (401) 51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 52 <h1>Authorization Required</h1></body></html> (401) 53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 54 <h1>Authorization Required</h1></body></html> (401) 55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN"> 56 <html><head> 57 <title>503 Service Unavailable</title> 58 </head><body> 59 <h1>Service Unavailable</h1> 60 <p>The server is temporarily unable to service your 61 request due to maintenance downtime or capacity 62 problems. Please try again later.</p> 63 <hr> 64 <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> 65 </body></html> 66 (503) 67 Sep 21 21:49:26 2020 (24918) Exception in the HyperKitty archiver: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 68 <html><head> 69 <title>503 Service Unavailable</title> 70 </head><body> 71 <h1>Service Unavailable</h1> 72 <p>The server is temporarily unable to service your 73 request due to maintenance downtime or capacity 74 problems. Please try again later.</p> 75 <hr> 76 <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> 77 </body></html> 78 Sep 21 21:49:26 2020 (24918) Traceback (most recent call last): 79 File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message 80 url = self._send_message(mlist, msg) 81 File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message 82 raise ValueError(result.text) 83 ValueError: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 84 <html><head> 85 <title>503 Service Unavailable</title> 86 </head><body> 87 <h1>Service Unavailable</h1> 88 <p>The server is temporarily unable to service your 89 request due to maintenance downtime or capacity 90 problems. Please try again later.</p>
Thanks Mohsen
-----Original Message----- From: Mohsen Masoudfar <mmasoudf@aaas.org> Sent: Monday, September 21, 2020 12:24 PM To: Mark Sapiro <mark@msapiro.net>; mailman-users@mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size
[EXTERNAL EMAIL]
Hi Mark,
Thank you Mark and Phil for your help.
It seems I got stuck!
1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size"
2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40
I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size
3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works.
4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/
Thanks Mohsen
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Friday, September 18, 2020 4:00 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size
[EXTERNAL EMAIL]
On 9/18/20 12:48 PM, Phil Stracchino wrote:
On 2020-09-18 15:32, Mohsen Masoudfar wrote:
Hi,
I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped.
Assuming that this works roughly the same in mm3 as it does in mm2, you can set max_message_size in your list configuration. It defaults to 40; units are KB.
Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear".
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
On 9/21/20 3:01 PM, Mohsen Masoudfar wrote:
It seems something is fundamentally wrong with Hyperkitty:
From /var/log/mailman3/mailman.log
49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 50 <h1>Authorization Required</h1></body></html> (401) 51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 52 <h1>Authorization Required</h1></body></html> (401) 53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 54 <h1>Authorization Required</h1></body></html> (401) 55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN"> ...
I doubt this has anything to do with the missing approved message, but what's in you mailman-hyperkitty.cfg file for api_key and does that match your settings_local.py setting for MAILMAN_ARCHIVER_KEY except for being quoted in settings_local.py and not in mailman-hyperkitty.cfg.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 9/21/20 9:23 AM, Mohsen Masoudfar wrote:
1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size"
This is <https://gitlab.com/mailman/mailman/-/issues/417> fixed by <https://gitlab.com/mailman/mailman/-/merge_requests/329> in Mailman core 3.2.0.
Either upgrade Mailman core or set it via mailman shell
2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40
I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size
Changing that file only affects the default setting for new lists. It doesn't affect any existing list.
To change this you can either update Mailman's database to set max_message_size = 0 in the entry for the list in the mailinglist table or do something like
$ /opt/mailman/mm/bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list
m.max_message_size 40 m.max_message_size = 0 commit()
3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works.
4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/
OK, but what if anything is in Mailman's mailman.log?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you so much Mark. I appreciate your help! I dropped the list and recreated it, the default value worked for the new list. Using Mailman shell is very helpful. I checked the mailman.log and found the issue.
Thanks Mohsen
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Monday, September 21, 2020 9:42 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size
[EXTERNAL EMAIL]
On 9/21/20 9:23 AM, Mohsen Masoudfar wrote:
1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size"
This is <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Fmailman%2Fmailman%2F-%2Fissues%2F417&data=01%7C01%7Cmmasoudf%40aaas.org%7Cb4f23b106bf343d57ac908d85e98c830%7C2eebd8ff9ed140f0a15638e5dfb3bc56%7C0&sdata=2T3IrXVwbwqARMVMHaV%2Fi%2B0qkN7Z849%2F0Vq5ztmNwAQ%3D&reserved=0> fixed by <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Fmailman%2Fmailman%2F-%2Fmerge_requests%2F329&data=01%7C01%7Cmmasoudf%40aaas.org%7Cb4f23b106bf343d57ac908d85e98c830%7C2eebd8ff9ed140f0a15638e5dfb3bc56%7C0&sdata=5hJnhhpsPzSDPBZkDR%2B2e2a4sav74LOIpHQxTbnUavE%3D&reserved=0> in Mailman core 3.2.0.
Either upgrade Mailman core or set it via mailman shell
2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40
I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size
Changing that file only affects the default setting for new lists. It doesn't affect any existing list.
To change this you can either update Mailman's database to set max_message_size = 0 in the entry for the list in the mailinglist table or do something like
$ /opt/mailman/mm/bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list
m.max_message_size 40 m.max_message_size = 0 commit()
3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works.
4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/
out/ pipeline/ retry/ shunt/ virgin/
OK, but what if anything is in Mailman's mailman.log?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
On 9/22/20 11:16 AM, Mohsen Masoudfar wrote:
I checked the mailman.log and found the issue.
I assume you mean why the message disappeared after approval. If so, what was the issue? I.e., was it something unique to your installation such as permissions or configuration, or was it something we need to fix?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 9/18/20 12:32 PM, Mohsen Masoudfar wrote:
Hi,
I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped.
Is the message in Mailman's var/queue/shunt queue? Is there an error in var/log/mailman.log?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro -
Mohsen Masoudfar -
Phil Stracchino