WEB UI fail to reply and create new thread
Hi,
Alpine Linux is testing mailman3 as system for project mailing lists. We created docker-compose which can be seen here https://gitlab.alpinelinux.org/alpine/infra/compose/mailman
We installed it and run in testing system here https://lists-test.alpinelinux.org/hyperkitty/
Sending mail by mail clients works and mails are sent to subscribers properly. Most other 'things' works but we have problem with reply to posts and creating new threads using web ui. When replying to post with web ui it says that the everything is ok and post is sent but post doesn't arrive to mailing list. Same happens with creating new thread.
Our debug says "KeyError: 'display_fixed'" but we are not sure what should be changed/fixed/set for this problem. Attached is excerpt from debug log.
TIA, mps
On 12/18/20 10:26 AM, Milan P. Stanić wrote:
Sending mail by mail clients works and mails are sent to subscribers properly. Most other 'things' works but we have problem with reply to posts and creating new threads using web ui. When replying to post with web ui it says that the everything is ok and post is sent but post doesn't arrive to mailing list. Same happens with creating new thread.
Our debug says "KeyError: 'display_fixed'" but we are not sure what should be changed/fixed/set for this problem. Attached is excerpt from debug log.
I don't think that exception is the problem. See https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/posting.p... for whit I think might be the issue. I.e., Hyperkitty won't send the mail if
DEBUG = True
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. I also doubt the shown error is the problem as I see more template errors. I have also tried to run the official docker images mailman-docker but im having the same issue.
When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email.
PS emails are send just fine via smtp posting.
On Sat, Dec 19, 2020, at 4:32 PM, Carlo Landmeter wrote:
We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. I also doubt the shown error is the problem as I see more template errors. I have also tried to run the official docker images mailman-docker but im having the same issue.
When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email.
PS emails are send just fine via smtp posting.
Unless I am missing something basic, I don't really know why it doesn't fail on our servers. May have something to do with Django versions or something. I need to work a bit more on verifying it.
This is the line in template1, rendered using this context2 which seems to be causing the issue.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
On Sat, Dec 19, 2020, at 6:29 AM, Abhilash Raj wrote:
On Sat, Dec 19, 2020, at 4:32 PM, Carlo Landmeter wrote:
We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. I also doubt the shown error is the problem as I see more template errors. I have also tried to run the official docker images mailman-docker but im having the same issue.
When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email.
PS emails are send just fine via smtp posting.
Unless I am missing something basic, I don't really know why it doesn't fail on our servers. May have something to do with Django versions or something. I need to work a bit more on verifying it.
This is the line in template1, rendered using this context2 which seems to be causing the issue.
I've made the change to remove the 'display_fixed' attribute for email 1.
You can update the pip install commands to git+https://gitlab.com/mailman/mailman@master after the MR gets merged to create a test image and see if it fixes the issue for you. You can see the sample .dev Dockerfiles i have in my docker-mailman repo for reference2.
Abhilash
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
-- thanks, Abhilash Raj (maxking)
On 12/19/20 3:02 AM, Carlo Landmeter wrote:
We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. I also doubt the shown error is the problem as I see more template errors. I have also tried to run the official docker images mailman-docker but im having the same issue.
When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email.
PS emails are send just fine via smtp posting.
The error reported from hyperkitty/ajax/temp_message.html in the OP has nothing to do with the replies not being sent or archived. hyperkitty/templates/hyperkitty/ajax/temp_message.html is called to build the HTML response sent to the web browser after the reply has been sent to Mailman core.
Abhilash's fix at https://gitlab.com/mailman/hyperkitty/-/merge_requests/299 will get rid of that error, but I would be very surprised if it fixes the problem.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Abhilash Raj -
Carlo Landmeter -
Mark Sapiro -
Milan P. Stanić