Skip to main content

Mailman (2.2.0) is severely broken

Christian Buser

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...

Comments

9 comments

Date Votes
  • cPRex Jurassic Moderator
    • Edited

    Hey there!  Yes, there have been some issues with Mailman since the recent updates and our team has multiple cases open regarding those fixes:

    CPANEL-46585 - Mailman cPanel webmail access autologin issues
    CPANEL-46556 - Unable to unshunt messages
    CPANEL-46545 - Non-English characters not working properly
    CPANEL-46537 - News Gateway sync
    CPANEL-46529 - Unicode digest issues
    CPANEL-46525 - Unable to view messages held for moderation
    CPANEL-46518 - Mailman restart issues

    so we're aware and working on this now.  I can say that we aren't moving 126 to Stable until these major issues are resolved.

    1
  • Anders Boholdt-Petersen

    Where can I be informed about when the issus is fixed?

     

    Regards,

    Anders

    0
  • cPRex Jurassic Moderator

    I'll post to this thread once those issues are resolved!

    0
  • cPRex Jurassic Moderator

    Update - our team is working on version 126.0.13 which will have the following two major issues resolved:

    CPANEL-46530: Update Mailman to 2.2.0.16-2: adds some limits to the one time backup that happens for mailman when upgrading to the python3 version.
    HB-8228: Update Mailman to version 2.2.0-15 to fix module imports.

    I'm not 100% certain when this build will be released, but it will likely be within the next few days.

    1
  • kenrbnsn

    I'm waiting for these two issues to be resolved:
    CPANEL-46537 - News Gateway sync
    CPANEL-46529 - Unicode digest issues

    Ken

    1
  • cPRex Jurassic Moderator

    I don't have anything for CPANEL-46537 yet.  CPANEL-46529 is fixed and will be merged into the next major public build, so I'd expect to see that within a week or so.

    -1
  • Christian Buser

    The main question remains:

    Why are you deploying untested / beta software?

    0
  • cPRex Jurassic Moderator

    Well, that's obviously a loaded question :D

    I touched on a bit of this in the other Mailman thread here:

    https://support.cpanel.net/hc/en-us/community/posts/31265322468887

    but ultimately, moving to Mailman 3 would be too disruptive for end users (yes, significantly worse than the issues we're seeing here with Mailman 2, with the addition of potential data loss and and entirely new UI that all users have never seen before, but work in the cPanel backend to make it work) so we made the decision to stick with Mailman 2.  This choice came with the issue of supporting Mailman 2 on Python 3, which also isn't something Mailman intended to work, and that's where many of the conflicts arose.

    I promise that although it may not look like it, this was the least disruptive of the options to continue to offer Mailman service.

    0
  • National Federation

    That is all well and good, but it has been three and a half weeks since Mailman broke, and you are saying it is likely to be another week. My 15,000 users will be thrilled. And ... we need real search in Mailman.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post