On 12/16/22 13:18, Gregg Roberts wrote:
Messages that I post to the forum have been taking as long as 48 hours to come back to me. The issue is not new and AFAIK no one has been messing with the settings. But the issue seems to have been becoming more and more severe in recent weeks.
This is a symptom of a backlogged out queue in Mailman.
Perhaps because of such delays, I also sometimes see responses to other posts before I see the original post. It takes extra time to understand the context when that happens. People's time gets wasted answering questions that have already been answered without their knowledge. It's just frustrating all around.
The email address from which messages are sent is not in the list of email addresses maintained in the hosting account cPanel. There seems to be one by the name "relay" that is being used by Mailman.
I actually don't know which version of Mailman is installed. I'm hoping it's the more recent of the two options so I optimistically joined this particular list.
The Mailman provided with cPanel is Mailman 2.1, not Mailman 3.
The hosting service tech support can't help because they can't see the forum email address or its logs. At least that's what they say.
The hosting service only offers Mailman because it is part of cPanel. Unfortunately this is true of many cPanel based hosting services. They offer Mailman but are incompetent to support it.
Your issue is a symptom of a backlogged out queue and it probably has nothing to do with your list. There will be only one Mailman instance on the cPanel host machine and it will be delivering messages for all the lists on all the virtual hosts supported by that machine.
There are threads in the archives on the backlogged out queue issue, e.g. <https://mail.python.org/archives/list/mailman-users@python.org/thread/QGVWWK6OJSND3LP6TF6MYBTQT7VQASGB/> and <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/EPNAIFZJ76C6U76XLPFGRF46UU5FVRHG/>. There is also a FAQ article at <https://wiki.list.org/x/17892002>.
A contract tech support guy has suggested that it might solve a problem if we started spending $100-$150 per month on a dedicated server. I think that is a wrongheaded suggestion. If the organization had thousands of members, it would make more sense. But throwing money at the problem if something is simply not set up right, or some critical file is corrupted, is not the right solution. Set the broken bone correctly first, THEN inject stimulants and send the player back out onto the field. :-)
A dedicated server might help, but probably only because it would remove you from the impact of Mailman lists from other vhosts on the shared server.
There are things the host can do to improve the situation, but only if they are competent in tuning Mailman and the outgoing MTA. If they are willing to work on this, they are welcome to post to mailman-users@python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/> and we will try to help, but you are at their mercy to fix this and your only recourse is to look for a different hosting service. If it's only for Mailman lists, see <https://wiki.list.org/COM/Mailman%20hosting%20services>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan