The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Mailman Broken

Discussion in 'E-mail Discussions' started by transitgallery, Mar 11, 2003.

  1. transitgallery

    transitgallery Registered

    Joined:
    Mar 1, 2003
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    It doesnt run or setup any right on cpanel6

    Any ideas? :confused:
     
  2. Brian Farkas

    Brian Farkas Well-Known Member

    Joined:
    Aug 12, 2001
    Messages:
    81
    Likes Received:
    0
    Trophy Points:
    6
    We ran into a problem where mailman was apparently not sending out messages -- they would appear in the /usr/local/cpanel/3rdparty/mailman/qfiles directory, but would not be sent to list members.

    We discovered that somehow during the cpanel upgrade, the mailman crontab was wiped out. We restored this (under the username mailman) and everything worked out fine.

    If you describe your problem in a little more detail we may be able to help you a little more -- but this worked for us when mailman was writing to the qfiles dir but not delivering.

    Good luck,

    Brian
     
  3. Chase

    Chase Well-Known Member

    Joined:
    Mar 19, 2003
    Messages:
    109
    Likes Received:
    0
    Trophy Points:
    16
    Hello,
    Coud you please provide me with the command that you used to restore this and an exact instructions on how to fix this. I'm familar with Cron But I don't know what the correct one would be for this.
     
  4. Chase

    Chase Well-Known Member

    Joined:
    Mar 19, 2003
    Messages:
    109
    Likes Received:
    0
    Trophy Points:
    16
    Run

    pico /var/spool/cron/mailman

    in this file make sure the file says the following:

    # DO NOT EDIT THIS FILE - edit the master and reinstall.
    # (/usr/local/cpanel/src/3rdparty/gpl/mailman-2.0.13/cron/crontab.in installed on

    Tue Mar 18 22:58:36 2003)
    # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
    # At 5PM every day, mail reminders to admins as to pending requests
    0 17 * * * /usr/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/checkdbs
    #
    # Noon, mail digests for lists that do periodic as well as threshhold delivery.
    0 12 * * * /usr/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests
    #
    # 5 AM on the first of each month, mail out password reminders.
    0 5 1 * * /usr/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/mailpasswds
    #
    # Every 5 mins, try to gate news to mail. You can comment this one out
    # if you don't want to allow gating, or don't have any going on right now,
    # or want to exclusively use a callback strategy instead of polling.
    #0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/python -S

    /usr/local/cpanel/3rdparty/mailman/cron/gate_news
    #
    # At 3:27am every night, regenerate the gzip'd archive file. Only
    # turn this on if the internal archiver is used and
    # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py
    27 3 * * * /usr/bin/python -S

    /usr/local/cpanel/3rdparty/mailman/cron/nightly_gzip
    #
    # Retry failed deliveries once per minute.
    * * * * * /usr/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/qrunner

    If so save it.
     
  5. cheapo

    cheapo Member

    Joined:
    Sep 6, 2002
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    It doesn't work.

    Is cpanel going to fix this? I have upset customers.
     
  6. chakky

    chakky Well-Known Member

    Joined:
    Sep 22, 2002
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    6
    If it s an internal server error your getting, I have been waiting for nick or someone to give me an idea on how to solve it.

    The solution I do these days is to disable suexec

    You can disable suexec for individual users as:
    vi /usr/local/apache/conf/httpd.conf

    then go to the virtual host entry of the user who is complaining of it and then comment out the User and Group which lies below the document root syntax.

    restart httpd and it will work :(.
    But I dont know what would happen if suexec is disabled. :(
     
  7. cPanelNick

    cPanelNick Administrator
    Staff Member

    Joined:
    Mar 9, 2015
    Messages:
    3,426
    Likes Received:
    2
    Trophy Points:
    38
    cPanel Access Level:
    DataCenter Provider
    Did you move mailman out of /usr/local/cpanel/3rdparty/mailman ?

    Did you build apache with the latest buildapache?
     
  8. chakky

    chakky Well-Known Member

    Joined:
    Sep 22, 2002
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    6
    Hi Nick,

    1.On a few servers I have moved mailman to /home/usr/mailman and set a symbolic link in /usr/local/3rdparty/mailman with ownership as mailman:mailman

    This was done due to sudden space limitations.

    But I have other servers where they are exactly in place but still have the problems.

    2.yes I have rebuilt apache on all servers especially since the vulnerability message came in the WHM

    Thanks for finally responding on this :)
     
  9. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    sorry to break topic...we show this in our WHM

    Apache Core 1.3.27

    what is the udated apache and how do you update it

    thanks
     
  10. regex123

    regex123 Registered

    Joined:
    Jun 25, 2002
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    mailman is quite particular in its setup.
    It relies on knowing the UID (not that actual username but the UID), and this will screw your mailman permissions up if the UID is not the mailman user.
     
Loading...

Share This Page