Mailman (2.2.0) is severely broken
Mailman is broken since the last cPanel update a few days ago:
- List archives are broken
- encoding / decoding of non-ascii characters are broken
- daily digests are no longer working
It is just a nightmare...
-
Unfortunately those words don't make sense to me - no one phones us for support as it's all communicated through email, and we would never tell a Partner not to submit a ticket for an issue.
0 -
Thanks cPRex. It likley did not make sense to you as I was wrong.
I reread the note he sent and I was totally out to lunch and owe cpanel a bit of an apology for my misunderstanding - I interpreted the ticket issue quite incorrectly. From what you are indicating I also misunderstood what "livechat" was, as I thought this was live person-to-person phone call.
His exact words were:
"I don't have a cPanel support ticket on the go as when I engaged with cPanel support via livechat, I was told that the present issues with mailman are not something that can be fixed via cPanel settings changes or configuration and are being addressed in version 130. I was encouraged to open a ticket for them to document the issue but that a solution would not be found prior to that update.
"I wasn't told this outright, but the impression I got is that they've been fighting to get Mailman 2 working cleanly on cPanel for a while, hence the fixes being 2 version releases away."
0 -
That does make sense! And from the wording there it seems these are known issues that we're working on.
While it may not seem like it right now, this really was the least disruptive option to continue offering mailman, as upgrading to version 3.0 just wasn't an option.
0 -
Our issue seems to have been fixed a few days ago. Fingers crossed it will not reoccur, but I expect the fix is permanent. Thanks to all at CPanel who worked to resolve our issue.
0 -
Bob England- glad to hear it!
0 -
Are there any known issues still unresolved, and if not, what version has all of them fixed? I still have a site on 124.0.34 and would like to update, but since cPanel versions apparently can't be rolled back, I want to make sure Mailman will work right before doing so.
0 -
rclemings - all the core issues are resolved as far as I know. There's likely still some of the more edge-cases happening, but the major issues mentioned in this thread are taken care of.
0 -
I still have eight open customer tickets from March/April that I'd love to resolve for them. rclemings, I agree with cPRex, the major issues are now behind us. My two issues are more edge-cases.
CPANEL-47503 - Involves use of RCPT_BASE64_HEADER_NAME which we do on all of our servers. The workaround isn't one we're willing to do. The issue stemmed from any of our customers that use the "Personalize" option, when this mailing list setting is turned on, and RCPT_BASE64_HEADER_NAME is being used, the list is completely broken. The workaround that we have been using, is having customers turn off personalize on their lists for now.
CPANEL-47499 - This stems from certain email clients sending smart quotes. UTF8 encodings appear in Mailman non-digest emails. The work-around for this one is also difficult, since it relies not on the list owner, but any member of any list, to turn off their smart quotes.
I don't see either of these in 128.0.x or 130.0.1 change log notes. Really hoping to see them resolved soon! It's been a long four months.
0 -
GBTim - those are indeed some of the more "edge" cases, with only one tickets attached to each. I've ensured they are on the development team's review list, although I can't say when they'll be picked up.
0 -
Thanks. I've followed both issues. I see I do have RCPT_BASE64_HEADER_NAME in my mm_cfg.py and the other doesn't seem to have a workaround so I guess I'll wait a little longer.
0 -
For those following this thread, I opened a new ticket last night. I was told it was a known bug, CPANEL-48109.
The bug is for incoming subscribe requests on the moderation screen, they show the subscribing email address as: b'username@example.com'
Which is a byte string, rather than a regular (Unicode) string. Another Python 2 to 3 upgrade bug. Luckily, it doesn't impact the actual email address subscribing to the list. It's just a display bug on the moderation screen. Approving the subscriber will add the correct address and everything is fine.
0 -
Any news about when CPANEL-47503 and CPANEL-47499 might be fixed? They weren't in yesterday's releases, as far as I can see.
0 -
rclemings - I don't see that those have received any action just yet. I did reach out to the development team just now to see if I can get those some priority.
0 -
Thanks cPRex! If I could add one more, I'm waiting for CPANEL-48109 in addition to CPANEL-47503 and CPANEL-47499 to be fixed. These three bugs are the issues for over 20 customer support tickets that are being held open for me.
Relative to what they've already fixed, these should be pretty simple code fixes and easy fixes to replicate/test. Fingers crossed we can put this Mailman upgrade behind us soon.
0 -
I've brought up 48109 with the team as well!
0
Please sign in to leave a comment.
Comments
75 comments