Skip to main content

Tier: Current 126.0.2 has broken mailman

Comments

26 comments

  • cPRex Jurassic Moderator

    I believe all the cases are currently resolved that are blockers for Stable, they just haven't been included yet.  We're likely 2-3 weeks out from anything getting promoted to Stable.

    1
  • Coley1

    Hi, 

     

    I have been on 126.02 since at least last week some time and I too am having the same issues. I am getting very little help from our data center or cPanel for that matter regarding this issue. We host a ton of these mailman lists and my customers are not happy.

     

    They intially tried to say it had somethign to do with DMARC, but that is not the case.

     

    Naturally, I can't get the ticket number from my provider either. So here is the person working on it.

    Ryland Robertson
    Technical Support Engineer III

     

    I am seriously considering migrating off of cPanel at this point.

    0
  • Damian

    Yes it is certainly not DMARC related. It's python or the mailman scripts.

    Some emails are delivered but the admin functions are all broken.

    0
  • Damian

    Does cPRex still help out in these forums?

    0
  • cPRex Jurassic Moderator

    Coley1 - I do see that ticket was escalated to our Level 3 support team, but so far we haven't been able to reproduce this on a test machine to know exactly what the issue is.

    Damian - are you able to submit a ticket on this as well?

    0
  • Coley1

    Hello,

    Below is from the error log on a seperately installed cPanel Server running Alma Linux 8 with Python 3.6.

    I also noticed when this verson of cPanel is freshly installed it doesnt create the default mailman list. This causes some of the inital errors at the top of the log below. Once I created the default list, Mailman was able to start successfully.


    cat error 
    Feb 03 10:04:25 2025 mailmanctl(54665): PID unreadable in: /usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid 
    Feb 03 10:04:25 2025 mailmanctl(54665): [Errno 2] No such file or directory: '/usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid' 
    Feb 03 10:04:25 2025 mailmanctl(54665): Is qrunner even running? 
    Feb 03 10:49:57 2025 (65620) Uncaught runner exception: sequence item 0: expected str instance, bytes found
    Feb 03 10:49:57 2025 (65620) Traceback (most recent call last):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop
        self._onefile(msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 184, in _onefile
        keepqueued = self._dispose(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
        more = self._dopipeline(mlist, msg, msgdata, pipeline)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
        sys.modules[modname].process(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/SpamDetect.py", line 110, in process
        Utils.IsDMARCProhibited(mlist, addr)):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1350, in IsDMARCProhibited
        x = _DMARCProhibited(mlist, email, '_dmarc.' + f_dom)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1400, in _DMARCProhibited
        "".join(txt_rec.items[0].strings))
    TypeError: sequence item 0: expected str instance, bytes found

    Feb 03 10:49:57 2025 (65620) SHUNTING: 1738597796.9066792+ac4b19e376f9afd3151dbaeef58c01d8979b3b7f
    Feb 03 10:54:20 2025 (65620) Uncaught runner exception: sequence item 0: expected str instance, bytes found
    Feb 03 10:54:20 2025 (65620) Traceback (most recent call last):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop
        self._onefile(msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 184, in _onefile
        keepqueued = self._dispose(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
        more = self._dopipeline(mlist, msg, msgdata, pipeline)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
        sys.modules[modname].process(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/SpamDetect.py", line 110, in process
        Utils.IsDMARCProhibited(mlist, addr)):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1350, in IsDMARCProhibited
        x = _DMARCProhibited(mlist, email, '_dmarc.' + f_dom)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1400, in _DMARCProhibited
        "".join(txt_rec.items[0].strings))
    TypeError: sequence item 0: expected str instance, bytes found

    Feb 03 10:54:20 2025 (65620) SHUNTING: 1738598060.2385314+bf00e044995b3fb70c37f472eede5ecff91b6c87
    Feb 03 10:58:29 2025 (65620) Uncaught runner exception: sequence item 0: expected str instance, bytes found
    Feb 03 10:58:29 2025 (65620) Traceback (most recent call last):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop
        self._onefile(msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 184, in _onefile
        keepqueued = self._dispose(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
        more = self._dopipeline(mlist, msg, msgdata, pipeline)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
        sys.modules[modname].process(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/SpamDetect.py", line 110, in process
        Utils.IsDMARCProhibited(mlist, addr)):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1350, in IsDMARCProhibited
        x = _DMARCProhibited(mlist, email, '_dmarc.' + f_dom)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1400, in _DMARCProhibited
        "".join(txt_rec.items[0].strings))
    TypeError: sequence item 0: expected str instance, bytes found

    Feb 03 10:58:29 2025 (65620) SHUNTING: 1738598060.2385314+5dcf203468e33b2c949c4fe99ab42bf748322e27
    Feb 03 10:58:29 2025 (65619) Uncaught runner exception: sequence item 0: expected str instance, bytes found
    Feb 03 10:58:29 2025 (65619) Traceback (most recent call last):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop
        self._onefile(msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 184, in _onefile
        keepqueued = self._dispose(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
        more = self._dopipeline(mlist, msg, msgdata, pipeline)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
        sys.modules[modname].process(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/SpamDetect.py", line 110, in process
        Utils.IsDMARCProhibited(mlist, addr)):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1350, in IsDMARCProhibited
        x = _DMARCProhibited(mlist, email, '_dmarc.' + f_dom)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1400, in _DMARCProhibited
        "".join(txt_rec.items[0].strings))
    TypeError: sequence item 0: expected str instance, bytes found

    Feb 03 10:58:29 2025 (65619) SHUNTING: 1738597796.9066792+88f1f2d1141b40881811d5e8d646afd92d76d058

    0
  • Zachary Karr

    Hi Coley1 !

    If you could update the ticket you have with that information, that would be most helpful. Looking through this thread there are a couple of different errors I've seen, and matching these to cPanel and OS version would greatly assist in tracking this down. So far in this thread I've noted the following errors that are causing the messages to be shunted:

    TypeError: sequence item 0: expected str instance, bytes found
    ModuleNotFoundError: No module named 'iterators'
    UnicodeDecodeError: 'utf-8' codec can't decode byte 0x91 in position 4851284091: invalid start byte
    AttributeError: 'Message' object has no attribute 'policy'
    KeyError: 0

     

    In order to best keep track of these I'd ask to open or update tickets with any relevant information.

    0
  • Coley1

    We have sent the above to our data center. There is a delay in getting it to you since we can’t open tickets directly anymore.

     

     

    0
  • Damian

    Thanks @cprex. Ticket number 95439714

    0
  • cPRex Jurassic Moderator

    Thanks for that - I'm following along with that ticket now as I see Brian is on it!

    0
  • cPRex Jurassic Moderator

    Update - Last night, Steven, one of our Level 3 techs, dove into this issue and created several cases for our development team to review.  Ultimately, the best way to follow along is with this support article here:

    https://support.cpanel.net/hc/en-us/articles/29762855785751-v126-Mailman-stopped-sending-emails

    as that will get updated once we have more details.

    0
  • henker

    Is there any ETA for a solution ?

     

    0
  • henker

    Uninstalled mailman, ran /usr/local/cpanel/scripts/check_cpanel_pkgs --fix , started mailman, looks like it's running now.

     

    sys.path.append('/usr/local/cpanel/3rdparty/mailman/Mailman') was missing in mm_cfg.py , it only had
    "from Defaults import *", should be

     

    import sys
    ###############################################
    # Here's where we get the distributed defaults.

    sys.path.append('/usr/local/cpanel/3rdparty/mailman/Mailman')
    from Defaults import *

    ##################################################
    # Put YOUR site-specific settings below this line.

    0
  • mtindor

    cPRex

    Wondering if this issue is fixed in 126 yet?

     

    126 Change Log

    Last modified: 2025 March 4


    126.0.9


    2025-03-04
    • Fixed HB-8200: Update Mailman to version 2.2.0.11-1, upgrade and archive related fixes.
    • Fixed HB-8201: Fix mailman AttributeError: 'Message' object has no attribute 'policy'.
    • Fixed RE-1319: Reject DB imports larger than PHP download limits in myadmin.
    • Fixed RE-1346: Resume use of BIND zone-checking utilities when ALIAS records are not present.
    • Fixed RE-1360: Update Mailman to version 2.2.0.11-2.

    Do you know if any/all of these fixes have resolved what was reported above?   I'm still sticking on 124 (set to Stable) and hoping that cPanel doesn't update Stable to 126 until the issues reported in this thread are fixed.

    Any idea if the issues are taken care of?

    0
  • henker

    Doesn't look like.
    My mailman broke last night during the update, 126 RELEASE

    0
  • cPRex Jurassic Moderator

    No, I don't believe all of the cases have been resolve just yet.

    0
  • mtindor

    henker I'm sorry to hear that, but thanks for reporting it.

    cPRex  This may be a willy question, but is it safe to assume that 126 will NOT proceed into Stable until all of the mailman issues are taken care of?

     

    Mike

    0
  • mtindor

    Thanks, cPRex .  That's good to know.

     

    Mike

     

    0
  • Damian
    • Fixed HB-8200: Update Mailman to version 2.2.0.11-1, upgrade and archive related fixes.

    Sadly, this is only partly fixed.  The archives are now being created BUT when trying to regenerate the pre-existing archives it is still failing with an error wipes the archive page.  The archives are still present on the filesystem and in the correct directories but the archives HTML page is wiped.

    /usr/local/cpanel/3rdparty/mailman/bin/arch listname

    Pickling archive state into /usr/local/cpanel/3rdparty/mailman/archives/private/listnamepipermail.pck
    Traceback (most recent call last):
    File "/usr/local/cpanel/3rdparty/mailman/bin/arch", line 202, in <module>
      main()
    File "/usr/local/cpanel/3rdparty/mailman/bin/arch", line 190, in main
      archiver.processUnixMailbox(fp, start, end)
    File "/usr/local/cpanel/3rdparty/mailman/Mailman/Archiver/pipermail.py", line 554, in processUnixMailbox
      mbox_iterator = iter(mbox.values())
    File "/usr/lib64/python3.6/mailbox.py", line 119, in values
      return list(self.itervalues())
    File "/usr/lib64/python3.6/mailbox.py", line 109, in itervalues
      value = self[key]
    File "/usr/lib64/python3.6/mailbox.py", line 76, in __getitem__
      return self._factory(file)
    File "/usr/local/cpanel/3rdparty/mailman/Mailman/Mailbox.py", line 88, in scrubber
      return mailbox.scrub(msg)
    File "/usr/local/cpanel/3rdparty/mailman/Mailman/Mailbox.py", line 110, in scrub
      return self._scrubber(self._mlist, msg)
    File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/Scrubber.py", line 272, in process
      url = save_attachment(mlist, part, dir)
    File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/Scrubber.py", line 543, in save_attachment
      fp.write(decodedpayload)
    TypeError: a bytes-like object is required, not 'str'

     

    0
  • kenrbnsn

    I found this thread while search for a solution to a problem with mailman 2.2.0. I use the gateway feature, since the update of mailman, I'm seeing these errors when the cronjob is running:

    Traceback (most recent call last):
      File "/usr/local/cpanel/3rdparty/mailman/cron/gate_news", line 286, in <module>
        main()
      File "/usr/local/cpanel/3rdparty/mailman/cron/gate_news", line 266, in main
        process_lists(lock)
      File "/usr/local/cpanel/3rdparty/mailman/cron/gate_news", line 243, in process_lists
        poll_newsgroup(mlist, conn, start, last+1, glock)
      File "/usr/local/cpanel/3rdparty/mailman/cron/gate_news", line 126, in poll_newsgroup
        headers = conn.head(repr(num))[3]
    IndexError: tuple index out of range
    0
  • cPRex Jurassic Moderator

    kenrbnsn - I'm not seeing any other reports of this issue just yet.  Would you be able to submit a ticket so this can be investigated directly on the server?

    0
  • kenrbnsn

    How does one submit a ticket?  I can message the owners of the service I rent my server from, but I think I have a fully self-managed hosting site.

    0
  • cPRex Jurassic Moderator

    If your license is purchased through us you would be able to submit a ticket directly through WHM.  If not, you would contact your provider and if they can't fix the issue they would escalate the ticket to us.

    0
  • kenrbnsn

    My provider submitted a ticket -- TT 95661125

    0
  • Yehuda Katz

    We are also having major issues due to this:

     

    Mar 20 16:31:18 2025 (2559215) Traceback (most recent call last):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop
        self._onefile(msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 184, in _onefile
        keepqueued = self._dispose(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
        more = self._dopipeline(mlist, msg, msgdata, pipeline)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
        sys.modules[modname].process(mlist, msg, msgdata)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/SpamDetect.py", line 110, in process
        Utils.IsDMARCProhibited(mlist, addr)):
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1359, in IsDMARCProhibited
        x = _DMARCProhibited(mlist, email, '_dmarc.' + o_dom, org=True)
      File "/usr/local/cpanel/3rdparty/mailman/Mailman/Utils.py", line 1404, in _DMARCProhibited
        "".join( [ record.decode() if isinstance(record, bytes) else record for record in txt_rec.items[0].strings ] ))
    KeyError: 0

    0
  • kenrbnsn

    The problem I described earlier about Mailman erroring out when trying to gateway news is a bug and is described in https://support.cpanel.net/hc/en-us/articles/30811133324951-Mailman-2-2-error-when-performing-News-Gateway-sync. The functionality probably wasn't well tested since UseNET newsgroups are not used very often these days.

    0

Please sign in to leave a comment.