On 3/10/25 10:49 PM, Mark Sapiro wrote:

On 3/11/25 12:32 PM, Jim Dory wrote:

...

I realize this may be a CPanel issue, but perhaps someone familiar with that can help out.

The web page for the list archives says 60 messages but none are visible. The messages are in the list directory. The unusual thing for this month is the "Starting: None". The other months previous all have the start date of the beginning of that particular month.

The shared server I'm hosted on is using UTC time of the server location, not my location. So although it is March 10 here now as I write this, it is showing March 11 tomorrow morning. I don't know if I'm supposed to change it to my location or leave it.. has been an issue particularly before. So I'm inclined to leave it.

Here's the March archives listing:

  March 2025 Archives by thread

  * *Messages sorted by:*[ subject ] <https://nomekennelclub.com/mailman/private/nome- announce_nomekennelclub.com/2025-March/subject.html#start>[ author ] <https://nomekennelclub.com/mailman/private/nome- announce_nomekennelclub.com/2025-March/author.html#start>[ date ] <https://nomekennelclub.com/mailman/private/nome- announce_nomekennelclub.com/2025-March/date.html#start> * *More info on this list... <http://nomekennelclub.com/mailman/ listinfo/nome-announce_nomekennelclub.com>*

*Starting:*/None/

None is strange here.

...

*Ending:*/Tue Mar 11 04:59:52 UTC 2025/ *Messages:*60

Links to all the messages should be here.

...

*Last message date:*/Tue Mar 11 04:59:52 UTC 2025/ *Archived on:*/Tue Mar 11 05:00:02 UTC 2025/

  * *Messages sorted by:*[ subject ] <https://nomekennelclub.com/mailman/private/nome- announce_nomekennelclub.com/2025-March/subject.html#start>[ author ] <https://nomekennelclub.com/mailman/private/nome- announce_nomekennelclub.com/2025-March/author.html#start>[ date ] <https://nomekennelclub.com/mailman/private/nome- announce_nomekennelclub.com/2025-March/date.html#start> * *More info on this list... <http://nomekennelclub.com/mailman/ listinfo/nome-announce_nomekennelclub.com>*

---

/This archive was generated by Pipermail 0.09 (Mailman edition)./

The above is a static page (re)generated by Mailman with each post. This process is not happening correctly. It is another cPanel issue with the upgrade, but I have no idea what is wrong or how to fix it. https://support.cpanel.net/hc/en-us/community/posts/29645975750423/comments/... points out this issue.

It appears cPanel Mailman is now running under Python 3. I'm not surprised there are issues. Migrating Mailman 2.1 to Python 3 is not an easy task,

Thanks Mark. I'll pass that on to the trouble ticket I have with the support staff. Not a critical issue at least.. not sure how many of the subscribers actually look at the archives.. but I would like to get it sorted.

Jim Dory writes:

Another error I'm now seeing in this update is below:

List: nome-announce_nomekennelclub.com: problem processing /usr/local/cpanel/3rdparty/mailman/lists/nome-announce_nomekennelclub.com/digest.mbox: 'utf-8' codec can't decode byte 0x93 in position 104: invalid start byte

This is very likely a footer or header setting that was saved as a Windows file, or perhaps has been corrupted in some way. The reason I suspect Windows is 0x93 is "opening double dumbquote" in the Windows encoding used by Western European languages, which seems pretty likely as the first non-ASCII character in an English text. It's not as likely to be used in a Subject tag. Also, the "once a day" part strongly suggests that it's related to digest processing itself, not to the messages in the digests.

Steve

David Andrews via Mailman-Users writes:

At 01:49 AM 3/11/2025, Mark Sapiro wrote:

...

It appears cPanel Mailman is now running under Python 3. I'm not surprised there are issues. Migrating Mailman 2.1 to Python 3 is not an easy task,

The other day, I read in the Mailman roadmap it said they were upgrading to Python 3. It also said they were "taking over the maintenance of Mailman." Not sure what they meant, but I guess we are starting to see the fallout of this!

I would guess it means they don't want to support migration of Mailman 2 sites to Mailman 3, and it's less effort to port Mailman 2 to Python 3. and support that product for them in the long run.

I don't think this is going to be good for their customers (who have traditionally treated us as the first responders even for cPanel- specific features), but we'll see. Perhaps the contingent who have been advocating for a continuation of the Mailman 2 product for a decade will join the cPanel user/development community. That combination might have legs if cPanel is smart.

Steve