Mailman issues

There was a recent mailman issue, when the customer tries to login to his mailing list it will not let him and it just times out. When we ran fix mailman script in the server, we got the error:

The locks for some lists could not be acquired.

This means that either Mailman was still active when you upgraded, or there were stale locks in the
/usr/local/cpanel/3rdparty/mailman/locks directory.

mailman got its own log files in the location: /usr/local/cpanel/3rdparty/mailman/logs

# ls -1 /usr/local/cpanel/3rdparty/mailman/logs
./
../
bounce
error*
locks*
post
qrunner*
smtp*
smtp-failure

You can check the logs to get the correct errors that is produced. In our scenario we checked the log 'locks' and found the error on the mailing list as follows:

" manage_netswest.org.lock lifetime has expired, breaking "
This error can be corrected by the following steps:
- first backup the directory /usr/local/cpanel/3rdparty/mailman/locks
- cd /usr/local/cpanel/3rdparty/mailman/locks
- remove the 'lock' files associated with that mailing list eg : rm -rf manage_netswest.org.lock*
- then killall mailman processes obtained from the command: ps aux | grep mail
- restart mailman /scripts/restartsrv_mailman
- run the fix mailman script: /scripts/fixmailman
- done. Try loggin in now.


If you still face isuses you could try the following scripts to check for permi carbon.elinuxservers.com ssion issues:
cd /usr/local/cpanel/3rdparty/mailman/bin/
./check_perms --> to check the permissions of the files and directories associated with mail man.
./check_perms -f --> to fix the permissions

Please update more issues regarding mailman that you come across to this post.

Another issue that we faced recently was the archives still listed even after deleting
After deleting the archives from archives/private folder, you need to rebuild the archive mailing list

mv pipermail.pck pipermail.pck.bkp /usr/local/cpanel/3rdparty/mailman/bin/arch mailinglist_name