[Mailman-Users] {RW-Spam?} New install problems
Hi folks, I had mailman installed on a server that crashed badly. So, I have installed a fresh copy of mailman on a new server, or at least a new server for mailman. This server is the main mail server and secondary DNS server. Initially, the original mailman was installed an another server which was our secondary mail server and primary DNS server. So, essentially, I had to create mail aliases so that mail sent to any of the lists, were forwarded over to this now missing server for processing by mailman. Now, with the new install of mailman, it still seems to be trying to forward to the old server and I cannot find out where this is happening. We use postfix with all the email accounts stored in MySQL and Postfix admin as the front end to that. I can find no instances of a alias/forward to the old server and our aliases in /usr/local/mailman/data/aliases is correct. There is not such reference in /etc/aliases as well. I had no trouble setting up the new list and received no errors. Anyone perhaps have an idea what might be going on here and possible ways to troubleshoot this? Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] move messages
Hi, Is it possible to move just the messages and archive from one list to another? This would be the same instance of Mailman on the same server (obviously). Cheers Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Errors on mailman startup
Mark Sapiro wrote: Dave Filchak wrote: Well .. I have ran through most of the FAQs and the debugging techniques listed in them and all SEEMS like it is functioning correctly. I have also upgraded Mailman to 2.1.8 from 2.1.6 and I still have the exact same problem. After upgrading, I didn't run the debugging stuff again so I will try it again but I honestly do not think that it will help me. The exception occurs in the Python smtplib and is independent of the Mailman version. Did you actually do the test described in the post at http://mail.python.org/pipermail/mailman-users/2005-May/044976.html (linked from the FAQ) as the Mailman user? Yes. This test was fine. Did you actually try to send mail as described in the post at http://mail.python.org/pipermail/mailman-users/2005-May/044746.html (linked from the FAQ) as the Mailman user? This worked as well although, as I mention below, I am not logged in a mailman as mailman has no login shell and no password. Do I need to create one for mailman and try it again? If you did those as the Mailman user and they didn't show any error, then I can't explain why it fails when OutgoingRunner does the exact same thing. Did not do them as the mailman user but as another user (not root). User mailman has no login shell (/sbin/nologin) Should mailman need a login shell and passwd? It never has before and mailman was working. Again, there was a UPS failure at my ISP and the servers lost power abruptly so something might have happened then. But everything else is working, including regular mail. Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Errors on mailman startup
Mark Sapiro wrote: Dave Filchak wrote: Mark Sapiro wrote: Did you actually do the test described in the post at http://mail.python.org/pipermail/mailman-users/2005-May/044976.html (linked from the FAQ) as the Mailman user? Yes. This test was fine. Did you actually try to send mail as described in the post at http://mail.python.org/pipermail/mailman-users/2005-May/044746.html (linked from the FAQ) as the Mailman user? This worked as well although, as I mention below, I am not logged in a mailman as mailman has no login shell and no password. Do I need to create one for mailman and try it again? If you did those as the Mailman user and they didn't show any error, then I can't explain why it fails when OutgoingRunner does the exact same thing. Did not do them as the mailman user but as another user (not root). User mailman has no login shell (/sbin/nologin) Should mailman need a login shell and passwd? It never has before and mailman was working. Again, there was a UPS failure at my ISP and the servers lost power abruptly so something might have happened then. But everything else is working, including regular mail. No. Mailman doesn't need a login shell or a password. You should be able to do, e.g. sudo -u mailman /bin/bash in order to get a command shell running as mailman or sudo -u mailman python to get a python interpreter. It seems there is a permissions issue somewhere that is preventing mailman from accessing something. Make sure /etc/hosts and /etc/resolve.conf are world readable. If that isn't it, try to narrow it down by running the tests as mailman using sudo as above. OK .. ran both tests as mailman. First one was fine. Second one, while it shown no errors initially, I only received the email that was sent as a rcpt (secondary email address). The To: email address did not get delivered. The smtp-failure logs do not show a specific error for that email transaction but it still shows a ton of the same errors, i.e.: May 29 16:21:04 2009 (6489) Low level smtp error: (-2, 'Name or service not known'), msgid: mailman.1.1243617046.6486.some...@domain.net May 29 16:21:04 2009 (6489) delivery to some...@domain.org failed with code -1: (-2, 'Name or service not known') Both /etc/resolv.conf and /etc/hosts are world readable. I am truly stumped. Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman-Users Digest, Vol 63, Issue 53
snip OK .. ran both tests as mailman. First one was fine. Second one, while it shown no errors initially, I only received the email that was sent as a rcpt (secondary email address). The To: email address did not get delivered. The smtp-failure logs do not show a specific error for that email transaction but it still shows a ton of the same errors, i.e.: May 29 16:21:04 2009 (6489) Low level smtp error: (-2, 'Name or service not known'), msgid: mailman.1.1243617046.6486.some...@domain.net May 29 16:21:04 2009 (6489) delivery to some...@domain.org failed with code -1: (-2, 'Name or service not known') Both /etc/resolv.conf and /etc/hosts are world readable. I am truly stumped. That example won't deliver to any addresses in the message headers. Also, it won't log any errors. Error will be written to Python's stderr (normally the terminal). It sends to the addresses in the rcpts list as those are the only addresses communicated via SMTP. I.e., the envelope is sent to the rcpts regardless of what the message inside the envelope says. OK. I'm stumped too. Check the definitions of SMTPHOST and SMTPPORT in Defaults.py and possible overrides in mm_cfg.py to make sure they are 'localhost' and 0 respectively. OK .. well maybe something here. In Defaults.py SMTPHOST is set to 'localhost' In mm_cfg.py, it is set to the actual public IP of the server. Also, another thing that occurred to me at one point which I don't think makes any difference and which looked OK in your prior post of 'ps' output, but make sure that a sendmail process didn't start on it's own after the power failure. chkconfig --list sendmail or however you set these things on your system should show sendmail is off at all run levels. sendmail should only be run by MailScanner. sendmail is turned off at all levels. If your python is 2.4.x or later, you can use the technique described in the FAQ at http://wiki.list.org/x/-IA9 to obtain debugging info from Python's smtplib. The extra information will be written to Mailman's error log. No such luck. This is an older system running the latest available for this system (2.3.4) I am going to change mm_cfg.py to match Defaults.py or I guess I could just comment it out? Dave -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman-Users Digest, Vol 63, Issue 53
Mark Sapiro wrote: Dave Filchak OK .. well maybe something here. In Defaults.py SMTPHOST is set to 'localhost' In mm_cfg.py, it is set to the actual public IP of the server. I'm fairly sure if you just remove the SMTPHOST = 'xx.xx.xx.xx' from mm_cfg.py and restart Mailman, it will work. I'm also fairly sure that if you set SMTPHOST to the IP instead of localhost in the tests that they will fail. Of course, none of this will explain why it quit after the power outage, but I'm pretty sure the difference is a DNS issue. Yup ... just sent a test email to a test list we have set up and it seems to be working. It is so weird though ... there is really no way I can think of that these would change even after an unscheduled abrupt shutdown like we had. And the thing is, this server was up and running for two years before that and running mailman with no issues. It is like a ghost in the machine. Very crazy!! I wan to thank you for hanging in there with me. I really do appreciate it. Dave -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Errors on mailman startup
My ISP had a major power outage a while back and I realized that mailman was no longer running. When trying to start it again, I am getting the following errors: /usr/local/mailman/bin/mailmanctl start Starting Mailman's master qrunner. [r...@ebony ~]# Traceback (most recent call last): File /usr/local/mailman/bin/qrunner, line 270, in ? main() File /usr/local/mailman/bin/qrunner, line 230, in main qrunner.run() File /usr/local/mailman/Mailman/Queue/Runner.py, line 70, in run filecnt = self._oneloop() File /usr/local/mailman/Mailman/Queue/Runner.py, line 99, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 143, in dequeue fp = open(filename) IOError: [Errno 2] No such file or directory: '/usr/local/mailman/qfiles/out/1243356180.407516+c6c334592170b450a79140940b2a3ba17d3b962a.pck' Traceback (most recent call last): File /usr/local/mailman/bin/qrunner, line 270, in ? main() File /usr/local/mailman/bin/qrunner, line 230, in main qrunner.run() File /usr/local/mailman/Mailman/Queue/Runner.py, line 70, in run filecnt = self._oneloop() File /usr/local/mailman/Mailman/Queue/Runner.py, line 99, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 143, in dequeue fp = open(filename) IOError: [Errno 2] No such file or directory: '/usr/local/mailman/qfiles/out/1243535478.4113281+cdfdfd56b6ebc1b658ed9c772038562cb6090a8f.pck' When we tried to send a message to the list ... it does not get sent. Anyone have any idea about what might be going on? Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Errors on mailman startup
Mark Sapiro wrote: Dave Filchak wrote: My ISP had a major power outage a while back and I realized that mailman was no longer running. When trying to start it again, I am getting the following errors: /usr/local/mailman/bin/mailmanctl start Starting Mailman's master qrunner. [r...@ebony ~]# Traceback (most recent call last): File /usr/local/mailman/bin/qrunner, line 270, in ? main() File /usr/local/mailman/bin/qrunner, line 230, in main qrunner.run() File /usr/local/mailman/Mailman/Queue/Runner.py, line 70, in run filecnt = self._oneloop() File /usr/local/mailman/Mailman/Queue/Runner.py, line 99, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 143, in dequeue fp = open(filename) IOError: [Errno 2] No such file or directory: '/usr/local/mailman/qfiles/out/1243356180.407516+c6c334592170b450a79140940b2a3ba17d3b962a.pck' Traceback (most recent call last): File /usr/local/mailman/bin/qrunner, line 270, in ? main() File /usr/local/mailman/bin/qrunner, line 230, in main qrunner.run() File /usr/local/mailman/Mailman/Queue/Runner.py, line 70, in run filecnt = self._oneloop() File /usr/local/mailman/Mailman/Queue/Runner.py, line 99, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 143, in dequeue fp = open(filename) IOError: [Errno 2] No such file or directory: '/usr/local/mailman/qfiles/out/1243535478.4113281+cdfdfd56b6ebc1b658ed9c772038562cb6090a8f.pck' When we tried to send a message to the list ... it does not get sent. Anyone have any idea about what might be going on? See the FAQ at http://wiki.list.org/x/_4A9. If you go through the steps in that FAQ and still have a problem, see http://wiki.list.org/x/A4E9. Well .. this worked to get rid of the errors ... thank you. However, while I see no errors in the maillog, emails sent to mailman get delivered TO mailman but the emails are not forwarded to the list users. I have restarted mailman and run the cron job manually but still nothing. However, I tried to send an email from the command line and did not receive that either. I am using Sendmail with MailScanner but mail looks like it is being processed in the logs. ps aux | grep sendmail gives me: ps aux | grep sendmail root 16749 0.0 0.2 9128 3632 ?S19:24 0:00 sendmail: server 189.27.106.155.dynamic.adsl.gvt.net.br [189.27.106.155] cmd read root 17070 0.0 0.1 9384 3100 ?Ss 19:28 0:00 sendmail: accepting connections smmsp17074 0.0 0.1 7388 2564 ?Ss 19:28 0:00 sendmail: Queue run...@00:15:00 for /var/spool/clientmqueue root 17079 0.0 0.1 7560 2680 ?Ss 19:28 0:00 sendmail: Queue run...@00:15:00 for /var/spool/mqueue root 17569 0.0 0.2 9864 3588 ?S19:39 0:00 sendmail: server pool-96-241-183-254.washdc.fios.verizon.net [96.241.183.254] cmd read root 17633 0.0 0.0 4708 692 pts/2R+ 19:40 0:00 grep sendmail ps aux | grep MailScanner root 17106 0.0 1.4 27608 22028 ? Ss 19:28 0:00 MailScanner: master waiting for children, sleeping root 17107 0.2 2.1 40812 32752 ? S19:28 0:02 MailScanner: waiting for messages root 17126 0.2 2.1 41020 33028 ? S19:28 0:02 MailScanner: waiting for messages root 17131 0.2 2.1 41016 33068 ? S19:28 0:02 MailScanner: waiting for messages root 17681 0.0 0.0 5104 712 pts/2R+ 19:42 0:00 grep MailScanner Seems good though not sure about the line root 17106 0.0 1.4 27608 22028 ? Ss 19:28 0:00 MailScanner: master waiting for children, sleeping Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Errors on mailman startup
Mark Sapiro wrote: Dave Filchak wrote: My ISP had a major power outage a while back and I realized that mailman was no longer running. When trying to start it again, I am getting the following errors: /usr/local/mailman/bin/mailmanctl start Starting Mailman's master qrunner. [r...@ebony ~]# Traceback (most recent call last): File /usr/local/mailman/bin/qrunner, line 270, in ? main() File /usr/local/mailman/bin/qrunner, line 230, in main qrunner.run() File /usr/local/mailman/Mailman/Queue/Runner.py, line 70, in run filecnt = self._oneloop() File /usr/local/mailman/Mailman/Queue/Runner.py, line 99, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 143, in dequeue fp = open(filename) IOError: [Errno 2] No such file or directory: '/usr/local/mailman/qfiles/out/1243356180.407516+c6c334592170b450a79140940b2a3ba17d3b962a.pck' Traceback (most recent call last): File /usr/local/mailman/bin/qrunner, line 270, in ? main() File /usr/local/mailman/bin/qrunner, line 230, in main qrunner.run() File /usr/local/mailman/Mailman/Queue/Runner.py, line 70, in run filecnt = self._oneloop() File /usr/local/mailman/Mailman/Queue/Runner.py, line 99, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 143, in dequeue fp = open(filename) IOError: [Errno 2] No such file or directory: '/usr/local/mailman/qfiles/out/1243535478.4113281+cdfdfd56b6ebc1b658ed9c772038562cb6090a8f.pck' When we tried to send a message to the list ... it does not get sent. Anyone have any idea about what might be going on? See the FAQ at http://wiki.list.org/x/_4A9. If you go through the steps in that FAQ and still have a problem, see http://wiki.list.org/x/A4E9. I have found the following in the smtp-failure logs: failed with code -1: (-2, 'Name or service not known') I have tons of these. I Googled this and one of the issues appears to be not having search my.domain in my resolv.conf file. I have added this but I still cannot get mailman to deliver any mail. Would really appreciate it if anyone has any other ideas about this. Dave -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Errors on mailman startup
Well .. I have ran through most of the FAQs and the debugging techniques listed in them and all SEEMS like it is functioning correctly. I have also upgraded Mailman to 2.1.8 from 2.1.6 and I still have the exact same problem. After upgrading, I didn't run the debugging stuff again so I will try it again but I honestly do not think that it will help me. Dave Mark Sapiro wrote: Dave Filchak wrote: I have found the following in the smtp-failure logs: failed with code -1: (-2, 'Name or service not known') I have tons of these. I Googled this and one of the issues appears to be not having search my.domain in my resolv.conf file. I have added this but I still cannot get mailman to deliver any mail. Would really appreciate it if anyone has any other ideas about this. So the problem is that Outgoing Runner can't send mail, so all the outgong mail gets put in the retry queue and gets periodically retried, but continues to fail. There are two FAQs with information about this. http://wiki.list.org/x/AoE9 and http://wiki.list.org/x/-IA9. Thes, together with some archived posts they link to give some information and debugging techniques. The resolv.conf addition worked in one case, but it is not the only thing that can cause this nor the only solution. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] adding users to MailWatch
Why is it that when you add a domain administrator for a particular domain, you get the following error when they try to look at or add to the white or black lists: Username is not in the correct format to use this utility. For instance, I gave him the username of: domainuser with a password (not his actual email password). This allows him to log into MailWatch and see the mail and quarantines for his domain. However, he gets the error noted above when he tries to access the lists. If I change his username to [EMAIL PROTECTED], it allows him to access the lists but retrieves no rows from the database, even though there is mail quarantined. The other weird thing is that, even though he can access the lists, the format is wrong i.e. @[EMAIL PROTECTED] rather than @hisdomain.com. What am I missing? Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] adding users to MailWatch
Sorry ... obviously I should watch which list I am posting to. Obviously ... this was sent to the wrong list. Sorry for the noise. Dave Dave Filchak wrote: div class=moz-text-flowed style=font-family: -moz-fixedWhy is it that when you add a domain administrator for a particular domain, you get the following error when they try to look at or add to the white or black lists: Username is not in the correct format to use this utility. For instance, I gave him the username of: domainuser with a password (not his actual email password). This allows him to log into MailWatch and see the mail and quarantines for his domain. However, he gets the error noted above when he tries to access the lists. If I change his username to [EMAIL PROTECTED], it allows him to access the lists but retrieves no rows from the database, even though there is mail quarantined. The other weird thing is that, even though he can access the lists, the format is wrong i.e. @[EMAIL PROTECTED] rather than @hisdomain.com. What am I missing? Dave /div -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Ubuntu/ISPConfig/Postfix/Mailman Installation Issues
Ki Song wrote: I recently installed the following: Ubuntu Apache ISPConfig Postfix Mailman As far as I know, Ubuntu, Apache, ISPConfig, and Postfix are running ok. I verified this by: - ssh'ing into the ubuntu server - logging into the ISPConfig pages on the server using a browser - sending/receiving email through the Postfix server I believe I installed mailman properly using this guide: https://help.ubuntu.com/community/Mailman However, when I try to log into my installation of mailman using a browser: http://www.myhostname.com/cgi-bin/mailman/admin, there is a 404 error. The only error message I see that may be relevant is: NameVirtualHost myipaddress has no VirtualHosts mailman What should I do? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/submit%40zuka.net Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp I don't believe you need the cgi-bin here. I think it should be http://www.myhostname.com/mailman/admin Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman not sending mail to list members
Hello, I am running Mailman version 2.1.6 and recently had to move my servers from one data center to another. This necessitated a change of IPs. Since the move, Mailman has refused to send out posts from my lists. Mail gets to the host and is redirected through aliases to the proper location, but then seemingly disappears. To be truthful, mail from the test list does show up very sporadically, sometimes hours later. But ... 90% of the time .. nothing happens. I am also running Linux ebony.zuka.net 2.6.9-11.ELsmp #1 SMP Wed Jun 8 17:54:20 CDT 2005 i686 i686 i386 GNU/Linux This is CentOS release 4.1 (Final) This is Perl version 5.008005 (5.8.5) This is MailScanner version 4.63.8 I have checked all the logs and can find nothing that sticks out. Nothing, other than the IP numbers have changed after the move. I am stumped so I am hoping someone might be able to suggest somewhere to look and some sort of troubleshooting that I may have missed. Cheers Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Approved: password
Thanks for the reply. I am using Thunderbird and wanting to send html email to Mailman. I looked through the instructions on how to add a custom header and I am sad to say ... I don't get it. Any chance you can walk me through it? I have opened about:config but I am not sure what I am supposed to put in there and really don't want to screw up the install. Thanks Dave Mark Sapiro wrote: Dave Filchak wrote: I am trying to post to a one way (announce only) list using a user whose moderation bit is set, but am using the method described in the FAQ i.e. adding Approved: password to the first line of the body, with a carriage return and blank line after it. It keeps rejecting it with the standard Sorry, this is an announce only list ...etc etc. Can someone tell me if this still works and how and perhaps how I add this to the header rather than the body? Yes, it works. Possible things that might be wrong are: the password - it must be the list's admin or moderator password; neither the site password nor a member's password will work, and it must not have angle brackets around it. the format of the post - if the post is HTML, the Approved: line in the body won't work. The Approved: line must be the first non-blank line in the first text/plain part of the message. If it is, it is removed from that part and an attempt is made to remove it from all other text parts of the message, but the removal from other parts is not guaranteed to work. In general, if the post is simple plain text, or multipart/alternative with text/plain and text/html alternatives, the Approved: line will work and it will usually be removed from both parts of a multipart/alternative message, but it can be left in the text/html part under some circumstances. If the Approved: line is an actual header rather than a body line, it will always be recognized and removed regardless of the MIME structure of the message. How to add such a header or if it is even possible depends on the user agent (mail client) used to compose and send the mail. You used Thunderbird to send this post. See http://kb.mozillazine.org/Custom_headers for information on adding custom headers with Thunderbird. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] OT Approved: password
Thanks very much ... works like a charm. Dave Mark Sapiro wrote: Dave Filchak wrote: Thanks for the reply. I am using Thunderbird and wanting to send html email to Mailman. I looked through the instructions on how to add a custom header and I am sad to say ... I don't get it. Any chance you can walk me through it? I have opened about:config but I am not sure what I am supposed to put in there and really don't want to screw up the install. In about:config scroll down to mail.compose.other.header which probably says Status-default, Type-string and Value will be empty. Right-click that line (or control-click if you don't have a multi-button mouse), select 'modify' from the context menu and then enter 'Approved' (without quotes and without a colon) in the dialog box and click OK. Note that there might already be headers listed in the value of mail.compose.other.header if you have added any customized headers to any filters. If this is the case, just add Approved to the end of the list separated by a comma and no spaces. Then, when you are composing mail, if you click the down arrow you use to select To:, Cc:, etc. for addresses, you will be able to select Approved:. Do that and type the password on that line where you would normally type an email address. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Approved: password
I am trying to post to a one way (announce only) list using a user whose moderation bit is set, but am using the method described in the FAQ i.e. adding Approved: password to the first line of the body, with a carriage return and blank line after it. It keeps rejecting it with the standard Sorry, this is an announce only list ...etc etc. Can someone tell me if this still works and how and perhaps how I add this to the header rather than the body? Mailman Version 2.1.9 Thanks Dave -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] unmoderated user being moderated
Issue Solved: I feel a bit stupid but it turns out that the message they were trying to send was over the size limit set in the list. A dumb mistake but I will learn from it. Thanks everyone. Dave Heather Madrone wrote: Also, check to make sure that the list member is posting from his subscription address. You can add non-subscription addresses to the approved posters list in Privacy Options...Sender Filters to allow posts from a member's additional addresses to go through without moderation. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] unmoderated user being moderated
Can someone give me a hint why an umoderated user, for the purposes of posting to a one-way list, wold continually be moderated? I have double checked the moderation bit and it is off. Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] A wee bit of help
Hello all, I need just a wee bit of help. I have just set up Mailman on my secondary mail server host and the installation all is well I believe. I am trying to set the list so that it is in the form of [EMAIL PROTECTED] This domain is a domain that we host both web and mail for. However, I can see an issue with this in that if I send an email to the list using [EMAIL PROTECTED], the email will go to my main mail server which does not have this list on it, nor does it have the user list or list-bounces, nor any of the other required users for the list to operate properly. I have all the required aliases on my secondary mail server but do I need some sort of alias in my file on the main mail server to point these emails back to the secondary server? I get a user unknown error for the user lists and of course lists-bounce when I send an email to it. By the way, I am also trying to set this up as a one way or newsletter list. If I send an email to [EMAIL PROTECTED], I get a Sorry, only the site administrator can post to this list. which means I am communicating with the new list, although I should not be getting this message as the email I sent it through is in the admin list on Mailman. Any help with this would most sincerely be appreciated. TIA Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Continuing problem
OK .. I am having a hell of a time trying to get this working so would very much appreciate a helping hand from someone with more experience with Mailman than I. Here is what I want to happen: I want to have a one-way list (Newsletter). I have set this up so that everyone is moderated and I have three email address in the moderators and admin slots. All of these users are members of the list. I want to be able to send an email from one of the admin or moderator users to [EMAIL PROTECTED] clientdomain.com is not the same domain as the servers but it is a domain we host web and mail for. Here is what I have so far: The list is set up on the secondary mail server. The list set up went without a hitch and Mailman emailed me the following aliases to add to the aliases file, which I did and ran newaliases. turningpoints: |/usr/local/mailman/mail/mailman post turningpoints turningpoints-admin:|/usr/local/mailman/mail/mailman admin turningpoints turningpoints-bounces: |/usr/local/mailman/mail/mailman bounces turningpoints turningpoints-confirm: |/usr/local/mailman/mail/mailman confirm turningpoints turningpoints-join: |/usr/local/mailman/mail/mailman join turningpoints turningpoints-leave:|/usr/local/mailman/mail/mailman leave turningpoints turningpoints-owner:|/usr/local/mailman/mail/mailman owner turningpoints turningpoints-request: |/usr/local/mailman/mail/mailman request turningpoints turningpoints-subscribe:|/usr/local/mailman/mail/mailman subscribe turningpoints turningpoints-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe turningpoints I also added to the alias file on the main mail server, the following: turningpoints: |/usr/local/mailman/mail/mailman post turningpoints turningpoints-admin:|/usr/local/mailman/mail/mailman admin turningpoints turningpoints-bounces: |/usr/local/mailman/mail/mailman bounces turningpoints turningpoints-confirm: |/usr/local/mailman/mail/mailman confirm turningpoints turningpoints-join: |/usr/local/mailman/mail/mailman join turningpoints turningpoints-leave:|/usr/local/mailman/mail/mailman leave turningpoints turningpoints-owner:|/usr/local/mailman/mail/mailman owner turningpoints turningpoints-request: |/usr/local/mailman/mail/mailman request turningpoints turningpoints-subscribe:|/usr/local/mailman/mail/mailman subscribe turningpoints turningpoints-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe turningpoints so that when sending to the clients domain, the main server did not reject the user as unknown. No matter what I do, when I send an email to either [EMAIL PROTECTED] or [EMAIL PROTECTED], I receive a bounce message saying that only admins are allowed to post to the list, of which the email I sent the original post from is a member. I have even tried removing the moderated bit for that particular email address with the same result. What the hell am I missing?? TIA Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Continuing problem
Ok .. I know now what I was missing ... brain cells is what! It never occurred to me that I had to approve the messages I was sending because I never expected that if my email address was in the admin list that I would still get the bounce message. That was wrong. So that is not such a big deal although I would like it if I didn't get the bounce message but I though there was a way to pass an Approved flag with the list password in order to circumvent the moderation thing. I tried to add Approved: listpassword to the subject line and as well as the first line of the email with an empty line after it but the message still gets held for moderator approval. What am I doing wrong with that? Sorry for my dull head with the moderator thing. Cheers Dave Dave Filchak wrote: OK .. I am having a hell of a time trying to get this working so would very much appreciate a helping hand from someone with more experience with Mailman than I. Here is what I want to happen: I want to have a one-way list (Newsletter). I have set this up so that everyone is moderated and I have three email address in the moderators and admin slots. All of these users are members of the list. I want to be able to send an email from one of the admin or moderator users to [EMAIL PROTECTED] clientdomain.com is not the same domain as the servers but it is a domain we host web and mail for. Here is what I have so far: The list is set up on the secondary mail server. The list set up went without a hitch and Mailman emailed me the following aliases to add to the aliases file, which I did and ran newaliases. turningpoints: |/usr/local/mailman/mail/mailman post turningpoints turningpoints-admin:|/usr/local/mailman/mail/mailman admin turningpoints turningpoints-bounces: |/usr/local/mailman/mail/mailman bounces turningpoints turningpoints-confirm: |/usr/local/mailman/mail/mailman confirm turningpoints turningpoints-join: |/usr/local/mailman/mail/mailman join turningpoints turningpoints-leave:|/usr/local/mailman/mail/mailman leave turningpoints turningpoints-owner:|/usr/local/mailman/mail/mailman owner turningpoints turningpoints-request: |/usr/local/mailman/mail/mailman request turningpoints turningpoints-subscribe:|/usr/local/mailman/mail/mailman subscribe turningpoints turningpoints-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe turningpoints I also added to the alias file on the main mail server, the following: turningpoints: |/usr/local/mailman/mail/mailman post turningpoints turningpoints-admin:|/usr/local/mailman/mail/mailman admin turningpoints turningpoints-bounces: |/usr/local/mailman/mail/mailman bounces turningpoints turningpoints-confirm: |/usr/local/mailman/mail/mailman confirm turningpoints turningpoints-join: |/usr/local/mailman/mail/mailman join turningpoints turningpoints-leave:|/usr/local/mailman/mail/mailman leave turningpoints turningpoints-owner:|/usr/local/mailman/mail/mailman owner turningpoints turningpoints-request: |/usr/local/mailman/mail/mailman request turningpoints turningpoints-subscribe:|/usr/local/mailman/mail/mailman subscribe turningpoints turningpoints-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe turningpoints so that when sending to the clients domain, the main server did not reject the user as unknown. No matter what I do, when I send an email to either [EMAIL PROTECTED] or [EMAIL PROTECTED], I receive a bounce message saying that only admins are allowed to post to the list, of which the email I sent the original post from is a member. I have even tried removing the moderated bit for that particular email address with the same result. What the hell am I missing?? TIA Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dfilchak%40sympatico.ca Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Continuing problem
Also sorry for not snipping my last post. ;-( Dave Filchak wrote: Ok .. I know now what I was missing ... brain cells is what! It never occurred to me that I had to approve the messages I was sending because I never expected that if my email address was in the admin list that I would still get the bounce message. That was wrong. So that is not such a big deal although I would like it if I didn't get the bounce message but I though there was a way to pass an Approved flag with the list password in order to circumvent the moderation thing. I tried to add Approved: listpassword to the subject line and as well as the first line of the email with an empty line after it but the message still gets held for moderator approval. What am I doing wrong with that? Sorry for my dull head with the moderator thing. Cheers Dave snip -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Continuing problem
Crap .. sorry .. must have mis-pasted, if that is a word! What I actually have on the main server is: turningpoints: [EMAIL PROTECTED] turningpoints-admin:[EMAIL PROTECTED] turningpoints-bounces: [EMAIL PROTECTED] turningpoints-confirm: [EMAIL PROTECTED] turningpoints-join: [EMAIL PROTECTED] turningpoints-leave:[EMAIL PROTECTED] turningpoints-owner:[EMAIL PROTECTED] turningpoints-request: [EMAIL PROTECTED] turningpoints-subscribe:[EMAIL PROTECTED] turningpoints-unsubscribe: [EMAIL PROTECTED] Dave Mark Sapiro wrote: Dave Filchak wrote: OK .. I am having a hell of a time trying to get this working so would very much appreciate a helping hand from someone with more experience with Mailman than I. Here is what I want to happen: I want to have a one-way list (Newsletter). I have set this up so that everyone is moderated and I have three email address in the moderators and admin slots. All of these users are members of the list. I want to be able to send an email from one of the admin or moderator users to [EMAIL PROTECTED] clientdomain.com is not the same domain as the servers but it is a domain we host web and mail for. Here is what I have so far: The list is set up on the secondary mail server. The list set up went without a hitch and Mailman emailed me the following aliases to add to the aliases file, which I did and ran newaliases. snip The main server group above are wrong. They say that mail to (for example) [EMAIL PROTECTED] should be piped to /usr/local/mailman/mail/mailman on the main server which probably doesn't exist. Thet should probably be turningpoints: [EMAIL PROTECTED] turningpoints-admin:[EMAIL PROTECTED] and so on for the other 8 No matter what I do, when I send an email to either [EMAIL PROTECTED] or [EMAIL PROTECTED], If [EMAIL PROTECTED] works at all, you either have mailman installed on that machine or the aliases on that machine are not what you said. I receive a bounce message saying that only admins are allowed to post to the list, of which the email I sent the original post from is a member. I have even tried removing the moderated bit for that particular email address with the same result. What the hell am I missing?? See next reply. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Continuing problem
Yeah, I missed that. Thanks. Almost there now. I really do appreciate your patience. I will work on that sending Approve + password thing tomorrow as its not a huge deal. However, one thing that still is. I have configured the reply to in a way that I thought that the end user would see a reply-to address in the headers that was not a reply to the list. I have set the following: Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields): yes Should any existing Reply-To: header found in the original message be stripped? If so, this will be done regardless of whether an explicit Reply-To: header is added by Mailman or not. : no Where are replies to list messages directed? Poster is /strongly/ recommended for most mailing lists. : Explicit Address Explicit Reply-To: header.: [EMAIL PROTECTED] However I still see: From: [EMAIL PROTECTED] Reply-to: [EMAIL PROTECTED] Should the reply-to address not be [EMAIL PROTECTED] Thanks again, Dave Mark Sapiro wrote: Dave Filchak wrote: snip -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Not Authorized
Hello, I have just installed Mailman on CentOS4. Everything seems to be fine until I try to set up a new list. I have searched the archives and the general consensus is that when you receive a You are not authorized to create a new list error, it means that you are not entering the sitewidepass correctly or the List Creator's password correctly. I can assure you that I am entering these both correctly and have tried these many times and have re-created both passwords to be sure. So I am wondering if anyone can shed some light on this? As an aside, we did try to install Mailman using an RPM file but the web server does not run under apache so we uninstalled Mailman and reinstalled from source. I am wondering if the previous install of Mailman might be affecting things. All help is appreciated as I have a client anxiously awaiting use of Mailman. Cheers Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Not Authorized
OK ... sorry for the waste of bandwidth but I did figure it out. It appears as though the rpm install did leave some remnants about that were not working. The paths were wrong in the /etc/httpd/conf.d/mailman.conf file for the ScriptAlias and the Alias directives. Once I changed them to the proper location all was well. Thanks Dave Dave Filchak wrote: Hello, I have just installed Mailman on CentOS4. Everything seems to be fine until I try to set up a new list. I have searched the archives and the general consensus is that when you receive a You are not authorized to create a new list error, it means that you are not entering the sitewidepass correctly or the List Creator's password correctly. I can assure you that I am entering these both correctly and have tried these many times and have re-created both passwords to be sure. So I am wondering if anyone can shed some light on this? As an aside, we did try to install Mailman using an RPM file but the web server does not run under apache so we uninstalled Mailman and reinstalled from source. I am wondering if the previous install of Mailman might be affecting things. All help is appreciated as I have a client anxiously awaiting use of Mailman. Cheers Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dfilchak%40sympatico.ca Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] HTML Newsletter
Two questions: 1. Can I use Mailman to send out a simple HTML newsletter? 2. Is there a way to import or subscribe a list of members to a particular list .. i.e. a list that will receive the above newsletter? Thanks for your help. Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] cgi user
Hello all, At this point, I am using the default install of Mailman that came with RedHat 9 and have updated the rpms to the latest RedHat release. However, I have always ran apache as another user other than the default apache. So naturally, when I try to go to the initial default mailman list that I set up while doing the initial setup and config of Mailman, I get the error : Group mismatch error. Mailman expected the CGI wrapper script to be executed as one of the following groups: [apache], but the system's web server executed the CGI script as group: webadmin. Try tweaking the web server to run the script as one of these groups: [apache], or re-run configure providing the command line option: '--with-cgi-gid=webadmin'. So my question is, other than re-installing Mailman from source, is there a way to: A: change a config option in the current installation to allow this to execute cgi as user webadmin or B: re-install from RPM using an install option --with-cgi-gid=webadmin Any help would be appreciated. Cheers Dave David Filchak President - Zuka Inc. art | technology | strategy | solutions www.zuka.net | www.screamingmedia.ca -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] cgi user
Ah ha ... yes I'll give that a try. Cheers Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Todd Sent: December 6, 2003 2:42 PM To: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] cgi user *** PGP Signature Status: unknown *** Signer: Unknown, Key ID = 0xD654075A *** Signed: 06/12/2003 2:42:07 PM *** Verified: 06/12/2003 4:25:59 PM *** BEGIN PGP VERIFIED MESSAGE *** Dave Filchak wrote: At this point, I am using the default install of Mailman that came with RedHat 9 and have updated the rpms to the latest RedHat release. However, I have always ran apache as another user other than the default apache. So naturally, when I try to go to the initial default mailman list that I set up while doing the initial setup and config of Mailman, I get the error : Group mismatch error. Mailman expected the CGI wrapper script to be executed as one of the following groups: [apache], but the system's web server executed the CGI script as group: webadmin. Try tweaking the web server to run the script as one of these groups: [apache], or re-run configure providing the command line option: '--with-cgi-gid=webadmin'. So my question is, other than re-installing Mailman from source, is there a way to: A: change a config option in the current installation to allow this to execute cgi as user webadmin or B: re-install from RPM using an install option --with-cgi-gid=webadmin I don't think so, but rebuilding the rpm is simple enough and will keep all the settings except the cgi-gid setting exactly like your current rpm install. Just grab the mailman-2.1.1-4.src.rpm (or whatever version you have) and install it, which puts the spec file in /usr/src/redhat/SPECS/mailman.spec if you do this as root (you'll know where it goes if you've customized rpm to install source rpms as a normal user). Then edit the spec file to change the cgiuser and cgigroup settings near the top of the spec file, increment the Release field, update the changelog (optional, but useful when you want to remember why you have a different rpm installed than what redhat's shipping), and rebuild using rpmbuild -ba /path/to/mailman.spec. -- ToddOpenPGP - KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp == Tax reform is taking the taxes off things that have been taxed in the past and putting taxes on things that haven't been taxed before. -- Art Buchwald *** END PGP VERIFIED MESSAGE *** -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/dfilchak%40sympatico.ca -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org