On Thu, Nov 28, 2024 at 01:04:13PM -0800, Mark Sapiro wrote: > > I did not see this y/day and created the entry in table django_site using > > SQL. > > This might be the cause of the other problems that we have been talking > > about. > > > It's not likely that this is the cause.
It is fixed - the mail list works. I had forgotten to put the reverse proxy into the Apache config -- this is what led to the many, rapid retries. I had a problem for a while in the nothing to one particular list was sent to users. This had several users who's delivery status was 'disabled' (correctly, as on the old instance). If was only after a lot of fiddling (trying to delete from the list) that it started to work for the others. There are still rough edges, eg trying to delete a list member gives a server error. In /var/log/mailman3/mailman.log I see a 404: "DELETE /3.1/lists/chat.bray.phcomp.co.uk/member/a.chent...@hotmail.com HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.5" I am not to worried about that today, will look at it in the future. Thanks for your help -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h> _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/OSYDPQJ4N74TDCJNWQFGBNG3LINRMEON/ This message sent to arch...@mail-archive.com
