When I send a mail to a list that exceeds the max size, I get the above answer. However, the moderator of that list does not get a message, and there is no entry in the list of hold back messages.
This should be a configuration problem, on another list on the same server this works fine. I cannot find any differences in the settings.
I think I solved that. The background might be of interest for other admins, and for the developers.
I had set up some new mailing lists on that server. I also had deleted an old mailing list for a domain that is no longer hosted on that server. To delete the old mailing list, I used the methods provided by postorius.
Now it turned out that there were several relicts of the old list in the database, in particular in the template table. I removed them using direct SQL commands.
Now my new mailing lists work as expected.
Is this a bug in postorius? I think when I delete a mailing list, all relicts should be deleted from the database.
Am Mittwoch, 21. Dezember 2022, 14:46:56 CET schrieb Eggert Ehmke via Mailman- users:
When I send a mail to a list that exceeds the max size, I get the above answer. However, the moderator of that list does not get a message, and there is no entry in the list of hold back messages.
This should be a configuration problem, on another list on the same server this works fine. I cannot find any differences in the settings.
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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message /AIYSQM3XBDBQOJTOJQVXRT5PGOVUIJ73/
This message sent to eggert@eehmke.de
It might be of interest that after deleting the old list, also the domain of the old list was deleted from the DNS (points to another server now). This explains several "Uncaught runner exception: HTTPSConnectionPool" message in the log file.
On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote:
Now it turned out that there were several relicts of the old list in the database, in particular in the template table. I removed them using direct SQL commands.
Now my new mailing lists work as expected.
Is this a bug in postorius? I think when I delete a mailing list, all relicts should be deleted from the database.
Were there Postorius custom templates for that list?, I.e. did the template table entries have Postorius URLs. If so, this is probably a Postorius issue. I haven't actually looked, but when Postorius deletes a list, it should delete any of it's templates from the postorius_emailtemplate table and revert the template table entries.
Beyond that, Postorius is just telling Mailman core to delete the list, and when Mailman core does that it should probably also remove any var/templates/lists/<list_id> directory and any entries from the template table with context = the list_id. If it doesn't, this is a core issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Yes, the templates did have URL's of the old lists. I changed them to refer to the new lists.
Am Mittwoch, 21. Dezember 2022, 21:33:26 CET schrieb Mark Sapiro:
On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote:
Now it turned out that there were several relicts of the old list in the database, in particular in the template table. I removed them using direct SQL commands.
Now my new mailing lists work as expected.
Is this a bug in postorius? I think when I delete a mailing list, all relicts should be deleted from the database.
Were there Postorius custom templates for that list?, I.e. did the template table entries have Postorius URLs. If so, this is probably a Postorius issue. I haven't actually looked, but when Postorius deletes a list, it should delete any of it's templates from the postorius_emailtemplate table and revert the template table entries.
Beyond that, Postorius is just telling Mailman core to delete the list, and when Mailman core does that it should probably also remove any var/templates/lists/<list_id> directory and any entries from the template table with context = the list_id. If it doesn't, this is a core issue.
participants (2)
-
Eggert Ehmke -
Mark Sapiro