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 mailinglist

Discussion in 'E-mail Discussions' started by adapter, Oct 13, 2003.

  1. adapter

    adapter Well-Known Member
    PartnerNOC

    Joined:
    Sep 17, 2003
    Messages:
    391
    Likes Received:
    0
    Trophy Points:
    16
    Hello

    the mailman 2.1.2 mailinglist have stop to work when i make a new mailinglist or i subscribe a new email address that require confirmation i dont get any email, also when not require confirmation mailman show that the email address is succeful add but isn't ;( any idea?

    cPanel.net Support Ticket Number:
     
  2. mickeymouse

    mickeymouse Well-Known Member

    Joined:
    Sep 16, 2003
    Messages:
    389
    Likes Received:
    0
    Trophy Points:
    16
    Dear adapter,

    Start out by checking Mailman and MTA logs they are the best source for information about the problem.

    The most frequent reasons for this are:
    1) You didn\'t setup the cronjobs needed by Mailman.
    --- Check the crontab for the mailman user and make sure the mailman entries are there. You can even try restarting the cron.

    2) You haven\'t properly setup the aliases for your list.
    ---The newlist command is used to print necessary aliases for the list. You will need to copy/add them to the alias file used for list setup present at ~mailman/data/aliases.

    3) You haven\'t run `newaliases` to \"compile\" the new aliases into a hash table or DBM. (Sendmail and Postfix)
    --- Run \'newaliases\' as root. For postfix users you will also need to do a \'postfix reload\'.

    4) You haven\'t configured your MTA to find the alias file you are using for your lists.
    ----For setting this up you can see the related documentaion. For exim users it is present at http://www.exim.org/howto/mailman.html.

    5) You haven\'t run the Mailman qrunner daemon (~mailman/bin/mailmanctl or ~mailman/scripts/mailman).
    --- This has to be run regardless of you MTA. You can refer the installation documentation.

    6) Check if you have set these variables.

    DEFAULT_URL_HOST = \'your.url.addess\'
    DEFAULT_EMAIL_HOST = \'your.host.name\'
    and added the following directive
    add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

    You have to make changes the following changes in mm_cfg.py

    7) Check if any Locks are set.
    ---- ls -l ~mailman/locks
    The output will be something like:
    qrunner.lock.moya.trilug.org.23423
    It indicate that process #23423 created the lock. To look at this process give
    ps aux | grep 23423 | grep -v grep

    Hope this might help you solve your problem.

    Regards,
     
Loading...

Share This Page