Re: [Mailman-Users] can't make a new list from the GUI
On Tue, 2005-05-24 at 13:52 -0700, Bo Gusman wrote: > On my FC3 box w/o SELinux, I just installed and configured the mailman > rpm according to the instructions at the mailman website. I can create a > list from the command line and can send mail to it and receive mail from > it. I can load the web interface and do most of the usual things. > However, I cannot create a new list. I've reset the site password > assuming that I missentered it somehow, but I get no change in behavior. > > Any clues? Did you install the Red Hat rpm? Are you positive SELinux is disabled? There was a bug in the FC3 security policy that caused web based list creation to fail, command line worked fine. Have you looked for error messages in /var/log/mailman/error and /var/log/messages (in /var/log/messages you especially want to look for lines with "avc") -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Installation/Config Problems
On Mon, 2005-05-23 at 14:38 -0400, Pelkey, Jeff wrote: > Greetings, > > I will start by saying that I both a newbie to both Mailman and Python, > although I have worked with Perl for years. I have installed Mailman 2.1.5 > and integrated with Postfix v2.1.5. I have search the FAQ's with little > success. > > The Mailman issue is that when I try to add the Mailman alias db using the > following line in main.cf: > alias_maps = > hash:/etc/aliases,hash:/etc/postfix/aliases,hash:/usr/local/mailman/data/aliases > > I get the following error messages: > May 23 11:53:27 dev postfix/smtpd[19360]: [ID 947731 mail.crit] fatal: > unsupported dictionary type: hash The following command will print out a list of supported map types: % postconf -m Is hash one of them? It would be surprising if it weren't, but this is the first place to start looking. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Mailman Bug?/no Admin level web access
On Tue, 2005-05-17 at 21:33 -0400, [EMAIL PROTECTED] wrote: > Mailman created a new file, but the others show as plain text and the > new one as octet stream. I'm afraid I don't understand. What "others" and what do you mean the new log file is octet stream? > Right now I'm at accept all on ports/firewall, with SELinux enabled > and enforcing but turned off on the httpd daemon. I can access all of > the pages except the Admin ones. Please turn ALL of SELinux off. There are many parts of the security policy that might come into play, not just httpd. For instance mailman has its own security policy that is mated to the red hat mailman rpm's, which you're not using, there is a tremendous opportunity here for problems due to the mismatch. Let's try to eliminate SELinux as a factor altogether. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Mailman Bug?/no Admin level web access
On Tue, 2005-05-17 at 13:02 -0400, [EMAIL PROTECTED] wrote: > May 10th was the day I put in the new hard drive after the old one > died. So basically I did a clean install. I had set up the domain/host > stuff on the old drive so all I did was reinstall. I only have one > domain/host name, and SELinux is on, but not on the snmpd daemon. How did you reinstall? This is important to determine if the security labels were applied. SELinux's control of smtpd is not relevant, its the httpd (e.g. apache) policy that probably affecting you. (I assume when you say the admin interface is not working you mean web access to it). Did you look for avc messages in /var/log/messages? Did you look at /var/log/audit/audit.log? (may not be present) -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Plain text attachments
On Mon, 2005-05-16 at 11:40 -0600, Joshua Ginsberg wrote: > Sorry to bug y'all again... A recent posting was composed as an HTML > email in MS Outlook 2k3... I've got the list configured to have a plain > text footer with the unsubscribe information... In MS Outlook, Outlook > Express, Horde IMP, and Apple Mail, the plain text footer was listed as > an attachment but not displayed inline. Is there something stupid I'm > doing to prevent the footer from being displayed inline? I usually send > out plain text posts, so this whole posting HTML thing is new to me. > Thanks! http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.039.htp -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
[Mailman-Users] group mismatch FAQ
The question of group mismatches comes up so often and people are often confused about the role of the different entities in this process I decided to write up a FAQ entry that explains how things work. 6.16. Understanding group mismatch errors - how mailman implements security ** http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.016.htp -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Group mismatch error
On Wed, 2005-05-11 at 17:12 +0100, John Poltorak wrote: > On Wed, May 11, 2005 at 09:08:40AM -0400, John Dennis wrote: > > On Tue, 2005-05-10 at 23:45 +0100, John Poltorak wrote: > > > Can someone explain what I need to do when I get this error - I don't > > > want > > > to have to re-run configure. > > > > > > Group mismatch error. Mailman expected the mail > > > wrapper script to be executed as group "mail", but > > > the system's mail server executed the mail script as > > > group "mailnull". Try tweaking the mail server to run the > > > script as group "mail", or re-run configure, > > > providing the command line option `--with-mail-gid=mailnull'. > > > 554 5.3.0 unknown mailer error 2 > > > > As has beem said, you have two choices, either re-configure, re-build, > > or change how your MTA executes child processes (or possibly just how > > your MTA executes) > > > > If this was working before then something must have changed with your > > MTA, but you didn't say which MTA you're using. Some MTA's can be > > configured via their config file to run with specific identities (e.g. > > the postfix mail_owner parameter). Ths is an MTA issue, please consult > > your MTA documentation. > > > I'm using sendmail but don't know which permissions need changing. I > thought this would have been the file which needed the correct > permissions:- > > > # ls -al /usr/local/mailman/mail > total 48 > drwxrwsr-x2 root mailman 4096 Jan 31 2004 . > drwxrwsr-x 20 root mailman 4096 Mar 19 2003 .. > -rwxr-sr-x1 root mailman 39385 Jan 31 2004 mailman No, this is the wrapper, the wrapper is trying to verify the identity of the process which is invoking it, which is your MTA. The wrapper is built with the MTA's gid in (via the --with-mail-gid parameter). > If I have mailman running with UID root, I don't understand what the > problem is. Should I just add mailman to the mail group? No, you've got this backwards. What is going on is that your MTA invokes the mailman wrapper. The wrapper in effect says "I will only execute if and only if I trust the program that invoked me, which must be an MTA". It makes that decision by looking at the group of the program that invoked it and compares it to the group that was inserted into its source code via the --with-mail-gid parameter. If those two groups match it trusts this is really the MTA that is asking mailman to process mail. The problem you're having is that the MTA that is invoking mailman is not running with the group identity that you told mailman it would execute with when you built it. > I guess this sounds like a FAQ... Yes, actually I wrote up a whole explanation of this a few weeks back on the developers list because this is so much misinformation and confusion with respect to this issue. It's time to get that into the FAQ. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Group mismatch error
On Tue, 2005-05-10 at 23:45 +0100, John Poltorak wrote: > Can someone explain what I need to do when I get this error - I don't want > to have to re-run configure. > > Group mismatch error. Mailman expected the mail > wrapper script to be executed as group "mail", but > the system's mail server executed the mail script as > group "mailnull". Try tweaking the mail server to run the > script as group "mail", or re-run configure, > providing the command line option `--with-mail-gid=mailnull'. > 554 5.3.0 unknown mailer error 2 As has beem said, you have two choices, either re-configure, re-build, or change how your MTA executes child processes (or possibly just how your MTA executes) If this was working before then something must have changed with your MTA, but you didn't say which MTA you're using. Some MTA's can be configured via their config file to run with specific identities (e.g. the postfix mail_owner parameter). Ths is an MTA issue, please consult your MTA documentation. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] mailman-postfix problem
On Tue, 2005-05-10 at 15:07 +1000, Lie, Jafaruddin wrote: > Hi gang > > Just joined the mailing list *waves to everyone > > I have problems getting mailman to run with postfix. Here's the story: > mailman installation went ok and it ran ok with sendmail. When I > installed and used system-switch-mail to switch to postfix, the problem > began. > > The setup: > I am setting mailman to run internally, so we have local mail accounts > on my fedora box ([EMAIL PROTECTED]) not accessible to the outside > world, only locally and anyone on the domain x.x.x. > > The postfix installation went ok, I can send and receive mails from my > local accounts just fine. I configured mailman in mm_cfg.py to use > postfix as the MTA. I followed the instruction on > http://www.gnu.org/software/mailman...all/node13.html. > > The problem: > I created one mailing list, with 3 email addresses suscribed to it. One > is my local mail account ([EMAIL PROTECTED] which is forwarded to > [EMAIL PROTECTED]) and two are addresses from x.x.x, lets call it > [EMAIL PROTECTED] and [EMAIL PROTECTED] These are real email addresses, > accessible > from the internet > > With sendmail, the mailing list works just fine. All the accounts can > send and receive emails from the list. > With postfix, only the local account can. The other two email addresses > can send to the list, but they will not receive anything from it. The > error message I get from /var/log/maillog: > > May 10 12:11:24 fedora postfix/smtpd[4341]: connect from > localhost.localdomain[127.0.0.1] > May 10 12:11:24 fedora postfix/smtpd[4341]: NOQUEUE: reject: RCPT from > localhost.localdomain[127.0.0.1]: 550 <[EMAIL PROTECTED]>: Recipient address > rejected: User unknown in local recipient table; > from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP > helo= > May 10 12:11:24 fedora postfix/smtpd[4341]: C36F82CC285: > client=localhost.localdomain[127.0.0.1] > May 10 12:11:24 fedora postfix/cleanup[4344]: C36F82CC285: > message-id=<[EMAIL PROTECTED]> > May 10 12:11:24 fedora postfix/qmgr[3071]: C36F82CC285: > from=<[EMAIL PROTECTED]>, size=2571, nrcpt=1 (queue > active) > May 10 12:11:24 fedora postfix/smtpd[4341]: disconnect from > localhost.localdomain[127.0.0.1] > May 10 12:11:24 fedora postfix/local[4345]: C36F82CC285: > to=<[EMAIL PROTECTED]>, orig_to=<[EMAIL PROTECTED]>, relay=local, delay=0, > status=sent (delivered to mailbox) > May 10 12:11:24 fedora postfix/qmgr[3071]: C36F82CC285: removed > > > That's when I send from my real email address to the list. Similar > error, about User unknown in local recipient table. > The only way I can get it to send is if I add the two email addresses > into the /etc/aliases file, something like daryl: [EMAIL PROTECTED] > Considering the list will contain a lot of people, I don't want to be > entering the aliases in the /etc/aliases when mailman obviously has the > email address stored in /etc/mailman/aliases and > /etc/mailman/aliases.db. > > What I have done: > I have ran postmap and postalias to /etc/aliases/ and > /etc/mailman/aliases, have changed /etc/postfix/main.cf, the alias_maps > to read: > Code: > alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases > > > I am at lost here, and about to pull out my hair.. Any suggestions? Yes, read this documentation :-) /usr/share/doc/postfix-*/README_FILES/LOCAL_RECIPIENT_README It looks like what is happening is that the two addresses that are failing are being interpreted by postfix as being local, which you claim they are not (I assume because local == fedora.x.x.x and non-local == x.x.x). Postfix by default won't attempt delivery to local users that don't exist (that would be pretty pointless wouldn't it?). So how does postfix determine who is local? It matches the domain in the email address against $mydestination or the IP addresses in $inet_interfaces or $proxy_interfaces. I suspect one of these is not properly configured in /etc/postfix/main.cf. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Help with Mailman 2.1 on RedHat 9
On Mon, 2005-05-09 at 20:27 -0700, DJ Freak wrote: > I am using the default Mailman 2.1 installed by RedHat. I can manage > groups via listinfo in my web browser and even add and remove members > to the groups that I create; plus, the mail log indicates that > messages are relayed on their merry way to the correct Mailman > commands location however no posts or admin mails are ever sent or > received. > > The big clue here is that when I go to >File "./mailmanctl", line 274, in check_privs > gid = grp.getgrnam(mm_cfg.MAILMAN_GROUP)[2] > KeyError: getgrnam(): name not found You don't say which mailman rpm you've installed. There was a bug several years ago in one of our rpm's where the variables MAILMAN_USER and MAILMAN_GROUP were not defined and one would get this error as a consequence. That bug has long since been fixed but you may have installed that rpm if you are working with an old distribution. The fix is to either add MAILMAN_USER = 'mailman' MAILMAN_GROUP = 'mailman' at the top of your mm_cfg.py file -or- upgrade to a newer rpm. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Cron error: /usr/bin/python -S /var/lib/mailman/cron/checkdbs
On Mon, 2005-05-09 at 08:09 -0700, James wrote: > I have yet another cron error that I get every day in my mail. I'm not > sure what it is. > > > > Cron <[EMAIL PROTECTED]> /usr/bin/python -S /var/lib/mailman/cron/checkdbs > > Traceback (most recent call last): > File "/var/lib/mailman/cron/checkdbs", line 178, in ? > main() > File "/var/lib/mailman/cron/checkdbs", line 84, in main > mlist = MailList.MailList(name) > File "/var/lib/mailman/Mailman/MailList.py", line 126, in __init__ > self.Lock() > File "/var/lib/mailman/Mailman/MailList.py", line 159, in Lock > self.__lock.lock(timeout) > File "/var/lib/mailman/Mailman/LockFile.py", line 243, in lock > self.__write() > File "/var/lib/mailman/Mailman/LockFile.py", line 422, in __write > fp = open(self.__tmpfname, 'w') > IOError: [Errno 13] Permission denied: > '/var/lib/mailman/locks/mailman.lock.mail.6528.0' I'm assuming you installed your cron entries using crontab and not via /etc/cron.d, if so then did you remember to add "-u mailman" to the crontab command so the scripts execute as the mailman user? (If you used /etc/cron.d scripts then the user name goes into the cron file as the 6th field). If cron is executing your mailman scripts as the user mailman then look at the file permissions on the lock file, its possible it got created with the wrong permissions during an earlier snafu with incorrect installation. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] CGI wrapper error
On Fri, 2005-05-06 at 11:13 +0200, Patrick Le Deault wrote: > Failure to find group name nobody. Try adding this group The cgi-gid needs to be the gid of the web server (the process is probably httpd and the group is probably apache). The mail-gid needs to be the gid of your MTA (e.g. sendmail, postfix, exim, the group is probably mail). How do find out what groups an process executes under? Do this: # ps -eo "%a %G" > What can i do ? Read this: http://www.list.org/mailman-install/index.html Then rerun configure using the cgi and mail gid's you discovered by running ps. Note, you can specify the group name to the configure parameters, it does not have to numeric. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Backup
On Tue, 2005-05-03 at 11:02 -0700, Staven Bruce wrote: > I know this topic pops up fairly regularly, however I was unable to find an > answer to my specific question going through the archives and the FAQ's. I > want to create a script that will output to a file a list of all subscribers > e-mail addresses, the list they subscribe to, and their associated > password. However, the issues I have run into are as follows: > > -- The standard script that requires nmh at > <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.006.htp> uses > the /var/lib/mailman directory which does not exist in my installation of > Mailman 2.1.5 on Red Hat Enterprise 3.0. No big deal, just edit the script and change the directory. > -- I can get list membership addresses using the > /var/mailman/bin/list_members script, however I have to specifcy each list > individually and I can not receive the password. In addition, I would have > to change the script everytime a new list was created. > > Does anyone have any suggestions on scripting this functionality? mm_bin=/usr/lib/mailman/bin for list in `$mm_bin/list_lists -b` do echo $list $mm_bin/list_members $list done You can always get fancier by using with_list which would give you more control over what gets printed, but that requires some python coding ability. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] messages not sending
On Mon, 2005-05-02 at 11:53 -0700, Tony Bibbs wrote: > I'm using postfix and getting this back from the > maillog after attempting to send the message: > > postfix/local[13131]: 011D527007C: > to=<[EMAIL PROTECTED]>, > orig_to=<[EMAIL PROTECTED]>, > relay=local, delay=1, status=sent (delivered to > command: /usr/local/mailman/mail/mailman post > geeklog-devel) > > However, nothing actually happens. I've ran > check_perms and all is well so what else should I be > checking? That mailman is running. If you're using a 2.1 version there is a daemon process that must be running. Depending on your system it is started either with an init.d script (e.g. /sbin/service mailman start|stop| status) or via mailmanctl. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
RE: [Mailman-Users] Bug Help
On Wed, 2005-04-27 at 11:38 -0400, Loomis, Todd, CTR, DMSO wrote: > No actually I get the following: > > Traceback (innermost last): > File "", line 1, in ? > KeyError: getpwnam(): name not found Since the command "id" can lookup up the mailman password info we know it's defined in the system and can be successfully queried. However, it appears python cannot successfully execute the same query. What the error is saying is that when python tries to lookup the name "mailman" it is failing. You might try replacing "mailman" with your username in the snippet and see if python can look it up. If you just added the mailman account you might be having problems with nss and/or nscd (its a bit overkill but rebooting will refresh the name cache), or you could be having python problems, it's hard to say. All of these I'm sorry to say are probably off topic for this list until you can get that little python snippet to work. BTW, mailman 2.0.x is pretty old, you may want to consider upgrading to 2.1.5 -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
RE: [Mailman-Users] Bug Help
On Wed, 2005-04-27 at 11:06 -0400, Loomis, Todd, CTR, DMSO wrote:
> Yes I get
> uid=41(mailman) gid=41(mailman) groups=41(mailman)
Then this command:
python -c "import pwd; print pwd.getpwnam('mailman')[2]"
should print 41, if it doesn't then I'm at a loss other than
you might have python problems.
But are you sure the line that is failing is:
pwd.getpwnam('mailman')[2]
and not something that references MAILMAN_USER?
--
John Dennis <[EMAIL PROTECTED]>
--
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=show&file=faq01.027.htp
Re: [Mailman-Users] Bug Help
On Wed, 2005-04-27 at 08:19 -0400, Loomis, Todd, CTR, DMSO wrote:
> I getting this error can anyone help? Mailman version 2.0.13
> File "../Mailman/mm_cfg.py", line 50, in ?
> MAILMAN_UID = pwd.getpwnam('mailman')[2]
> KeyError: getpwnam(): name not found
Did you create the user account "mailman" and the group "mailman"?
Does this command return something like this:
id mailman
uid=41(mailman) gid=41(mailman) groups=41(mailman)
--
John Dennis <[EMAIL PROTECTED]>
--
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=show&file=faq01.027.htp
RE: [Mailman-Users] Changing Contact Mailing Address
On Fri, 2005-04-22 at 15:35 -0700, Staven Bruce wrote: > Ok, so I've figured my issue out, but I would really appreciate someone > explianing to me what's happening. I'm using Mailman version 2.1.5 on Red > Hat Enterprise 3.0 update 4. Originally, Mailman made two entries in > /etc/aliases under 'Mailman Aliases': > > #mailman aliases > > mailman:postmaster > mailman-owner: mailman > > However when I set up the recommended 'Mailman' site list, these two entries > were duplicated under 'Mailman Mailing List': > > #mailman mailing list > mailman: "|/var/mailman/mail/mailman post mailman" > mailman-owner:"|/var/mailman/mail/mailman owner mailman" > > As a result, /etc/aliases was complaining about having identical aliases. So > what I decided to comment out one of the duplicate entries. > > However, what I found was that if I commented out the 'mailman' entry under > the 'Mailman Aliases' section, any mail sent to [EMAIL PROTECTED] > **seemed** to disappear. It wasn't sent to me, it wasn't returned and it > wasn't held in the MTA que. > > But then I found if I uncommented the 'mailman' entry under the 'Mailman > Aliases' section and commented out the 'mailman' entry under the 'Mailman > Mailng List' section, then mail sent to [EMAIL PROTECTED] was delivered > to me with no problem. So, now I'm just trying to figure out why this > happens? Any ideas? It's clearly wrong to have the duplicate aliases defined. I went back to see where the original "mailman: postmaster" aliases came from because our mailman rpm does not create these. In fact, I'm pretty sure these aliases are from a much earlier version of mailman (2.0.x?). It turns out that the "setup" rpm which is responsible for installing core files installs a default version of /etc/aliases which include these deprecated mailman aliases. I have filed a bug report against setup so these aliases are not created when the system is first setup. This is the bugzilla. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=155841 However, I'm not sure I can explain the behavior you're seeing, but here is the bottom line, the mailman:postmaster and mailman-owner:mailman should be deleted from your aliases file, the aliases that pipe into /var/mailman/mail/mailman are the ones you want to keep. You didn't say which MTA you were using, I assume its sendmail. When you were experimenting did you regenerate your aliases and restart sendmail? In any event make sure you remember to do that after you delete the bogus aliases. Although on my test machines I have the duplicate bogus mailman aliases as a result of the setup rpm I've never had a problem which is why I probably never noticed this. However, I use postfix as my MTA which might overwrite the duplicate alias with the 2nd correct version thus masking the problem, but thats just a theory. If after you delete the bogus aliases and rebuild the aliases and restart your MTA you're still having problems let me know. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
RE: [Mailman-Users] Changing Contact Mailing Address
On Fri, 2005-04-22 at 11:17 -0700, Staven Bruce wrote: > I hope I'm just not missing the forest for the trees, but when I go to > http://your-server/mailman/admin/mailman/members, the only options I have > are to view the Members List, or tend to Addtional Member Tasks. Am I just > missing it? I can go down into Mass Subscriptions or Mass Removals, however > I don't see an option their either. > > -Original Message- > From: Jardar Eggesbà Abrahamsen [mailto:[EMAIL PROTECTED] > Sent: Friday, April 22, 2005 10:58 AM > To: mailman-users@python.org > Subject: Re: [Mailman-Users] Changing Contact Mailing Address > > > On Fri, 22 Apr 2005, Staven Bruce wrote: > > > I am trying to figure out how to configure > > Mailman so that messages sent to '[EMAIL PROTECTED]' go to a specific > > address such as [EMAIL PROTECTED] > > http://your-server/mailman/admin/mailman/members It's not the members page, its the General Options page, http://your-server/mailman/admin/mailman It the second item down labeled "The list administrator email addresses." -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
RE: [Mailman-Users] Changing Contact Mailing Address
On Fri, 2005-04-22 at 21:41 +0200, Jardar Eggesbà Abrahamsen wrote: > On Fri, 22 Apr 2005, John Dennis wrote: > > > It's not the members page, its the General Options page, > > http://your-server/mailman/admin/mailman > > > > It the second item down labeled "The list administrator email > > addresses." > > Wouldn't that be the address that messages for [EMAIL PROTECTED] > are sent to? Whereas messages for [EMAIL PROTECTED] are sent to the > member(s) of the mailman list? Or did I miss something? People don't email to the mailman list, its not meant to exist as a mailing list. It serves a structural (admin) purpose, for example so there is an origin for password reminders. There are normally no members of the mailman list, its a special list often called the "site list". -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] moving lists from one server to another
On Mon, 2005-04-11 at 15:23 -0400, Dave Pisarek wrote: > One thing that I do not have is a "var" directory in mailman. Below is > the what I have after I su - mailman > > bash-2.05$ pwd > /usr/mailman > bash-2.05$ ls > Mailmanarchives cgi-bindata icons locks mail > pythonlib scriptstemplates > TM bincron htdocs lists logs > messages qfiles spam tests > > Not sure if this helps you but i am a little confused by the "var" As typically shipped and installed mailman has two "root" directories it can install into, "prefix" and "var_prefix". In this instance "var" mean variable, or where mailman will place its variable data as opposed to its static run time files. Use of var_prefix is optional and depends on how the installation was done initially. Typically what is in var_prefix is archives, data, lists, logs, spam (off the top of my head and thats from a 2.1 perspective, 2.0 is fuzzy these days). It looks like your previous installation didn't separate static runtime files from varible data files. There are two files in the root of the tarball you'll want to read carefully, one is INSTALL, it explains many things and the steps involved. You will also want to read UPGRADING, it will help you go from 2.0 to 2.1. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] moving lists from one server to another
On Mon, 2005-04-11 at 13:59 -0400, Dave Pisarek wrote: > Hello all, > > I am new to mailman and need to move around 200 lists from one server > to another. I am looking for an easy way and fast way to do so. If > someone could explain how or point me to good docs on how to do this I > would greatly appreciate. You left out some information that would help answer your question: * Do you have shell access to both servers? If so you can copy the files in the mailman "var" directory. * Will both servers be running the same basic version of mailman? E.g. 2.1 vs. 2.0? If you're upgrading versions at the same time you may need to run bin/update after the data files have been copied. * Will the new server have a new domain? If so, and you have shell access then you'll also have have to run bin/fix_url to change the domain. * You almost certainly have to check the values mm_cfg.py so they match the new server. * If you don't have shell access then I think its going to be very difficult. Don't forget to stop mailman from running before taking a snapshot of the files to copy and give yourself time to test the new installation before you turn your lists back on. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] mailman path issue FC3
On Tue, 2005-04-05 at 21:30 -0700, Mark Sapiro wrote: > Obantec Support wrote: > > > >I am running FC3 and installed mailman using yum. > >now the cron is running but root emails show > > > > Subject Cron <[EMAIL PROTECTED]> mailman > >/usr/lib/mailman/cron/disabled > > > > > >Illegal command: /usr/lib/mailman/cron/disabled > > > >i put a link in /bin/mailman to /usr/lib/mailman/mail/mailman > > I don't know why you would need to link /bin/mailman to anything, but > in any case, /usr/lib/mailman/mail/mailman is the wrapper that handles > incoming mail. It has nothing to do with cron jobs. > > >and from bash with mailman i get Usage: mailman program [args...] so it > >seems to find mailman ok. > I'm not a Red Hat guy so this probably isn't the optimum advice, but it > should give you a clue. Well, I'm a Red Hat guy :-) You shouldn't need to link anything, especially mailman. The commands executed via cron located in /usr/lib/mailman/cron are python programs that have no relation to the mailman wrapper program (/usr/lib/mailman/mail/mailman). You shouldn't need to do anything to get the cron part of mailman with our RPM's working, it should just work automatically. I trust you installed an FC3 rpm on FC3, and not an RPM from an other distribution. What rpm is installed? (hint: rpm -q mailman) In theory what should happen is that when you start the mailman service a cron file is copied into /etc/cron.d/mailman (its done this way so that mailman cron jobs don't run if the mailman rpm is installed but not enabled). The format of cron entries in that file is different then in a crontab file. The difference in the two file formats is the insertion of extra field, after the time fields and before the command (this the user the cron job is to be run as), in this case the user is mailman. Crontab files DO NOT have the user field. Crontab files are not stored in /etc/cron.d. Crontab is never used by our mailman rpm. If I were a betting man I'd say it looks like the /etc/cron.d/mailman file with the extra "mailman" user id before the command has been passed to crontab and cron is trying to execute the username "mailman" because its been passed a file of the wrong format. BTW, the reason crontab files don't have the username in them is because its passed on the command line (via -u) when intalling the crontab file. But cron files are not installed via crontab, they are merely deposited in /etc/cron.d and thus they need the user id field. By any chance did you run crontab and pass it the cron file from the rpm? If thats your problem. The only other thing I can think of is older rpms used to use crontab (although not on FC3), did you overlay a newer mailman rpm over an older installation? The rpm is supposed to remove the old crontab, but it might have failed to do this, but the old crontab would have had the old format without the username. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] digest options
On Mon, 2005-03-28 at 21:44 -0800, Jennifer Stanley wrote: > hi. > > i manage several discussion lists hosted by Dreamhost. for subscribers > who prefer digests, there are, it appears, few options for controlling > or customizing digest delivery. i had a request that digests be sent > weekly, but it appears that the frequency is dictated only by the size > of the volume. is there any way to (a) make digest delivery calendar > based rather than folder-size based? (e.g., sent weekly, daily, or > whatever, vs. after the folder reaches 30k or 250k or whatever) and/or > (b) is there any way to allow the subscriber to set these options for > themselves? You can set it to daily delivery if its size threshold has not been reached. Its the 5th option on the digest page labeled "Should a digest be dispatched daily when the size threshold isn't reached?". Unfortunately you cannot select the granularity of the of the interval. If you had command line access there are other options, but hosting companies for obvious reasons do not permit this. The digest delivery "event" is a property of the list, not a subscriber preference, although I can see the value in that, its not currently supported. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Transfering mailman lists between servers
On Tue, 2005-03-29 at 17:13 -0500, James B. Byrne wrote: > Ok. I fixed the errors. The 403 Forbidden was caused by restoring > logical links dependent upon a different directory layout than that > used by CentOS4 (RHEL4), "/var/mailman/archives/public" vice > "/var/lib/mailman/archives/public." The version of mailman in rawhide and the version set to appear in FC4 has a migration script that moves directories and files from the old layout to the new FHS layout. It is located in /usr/share/doc/mailman- */contrib and documentation on the directory structure and change can be found in /usr/share/doc/mailman-*/INSTALL.REDHAT. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] mail -r?
On Wed, 2005-03-23 at 15:50 -0500, Matthew A. Marshall wrote: > Hello. I've just converted from mailman 2.0.x to mailman 2.1.x. Also, it just occurred to me, the aliases changed between 2.0 and 2.1, do you still have the old aliases in your alias file? -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] mail -r?
On Wed, 2005-03-23 at 15:50 -0500, Matthew A. Marshall wrote: > Hello. I've just converted from mailman 2.0.x to mailman 2.1.x. After > sending the confirmation back to the list-request email address, I > receive this error: > >- Transcript of session follows - > mail: invalid option -- r > Usage: mail [-iInv] [-s subject] [-c cc-addr] [-b bcc-addr] to-addr ... > [- sendmail-options ...] >mail [-iInNv] -f [name] >mail [-iInNv] [-u user] > 554 5.3.0 unknown mailer error 1 Who is giving you this error? When you reply in your MUA? > Also, if I attempt to run the mailman command from the command-line I > receive this: > > Group mismatch error. Mailman expected the mail wrapper script to be > executed as one of the following groups: > [mail, postfix, mailman, nobody], > but the system's mail server executed the mail script as group: "root". > Try tweaking the mail server to run the script as one of these groups: > [mail, postfix, mailman, nobody], > or re-run configure providing the command line option: > '--with-mail-gid=root'. > > The mailman command is chgrp'd to mailman with the group sticky bit enabled. Thats because "mailman" is a wrapper script meant to be executed by your MTA, its not a command line program (e.g. what's in the mailman bin directory). Mailman is guarding against anybody else executing what is supposed to be a private command only to executed by an MTA. The list presented to you in the error is a common list of of uid's that have the permission to execute the command. You will need to either logon as one of them or su to one of them. P.S. I assume the only reason you're attempting to execute the mailman command, is for testing purposes, one would never normally do this. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Vijay - Mailman bug 2.1.5
On Wed, 2005-03-23 at 16:58 +0530, Vijay Kumar wrote: > RuntimeError: command failed: /usr/sbin/postalias > /usr/local/mailman/data/aliases (status: 1, Operation not permitted) This is not a bug in mailman. Mailman has been asked to run a separate program when you add a new list, postfix's postalias command. It is postalias that is failing. I suspect its failing because postalias does not have the correct permissions when it runs to modifiy the postfix alias database. Did you read the instructions for how to set this up in README.POSTFIX? Is the alias database you're pointing to owner and group "mailman"? -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Security update for 2.1.5
On Tue, 2005-03-22 at 22:28 +0100, Brad Knowles wrote: > At 7:37 AM +1100 2005-03-23, Terry Allen wrote: > > > The output into the .rej file has only the comments at the start > > of private.py - I ran the patch 3 times but on the second time I > > answered Y on the reverse apply question, then the 3rd time, it > > ran without error. does this indicate to you that I have already > > applied the patch successfully? > > Hmm. Not sure. Have you compared the file being patched against > what it used to be, and what was in the patch? Here's a hint. The change is only a couple of lines, if you're having trouble applying the patch open up a text editor and manually cut-n-paste the changes. Or download the 2.1.6 beta and copy private.py from it into your installation. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Question on Mailman
On Tue, 2005-03-22 at 11:50 +0800, Marco Ng wrote: > Dear Sir/Madam, > > I want to ask whether Fedora Core 3 can install Mailman?? > And what is the system requirements for FC 3??? Yes, FC3 has the latest mailman along with the latest security fixes. Do make sure to read /usr/share/doc/mailman-*/INSTALL.REDHAT after you install the rpm. Many people are running the RH rpms's on Fedora. BTW, the bugs referenced in the FAQ were fixed a long time ago. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Mailman maintenance from the shell and "mailman" group
On Mon, 2005-03-21 at 11:01 -0700, Ivan Fetch wrote: > Hello, > > We'd like to have multiple people manage our mailman installation via > shell access, and are looking at adding their Unix accounts to the mailman > group. This seems to work, but I wanted to verify that this doesn't cause > any problems down the road. > > We could have folks login as the mailman > account, but it'd be nicer if they could use their own accounts. Yes, and no. It depends on what they're doing, but in general I would suspect this will work fine as long as they stick to using the command line interface (CLI), e.g. whats in the bin directory. Here is the issue: All of mailman's security is group based. As long as the user is just running commands and is in the group mailman you should be fine. However, if they edit or create files on their own they will end up having themselves as the owner, and their primary group, which will not be mailman. *SOME* of these files have the potential to exhibit permission problems. So as long as they stick to the CLI and are not editing python files you should be fine, if they are creating/modifying files by using a text editor, you could end up with bad permissions. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Mailman Database....
On Mon, 2005-03-14 at 15:36 -0500, Forrest Aldrich wrote: > It seems that many of the scalability issues could be addressed by > changing the backend database that Mailman uses... to SQL. > > If we had the ability to store content in a backend SQL database - we > could further scale this using standard mechanisms. > > Thoughts? I believe this is on the to-do list for Mailman Version 3.0 (a.k.a MM3) -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Another mailman install question
On Fri, 2005-03-11 at 13:20 -0600, Olson, Gary wrote: > In looking for the mm_cfg file, I can only find in path/mailman/Mailman > the files mm_cfg.py.dist and mm_cfg.py.dist.in -- there isn't an mm_cfg > or an mm_cfg.py file. Do I need to install this differently? How can I > get around this? Sounds to me like you never ran configure. The three basic steps are: ./configure make make install -OR- since you're on RHEL3 you could just install the mailman rpm and save yourself from learning the details of how to correctly build and install mailman :-) If you do install the rpm don't forget to read the file /usr/share/doc/mailman-*/INSTALL.REDHAT for important final installation and configuration tips. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] problem with cron jobs
On Wed, 2005-03-09 at 12:07 -0700, Jon Jacobsen wrote: > Hi, > > I installed a Redhat rpm mailman-2.1.5-23 on a Redhat enterprise server. > The mailman appears to be working, but I'm having problems with cron. > When the job run root posts to the 'mailman' list I created the following: > > /bin/sh: line 1: mailman: command not found > > I have no errors with 'check_perms' and /etc/cron.d/mailman looks fine. > I can run: > > #su - mailman -c "/var/mailman/cron/gate_news" > > without errors. > > Any Ideas? There is a difference between the format of cron jobs created with crontab vs. what is the system cron files located in /etc/cron.d. That difference is the insertion of the username (uid) that the cron job is to be run as. The username is inserted after the 5 time fields and before the command. Look at the file /etc/cron.d/mailman, you'll see lines that look something like this: 0 5 1 * * mailman /usr/lib/mailman/cron/mailpasswds Note that the 6th field is the username "mailman" which is the user the command is supposed run with the privileges of. ONLY files in /etc/cron.d have this extra field. If you installed the cron jobs using the command "crontab" using a file that has this format (recall that crontab files DO NOT have the username in them, its specified as an argument to crontab (e.g. -u) then cron will be confused into thinking the command is "mailman" because the 6th entry in a crontab file is the command (its the 7th entry in a system cron file). This is the most likely cause of the symptom you report. The rpm is supposed to correctly handle the cron installation and is aware of the difference between "system cron files" and files passed to crontab (of course there might be an rpm bug, especially if you didn't manually try to modify what the rpm installation did). I just spoke with the cron maintainer here who said there were some versions of cron in RHEL3 (which is the distribution your mailman rpm came from) that had some bugs. You could try updating your version of cron and see if that helps, but it really sounds to me like a mismatch of the cron formats. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] name not defined
Tzaia wrote: Hello list, I've been working on this for 4 days and haven't been able to resolve it. System with Fedora Core3 installed. All patched up FQDN is stinson3.amys-answers.com hostname is stinson3 modified the mm_cfg.py to reflect changes I will say that I'm completely new to the linux OS. I've been running NT and LISTSERV since 1997, but I wanted to be able to run discussion lists in tandem with one of my web sites, so I'm looking at Mailman. Here is what I get: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 63, in run_main from Mailman.Logging.StampedLogger import StampedLogger File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 20, in ? from Mailman.Logging.Logger import Logger File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 24, in ? from Mailman import mm_cfg File "/usr/lib/mailman/Mailman/mm_cfg.py", line 81, in ? DEFAULT_URL_HOST = stinson3.amys-answers.com NameError: name 'stinson3' is not defined Fedora installs Mailman differently than what any of the Mailman instructions say, but I've been able to find all the necessary files. I have no idea where it's getting the information to throw the error. Where do I "define" the DEFINE_URL_HOST except in the mm_cfg.py file? Any help would be appreciated. Looks like you've got a syntax error in mm_cfg.py, perhaps did you forget to quote the string "stinson3.amys-answers.com"? Single or double quotes should do the trick if my theory is right. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
RE: [Mailman-Users] permission error on email create
> I am trying to create a list, but I am running into permission problems: > > admin(8194): os.mkdir(self.archive_dir()+'.mbox', 02775) > admin(8194): OSError: [Errno 13] Permission denied: > '/usr/local/mailman/archives /private/49ers.mbox' > > I ran the check_perms script and it did not find any errors. > > What are the permissions supposed to be for this? What needs to be done > to get this to create the directories itself? If you are running FC3 or RHEL4 there is a known bug in the SELinux security policy. These OS's introduced SELinux a much more secure protection mechanism that goes far beyond traditional UNIX permissions. It monitors everything and decides based on rules if an operation is to be permitted. These rules are called the security policy. In FC3 and RHEL4 SELinux was enabled by default for a tartgeted set of systems services, especially services connected via the network. Mailman was one of the services that was put under the control of SELinux, along with apache, the MTA's etc. If an operation violates the security policy it appears to a traditional application as a permissions problem, but the traditional permissions may be just fine. When this happens its logged in /var/log/messages with line containing something like "avc access denied". There is a known bug in the SELinux policy for FC3 (RHEL4?) that trips up mailman's ability to create a new list from the web interface. This is not a mailman bug. Running check_perms -f will not fix this because the permissions are fine, its the security policy. The bug has been fixed in selinux-policy-targeted-1.17.30-2.80. If you upgrade to this version or later of the selinux-policy-targeted the problem should go away. Or you can disable SELinux by running the system-config-securitylevel applet. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] mail not being sent/received
Sythos wrote: Look archive, few day ago somebody post a method to use an external pop3, fetchmail and procmail to do mailman working without local mta. The easiest option, although it costs money, but not much, is to sign up with a virtual domain provider. Find one that is UNIX based, many offer mailman lists as a base feature. One that I'm familar with is www.dreamhost.com, for about $100 a year you get your own doman, email, mailman, web, etc. and they do all the work for you. Consider the cost/benefit ratio of spending days trying to figure out what's wrong in obscure config files or just throwing them $100 bucks and being done with it. Then you'll be able to get on with the real reason you're setting a mailing list up. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] mail not being sent/received
[EMAIL PROTECTED] wrote: I believe this is most likely the problem. I'm using comcast residential service and it issues dynamic IP addresses. I don't know for sure if this is the case -- does anyone know? Secondly, assuming this is the case, how can I get around this problem without changing my ISP? If you're using an ISP that issues you a dynamic DNA address then you don't have any visible domain and mail server to anyone outside. Without a permanent domain, IP address, and MX record other MTA's can't reach you. You might want to look into www.dyndns.com, they provide the service you will need at a fraction of the cost of having Comcast convert you to a commercial account with a static IP address. I make no claims for dyndns, I just know it as a possible option, I have no experience with it. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Re: mail not being sent/received
[EMAIL PROTECTED] wrote: Okay, here's some more potentially useful info. I sent a message to one of the user accounts and here's what I got back: Technical details of temporary failure: TEMP_FAILURE: Could not initiate SMTP conversation with any hosts: [hostname.dyndns.org (1): Connection refused] I think this echoes what I said about incoming mail not even reaching the server. There are 2 likely problems: 1) Your firewall is not allow port 25 SMPT traffic, open the port up. This is the most likely. 2) Your MTA is only listening your local loopback, i.e. your own machine 127.0.0.1, and not your machines IP address. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] bug in mailman
You've probably hit a bug in the SELinux policy, it was fixed in selinux-policy-targeted-1.17.30-2.80. Therefore you can either update your selinux-policy-targeted rpm to the latest version or disable SELinux with system-config-security level. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Lists are missing
Scot Condry wrote: Thanks. That got me in the right direction that I got mailman working again and postfix needed to know where the aliases had moved to. But now I have created a new list named the same as the old list and it is working. But I would like to move all the old users, password, archives etc. to the new directories. Is that possible? If you copy the following 3 directories you should pick up your old list and member data. /var/mailman/archives--> /var/lib/mailman/archives /var/mailman/data--> /var/lib/mailman/data /var/mailman/lists --> /var/lib/mailman/lists You may also want to copy over the pending queue files: /var/mailman/qfiles --> /var/spool/mailman -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] bug in Mailman when accessing Private Archives
Mark Sapiro wrote:
Christopher Adams wrote:
Traceback (most recent call last):
File "/lists/scripts/driver", line 80, in run_main
pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname])
File "/lists/Mailman/Cgi/private.py", line 43
parts = path.split(SLASH)
^
SyntaxError: invalid syntax
The patch at http://www.list.org/CAN-2005-0202.txt has been appied to
private.py and it looks like it may not have been applied correctly.
There is an issue with this patch and older versions of Python, but
the above error doesn't look like that.
It is mostly likely incorrect white space at the beginning of the line,
leading white space in python is significant, fix the the white space to
match the correct indendation level.
Also some folks forgot the definition of SLASH at the top of the file,
don't forget that or you'll discover a new problem, SLASH isn't defined
--
John Dennis <[EMAIL PROTECTED]>
--
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=show&file=faq01.027.htp
Re: [Mailman-Users] bug in Mailman when accessing Private Archives
Christopher Adams wrote:
Has anyone seen this problem?
Bug in Mailman version 2.1.5
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy
of this page to the webmaster for this site with a description of what
happened. Thanks!
Traceback:
Traceback (most recent call last):
File "/lists/scripts/driver", line 80, in run_main
pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname])
File "/lists/Mailman/Cgi/private.py", line 43
parts = path.split(SLASH)
^
SyntaxError: invalid syntax
Looks like the CAN-2005-0202 patch was not applied correctly.
--
John Dennis <[EMAIL PROTECTED]>
--
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=show&file=faq01.027.htp
Re: Fwd: [Mailman-Users] Mailman CGI error!!!
[EMAIL PROTECTED] wrote: I think we may be getting somewhere because my httpd.conf file is not consistent with yours. I'm running apache2, and I seem to remember installing it from source (although I'm not sure about that). hehe ... I'll bite my tounge :-) :-) BTW, we've been shipping apache 2 for a long time now. Here's the only User and Group entry in the file: # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # . On SCO (ODT 3) use "User nouser" and "Group nogroup". # . On HPUX you may not be able to use shared memory as nobody, and the #suggested workaround is to create a user www and use that user. # NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET) # when the value of (unsigned)Group is above 6; # don't use Group #-1 on these systems! # User nobody Group #-1 Should I remove the IfModule clauses and add the following instead? User apache Group apache I think, but I'm not sure, you should check the apache doc, but those IfModules are saying if you're not on Windows and not on NewWare then you must be Unix so set the user and group, thus I think you can leave them alone. At any rate, User has to be apache and Group has to be apache. I'll bet that gets you a lot further. Of course you'll have to restart apache. Given that you're not using our rpm I don't know if you've got the right init.d script for apache, (using our rpm will assure you've got all this ancillary stuff working and configured correctly too). If you do then the command as root is: /sbin/service httpd restart Oh, one more thing apache as a system service is known as "httpd" HTH John -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
RE: Fwd: [Mailman-Users] Mailman CGI error!!!
The default user and group for apache if not set in the apache config file is -1. The user and group must be set in the apache config file to be "apache" (/etc/httpd/conf/http.conf), you should see lines like this: User apache Group apache If you don't set apache's user and group the cgi scripts will execute with user and group of -1, which appears to be what is happening. Our mailman rpm expects the cgi scripts to be executed by a process that is the user apache and a member of the group apache. If apache's user and group are not set to apache in the config file it would perplex me because all our rpms are self consistent with respect to configuration (or at least we try really hard to be :-) -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: Fwd: [Mailman-Users] Mailman CGI error!!!
[EMAIL PROTECTED] wrote:
Hi, I'm still having trouble with installing Mailman. The original
error is as follows:
Mailman CGI error!!!
The Mailman CGI wrapper encountered a fatal error. This entry is being
stored in your syslog:
Failure to lookup via getgrgid() the group info for group id -1 that
this Mailman CGI wrapper is executing under.
This is probably due to an incorrectly configured system and is not a
Mailman problem
The really odd thing is that getgid is apparently returning ~0 (gid's
are unsigned, but the error message prints it as an int, hence the -1).
I just looked at my groups and the only group with a large number is
nfsnobody. Are you trying to run this across NFS? If so I'm guessing
your mount point is not correct because if I recall correctly NFS mount
points need special flags added to allow execute permissions to pass
through. I would check that first. If you're not on NFS and/or NFS mount
point is correctly configured then I would check the following:
Are all the scripts in /usr/lib/mailman/cgi-bin/ owned by root in the
group mailman with the group sticky bit set (the 7th letter printed out
by ls -l)
here is an example:
-rwxr-sr-x 1 root mailman 17079 Feb 15 11:21 admin*
What is the contents of your /etc/httpd/conf.d/mailman.conf file? The
cgi script should look like this:
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
AllowOverride None
Options ExecCGI
Order allow,deny
Allow from all
--
John Dennis <[EMAIL PROTECTED]>
--
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=show&file=faq01.027.htp
RE: [Mailman-Users] Lists are missing
> I recently upgraded (*not* a fresh install) from Fedora 2 to > Fedora 3. > Seems as though everything came over OK except my Mailman is > messed up now. > Emails to my list are not being distributed and when I go to > the mailman listinfo page it says I have no lists, when I had > three. Only one of these was actually in use, but anyone > know what FC3 might have done to change things? FC3 relocated the installation directories for mailman to be FHS compliant and allow better integration with SELinux, this is documented in /usr/share/doc/mailman-*/INSTALL.REDHAT and it explains the directories you need to move if you are trying to overlay a new release on an old release and want to preserve a previous installation. -- John Dennis <[EMAIL PROTECTED]> -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Re: Critical security update for Mailman 2.1.5
On Fri, 2005-02-11 at 08:34 -0500, AJ wrote: > This also stripped it down for me. > I do not see any logs in error or mischief. > How can I get it to actually log the attempt so I know this is working. If you are running with apache >= 2.0, which many sites are, then apache will strip the malicious components of the URL and the defense in true_path will never get triggered because it will never see the malformed URL passed by apache. Thus there is no way to test it with apache >= 2.0, in fact you're not vulnerable to begin with. -- John Dennis <[EMAIL PROTECTED]> -- 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
Re: [Mailman-Users] Critical security update for Mailman 2.1.5 and earlier
To answer a few recent questions. To the best of my knowledge the patch is safe for any version of mailman that contains the function true_path in private.py. You will not see a new .pyc or .pyo file generated until the script is executed for the first time after the change. In other words until someone logs into a private archive for the first time. If you're really concerned about the old .pyc or .pyo files you can manually remove them. -- John Dennis <[EMAIL PROTECTED]> -- 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
RE: [Mailman-Users] security heads up - path traversal with 2.1.5
Well, as long as the cat is out of the bag, here is some info that might be
helpful to folks. I was told the security alert was made public this
afternoon so not much is being compromised by helping folks address the
issue given its new found visibility :-( Red Hat has patched all of its
Mailman rpm's which are in the process of getting pushed out through our
distribution channels. Here are the package versions for each distribution:
AS2.1: mailman-2.0.13-7
FC2: mailman-2.1.5-8.fc2
FC3: mailman-2.1.5-30.fc3
FC4: mailman-2.1.5-30.fc4
RHEL3: mailman-2.1.5-24.rhel3
RHEL4: not yet released.
The good news is that the exploit is only possible when mailman is combined
with a version of the Apache Web server (httpd) less than version 2.0 (e.g.
1.3)
I am not going describe in this forum how the exploit occurs for obvious
reasons. It has been reproduced on a number of systems. It is a serious
exploit that can give attackers access to most of the file system. If you
are running Apache < 2.0 you will want to patch your mailman code -OR-
upgrade to Apache >= 2.0.
If you are running Apache >= 2.0 breath a sigh of relief, you are not
vulnerable.
BTW, I do not believe this is limited to mailman 2.1.5, it is present in
earlier mailman versions (or at least from code inspection it seems to be)
Here are two proposed fixes, either should work:
The implementation of the function true_path in Mailman/Cgi/private.py needs
to be changed:
import re
def true_path(path):
"Ensure that the path is safe by removing .."
path = re.sub('\.+/+', '', path)
return path[1:]
-OR-
SLASH = '/'
def true_path4(path):
"Ensure that the path is safe by removing .."
parts = [x for x in path.split(SLASH) if x not in ('.', '..')]
return SLASH.join(parts)[1:]
--
John Dennis <[EMAIL PROTECTED]>
--
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
Re: [Mailman-Users] Moving the data to a different disk or partition
On Sat, 2005-02-05 at 09:48 +0800, Glen Low wrote: > Dear All, > > On the installation instructions at > http://www.gnu.org/software/mailman/mailman-install/create-install- > dir.html I read: > > = > > Typically, Mailman is installed into a single directory, which includes > both the Mailman source code and the run-time list and archive data. It > is possible to split the static program files from the variable data > files and install them in separate directories. > > = > > Unfortunately I couldn't figure out how to split off the data > (variable) portions onto a different disk or partition or directory, > especially after installation -- short of creating symlinks. Anyone > know? by running configure with the --with-var-prefix set to the directory of your choice. When you do the "make install" step that directory will be created and populated with mailman's data files. The shorthand "var" means variable. This is documented elsewhere in the manual http://www.gnu.org/software/mailman/mailman-install/node7.html and in the INSTALL file in the tarball, unfortunately the page you were reading does not have a link to the configure parameters, which perhaps it should and is probably why you missed it. -- John Dennis <[EMAIL PROTECTED]> -- 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
Re: [Mailman-Users] Mailman CGI error!!!
On Thu, 2005-02-03 at 18:40 -0500, [EMAIL PROTECTED] wrote: > Hi All, > > I'm getting the following error after I configured mailman as per > instructions. Can someone please shed light on this? I can give you > system details -- please just ask. > > Many thanks, > jim > > > Mailman CGI error!!! > The Mailman CGI wrapper encountered a fatal error. This entry is being > stored in your syslog: > > Failure to lookup via getgrgid() the group info for group id -1 that > this Mailman CGI wrapper is executing under. > This is probably due to an incorrectly configured system and is not a > Mailman problem I suspect you omitted either Step 1 or Step 2 of the INSTALL instructions: Step 1: - Add a new user called `mailman'. ... - Add a new group called `mailman'. ... Step 2: TAKE SPECIAL NOTE OF THE --with-mail-gid AND --with-cgi-gid OPTIONS BELOW. ... > -- > 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/ -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Mailman on UML?
On Thu, 2005-02-03 at 12:53 -0500, Todd Slater wrote: > I'd be interested in knowing if anybody is successfully using Mailman > under User Mode Linux and what sort of specs this requires. I am trying > it with 64MB RAM and have memory errors, but I'm also running Apache and > Dovecot for IMAP mail. httpd and python seem to use the most memory. > That's running on Fedora Core 2. > > FAQ 1.24: > In theory, Mailman should work on any hardware/operating system that > fully supports the current version of Python (e.g., 2.3), and includes > compatible web and mail servers. This does include virtual machine > configurations. I believe you're assumption is correct, mailman should run fine in a virtual machine. When you say you're getting memory errors I assume you meant you've exhausted virtual memory and swap space in your VM, if that's correct I don't think there is much you can do aside from improve your VM. I don't personally have any experience with UML but I can tell you that virtualization is getting a lot of attention here of late and the preferred technology is Xen, not UML, info on Xen can be found here: http://www.cl.cam.ac.uk/Research/SRG/netos/xen -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] problem using mailman
On Thu, 2005-02-03 at 04:07 +0500, dinar ali kadri wrote: > i solved my problems and my mailman is working fine but do i have to > do all these aliases jobs manual and then restarts my MTA for every > new list ? > I am using Fedora core 2 and sendmail as my MTA See this FAQ entry http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.049.htp However, if you were to use postfix instead of sendmail it would be really easy, just add MTA='postfix' in your mm_cfg.py file and you're done (provided postfix is set up and running) You might need to install the postfix rpm and it would be handy to install the system-switch-mail rpm so you can run system-switch-mail to convert from using sendmail to postfix. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] cant't create lists within the webinterface
Markus> I can't create a new list within the webinterface. ... John> There is a possibility you may have run afoul of SELinux ... Markus> ok I disabled set selinux=0 in grub.conf and all works fine FYI, I've created the following bug entry to track this problem. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=146890 -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] cant't create lists within the webinterface
On Mon, 2005-01-31 at 11:01 +0100, Markus Darges wrote: > Hi, > > I cant' create a new list within the webinterface. Could someone tell > mit whether it's a known bug? Even if I change the permission of the > folder lists to 777 I get the same error. > My OS is Fedora Core 3. Mailman 2.1.5, Python2.4, Apache2.0.52 First, off I trust you are using Red Hat's mailman rpm for FC3. There is a possibility you may have run afoul of SELinux, but its very hard to tell from the information presented. SELinux is a security enhancement that restricts operations beyond the traditional UNIX permissions. In FC3 SELinux is enabled by default in what is called "targeted" mode, meaning SELinux is only used for "targeted" applications and services because those applications and services are open to the network and are much more vulnerable to exploit, mailman is one of the services under SELinux protection. The security policy is non-trival to author correctly it is possible we may have missed a corner case. Here are two simple things you can do to determine if SELinux is responsible for your access problems. 1) Look in /var/log/messages for any lines with "avc" in it, it will probably read something like "audit avc access denied ..." but I'm going from memory so don't use the full string I gave you to search for, I'm almost positive the exact string is slightly different. If the security policy is denying access it will log it in /var/log/messages and it should be pretty obvious. 2) Turn off SELinux, run your mailman action again, does the problem go away? If so, this is a sure sign its a bug in the security policy. To disable SELinux, su to root and run system-config-securitylevel, you'll see a dropdown box for SELinux, select the option to disable it. If this fixes the problem, then make sure you're fully up to date with the security policy, use your favorite package manager (e.g. yum) to update this rpm: selinux-policy-targeted. Go back and enable SELinux, do you still have the problem? If not great, if so then please file a bug here: https://bugzilla.redhat.com and be sure to include the operation being performed, the avc error messages from /var/log/messages, and the rpm versions of mailman and selinux-policy-targeted. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] cron for which user?
On Fri, 2005-01-28 at 23:57 +0800, Glen Low wrote: > I had followed the Mac OS X install instructions at > http://mail.python.org/pipermail/mailman-users/2004-September/ > 039600.html which say to install the crontab under su -- is that > correct? should not the crontab be under the mailman user instead? FWIW, different versions of cron and different UNIX's have different rules on who can install cron jobs. So this is really specific to the particular cron implementation, I'm not a Mac OS X user, but I think what is being suggested is that you need to be root to install the crontab, but execute the job under the mailman user (e.g. -u mailman). In other words I think you need to be root to add this set of cron jobs, or at least that would be my interpretation. HTH, -- John Dennis <[EMAIL PROTECTED]> -- 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/
RE: [Mailman-Users] It happened again: qrunners stopped on their own.
> Stopped exactly after one day. I didn't catch it before. > What could be happening? By any chance did they stop at the same time one of the mailman cron jobs ran? -- 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/
Re: [Mailman-Users] mailman on RHAS3
On Wed, 2005-01-19 at 22:09, Steven Jones wrote: > OK, so has anybody successfully installed RH's mailman like this? yes :-) > I also want to use the sourceforg webmin module to create lists I'm sorry, but I'm not at all familar with webmin, however I can answer questions concerning RH mailman. > so does anybody have ideas where, > > 1) Errors might be logged? mailman errors are logged to /var/log/mailman/error I don't know where webmin errors are logged, but you should look at /var/log/messages for anything suspicious. > I have created the mailman list using newlist successfully (as far as I can > tell) > and mailman is running as "service mailman status" shows a PID and > ps aux |grep mailman shows 9 processes, 8 of which are runners. Sure sounds to me like mailman is running fine. I assume aside from creating the mailman list and checking process status you've verified mailman you can send and receive mail to a test list and that your web server is serving mailman cgi correctly. I suspect your problems may lie with webmin, perhaps a webmin user list would be better able to answer your questions. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] AssertionError
Just so you're not left in the woods, here is a brief summary of what mailmanctl does. First of all its a daemon, which in UNIX speak means its a system service that always runs in the background, is started by the system, and does not interact with a user with any IO. It's job is to start a number of children processes, these are the qrunners, each has a specific queue it monitors. Mailmanctl watches for the "health" of its children, if one of its child qrunner processes die it will restart it (up to a certain restart limit, otherwise when there is a serious problem it would flood the system with processes that start and just immediately die). Communication with the child processes occurs with UNIX signals. Mailmanctl also manages locks to assure exactly one instance of mailman is running and can identify the running master process. It does some other housekeeping work as well, as well as verifying permissions, which are based on UNIX groups. Another part of mailman 2.1.5 that is very UNIX specific is the whole security and permission framework. If you look in the src directory you'll find C code which is compile into several "wrapper" programs. This is what the web server and the MTA exececute. They validate the calling process has permission to execute the requested python code. Also you'll discover that the web server (cgi) and MTA alias piping mechanism is probably very UNIX specific as well. Bottom line, the guts of mailman are platform neutral but it must hook into a larger system to actually perform its work and that system is very much UNIX. To get mailman to run with another OS you'll have to at a minimum address each of the issues I outlined above. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] AssertionError
On Wed, 2005-01-19 at 05:42, John Poltorak wrote: > I thought Mailman was supposed to be platform independent... I didn't have > this particular problem with v2.0.13 but I guess this must be some thing > new related to mailmanctl. Mailman is UNIX only. Perhaps you've confused the fact that python the language it's written in is OS independent. That said much of mailman is platform independent, its just not %100 independent and I'm not aware of any effort to make it %100 independent of UNIX. Also the problem you're having is with the most UNIX specific part of mailman, the control of processes. I suspect if you work through the issues with mailmanctl you'll be a long way towards getting your port finished. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] AssertionError
On Tue, 2005-01-18 at 16:21, John Poltorak wrote: > What is an AssertionError and how do I get rid of it? > > It occurs when I start mailmanctl which outputs this error:- > > > Traceback (most recent call last): > File "mailmanctl", line 547, in ? > main() > File "mailmanctl", line 402, in main > lock._transfer_to(pid) > File "/usr/local/mailman/Mailman/LockFile.py", line 398, in _transfer_to > assert self.__linkcount() == 2 > AssertionError > > > What is this trying to do? In UNIX file systems files are represented as inodes. There is a list in every directory of file names and the inodes they point to. Multiple names can point to one inode. When a name points to an inode it is called a link. Thus both "fileA" and "fileB" can be the exact same file if their links point to the same inode. The code in question just created a 2nd link (2nd filename) to the same file and its asserting that exactly two names exist for that file. Since you're porting to OS2 which does not to the best of my knowledge support UNIX filesystems you'll have to rewrite this code. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Restoring Mailman configuration from a distro to another
On Fri, 2005-01-14 at 13:49, Luis Fernando C. Talora wrote: > Fellows, > > IÂm having some trouble restoring a Mailman server. The problem is that > WeÂve built our mailman server originally with Fedora Core 2. Yesterday, the > Hard Disk stoped working, so we restored our backup (a 250 mb tgz file, > restored to another server). Since I donÂt have Fedora Core 2 CDs in here, I > had to install Fedora Core 3 instead, but so many things had changed for > Mailman from one version to the other (the directory where itÂs placed is > one of them). There is documentation in /usr/share/doc/mailman-*/INSTALL.REDHAT which tells you the mapping of old directory locations to new directory locations. Because both FC2 and FC3 both shipped mailman 2.1.5 you should be able to just copy your data and queue files over to the new location. In addition you'll want to copy over your mm_cfg.py file. I think the following minimal set of changes will get you on your way Directory Mapping: /var/mailman/archives --> /var/lib/mailman/archives /var/mailman/data --> /var/lib/mailman/data /var/mailman/lists --> /var/lib/mailman/lists /var/spool/mailman/qfiles --> /var/spool/mailman File Mapping: /var/mailman/Mailman/mm_cfg.py --> /usr/lib/mailman/Mailman/mm_cfg.py (sym linked from /etc/mailman/mm_cfg.py) /var/mailman/data/adm.pw--> /etc/mailman/adm.pw /var/mailman/data/creator.pw--> /etc/mailman/creator.pw /var/mailman/data/aliases --> /etc/mailman/aliases -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Group mismatch error. Mailman expected the mail
On Mon, 2005-01-10 at 09:04, [EMAIL PROTECTED] wrote: > Group mismatch error. Mailman expected the mail wrapper script... > I am unsure how to resolve THIS error=2E I am hoping there is some > configuration file that I can update, instead of having to reconfigure my > Mailman installation entirely=2E=20 The group information is compiled into the mailman wrapper. You have two choices, you can either change the group the MTA operates under to match mailman or rebuild mailman again passing the group in the configure step as recommended in the error message, this is probably the best solution. FWIW a complete rebuild of mailman only takes a short while on most boxes so it shouldn't be to painful, then just install to the same location, nothing else should be affected although it might be prudent to stop mailman during the install. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] (Off topic - kinda) Postfix again
On Sun, 2005-01-09 at 18:04, Christian Schoepplein wrote: > Hi! > > On So, Jan 09, 2005 at 12:04:00 -0500, Josà Zapata wrote: > > Well, I'm trying again Postfix instead of Sendmail and hopefully all > > will work this time. However, I have one little problem. Even if > > Postfix is running and Sendmail isn't, when I check the queue with > > "mailq" the result I get belongs to the Sendmail queue. > > Have you really installed both postfix and sendmail on the same server? > > > Can you please tell me how to make the "mailq" command work with the > > Postfix queue? > > Use the command > > postqueue -p > > Thats the same like mailq and it shows you the postfix queue. If you > want to use the mailq command, remove sendmail and install and > configure postfix properly. >From previous correspondence on a different topic I seem to recall Jose may be running a Red Hat distribution. If that is the case then there is a little configuration utility used to switch between sendmail and postfix that should be a much easier solution. On the Fedora releases its /usr/sbin/system-switch-mail, it is not installed by default, you will probably need to install the system-switch-mail rpm. On RHEL systems its called redhat-switch-mail and is in the redhat-switch-mail rpm. On Red Hat systems we use the "alternatives" mechanism to support multiple installed subsystems and switch between them. This is done via symbolic links. If you're a "I program on bare metal" person you can invoke alternatives directly, the system-switch-mail is just a simple GUI that wraps "alternatives" HTH -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Single user's mail delayed ONLY to list
On Tue, 2004-12-21 at 11:54, blindman jones wrote: > I have a list, 10 users... 9 users send mail to list and their mail is > sent out in minutes and all 10 users get the mail from the list... no > problem. The 10th user sends a mail to the list and it is not sent > back out to the list for 4-10 hours. Mail sent to anyone else in the > world by the 10th user gets sent and delivered in minutes. I doubt this is an issue with mailman, rather with your service providers MTA (Mail Transport Agent). Mailman does not actually send the mail, rather it contacts the MTA and says "I have mail for these N addresses, would you please send them when you get a chance?". The MTA then queues the request, when the message is sent depends on a host of factors that often dynamically change (hence why the delay is not consistent or repeatable). Given both Mailman and the MTA are under the control of your service provider there is not much you can do as a list owner other than engage your service provider in tracking down the bottleneck. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Error: mailmanctl -s -q start
On Mon, 2004-12-13 at 21:14, Roger Tsang wrote: > I'm running mm-2.1.5 install from source with Python-2.3.3 on Fedora Core > (kernel-2.4) and getting the following error when starting mailman from the > provided init.d script. > > # service mailman start > and it runs mailmanctl -s -q start > > I keep on getting the same error messages. Mailman is installed on a ext3 > partition. What does the trace mean? Bad filesystem? Anybody seen it? I assume you're not running FC3 since that is a 2.6 kernel and hence you're not running afoul of SELinux security. It's a little hard to tell from the traceback what is failing but a reasonable assumption is you've got configuration problems or possibly permission related to the lock file and/or directory. Did you run bin/check_perms to verify your installation? In general, if at all possible, one should install the packages provided by distributions rather than building from source, that eliminates many common pitfalls and headaches (especially those related to system services) because the distribution has already sorted these issues out and crafted an installation tailored to the distribution. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Mailman file and directory permissions
On Mon, 2004-12-13 at 19:05, Matt Ruzicka wrote: > My company is running and testing Mailman to replace majordomo (finally) > in a FreeBSD environment. From the README.BSD file I see that it is > possible to io install without turning on the setgid bit on directories. > However, even with a 'make DIRSETGID=: install' a number of executable > files are installed with the setgid bit. The fact that these same files, > as well as pretty much everything else in the mailman directory, are set > to allow world read and execute makes us very nervous, especially since > this is a shared environment. Are we missing something or is this not a > recipe for anyone being able to run these commands? > > I realize that most things are password protected as well and it appears > only the cgi-files are setgid, but we were toying with this idea and were > wondering how bad of an idea it is. > > chmod -R go-rwxs /u/mailman > chmod 4550 /u/mailman/cgi-bin/* > chown -R mailman:webgroup /u/mailman/cgi-bin > chmod 750 /u/mailman/cgi-bin > chmod 644 /u/mailman/data/* > chmod 711 /u/mailman > chmod 711 /u/mailman/data/ > > > We also did this, but are not sure they are necessary: > > chmod 711 /u/mailman/mail > chmod 711 /u/mailman/mail/mailman > > We figure we would rather have the web server running these scripts as > mailman instead of allowing anyone to execute all of these scripts. > > After we made these changes in the test environment everything seems to be > functioning normal from the outside perspective. > > If this is a horrible idea, why? And if this is highly discouraged, has > anyone else done anything to limit permissions further from the default > install to disallow prying eyes and curios fingers? The reason why DIRSETGID is different on BSD is because of "directory inheritance" of the setuid and setgid bits, this is explained here: http://www.linuxpowered.com/html/editorials/file.html A few months back I went over the installation process with a fine tooth comb and noted some parts of the installation relied on this inheritance property which is system specific. I cleaned some of this up to make it explicit and system agnostic, although the patch was sent to the developers list I didn't add it to the SourceForge patch area which I need to do so its in the official queue. I doubt you will run into problems with the world execute bit set, Mailman's security is group based. This is the point of having those executables be setgid. I believe you will discover all the executables you are concerned about check the group (src/common.c) of the user executing them. If it the group is not valid (a build time option) then the executable exits with a fatal error, otherwise the command runs with an effective group id (hence the setgid bit) of mailman (or whatever it was defined to be a configure/build time). Thus only defined groups are allowed to execute the command and when it executes its only executes as group mailman. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Not getting messages sent to list I created and subscribed to
On Mon, 2004-12-13 at 11:33, Jody Cleveland wrote: > I'm running Mailman 2.1.5 on Redhat 3.0AS using postfix. I installed > Mailman from source. > > I was able to create a list using the web interface: > http://mailman.winnefox.org/mailman/create. I was able to subscribe, and > accept that subscription. I can modify all my user info. But, whenever I > try posting to that list, I never get that post I made. Also, nothing > appears in the archives for that list. I've read the faq here: > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.014.htp > and came up with this: > > Ran check_perms, everything is fine. > Checked cron, everything is set there. > Checked the aliases. All were created just fine. > I'm using Postfix, and didn't notice anything about smrsh > I tried adding SMTPHOST = '199.242.176.200' - made no difference > Nothing appears to be in the queue. > Nothing added to any of the logs for Mailman > > Any ideas what may be wrong? Ah, is mailmanctl running? When you build from source one of the things that is easily missed is all the service process control stuff thats in the RH rpm (using the RH supplied rpm should offer you the easiest path to a working mailman installation on 3.0AS). Mailman requires a master process (daemon) to be run (mailmanctl), typically it is automatically started by adding it to the init sequence. This requires an init script be installed, chkconfig be run to add it, and for the service to be initially started. Did you do all these things? Is mailmanctl running? -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] mailman 2.1.5 - genalias not working for postfix?
On Sat, 2004-12-11 at 15:50, Jeffery Cann wrote: > I have seen several threads related to the genalias command. The idea > is that with postfix, when you run genalias (and you have added the > mailman alias files to your postfix main.cf), it will automatically > update your mailman alias file. > > The problem for me on Fedora Core 3 is that when I set my > MTA='Postfix' in the mm_cfg.py file and then run 'genalias', the alias > file is supposed to be written to the data/aliases file. On FC3, this > is located in /var/lib/mailman/data/ If you are running the official FC3 rpm the location of the file is /etc/mailman/aliases. This is documented in /usr/share/doc/mailman-*/INSTALL.REDHAT. You will also have to edit your /etc/postfix/main.cf file and make sure that the alias_maps variable contains hash:/etc/mailman/aliases and restart postfix so it pick up the configuration change. Note the location of the MTA alias file changed during the beta period of FC3, this means there is a possibility you may have installed an RPM on your system prior to the official GOLD release which contains an older location. You can verify the location of the alias file by looking at the ALIASFILE variable in /usr/lib/mailman/Mailman/MTA/Postfix.py -- John Dennis <[EMAIL PROTECTED]> -- 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/
RE: [Mailman-Users] Not getting messages sent to list I created a nd subscribed to
On Mon, 2004-12-13 at 12:22, Jody Cleveland wrote: > Hi John, > > > Mailman requires a master process (daemon) to be run (mailmanctl), > > typically it is automatically started by adding it to the > > init sequence. > > This requires an init script be installed, chkconfig be run to add it, > > and for the service to be initially started. Did you do all these > > things? Is mailmanctl running? > > I double checked, and it is running. I also did chkconfig to have it > start automatically. I assume you installed the mailman init script in /etc/init.d and not mailmanctl. > I just checked the maillog, and there's nothing > there after I try sending a message to the list. Is postfix running? Has postfix's alias file been updated with the list aliases? What's in /var/log/maillog? Did postfix see your test message and attempt to pipe it into the mailman wrapper (the aliases created by bin/newlist supplies these and postfix has to know about them, or you can have mailman autogenerate them for postfix by setting your MTA to postfix). -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Archives, the "Forbidden Zone"
On Sun, 2004-11-21 at 15:43, Nathan Fiedler wrote: > It turns out the problem was simple and so was the solution. When > importing my existing list data and archives from another machine, I did > not know to update the selinux context labels appropriately. Thus, the > kernel was unable to determine if the apache user was allowed to access > the files. Normally it should be, but without the labels it wouldn't > succeed. > > To correct the labels, I ran both of these commands as root: > > # fixfiles relabel > # restorecon -Rv /var/lib/mailman I'm glad you got this problem fixed. I'm also relieved it was not a bug in the security policy after all, we did try pretty hard to make sure the policy shipped without problems but our testing centered around new installations and didn't take into account copying in foreign files. This sounds like something that needs documentation. restorecon is the right tool to relabel files to their defaults in specific directories. fixfiles would have relabeled the entire system and is not generally recommended. It may have helped if you had been the user mailman when you copied the files as opposed to root, but there are many issues that impinge. Was the operation a move or a copy? Did destination file previously exist? Would you have had permission as mailman to read the files? etc. Rather than enumeration all the possible considerations when dealing with files and directories under the protection of SELinux the most expedient path is to copy the files and relabel the files using restorecon, just as you did. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Archives, the "Forbidden Zone"
On Sun, 2004-11-21 at 15:07, Nathan Fiedler wrote: [ SELinux permission problem snipped for brevity ] FC3 installs with the SELinux "targeted" policy enabled by default. The targeted policy is a restricted security policy that "targets" only the most vulnerable system services rather than the entire system. Anytime you see messages in your system log (/var/log/messages) with "'avc: denied" it means the security policy has prohibited access and has logged a warning. SELinux has much to offer in terms of enhanced security in the day and age of rampant attacks by malicious intruders however one of the downsides of SELinux is authoring a security policy that both prevents invalid access but does not interfer with valid operation of the system is challenging. This is one reason the current security policy is "targeted", it applies only to system services that make active use of network connections. Mailman was added to the list of of system services under the protection of the SELinux targeted policy in FC3. Just prior to the freeze on FC3 we discovered a bug in the security policy during our testing that prohibited access to archives, if my memory serves me correctly it affected only private archives, this would appear to be what you hit. The security policy was fixed. However you may not have the latest security policy. I suggest you bring your system up to date with RPM packages, in particular you will want to be sure you're running the latest selinix-policy-targeted rpm. You also have the option to disable SELinux using the system-config-security-level applet. It is my belief that the GOLD master release of FC3 had the version of the selinux targeted policy which fixed the access to private archives, so it might be that you installed prior to the GOLD release, but I will verify this so no else gets tripped up by this. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] changing MTA from sendmail -> procmail
On Fri, 2004-11-19 at 14:02, Aaron Bennett wrote: > make sure I've got backups of /etc/aliases P.S. you may want to define your MTA in mm_cfg.py to postfix. This will cause mailman to automatically add the aliases to your list of aliases. This is a separate alias file unique to mailman. You'll have to add this alias file to postfix's alias_maps parameter in /etc/postfix/main.cf. Full instructions are in the /usr/share/doc/mailman-*/READEME.POSTFIX file. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] changing MTA from sendmail -> procmail
On Fri, 2004-11-19 at 14:02, Aaron Bennett wrote: > Hi, > > I've got an established mailman installation on RHEL 3 and I'm planning > to change that system's MTA from sendmail to procmail. Does anyone know > of any gotchas or other things I need to look out for? I'm assuming > that in a non-virtual-domain setup like this it should be fairly simple: > make sure I've got backups of /etc/aliases and then uses Redhat's nifty > little redhat-switch-mail program to change to postfix > > Anyone have scars from a similiar assumption? Ah, I'm assuming your got your names mixed up and you meant postfix not procmail. And yes, postfix works quite well with mailman. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] {Oink!!} Pig at the wedding question/diatribe
On Fri, 2004-11-05 at 15:09, Stewart Dean wrote: > I'd think it wouldn't have taken any longer to design the GNU packaging tools > and process > to build single-binary, host-portable output. A lot of thought has gone into > Mailman...a > little more into in packaging would have boosted its acceptance enormously Most open source projects, mailman included, are designed to run on wide variety of systems, each with their own peculiar installation and run-time behavior. In fact your desire for a GNU tool to produce a portable binary installation is exactly what Mailman uses, it is called "autoconf" but is more familiar to people as "configure", the script that executes first to figure out how to make and install the package on a given system. No, its not a GUI tool, but its not hard to use and to be honest it's probably the closest we'll ever get to a GNU packaging tool for a host of reasons. Because packaging across a wide variety of systems is hard/impossible to do in a portable manner the responsibility for producing binary packages falls not to the open source project but rather the OS vendor. The OS vendor knows how to produce binary packages. All this means is you want to go to your vendor for a pre-built binary package with easy installation, not the open source project. In the Linux domain OS vendor equates to "distribution" (e.g. Red Hat, SuSE, gentoo, debian, etc.) For other commercial OS's such as Sun Solaris, IBM AIX, HP hpux, etc. you go to the company you bought your OS from. Or you do the installation yourself with "./configure; make install" -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] {Oink!!} Pig at the wedding question/diatribe
On Fri, 2004-11-05 at 12:36, Stewart Dean wrote: > [ snip free software is hard to use rant ] It seems to me you have several options are your disposal: 1) Pay a nominal fee for your software. In the Linux domain Red Hat and other distribution vendors work hard to provide the type of end user experience you want. Enterprise versions seek to provide stability, security, and ease of use for demanding enterprise class situations by doing active engineering on open source software. Red Hat, SuSE, and others are in business, its not a charity (but you can download free versions of our RPM from the Fedora project, which forms the base for the next enterprise distribution). 2) Contribute your time to the project. Most everything you get for free with an open source project was done by volunteers who thought it was more productive to contribute than complain. Your work in making the project better will be appreciated by all. 3) Don't use something you never paid for or contributed to. John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Error Adding list
On Sat, 2004-10-30 at 14:27, Bernie Johnson wrote: > I am running RH ES 3 and installed the mailman rpm. Every time I try to > create a list it give me this error: > > Error: You are not authorized to create new mailing lists > > Can some one please give me a hand. > > Thanks in advance, > > Tech What user are you trying to do this as? Is it mailman? Permissions are granted on a group basis with the group mailman as the group having permission on the mailman files. When the rpm is installed the user mailman is created and group mailman is created, both uid and gid should be 41. By default the only member of the mailman group is the user mailman. Unless you're executing as a member of the mailman group you're going to have permission problems. For security reasons, even though the user mailman is created by the rpm installation the mailman user is not assigned a password and the mailman login shell is set to "nologin" preventing logging on as the user mailman. This done because the act of installing the mailman rpm should not grant login privileges just because the package was installed (many admins and users install all packages without ever intending to run them, it would be a security hole for installation to open up accounts). The root user will need to assign mailman a password and unlock the mailman account by changing the login shell to something other than "nologin". At that point the proper course of actions is to "su" to mailman or login as mailman which will put you in the mailman directory where you will find the bin subdirectory with the command line utilities. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Question about 2.1.5 Install
On Sat, 2004-10-30 at 23:08, Branden Simbeck wrote: > I have a server using a chrooted environment for my various websites > (running 3 websites). Specificly I am running an a red hat server with ensim > basic. Are there any modiciations to Mailman 2.1.5, outside the regular > configuration, to make it work in a chrooted environement. Is a chroot jail worth it? Chroot jails can be compromised. Mailman does not run in isolation, it has a heavy interaction with your MTA and your web server, it also depends on cron. Both MTA and HTTP servers now reach their tentacles into the overall system very far when trying to utilize various authentication methods, LDAP, etc. Communication between these various components is mostly done via sockets. All of this has to be visible in the chroot, AND all changes outside the chroot have to be reflected back into the chroot, its enormous. Even Wietse Venema the author of postfix has cooled his earlier recommendation for chroot environments. By all means go for it, just don't under estimate the task and weigh the cost against the benefit. Eschewing chroot and instead focusing on best practices, aggressive tracking of security updates, and possible adoption of SELinux (verdict on SELinux is still out) is probably a more realistic security approach than chroot isolation. Just my opinion ... -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Pig at the wedding question/diatribe
On Fri, 2004-10-29 at 17:09, Stewart Dean wrote: > [ installation difficulty rant snipped for brevity ] If your OS vendor (or distribution) provides packages you typically only need to do something as simple as "install mailman" and do a few basic post-install configuration steps. The installation complexity burden is borne by the pre-supplied package and your life is much simpler. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] install from scratch
Your best bet is the INSTALL file in the root of the tree (e.g. after you unpack mailman-2.1.5.tgz). There are also some other README files specific to particular OS's etc. However you might find it easier to just install a prebuilt package for your OS (e.g. rpm, debian package, etc., its up to you know your OS and where to find packages for it) then all you have to do is configure. You may also want to look at the doc here: http://www.list.org/docs.html But note there isn't any build/install doc there, just useful "how do I do this" kind of stuff, you'll also find an excellent FAQ there too. On Wed, 2004-10-27 at 14:17, Nuno Carreiro-Ladeiras wrote: > Hi All. > > Thanking you in advance, I would like someone to help me installing mailman. > I have runned a 30mn research in the Web, Faqs, but I canÂt find a tutorial > that is easy to understand since I am not a programmer or even similar. > > The link that until now I can better understand is > http://sxs.thexdershome.com/internet_serving/mailman.html > > However, still, I think I am not going to be able to install it following > those instructions. > > Can anyone give me a easier link to do it? Like a "idiotÂs guide" ;) > > Regards > Nuno > > > -- > 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/ -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Mailman configuration error
You specified the python directory to configure instead of the path to the python interpreter. What does "which python" give you? Probably /usr/bin/python, you probably don't need to use the --with-python argument (unless you have another version of python installed and you want to force one over the other) John On Wed, 2004-10-27 at 13:55, Adam G. Garson wrote: > Hi -- I'm trying to install Mailman on a Mandrake 10.1 system. I have new > installations of Python 2.3.4 and GCC 3.4.2 both compiled from source -- no > rpms. When I run the configure script I get the error quoted below. This > occurs even as root, so I don't think it's a permission problem. I've done > everything I can think of but can't resolve the issue. Can anybody give me > some guidance on how to troubleshoot this one (I'm not a programmer)? > Thanks very much. > > Adam Garson > > * Distutils is not available or is incomplete for /usr/bin/python > * If you installed Python from RPM (or other package manager) > * be sure to install the -devel package, or install Python > * from source. See README.LINUX for details > bash-2.05b$ > > /configure --with-username=adam --with-cgi-gid=webgroup --with-mailhost=nan > nypay.net --with-urlhost=nannypay.net --with-python=/usr/local/lib/python2.3 > checking for --with-python... /usr/local/lib/python2.3 > checking Python interpreter... /usr/local/lib/python2.3 > checking Python version... ./configure: line 1379: > /usr/local/lib/python2.3: is a directory > cat: conftest.out: No such file or directory > configure: error: > > * /usr/local/lib/python2.3 is too old (or broken) > * Python 2.1 or newer is required > * Python 2.1.3 or better is recommended > > > -- > 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/ -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] qrunner running but not flushing qfiles/in
On Fri, 2004-10-22 at 12:41, [EMAIL PROTECTED] wrote: > Hey Mark, thanks for the reply. Yeah I figured that the missing qrunners were > the problem but there was no log entry that was revealing. Then I read in the > mailmanctl script that restart doesn't kill the parent ps, just the qrunners. > So I manually stopped and started and that did it. We'll see what happens on > the next boot (last one before yesterday was 72 days ago so I'll have to write > a note to myself). Hmm ... depending on your host system arguably its preferable to use the service command to manage services (e.g. invokes the mailman init.d script, which then in turn invokes mailmanctl). For what its worth the vanilla init.d script supplied with mailman calls mailmanctl with the restart argument when invoked with restart. But a more typical restart implementation in init.d scripts for services is stop followed by start (currently done in our distribution). It sounds like Tom would not have run into this problem if that were the case and perhaps the default init.d script (misc/mailman.in) should do that, but read on ... However I'm a little bit perplexed by why a stop followed by a start caused a missing qrunner to be recreated. The master watches for the death of a child and automatically restarts it unless the norestart option is given or a handful of other conditions exist including exceeding the max number of restart attempts, all of which are logged. A master restart is implemented via sending the watcher a SIGINT. If the watcher were dead you should have gotten an error on restart. I'm mildly troubled you had to perform a stop/start sequence without any errors logged. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Beginner questions
On Fri, 2004-10-22 at 10:43, AntÃnio P.F.Ferreira de Almeida wrote: > I' m very new to Mailman and would like to ask a few questions : > 1. For creating a small mailing list (200/300 members), using Mailman and Apache, in > a home computer running Linux, can I use a dynamic IP or do I need a fixed IP ? > 2. How do I assign that IP (fixed or dynamic) to an existing domain ? In general you need a fixed IP, however you might take a look at http://www.dyndns.org, they are one of several organization that provide the type of dynamic to static IP mapping which would be required for this to work with a dynamic IP provided by your ISP. Whether in practice this is reliable and robust is not something I can comment on. You may also have to contend with your ISP performing port blocking. Many ISP's who sell you a personal/home account do not want you to be running servers for which they believe they should be receiving commercial/business class revenues. You will certainly want to address the issue of port blocking and procurement of a static IP with your ISP first. A more viable approach might be to utilize one of the many hosting services that for a very minimal amount of money provide you with a domain, web server, mailman, etc. all managed by them on their servers. I personally have had good experiences with www.dreamhost.net and their costs are very reasonable, but there are many many service providers that will take a lot of the headaches out of running servers yourself. However, these are not in general mailman issues and you're best to pursue the issues with service providers. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Mailman on Solaris-based web server
On Thu, 2004-10-21 at 17:00, Brad Knowles wrote: > At 4:37 PM -0400 2004-10-21, John Dennis wrote: > > > FWIW, the dovecot IMAP server supports Maildir. > > Never heard of it. Is it based on UW-IMAP, Courier-IMAP, or Cyrus? > > Those are the big three. I don't know of any other IMAP server > that anyone is using in any kind of significant operation that isn't > at least based on one of these three systems. I believe it was written from scratch, principal author is Timo Sirainen, [EMAIL PROTECTED], info here: http://dovecot.org We (Red Hat) were looking for a replacement for UW-IMAP and beginning about a year ago began shipping both Dovecot and Cyrus as potential replacements for UW-IMAP. Dovecot is equivalent in ease of use (configuration) as UW-IMAP and has a focus on security (think of it as postfix's response to sendmail). Cyrus fills the need for an industrial strength IMAP server in large organizations. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Mailman on Solaris-based web server
> the only IMAP server > I know of that uses Maildir (a storage format that is supposedly > NFS-friendly) is Courier-IMAP FWIW, the dovecot IMAP server supports Maildir. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Fwd: -1 cluster-admins moderator request(s) waiting
On Sun, 2004-10-17 at 05:25, Martin F Krafft wrote: > This just in from a new list on Mailman 2.1.5-1. A bug? Or 2^32-1 > approval requests? :) FAQ 3.38 http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.038.htp -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Mailman 2.1.5 crashing
On Tue, 2004-10-12 at 16:18, Sasa Stupar wrote: > Version is 2.1.5 as I stated in the subject. Sorry, finger fumble on my part, you did state that, I meant to ask what python version. I've heard an assertion, but not verified by anything I've seen that running mailman 2.1.5 with anything less than python 2.3 can lead to random crashes, a RH 8 system won't have the latest python unless you've installed a newer python yourself. > The last message in the log is: Starting mailman: succeeded. mailman did no processing inbetween being restarted and crashing? Did you look at all the logs, including the SMTP logs? After you restart mailman does the master qrunner process persist until it crashes at some distant random point in the future or does it almost immediately exit? I assume you're not running a Red Hat supplied mailman RPM on your Red Hat system based on the need to remove stale locks since our init.d script always passes the -s flag to mailmanctl and you don't need to invoke mailmanctl directly. Have you tried a Red Hat RPM? You might try setting the core file limit so you generate a core file (uname -c XXX). This needs to be done in the environment that starts mailman. -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] Mailman 2.1.5 crashing
On Tue, 2004-10-12 at 03:03, Sasa Stupar wrote: > Hi! > > I have problems with my instalation of mailman on my RH8 box. I had it > installed for quite some time now and few days ago it is starting to crash > without any explanation in any log. And when I try to restart it first I > have to remove stale pid and then it would start. > Can anyone help me to solve this problem? It would be immensely helpful if you could be specific about the failure. I'm afraid "crash" is too general to offer a diagnostic insight. Are you getting a python trace back due to an exception? If so what is it. Is there anything in /var/log/messages, /var/log/mailman, /var/log/maillog that points to a problem? Is it the master process that's dieing or one of the child queue runners? What is the last thing mailman recorded to a log? What version of mailman are you running? -- John Dennis <[EMAIL PROTECTED]> -- 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/
Re: [Mailman-Users] More help - please
Hmm... now that I think about it, connection refused, are you hitting a firewall on that port? -- 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/
Re: [Mailman-Users] More help - please
Looks like you're getting smtp connection failures. What is your DELIVERY_MODULE set to? What is your SMTP_HOST and SMTP_PORT set to? Can you telnet to these? Does your SMTP server require authentication? John -- 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/
Re: [Mailman-Users] More help - please
Did you look in the mailman logs? Did you look at the system log file? I assume since you can see your message in the mm queue parts of mail are running, but some reason its not getting into the MTA? Have you verified you can use SMTP with postfix? Have you configured the postfix local SMTP delivery? Are you having a postfix vs. sendmail personality conflict? (e.g. some postfix files can be installed to emulate sendmail) What happens when you "telnet localhost 25"? -- 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/
Re: [Mailman-Users] More help - please
On Tue, 2004-10-05 at 15:33, Brad Knowles wrote: > I don't know if this is the only problem, but Python 2.3 is > required for use with Mailman 2.1.5. See > <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq05.008.htp>. Either that FAQ entry is misleading or not quite true (no pun intended :-). It seems to suggest that the need for python 2.3 comes from unresolved symbols True and False. But according to the python doc (see below) the symbols were added in 2.2.1 but with a different type, but it should still work. We (Red Hat) have several distributions that have 2.2.x installed and successfully run mailman 2.1.5. Perhaps I've misinterpreted 2.3 requirement issue cited in the FAQ. http://docs.python.org/whatsnew/section-bool.html A Boolean type was added to Python 2.3. Two new constants were added to the __builtin__ module, True and False. (True and False constants were added to the built-ins in Python 2.2.1, but the 2.2.1 versions are simply set to integer values of 1 and 0 and aren't a different type.) -- John Dennis <[EMAIL PROTECTED]> -- 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/
RE: [Mailman-Users] some questions
On Wed, 2004-09-29 at 15:10, Russ Michaels (Snake) wrote: > Is there anyone on this list or wot ? This FAQ entry should answer your question: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.039.htp > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Russ > > Michaels (Snake) > > Sent: 29 September 2004 16:21 > > To: [EMAIL PROTECTED] > > Subject: [Mailman-Users] some questions > > > > Greetings, > > > > I have recently moved over all our lists to mailman and am > > having the following issues which I cannot seem to find any > > option for in the admin menu. > > > > When messages come in HTML format, the HEADER text is > > missing and the FOOTER text comes as an attachment. > > Some users are also complaining that the whole message now > > comes as an attachment. > > > > How can I fix this ? > > > > Russ Michaels > > Macromedia Certified ColdFusion Professional > > > > Satachi Internet Development > > > > Phone: 0870 787 3610 > > Tech Support: 0906 9607800 > > FAX: 0709 2212 636 > > <http://www.satachi.com/> http://www.satachi.com email > > general: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] email > > support: [EMAIL PROTECTED] > > -- > > -- > > -- > > - > > For ColdFusion hosting, visit www.cfmxhosting.co.uk > > <http://www.cfmxhosting.co.uk/> Join our Coldfusion forums > > and discussion lists at www.cfdeveloper.co.uk > > <http://www.cfdeveloper.co.uk/> > > -- > > -- > > -- > > -- > > > > <mailto:[EMAIL PROTECTED]> > > > > -- > > 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/ > > > > > -- > 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/ -- John Dennis <[EMAIL PROTECTED]> -- 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/
[Mailman-Users] Re: [Mailman-Announce] RELEASED Mailman 2.1.5
On Sat, 2004-05-15 at 19:22, Barry Warsaw wrote: > This version also contains a fix > for an exploit that could allow 3rd parties to retrieve member > passwords. It is thus highly recommended that all existing sites > upgrade to the latest version. Could you be more specific about the exploit? Is there a CVE or CAN open against it? I assume given the public announcement this is not an embargoed security exploit, or is it? -- John Dennis <[EMAIL PROTECTED]> -- 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/
RE: [Mailman-Users] no 2.1 version on Gnu FTP site?
On Wed, 2003-01-08 at 13:19, Angel Gabriel wrote: > When will this RPM be produced? And where can I get it from? In the next few days. I will post a pointer when its done. I'm trying to clean up some issues in the spec file at the moment. Getting some testing on installing this package will be appreciated. On Wed, 2003-01-08 at 13:37, Adam Beatham wrote: > along these same lines.. I don't suppose there's a BSD package, I'm sorry I can't help you with BSD, perhaps someone else can. John -- 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/
[Mailman-Users] no 2.1 version on Gnu FTP site?
I went looking for the new 2.1 version so we can update the RedHat RPM with it, but I was surprised that there was no 2.1 version on the GNU FTP site, but I did find it on SourceForge. Is this an oversight? John -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
