1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Mailman Problem - Uncaught runner exception: unbound method

Discussion in 'Plesk for Linux - 8.x and Older' started by widomaker, Mar 5, 2008.

  1. widomaker

    widomaker Guest

    0
     
    If you try to send a post to a moderated mailing list, the message never shows up in the moderation queue. Here is what the error log says:

    Mar 05 11:58:29 2008 (907) Uncaught runner exception: unbound method reason_noti
    ce() must be called with NonMemberPost instance as first argument (got nothing i
    nstead)
    Mar 05 11:58:29 2008 (907) Traceback (most recent call last):
    File "/usr/local/psa/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
    self._onefile(msg, msgdata)
    File "/usr/local/psa/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
    File "/usr/local/psa/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _d
    ispose
    more = self._dopipeline(mlist, msg, msgdata, pipeline)
    File "/usr/local/psa/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _d
    opipeline
    sys.modules[modname].process(mlist, msg, msgdata)
    File "/usr/local/psa/mailman/Mailman/Handlers/Moderate.py", line 109, in proce
    ss
    Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
    File "/usr/local/psa/mailman/Mailman/Handlers/Hold.py", line 212, in hold_for_
    approval
    reason = Utils.wrap(exc.reason_notice())

    TypeError: unbound method reason_notice() must be called with NonMemberPost inst
    ance as first argument (got nothing instead)

    Any help would be great.....

    Thanks W

    P.S. FreeBSD 6.2 / Plesk 8.3 / Python 2.5.1 / Mailman 2.1.6 (from what we can tell)
     
  2. widomaker

    widomaker Guest

    0
     
    I also ran the command 'check_perms' and here is the output:

    directory permissions must be 02775: /usr/local/psa/mailman/archives/private/wabmembers/attachments
    directory permissions must be 02775: /usr/local/psa/mailman/archives/private/wabmembers/attachments/20080208
    directory permissions must be 02775: /usr/local/psa/mailman/archives/private/wabmembers/attachments/20080303
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/retry
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/shunt
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/out
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/bounces
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/in
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/commands
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/virgin
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/archive
    directory permissions must be 02770: /usr/local/psa/mailman/qfiles/news
    Warning: Private archive directory is other-executable (o+x).
    This could allow other users on your system to read private archives.
    If you're on a shared multiuser system, you should consult the
    installation manual on how to fix this.
    Problems found: 12
    Re-run as mailman (or root) with -f flag to fix

    Is this normal or does any of the following need to be fixed?

    Thanks W
     
  3. ib1984

    ib1984 Basic Pleskian

    23
    70%
    Joined:
    Jun 25, 2008
    Messages:
    91
    Likes Received:
    0
  4. widomaker

    widomaker Guest

    0
     
    I will look into that. Thanks for the info. But on the other hand this is what PLESK installed. It also tells me that Mailman is up-to-date based on 2.1.6.... Anyone eles having this problem?
     
  5. mikk

    mikk Basic Pleskian

    23
    73%
    Joined:
    Jan 29, 2005
    Messages:
    83
    Likes Received:
    0
    Are you still having issues with this?

    I had the same issue and based on this thread and some various other threads on other sites managed to confirm that this is indeed an issue with python 2.5, after contacting plesk support there will not be a fix for this until Plesk9 at the earliest.

    However this should fix it in (or it did for me)

    cd /usr/ports/lang/python2.4 && make install clean # install python 2.4, may not be necessary
    /usr/local/psa/mailman/bin/mailmanctl stop #stop current mailman
    cp -pr /usr/local/psa/mailman /usr/local/psa/mailman.orig #precautionary backup
    find /usr/local/psa/mailman -type f | xargs perl -pi -e 's/python2.5/python2.4/g' #replace python2.4 with python2.5 in all filles
    /usr/local/psa/mailman/bin/mailmanctl start #start mailman back up.

    From this point you should find this working.

    Hope it helps.
     
Loading...