Koozali.org: home of the SME Server

Mailman on SME-10 : I'm Confounded

Offline mdrone

  • 19
  • +0/-0
Mailman on SME-10 : I'm Confounded
« on: April 10, 2022, 01:38:30 PM »
Hello Everyone,

With the perpetual urgent notice that "SME Server 9 is obsolete and potentially INSECURE", I installed SME-10 and have hit a stumbling block with the Mailman contrib. Let me preface this by saying that installation was flawless and the web interface works as expected. No issues creating or managing lists. I would also like to say that I have Mailman running on two SME-9.2 servers and have never had any problems.

The most pressing issue I have is that I can't send mail to the test@mydomain mailing list that I set up. The logs reveal nothing (at least nothing that points to a problem that I can decipher). All the DNS acronym alphabet items are in place (SPF, DKIM, DMARC). Just to make sure it wasn't server-related, I also installed the ezmlm contrib package, set up a test list and was able to send/receive mail through that list with no problems whatsoever. I've been watching log files (with tail -f) during email transactions trying to see where the problem lies, but I'm not smart enough to figure it out. The differences between the SME-9.2 server's mailman install and the SME-10 server's mailman install appear to be that the SME-9.2 uses Mailman version 2.1.12 and Python 2.6.6, whereas SME-10 uses Mailman version 2.1.15 and Python 2.7.5. It's doubtful that those differences are significant to the problem I'm having.

Two other issues that I'm scratching my head about are:
(1) I find that I have to issue the "/opt/mailman/bin/check_perms -f" command every couple of days because permissions on one of the files changes (apologies for not recording the filename and including it here . . . my negligence)
(2) I also find that "/opt/mailman/bin/mailmanctl status" tells me that mailman isn't running and I have to manually start it.

If anyone has any insight into potential solutions to any (or all) of these problems, I would certainly be grateful.

Thanks,
-MD

Offline Jean-Philippe Pialasse

  • *
  • 2,746
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Mailman on SME-10 : I'm Confounded
« Reply #1 on: April 10, 2022, 06:28:01 PM »
The most pressing issue I have is that I can't send mail to the test@mydomain mailing list that I set up. The logs reveal nothing (at least nothing that points to a problem that I can decipher). All the DNS acronym alphabet items are in place (SPF, DKIM, DMARC). 
that is an issue indeed


Just to make sure it wasn't server-related, I also installed the ezmlm contrib package, set up a test list and was able to send/receive mail through that list with no problems whatsoever. I've been watching log files (with tail -f) during email transactions trying to see where the problem lies, but I'm not smart enough to figure it out.
maybe you could paste here the log, so we can have a look and help.


The differences between the SME-9.2 server's mailman install and the SME-10 server's mailman install appear ...
well you forgot the major change: systemd ! as pointed by your problem (2)


Two other issues that I'm scratching my head about are:
(1) I find that I have to issue the "/opt/mailman/bin/check_perms -f" command every couple of days because permissions on one of the files changes (apologies for not recording the filename and including it here . . . my negligence)
please report it so we can fix it



(2) I also find that "/opt/mailman/bin/mailmanctl status" tells me that mailman isn't running and I have to manually start it.
this might need to be bugged to be fixed, well it is already

https://bugs.koozali.org/show_bug.cgi?id=11278#c17

have you tried creating the list after lauching the service, and trying to send to the list after it has been launched on a list created while it was running ?


Offline mdrone

  • 19
  • +0/-0
Re: Mailman on SME-10 : I'm Confounded
« Reply #2 on: April 11, 2022, 02:50:38 PM »
  • maybe you could paste here the log, so we can have a look and help.
    please report it so we can fix it
    have you tried creating the list after launching the service, and trying to send to the list after it has been launched on a list created while it was running ?
Thanks for the response and suggestions.

Per your advice, I created another list after making sure all Mailman processes were up and running.

When creating a list . . . this is the message that appears on the screen:

Bug in Mailman version 2.1.15
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.


Examining the /var/log/mailman/error reveals quite a few things that I wasn't looking at before (I was watching qmail and qpsmtpd logs). Have a look . . .

   https://lists2.roe3.org/mdrone/error.txt

The scripts in this particular installation seem to be having problems writing to subdirectories in /var/spool/mailman/qfiles/ complaining that there is "No such file or directory" when in fact those directories do indeed exist. Ownership doesn't seem to be a problem as all subdirectories are owned by group:mailman user:mailman and permissions are drwxrws---

Here's the error that appears when I run the /opt/mailman/bin/check_perms script (typically after a server reboot):

   /opt/mailman/bin/check_perms
   /usr/lib/mailman/Mailman/mm_cfg.py bad group (has: root, expected mailman)
   Problems found: 1
   Re-run as mailman (or root) with -f flag to fix

Other logs don't seem that much different from the fully functional SME-9.2 Mailman installations . . .

cat /var/log/qmail/current | grep test2

@4000000062532d473631fc3c info msg 1551599: bytes 2464 from <test2-bounces@lists2.roe3.org> qp 25075 uid 453
@4000000062532d480985d014 info msg 1578337: bytes 2462 from <test2-bounces@lists2.roe3.org> qp 25080 uid 453
@4000000062532d9c2c6fc544 starting delivery 47: msg 1551599 to local alias-localdelivery-test2@lists2.roe3.org
@4000000062532d9c32e7845c starting delivery 48: msg 1551601 to local test2@dell-emc.lists2.roe3.org

cat /var/log/qpsmtpd/current | grep test2
@4000000062532d4731097974 25073 dispatching mail FROM:<test2-bounces@lists2.roe3.org> size=1719
@4000000062532d47310c7714 25073 250 <test2-bounces@lists2.roe3.org>, sender OK - how exciting to get mail from you!
@4000000062532d4733129b9c 25073 (queue) logging::logterse: ` 127.0.0.1   localhost   dell-emc.lists2.roe3.org   <test2-bounces@lists2.roe3.org>   <mdrone@gmail.com>   queued      <mailman.0.1649618236.25072.test2@lists2.roe3.org>   
@4000000062532d473636e224 25073 250 Queued! 1649618237 qp 25075 <mailman.0.1649618236.25072.test2@lists2.roe3.org>
@4000000062532d473ae0420c 25076 (queue) logging::logterse: ` 127.0.0.1   localhost   dell-emc.lists2.roe3.org   <mailman-bounces@lists2.roe3.org>   <mdrone@gmail.com>   queued      <mailman.1.1649618236.25072.test2@lists2.roe3.org>   
@4000000062532d480292591c 25076 250 Queued! 1649618238 qp 25078 <mailman.1.1649618236.25072.test2@lists2.roe3.org>
@4000000062532d480510593c 25079 dispatching mail FROM:<test2-bounces@lists2.roe3.org> size=1717
@4000000062532d4805144cf4 25079 250 <test2-bounces@lists2.roe3.org>, sender OK - how exciting to get mail from you!
@4000000062532d48063fe05c 25079 (queue) logging::logterse: ` 127.0.0.1   localhost   dell-emc.lists2.roe3.org   <test2-bounces@lists2.roe3.org>   <mdrone@roe3.org>   queued      <mailman.2.1649618236.25072.test2@lists2.roe3.org>   
@4000000062532d4809897994 25079 250 Queued! 1649618238 qp 25080 <mailman.2.1649618236.25072.test2@lists2.roe3.org>
@4000000062532d480c426f74 25082 (queue) logging::logterse: ` 127.0.0.1   localhost   dell-emc.lists2.roe3.org   <mailman-bounces@lists2.roe3.org>   <mdrone@gmail.com>   queued      <mailman.3.1649618236.25072.test2@lists2.roe3.org>   
@4000000062532d4810034034 25082 250 Queued! 1649618238 qp 25083 <mailman.3.1649618236.25072.test2@lists2.roe3.org>
@4000000062532d9b28a6f98c 25096 dispatching RCPT TO:<test2@lists2.roe3.org>
@4000000062532d9b28c37e54 25096 250 <test2@lists2.roe3.org>, recipient ok
@4000000062532d9c24dfb85c 25096 (queue) logging::logterse: ` 209.85.167.49   mail-lf1-f49.google.com   mail-lf1-f49.google.com   <mdrone@gmail.com>   <test2@lists2.roe3.org>   queued      <CANq2t75QnbAafeNyQjwK8Z_6vVWBUp-VpBXFpcN2CT5x047jjg@mail.gmail.com>   

Offline Jean-Philippe Pialasse

  • *
  • 2,746
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Mailman on SME-10 : I'm Confounded
« Reply #3 on: April 11, 2022, 08:40:52 PM »
try the new version in smetest. there are two but yum will pull the newest.

i hit the bug and fixed it yesterday. 

confirm it is better and i release it.

Offline mdrone

  • 19
  • +0/-0
Re: Mailman on SME-10 : I'm Confounded
« Reply #4 on: April 12, 2022, 12:38:03 PM »
try the new version in smetest. there are two but yum will pull the newest.

i hit the bug and fixed it yesterday. 

confirm it is better and i release it.
Many thanks for your work on this.

After installing smeserver-mailman-1.5.0-13.el7.sme.noarch.rpm from smetest . . .

# /opt/mailman/bin/check_perms

directory must be at least 0755: /var/spool/mailman/qfiles
/usr/lib/mailman/Mailman/mm_cfg.py bad group (has: root, expected mailman)
/usr/lib/mailman/bin/smelist.pl bad group (has: root, expected mailman)
Problems found: 3
Re-run as mailman (or root) with -f flag to fix

I ran it with the -f flag and then went through the post-upgrade/reboot sequence just to see the effect.

After signal-event post-upgrade; signal-event reboot

# /opt/mailman/bin/check_perms
/usr/lib/mailman/Mailman/mm_cfg.py bad group (has: root, expected mailman)
Problems found: 1
Re-run as mailman (or root) with -f flag to fix

Hmmm . . . this is an issue that continues to haunt.

I checked tail -n 50 /var/log/mailman/error.  Nothing new written to it since Apr 10. That's a good sign given today is Apr 12.

On a whim, I took a look at the output of # systemctl -l status mailman

https://lists2.roe3.org/mdrone/systemctl.png

Everything looks nominal.

Still no luck sending mail through the mailman list(s).

Offline Jean-Philippe Pialasse

  • *
  • 2,746
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Mailman on SME-10 : I'm Confounded
« Reply #5 on: April 12, 2022, 06:53:27 PM »
just do not run this script, it has no knowledge of sme specific, and reverse the initial values please, except for folder 755 which is ok and  i will fix that.


smelist.pl HAVE TO BE root:root

smelist c wrapper call it as setuid to allow the execution of the script as root or creation of qmail alias and update of sme db will fail


for lists created before the fix.  you will have to remove them from mailman and create them again, as they are not in sme db and unknown of qmail

Offline mdrone

  • 19
  • +0/-0
Re: Mailman on SME-10 : I'm Confounded
« Reply #6 on: April 12, 2022, 09:14:52 PM »
just do not run this script, it has no knowledge of sme specific, and reverse the initial values please, except for folder 755 which is ok and  i will fix that.


smelist.pl HAVE TO BE root:root

smelist c wrapper call it as setuid to allow the execution of the script as root or creation of qmail alias and update of sme db will fail


for lists created before the fix.  you will have to remove them from mailman and create them again, as they are not in sme db and unknown of qmail

Good sir . . . you are a wizard!  I changed the ownership on the /opt/mailman/bin/smelist.pl script to root:root, removed the existing lists, re-created one of them, and VOILA! It works! Merci beaucoup!

Offline Jean-Philippe Pialasse

  • *
  • 2,746
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Mailman on SME-10 : I'm Confounded
« Reply #7 on: April 13, 2022, 02:23:05 AM »
and some more kudos

i added a stronger password for admin on initial creation (no change if you already have it set

enabled as default

default is admin and archive only lan accessible and listinfo /subscribe/options available to public. 

all settings available in manager

in smetest currently.