Mailman 3 April 2015 - Mailman-Users

Re: [Mailman-Users] Issue with postfix-to-mailman.py (Command died with status 127)
by Laura Creighton 19 Apr '15

19 Apr '15

In a message of Sun, 19 Apr 2015 18:01:17 +0200, Matthieu Berjon writes: > > >On 04/19/2015 05:27 PM, Mark Sapiro wrote: >> On 04/19/2015 02:30 AM, Matthieu Berjon wrote: >>> Hello to all, >>> >>> I met an issue in trying to set up Mailman. Here is the error message I >>> get from postfix: >>> >>> Command died with status 127: >>> "/usr/local/mailman/postfix-to-mailman.py". Command >>> output: env: python: No such file or directory >> ... >>> /usr/local/mailman/postfix-to-mailman.py >>> >>> # Configuration variables - Change these for your site if necessary. >>> MailmanHome = "/usr/local/mailman"; # Mailman home directory. >>> MailmanOwner = "postmaster(a)earswideopen.net"; # Postmaster and abuse >>> mail recipient. >> >> >> Is the above missing something? I suspect the above is actually preceded >> by something like >> >> #! /usr/bin/env python >> >> and env is complaining that it can't find 'python' because there is no >> 'python' in $PATH (i.e. Postfix's search path). >> >> Also, please read <http://wiki.list.org/x/15564817> and the things >> linked from the last paragraph thereof. > >Thanks a lot to all of you. You let me to understand that >postfix-to-mailman.py was unecessary and not part of inital project. I >removed it from the equation, updated the postfix configuration and it >worked like a charm. > >Many thanks to all of you :) > >Have a good evening, >-- >Matthieu Berjon Very happy to help. Thank you for letting us know that things worked. Laura Creighton

1 0

Issue with postfix-to-mailman.py (Command died with status 127)
by Matthieu Berjon 19 Apr '15

19 Apr '15

Hello to all, I met an issue in trying to set up Mailman. Here is the error message I get from postfix: Command died with status 127: "/usr/local/mailman/postfix-to-mailman.py". Command output: env: python: No such file or directory I have a working postfix server running (at least, that's what I believe as emails for user account works). When I sent a message a message to the list, postfix seems to manage correctly the email and doesn't complain about it. My guess is that I probably missed something obvious or didn't understand something in the configuration. What I'm using: - FreeBSD 10.1-RELEASE-p6 - Postfix 2.11.4,1 - Mailman 2.1.20 Here some outputs that maybe would help. postconf -n alias_maps = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases command_directory = /usr/local/sbin config_directory = /usr/local/etc/postfix daemon_directory = /usr/local/libexec/postfix data_directory = /var/db/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 home_mailbox = Maildir/ html_directory = /usr/local/share/doc/postfix inet_protocols = ipv4 mail_owner = postfix mailman_destination_recipient_limit = 1 mailq_path = /usr/local/bin/mailq manpage_directory = /usr/local/man mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mydomain = earswideopen.net myhostname = smtp.earswideopen.net mynetworks_style = host myorigin = $mydomain newaliases_path = /usr/local/bin/newaliases queue_directory = /var/spool/postfix readme_directory = /usr/local/share/doc/postfix recipient_delimiter = + relay_domains = lists.earswideopen.net sample_directory = /usr/local/etc/postfix sendmail_path = /usr/local/sbin/sendmail setgid_group = maildrop smtpd_banner = $myhostname ESMTP $mail_name soft_bounce = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550 /etc/postfix/master.cf smtp inet n - n - - smtpd mailman unix - n n - - pipe flags=FR user=mailman:mailman argv=/usr/local/mailman/postfix-to-mailman.py ${nexthop} ${user} /usr/local/mailman/postfix-to-mailman.py # Configuration variables - Change these for your site if necessary. MailmanHome = "/usr/local/mailman"; # Mailman home directory. MailmanOwner = "postmaster(a)earswideopen.net"; # Postmaster and abuse mail recipient. By the way, this file belongs to mailman:mailman I'm quite lost on this error and didn't find any information about this kind of issue lately. If someone has some ideas, that would be much appreciated. If I forgot to mention something or if you need any more clarification, please ask, I will be more than happy to help. Have a great Sunday, -- Matt

3 3

Re: [Mailman-Users] Issue with postfix-to-mailman.py (Command died with status 127)
by Laura Creighton 19 Apr '15

19 Apr '15

>On 4/19/2015 4:30 AM, Matthieu Berjon wrote: >> Hello to all, >> >> I met an issue in trying to set up Mailman. Here is the error message I >> get from postfix: >> >> Command died with status 127: >> "/usr/local/mailman/postfix-to-mailman.py". Command >> output: env: python: No such file or directory >> >> >> I have a working postfix server running (at least, that's what I believe >> as emails for user account works). When I sent a message a message to >> the list, postfix seems to manage correctly the email and doesn't >> complain about it. Your problem is that env is complaining that it cannot find python. Therefore I would conclude that there is no python in Postfix's search path. Laura Creighton

1 0

Re: [Mailman-Users] Port is closed
by Mark Sapiro 19 Apr '15

19 Apr '15

On 04/19/2015 02:23 AM, EyeLand wrote: > control panel mailman http://vps1.ournet.biz/cgi-bin/mailman/admin/mailman It works for me. What is your issue? That URL works and returns Mailman's admin login page in Russian. If you are still having a problem, the issue is either your particular IP is being blocked by the server or it is somewhere in the route from you to the server. > root@vps1:~# netstat -L -n -t > netstat: invalid option -- 'L' Sorry, that should have been netstat -l -n -t but that is no longer relevant as we have already determined that the server is listening. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Port is closed
by EyeLand 19 Apr '15

19 Apr '15

Hello, on VPS port 80 is closed and I can not open control panel mailman, how open port, can you consult? Thank you.

2 2

Downgrade from 2.2.0a2 -> 2.1.20
by Odhiambo Washington 18 Apr '15

18 Apr '15

I am trying the above and I end up at: <cut> Downgrade detected, from version 0x20200a0 to version 0x20114f0 This is probably not safe. Exiting. *** Error code 1 Stop in /usr/home/wash/Tools/Mailman/2.1.20/mailman-2.1.20 </cut> I hope there is a way around this? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 "I can't hear you -- I'm using the scrambler."

2 2

3.0 testing...
by Farokh Irani 17 Apr '15

17 Apr '15

If I set up a machine to test 3.0, will I be able to simply install the official 3.0 release over it, or should I plan on doing a completely clean install? Thanks! Farokh ---------------------------------------------------------------------------- MCF Software...simply dependably engineered For all your computer and networking needs including hosting solutions for every need. Phone: 845-735-0210 Cell: 914-262-1594

2 2

The "right" way to reply to a mailing list
by Andrew Stuart 15 Apr '15

15 Apr '15

When I reply to a message on a mailing list, what is the “right” way to do it? Should I be deleting previous thread text from my response? Should I be adding anything in? Is there some general ideas for the “right” way to reply to a message on a list? as

31 147

Version number?
by Thomas Gramstad 15 Apr '15

15 Apr '15

How can I find out what version number of Mailman I'm using? Thomas Gramstad

3 3

force re-authentication in web UI
by Devin Reade 11 Apr '15

11 Apr '15

In the case where a list owner or moderator password has been compromised, or when performing a change of owner/moderator, one should obviously change the related passwords. However, if a former owner/moderator (or the person who stole the password) still has their browser open, their cookie is still valid and they can continue to access and change the list. I've been perusing the various docs to see if there is a method to purge state such that web UI users are required to re-authenticate (either globally or on a per-list basis), but cannot find anything. Simply restarting apache isn't sufficient (determined emperically). Does this feature exist? If so, any pointers are appreciated. Running mailman-2.1.16 with httpd-2.2.15. Devin

2 1