Re: [Mailman-Users] move from version 2.0.11 to 2.1.5
On Wed, 2006-01-25 at 12:32 -0500, Chad Rebuck wrote: I've installed a new server running Fedora 4. I can create a new list, but I have not determined why mailman is not seeing the users from my 2.0.11 list. I copied the lists/ and archives/ dir from the old server to the new one. I have read through the INSTALL and UPGRADE docs following all the steps -- I think. If more details are needed please let me know. How did you install mailman? Was it from scratch or did you use our RPM? If you used the RPM then you should look at /usr/share/doc/mailman-*/INSTALL.REDHAT for documentation on the directory structure, you may not have copied the old list data into the locations currently used. -- John Dennis Red Hat Software -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] domain change for mailman
On Mon, 2006-01-23 at 15:21 -0800, Mark Sapiro wrote: noc ops wrote: i'm looking at changing domain name for an operation mailman server and looking at the following mailman config files to reflect this change. /etc/hosts and host related files /etc/postfix (in my case) /etc/mailman/mm_cfg.py /usr/lib/mailman/Mailman/mm_cfg.py are these config files sufficient to reflect the change for mailman not to break? did i miss anything? It is unclear to me why you have two mm_cfg.py files. Something to do with your 'package' I suppose. Does one import from the other? They are the same file. The mm_cfg.py in /etc/mailman is a sym link to /usr/lib/mailman/Mailman/mm_cfg.py. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
what does ls -l /home/mailman/domains/chuckie.co.uk/scripts/driver say? what does /usr/sbin/getenforce say? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error when accessing Mailman CGI web interface
On Tue, 2005-12-20 at 16:42 +, Mark Cave-Ayland wrote: Thanks for your help. This is what I get from the two commands above: $ ls -l /home/mailman/domains/chuckie.co.uk/scripts/driver -rw-r--r-- 1 mailman mailman 9736 Dec 20 14:20 /home/mailman/domains/chuckie.co.uk/scripts/driver $ /usr/sbin/getenforce Disabled Then I don't think I can help :-( Your original post said the you built mailman with uid=gid=mailman and the wrapper seems to be executing correctly based on a subsequent post. All looks good from here. Here is the sequence that should be happening, see if you can find any reason why its not: apache invokes the cgi wrapper as the user 'apache', the cgi wrapper verifies it was called by apache, then the wrapper does a setgid to mailman and invokes the driver script, the driver script should be group mailman, so it should have no problems reading the driver script, but that is what is failing, go figure, seems like it should work. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Archive browsing question
On Mon, 2005-12-19 at 11:47 -0800, Elvis Fernandes wrote: From a web browser, non-members of a mail list can browse the archives. Is this a correct statement? For example, if I am NOT a member of mail-list, I can still go to http://mailman/pipermail/mail-list and browse the archives. Now, there must be a way to block non-members to browse the archives of mail-list In todays security world there sure must be a way. I would like to know others experiences. Some lists are appropriate for public consumption, some are not. That is why mailman supports both public and private archives, it is a per list configuration. However please note, the security protection on the private archives is not terribly strong, it requires only a username/password, something which by default is mailed in the clear once a month. Security in general was not a prime design point for mailman, a limitation which is recognized and hopefully will be better addressed in MM 3.0. If you have very sensitive information in your archives you may want to consider an alternate solution. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] High usage -- making Mailman nice
On Thu, 2005-12-08 at 17:50 -0800, Mark Sapiro wrote: John Dennis wrote: If your MTA can only handle one, or a small number of client connections then each connection will be busy handling SMTP_MAX_RCPTS and other client connections will queue up. If you have 4,000 recipients then you have the potential to tie up 8 SMTP client connections. I don't think this is correct. Unless there are multiple outgoing runners processing slices, I don't see how SMTP delivery is multi-threaded, and even if there are multiple runners, a single message to even 4000 recipients is going to be processed in its entirety by one runner. Depends on whether the client waits for a success status or not, which if my memory serves me correctly (its been failing lately :-) is not the behavior in an SMTP transaction. I believe the MTA accepts the input, queues the request and control is returned, at that point I believe the connection is typically closed. At this point the outgoing running will loop again and attempt initiate a new SMTP transaction. At least that how I think it works, plus the behavior is specific to each MTA. If the client waits for the transaction to complete they of course you're right. Mailman is not multi-threaded but many MTA's are or more properly many MTA's pre-fork a pool of processes which are managed like threads. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Permissions problem accessing commands via php
On Fri, 2005-12-09 at 12:46 -0600, Dave B wrote: I am trying to create some php forms that use the shell_exec function to run some of the Mailman command line commands. i.e. I have a script that lets an admin user enter an email address and then uses the find_member script to return all lists that email address is in. To do this I had to set the permissions on the config.pck files to 664 (I am the only one with shell access to the server). This works fine except that for some reason the permissions will sometimes revert back to 660 and then the script won't work. Only one config.pck file has to have 660 permissions for the script not to work. When I change that particular file back to 664 - the script works again. ANy ideas on what would cause the permissions to change back to 660? I would also like to be able to add members or remove members etc using this method but I get permissions errors even if I change the permissions to 666 on all the files in particular list directory. Any ideas on what I would need to do to be able to do this? Thanks for any help on this one. Essentially you have two choices: 1) The php script executes as a member of the mailman group 2) The php script invokes a wrapper just like the CGI does. This is preferred for a variety of security reasons. It would not be hard to create a new wrapper from the existing wrapper src 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] High usage -- making Mailman nice
On Thu, 2005-12-08 at 11:10 -0600, Caylan Van Larson wrote: Morning, We're running MM v2.1.4-4, we're experiencing such high usage on our dual xeon server when mailman sends to 4000 users that port 25 becomes unresponsive. is there a way to nice the mailman delivery? It sounds like your MTA is inefficient in some manner, is not a huge load for a dual server backed with a high bandwith connection. How many client connections can it simultaneously handle? Any chance you've got DNS delays (especially reverse lookup)? There are ways to control how many recipients are sent in each SMTP transaction. SMTP_MAX_RCPT = 500 is the default in mailman, defined in Defaults.py, overridden in mm_cfg.py If your MTA can only handle one, or a small number of client connections then each connection will be busy handling SMTP_MAX_RCPTS and other client connections will queue up. If you have 4,000 recipients then you have the potential to tie up 8 SMTP client connections. If you raise SMTP_MAX_RCPTS you may exceed your MTA's limit on number of recipients, but you'll consume few connections increasing the pool of available connections. If you lower it you'll increase the total connections needed, but your MTA should take connections round robin allowing other to jump in. By all means verify how many client connections your SMTP can handle. If you have VERP or personalization turned on mailman will have to initiate one SMTP transaction per recipient (are these features turned on?). This is inefficient because there is one recipient per SMTP connection. It will take the SMTP much longer to process because of the higher overhead, but on the other hand there should be plenty of opportunity for other clients to obtain a connection from the SMTP connection pool because mailman will cycle through connections in a serial manner leaving the rest of the SMTP client connection pool available for other SMTP clients. 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Uhhuh, my GID blues goes on... :( - Case SOLVED!
On Mon, 2005-11-28 at 10:23 +0200, Niemi Hannu wrote: This would seem to say that postfix is using two different GIDs to invoke the wrapper depending on the list (or, if this is the case, on where the list's aliases come from). I think you need to carefully look over your Postfix configuration and see if it might be getting mailman aliases from two different places and using different GIDs for the different places. Aargh.. I feel dumb, dumber, dumbest... Though, I still don't 100% grab it, I managed to solve the problem, which was MUUUCH silleer I did even anticipate. I had read the postfix configuration many times through but forgot to check the postfix aliases-file, which had all the vintage lists in it. After removing the lists form the aliases file everything started to act logically. I did put the lists in there when setting the listserver fast up after the previous server crashed (physiaclly). Afterwards I added the mailman-generated aliases-file into postfix aliases and just forgot to delete the mailman-related aliases from the aliases file. As the lists worked all right (through the probably primary aliases file) I didn't notice any problems during that time. The problem just manifested itself as now, as we needed a new list. What is strange is that the wrappers in the aliases file was just the same as in the mailman aliases file, so it still beats me, why it didn't work. But, let's hope this cured the problem until forever! :) The reason is because of a Postfix feature. Postfix will by default, although it is configurable, run external commands found in an alias file under the uid/gid of alias file it found the alias in. Thus you can have postfix run external commands using a specific uid/gid by partitioning your aliases into separate files, all of which share a common uid/gid requirement. If you keep all the mailman aliases in an mailman only alias file with mailman specific uid/gid then when those aliases instruct postfix to run a command (e.g. the wrapper) then it will do so with the uid/gid of the mailman alias file. In your case you ended up with a mixed bag of aliases and depending on which bag the alias was found in first you got the uid/gid of that bag, hence the seemingly inconsistent behavior, which was in fact very consistent. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Setting up lists on a replacement list server w/different name
On Fri, 2005-11-18 at 06:58 -0800, Greg Earle wrote: Turning off the old machine and creating the lists on the new, renamed-to-be-the-old machine would then mean that the new lists would have to work straight out of the box, with no downtime. Given my unfamiliarity with the software, this isn't too likely (in fact, I can't even get the crontab.in cron jobs working; why do the default entries in that file contain entries that say mailman /var/mailman/mail/program instead of just /var/mailman/mail/program? It results in the not-unexpected error /bin/sh: line 1: mailman: command not found), so I was looking at possible alternatives - surely I'm not the first person to install Mailman on a new system that is designed to replace an old one (with the new one being renamed to take over the old one's name)? The reason the cron entries have mailman in front of them is because that's the user the job is supposed to run under. Cron has been evolving, there are multiple ways to specify cron jobs with different syntax. If at all possible I recommend you install a mailman package prepared by your vendor as all this issues have been worked out. I see that your new system is RHEL, the Red Hat RPM has been pre-configured to integrate with the rest of the system, installation questions can be answered by reading /usr/share/doc/mailman-*/INSTALL.REDHAT. Also note starting about 1.5 years ago we modified the mailman RPM so that the cron jobs are only run if you are running the mailman service, it used to be that installing the RPM, something many people did without ever running mailman, would then also install the mailman cron jobs which was a drag on system resources and filled the log files with pointless messages. Now the cron job only run when you start the mailman service, once again, this is all explained in INSTALL.REDHAT. With respect to your host name change. What you are in effect doing is trying to create a virtual host (you want one host to respond as if it were another). Both mailman and apache have mechanisms to support virtual domain, extensive documentation can be found in the mailman FAQ and at apache.org. So does postfix, I don't know about the other MTA's. However, you're going to have a problem if you don't turn off the old name, you can't have two machines trying to answer service requests for the same name without a very complex scheme which is probably far beyond what you want to get involved with. Mailman's involvement with the name change is minimal, it effects all internet services. The short answer is for all practical purposes there can only be one machine who answers to that name. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can't run qrunner because of permissions problem
On Thu, 2005-11-17 at 12:09 -0500, Eric Evans wrote: Thanks for you response, Mark. However, I've tried running mailmanctl both as root and as mailman and it still fails with the permission denied error on the pid file. So now I'm wondering if there is some kind of incompatibility between the new version of Mailman and Solaris 8? We have run Mailman 2.1.2 successfully on Solaris 8 before, but we recently upgraded to 2.1.5. If anybody has any further suggestions for things to try, I'd appreciate hearing them. mailmanctl will attempt to run as mm_cfg.MAILMAN_GROUP, mm_cfg.MAILMAN_USER if you run it as root unless you defeat it with the -u or --run-as-user argument. Let's start with the basics, what are the owner and group for the pid file which cannot be modified? If they are not mm_cfg.MAILMAN_GROUP, mm_cfg.MAILMAN_USER then remove the file manually because most likely someone during initial testing/setup ran it in some other way. You should then be fine. Do verify the values of mm_cfg.MAILMAN_GROUP, mm_cfg.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=showamp;file=faq01.027.htp
Re: [Mailman-Users] having trouble getting webpages to come up
On Thu, 2005-11-17 at 15:10 -0500, Eric Evans wrote: Hello, I think I've finally gotten my Mailman installation setup, but when I try to access the administrative webpages through my browser I get the generic Apache page coming up instead of the Mailman admin page. I would assume that DocumentRoot has to be set in the httpd.conf, but to what? The Mailman documentation doesn't say anything about this. Thanks, Eric Is your ScriptAlias defined? http://www.gnu.org/software/mailman/mailman-install/node10.html -- 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/jdennis%40redhat.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.027.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=showamp;file=faq01.027.htp
Re: [Mailman-Users] having trouble getting webpages to come up
On Thu, 2005-11-17 at 15:35 -0500, Eric Evans wrote: Yes, the ScriptAlias is properly defined in my httpd.conf, as specified in the installation instructions. I still can't get the Mailman admin webpage to come up, just the Apache page instead. If anybody has any further troubleshooting ideas about this I'd appreciate hearing them. Thanks a lot... And did you restart Apache so it would reread its configuration? Are you getting a 404 Not Found error? Do you have any rewriting rules enabled which might rewrite the mailman URL by mistake? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] having trouble getting webpages to come up
On Thu, 2005-11-17 at 16:26 -0500, Eric Evans wrote: Hello again, And did you restart Apache so it would reread its configuration? Yes. Are you getting a 404 Not Found error? No, when I try to connect to the Mailman admin web page with my browser, I get a generic Apache page instead of the Mailman admin web page. Do you have any rewriting rules enabled which might rewrite the mailman URL by mistake? No, we're definitely not using any rewriting rules. What I'd really like to know is, what exactly is it that connects Mailman to Apache? Is it just that one ScriptAlias statement in the httpd.conf? If so, then how exactly how does this work? I'd really like to understand the process by which the Apache server is able to find the Mailman admin web page. There is clearly some kind of big disconnect between Mailman and Apache on our server. What connects mailman to apache can be answered two ways, both are important. 1) The proper URL, which makes sure you're connected to the right server, and it has the right path to get to the mailman cgi. 2) Apache must understand the path part of the URL is to be directed to mailman's cgi, this is what ScriptAlias does. For example: http://myserver.example.com/mailman/listinfo/mylist the myserver.example.com part of the URL directs to the web server on the node myserver in the domain example.com provided that's the right web server and its apache then apache looks at the path part of the URL, which is: mailman/listinfo/mylist ScriptAlias /mailman/ /usr/local/lib/mailman/cgi-bin/ ScriptAlias tells apache that paths which have mailman should be translated so that mailman is replaced by the cgi location and executed. In this case the cgi location is /usr/local/lib/mailman/cgi-bin, it will try to find the script listinfo in that directory because that is the next part of the path and it will pass mylist as a parameter. See the following doc: http://httpd.apache.org/docs/2.0/mod/mod_alias.html#scriptalias -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Digest Option Problems
On Wed, 2005-11-16 at 11:00 -0500, Marty Wiggins wrote: I have the Digest Option available to my members (about 1003), but it does not work automatically. I can make it submit, but it does not do it automatically. Can anyone offer a suggestion? Have you enabled mailman's cron jobs? In particular the senddigests cron job needs to be scheduled to run periodically. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] migrating lists from 2.0.13-7 to 2.1.5-33
On Mon, 2005-11-14 at 12:58 -0500, Axel Haenssen wrote: Hi Folks, I am currently running mailman on an older computer. OS is Redhat Linux 7.3, Mailman Version 2.0.13-7 I would like to move all the lists to another, newer server running RedHat Enterprise Linux 4 and Mailman 2.1.5-33 installed Could anyone tell me which folders from the old version I have to move where? Do I have to convert the old /etc/aliases file to the new settings? Can I just move the archives?? There is a script, /usr/lib/mailman/bin/update, which is supposed to update from a prevous version to the current version. I have never used it so I cannot testify as to how well it works. Also note the 2.1.5 versions have slightly different directory locations than does the standard upstream mailman. A quick look at the update script suggests that as long as you install the new version and run update from that it should use the new directories because it will be reading the directory locations from the new Defaults.py file. The aliases from 2.0 are not the same as used in 2.1. Don't move them over, instead use /usr/lib/mailman/bin/genaliases to generate a new set of aliases. Please read the file /usr/share/doc/mailman-*/INSTALL.REDHAT for Red Hat specific tips and to learn that 2.1 has a different way of being run than 2.0 did, you'll now start mailman as a regular service. Cron will be taken care of automatically. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Having mailman treat two domains as equal during migration...
On Fri, 2005-10-28 at 09:30 -0600, Mike Cisar wrote: At this point the mail server is configured to respond to both domains, and treat them as the same. Mailman itself is configured to use the new domain both on the web side, and all the lists have been changed to use that as their preferred domain. However the problem arises with the list subscribers themselves. We can't simply export the membership for the lists and change everyone to the new domain because everyone won't be sending with the new addresses at once. In the worst case scenario we could export the list make the changes and reimport with nomail set so that everyone has a duplicate membership, and then remove the old domain accounts once the conversion is complete. I'd prefer to save this as a last resort at this point as it is kind of messy. What I would like to do is do a one-shot conversion of all the users to the new domain name and then internally to mailman, when the message is first submitted into the mailman process simply have a regex replacement of the sender's domain name so even though the message might actually be coming from [EMAIL PROTECTED] mailman would read that in, do a quick replace in its mind and for the rest of the process treat the message as if it had come from [EMAIL PROTECTED] Why involve mailman? Why not use either the alias feature or the address rewriting feature of your MTA? But don't you have a larger problem? If the user is still using his old address and thus receiving mail at his old address and you change his address to the new domain when mailman sends the mail to the list then how is somebody going to respond to that user? It's going to go to the new address right where he won't see it (or were you planning on aliasing these as well?). -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Having mailman treat two domains as equal duringmigration...
It's Friday afternoon so forgive me a little tongue-n-cheek humor :-) On Fri, 2005-10-28 at 12:54 -0600, Mike Cisar wrote: Rule #1 in configuring sendmail... if it's working don't touch it :-) Corollary #1 follows from Rule #1: sendmail configuration is so painful it can't be changed readily. Thus Rule #2 follows from Corollary #1: Don't use sendmail :-) -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman without hosting mail server
On Thu, 2005-10-27 at 10:27 -0400, Darich Runyan/OMNI INFOSEC HQ wrote: All, New to the list and mailman so please go easy. ;^) I did check the archives as well as did some extensive searching online and was unable to find an answer to my question. My company's email is hosted by an email provider. This has not been a bad arrangement; however, now we would like to provide some email lists. Is it possible to host mailman and lists without hosting our own mail? If it is possible would any of you please point me to some documentation or possibly point me in the right direction? The general answer is no. The standard mailman deployment requires access at the root (e.g. admin) level to the mail transport agent (MTA) and the web server. There are various schemes whereby one can decouple these components and some folks have tried this, I cannot comment on their success or satisfaction. But there are two things to be aware of here. 1) Setting up a decoupling strategy requires a moderately sophisticated knowledge of how the various components work, if you have that level of expertise you probably could be doing your own hosting instead of relying on an external hosting vendor. 2) Many hosting vendors provide mailman mailing lists as part of their hosting package. If your company prefers to use a hosting vendor, and there are many fine reasons for that decision, then perhaps the path of least resistance and greatest success to select a hosting vendor that provides mailman support in addition to the other services your company needs. FWIW, I've had good luck with www.dreamhost.com, they offer many excellent features on their accounts for a very reasonable fee. I'm not affiliated with the company at all. Although I'm more than qualified to provide my own hosting for my personal computing endeavors I believe the approximate $10/month for what I get is not worth the headache of DIY (Do It Yourself), YMMV. A little bit of searching will yield a number of other hosting companies with mailman support. One caveat, if you do go with the hosted solution you won't be able to perform some of the fine grained administration tasks you'll see discussed here (using the command line utilities) because that requires root level access to the server. In practice I tend to believe that is not a huge issue, but you should be aware it is a limitation. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Host not found
On Tue, 2005-10-25 at 15:17 +0200, Daniel Cuschieri wrote: Woops my bad! I quoted the incorrect error message! The error msg I am getting is this one: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 [EMAIL PROTECTED]: Recipient address rejected: User unknown in virtual alias table) - Transcript of session follows - ... while talking to mail.mydomain.org.: DATA 550 [EMAIL PROTECTED]: Recipient address rejected: User unknown in virtual alias table 550 5.1.1 [EMAIL PROTECTED]... User unknown 554 Error: no valid recipients This is a postfix MTA error, as such it is not a mailman error, as such you should direct your research towards postfix (www.postfix.org) not mailman. However, that being said I'll try to explain what is going on and I hope that will point you in the right direction. At the core of the problem is that postfix does not know about your mailman aliases. There is documentation in the mailman installation guide on configuring mailman and postfix (http://www.list.org/mailman-install/node12.html), start by reading that. Next postfix has an option to reject mail for local users which are not known to postfix, that is what is getting triggered here, so read this postfix documentation (http://www.postfix.org/LOCAL_RECIPIENT_README.html). Finally, it appears you have virtual addressing enabled for postfix, I'm not sure why you need this, its seems like an unnecessary complication for your set up. The mailman postfix integration guide how to configure this, but like I said, I don't see why you need this, or at least you haven't indicated why you need to map a non-existant domain. The postfix site has good documentation on virtual domains (http://www.postfix.org/VIRTUAL_README.html), reading that might shed some light. 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Restart Mailman and IP help
On Sat, 2005-10-22 at 20:47 +0800, ML wrote: Hi, I paid to have Mailman installed on my DirectAdmin CentOS server a few months ago, recently I had to change the server hostname and IP and Mailman no longer sends out emails! (the people that originally installed Mailman will fix the problem if I pay for a one hour support charge, but I believe it is just a matter of updating to the new IP or hostname) Also: 1) I can¹t find the mm_cfg.py file! Where should it be? 2) how exactly do I restart mailman, what directory must I be in? Does anyone know where on Mailman or server I need to enter/change the new IP or hostname? CentOS is a repackaging of Red Hat Enterprise Linux, assuming your consultant installed the Red Hat mailman rpm then the mailman source files are in /usr/lib/mailman/Mailman. mm_cfg.py is also sym linked from /etc/mailman/mm_cfg.py. You could also locate the files via rpm -ql mailman or by reading /usr/share/doc/mailman-*/INSTALL.REDHAT (unless CentOS changed the name, they are required to remove all branding). The mm_cfg we ship derives the host name from the socket networking code, you don't have to explicitly set it in mm_cfg. However, if you created a list and then changed the hostname you'll have to fix the lists you already created because that information is embedded in the list after creation. The mailman FAQ covers this topic in detail. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] to install MAILMAN at a provider
On Fri, 2005-10-21 at 19:33 +0200, antoine wrote: Hallo, I have a account at a provider (1 1) (space on their Server) with Python implemented and actived. Is it possible to install Mailman ? No. Mailman requires integration with other system services (MTA, httpd, cron) that you almost certainly would not have access to. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] add_members and email confirmation
On Fri, 2005-10-21 at 14:23 -0400, Ren Bucholz wrote: Hello, I have a signup sheet that subscribes people to a Mailman list by using PHP to call add_members (the PHP is below, FYI). My problem is that add_members seems to ignore the email confirmation settings from the admin interface. Even though my list is configured to send a confirmation message, subscribers only get the Thanks for signing up! email. Does anyone know of a way to use add_members in a confirmed-opt-in list? Thanks very much! Not is its current manifestation. The reason is that manual adding of members assumes this is an approved action. You have two choices: 1) redirect them to the signup page for the list (this has the advantage of allowing the user to set some preferences and see some basic info). 2) Copy the add_members script to a new name and edit it so that it calls AddMember instead of AddApprovedMember. See Mailman/Cgi/subscribe.py for an example of how to do this and the various exceptions you'll have to catch and handle. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Interface questions
On Wed, 2005-10-19 at 13:42 -0400, JOSEPH DAMICO wrote: Hello, We are considering a conversion from Listproc to Mailman. We have a few concerns, but our chief one is authentication. Here are two questions in this regard: (a) We would like to have Mailman interface with our Kerberos system, so that the passwords our students and faculty use for their e-mail, course logins, and almost every other authentication procedure would be the same passwords they use to access mailing lists. Has anyone developed a Mailman-Kerberos interface? (b) A number of people subscribed to our lists are from outside the university, so a Mailman-Kerberos interface would not work for them. Ideally, we would have users communicate with another program (such as Shibboleth). Then we would determine whether to use the Kerberos interface (for university people) or the regular Mailman password (for those non-university people) to communicate with Mailman. Has anyone developed a Mailman-Shibboleth interface? To the best of my knowledge neither has been developed. However, it isn't terribly hard and you should consider developing it yourself and contributing the code. Here is what you would need to do: Mailman comes with a member adapter plugin. You would override the method authenticateMember() to perform a authentication validation. I'm not sure if there is an existing python module for kerberos authentication, if not you would need to write one that checks the user's ticket. You would also need to add some code to automatically invoke your member adapter. You also need a method to determine if the user is in your kerberos realm, -or- you could attempt a kerberos authentication and if you get a unknown principal error attempt authentication with your fallback mechanism. Mailman lets its members set and get their passwords, YOU DO NOT WANT to allow this with kerberos so you would probably also override setMemberPassword() and getMemberPassword() to be a no-op. You would also want to configure the site defaults to never send password reminders. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Interface questions
On Wed, 2005-10-19 at 13:42 -0400, JOSEPH DAMICO wrote: (a) We would like to have Mailman interface with our Kerberos system... hmm... thinking about this a bit more, while getting mailman to authenticate with kerberos wouldn't be hard you're going to run into some other nasty problems you can't ignore 1) The web pages will prompt for credentials, you do not want this because kerberos is a single signon system (SSO). You would want to remove this prompting, that is a larger task. But you may need to retain it for users not your kerberos realm, but see points 2 and 3. 2) You will be dependent on external mechanisms for ticket generation. That may or may not play well for your mailman user community. For example if I'm trying to access mailman remotely via the web how would I establish a ticket? 3) Unless you force all your mailman URL's to use SSL (TLS) and you allow password entry you will have exposed a very critical password to the world, potentially the kerberos passwords of your entire user community. Mailman currently transmits passwords in the clear in many circumstances, the only reason this has not become more of an issue is because user's are encouraged not to use an important password for 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Debian Mailman Setup Question
On Sun, 2005-10-09 at 04:18 -0400, Michel Vaillancourt wrote: Hello to the list. I am setting up my second mailman box; this one is a Debian 'Etch' installation. It is a Postfix MTA, with two domains that I wish to host lists for on the one box. I am attempting to use the '/var/lib/mailman/bin/postfix-to-mailman.py' file as a Postfix transport engine, per the instructions. However, for some reason, I can't get Postfix to accept mail for my testing list; it returns: 550 [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table I am presuming that there is a step that I have missed in the set-up, but I can't for the life of me figure out what it is. Can someone who has gotten this working give me a shout and let me know what the gotcha is? Many thanks in advance. This has nothing to do with mailman, it is a postfix configuration issue. Postfix can be configured to reject mail if the receipient is not local. You have this configuration setting in effect. I suspect your problem is that you don't include $alias_maps in the local_recipient_maps parameter in postfix's main.cf. This is very clearly documented in the comments in main.cf and the LOCAL_RECIPIENTS_README file that is part of the postfix distribution and available on www.postfix.org. You need the alias_maps because that is where you've defined mailman's 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] How to alias /lists/mylist to /lists/mailman/listinfo/mylist?
On Mon, 2005-10-03 at 11:44 -0500, Matt England wrote: How can I change/add to the RedirectMatch alias structures in my httpd.conf file excerpt below such that a /lists/mylist URL path gets redirected to /lists/mailman/listinfo/mylist while still supporting the /lists redirect to /lists/mailman/listinfo? I believe you will need to perform a URL rewrite which special cases the component mailman when following the lists component. This type of functionality is available in the mod_rewrite module. http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html Practical examples here: http://httpd.apache.org/docs/2.0/misc/rewriteguide.html Be aware that mod_rewrite is not an easy module to master, at a minimum you will need a solid understanding of regular expressions. I think what you need to do is craft a rule which first attempts to match /lists/mailman and if that matches terminate the rule processing outputting the matched URL, else continue to process and rewrite the URL to the per list URL. BTW, rewrite != redirect -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] apache errors
On Thu, 2005-09-29 at 13:55 -0400, Joe Damico wrote: Bryan: I had this problem myself - very recently. This was on a Solaris implementation of Mailman. The values in question are: DEFAULT_EMAIL_HOST = 'hostname' DEFAULT_URL_HOST = 'hostname' I had appended these values to the file: /usr/local/mailman/Mailman/mm_cfg.py That didn't work, so I replaced the hostname with the fully qualified network name: 'hostname.domain.edu' That didn't work either. So, then, I put these values into the file: /usr/local/mailman/Mailman/Defaults.py And then everything worked correctly! Something is not right then. One should never edit Defaults.py. mm_cfg.py includes the contents of Defaults.py via this line: from Defaults import * Then in mm_cfg.py one overrides any settings previously imported from Defaults. In addition, the HTTP Error 403 - Forbidden, is not generated by invalid host names or URL's. This error says the URL was located but the client does not have permission to access it, this is a http server configuration issue, not a mailman configuration issue. I suspect the problem is the http configuration for the directory that was originally posted omitted the Options ExecCGI which is required to tell the http server it is permissible to execute cgi scripts in this directory. Here is what I use, adjust the path to your installation: ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Directory /usr/lib/mailman/cgi-bin/ AllowOverride None Options ExecCGI Order allow,deny Allow from all /Directory -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] apache errors
On Thu, 2005-09-29 at 14:23 -0400, John Dennis wrote: I suspect the problem is the http configuration for the directory that was originally posted omitted the Options ExecCGI which is required to tell the http server it is permissible to execute cgi scripts in this directory. Oh, almost forgot, but any changes to httpd configuration require the httpd server to be restarted in order for it to see the change. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] changing config.pck values? (I'm in a pickle)
You probably want to use the fix_url utility. Look in PREFIX/bin/fix_url.py, you will find documentation at the top of the file. Note, you don't run fix_url directly, its invoked by running PREFIX/bin/with_list, the doc explains 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can we use an external mail server with mailman ?
On Fri, 2005-09-23 at 16:27 +0200, julien grosjean wrote: MAIL SERVER DETAILS My Mail Server is NOT on the same server than my mailman server... My mail server is proxiad.com (217.109.179.10) with smtp.proxiad.com and pop.proxiad.com (This server requiert an authentification... ) My mailman server is extranet-proxiad.com (193.252.219.206) All emails are create on the mail server. The mail server receive the mail correctly. With my mail client, [EMAIL PROTECTED] receive the mail, but not suscribers... THE PROBLEM : I create a test list via web interface. We can suscribe to the list, but the problem is than when we sent an email to the list email, such as [EMAIL PROTECTED], just this email receive the mail... Only [EMAIL PROTECTED] receive the mail from the sender... Is there a configuration to make ? Perhaps there is an aliases problem ? Should aliases be on the mail server or on the mailman server ? Part of the problem is the term mail server can be confusing because there are two mail servers in the picture, a receiving mail server and a sending mail server. Mailman needs run on the same machine the receiving mail server is on otherwise your aliases will not work. The reason is because when the receving mail server receives an email destined for a mailman list the mail server will via its aliases determine the destination for that list email is a program called mailman, thats what all those aliases are all about. The receiving mail server then hands the incoming list email to the program mailman. It can only give it to the program mailman if mailman is running on the same machine. Mailman in turn takes the email it received and looks up all the members of the list and forwards the email to each of them. To do this mailman invokes a sending mail server. Often the sending and receiving mail servers (SMTP) are the same and run on the same box. But you can direct mailman to use a different sending SMTP server via the SMTPHOST variable. Summary: mailman and the receiving SMTP server must be on the same machine. You description is a bit confusing because the way I read it mailman has in fact received the list email (your previous post shows mailman sending smtp posts). It could only have done that if it the its running on the same machine as the receiving SMTP server and the aliaes are correct. I suspect what actually occurred is those are examples from mail sent on the machine mailman is running on where everything will resolve 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can we use an external mail server with mailman ?
On Fri, 2005-09-23 at 16:27 +0200, julien grosjean wrote: DEFAULT_EMAIL_HOST = 'proxiad.com' My mailman server is extranet-proxiad.com (193.252.219.206) We can suscribe to the list, but the problem is than when we sent an email to the list email, such as [EMAIL PROTECTED], Sorry, I should have said this in my last email. This will not work. You are tyring to send mail to proxiad.com but mailman is on extranet-proxiad.com. proxiad.com won't know what to do with the mail, Unless proxiad.com knows to relay the mail to extranet-proxiad.com. Issues of relaying and SMTP configuration are outside the scope of the mailman-users list. You will need to learn what the SMTP server is on proxiad.com and configure it correctly. Or, locate everything on one server. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] new and improved stupid error
On Fri, 2005-09-23 at 09:22 -0700, Sean Roe wrote: Hi All, I am getting the following error now when I start up mailman: [client 192.168.4.199] Exception exceptions.A ttributeError: MysqlMemberships instance has no attribute 'cursor' in bound m ethod MysqlMemberships.__del__ of Mailman.MysqlMemberships.MysqlMemberships ins tance at 0x40221a8c ignored I think the other sysadmin may of removed something by accident (or on purpose) :) Again, I am not a python guy at all, so be gentle. You are getting this error because either MysqlMemberships did not initialize (the variable cursor is set in the MysqlMemberships constructor) or possibly because the MysqlMemberships class instance was destroyed more than once, but that seems unlikely. I would check how the MysqlMemberships class instance is being created, which is likely in a file called extend.py in the list directory ($prefix/lists/NAME where NAME is the name of one of your lists). Sorry, I realize this is a very python'ic answer but its the best I can do given the info. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with mailman
On Thu, 2005-09-22 at 18:39 +0200, julien grosjean wrote: By example, i create a list nammed test We can suscribe to the list, but the problem is than when we sent an email to the list email, such as [EMAIL PROTECTED], just this email receive the mail... Only [EMAIL PROTECTED] receive the mail from the sender... Is there a configuration to make ? Our email server is not on the same server... If your mailserver is not local have you configured your SMTPHOST in mm_cfg? i found nothing in logs... Which logs? Did you look at /var/log/mailman/smtp to see if the message was sent? If so does /var/log/mailman/bounce show the mail bounced? Does /var/log/mailman/error show anything? Does your test list have members? Are you looking in the inbox of the test list members to see if it was received? Are you aware that there is a flag to prevent a sender from receiving their own post, if you send the mail from the same address you're expecting to see it returned in from the list, you won't. Have you looked in /var/log/maillog for SMTP messages? Have you reloaded your 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Password protection
On Wed, 2005-09-21 at 08:03 -0500, George Payne wrote: I can't find in the documentation how you post a message to a list with password protection. Please help. Your previous was seen, but perhaps it was not answered because it's not clear what you're asking. If you could provide some further explanation it would help. Mailman has no direct support for password protecting an email. Mailman is only in the business of being a relay, taking a message from you and redistributing to members of the list. For the most part mailman cares very little about the content of the email and has no password protection of email receipt and delivery. On the other hand there are a variety of schemes by which a sender of email can digitally sign and/or encrypt an email, but all of those schemes are local to the sender and receiver and embedded in the content of the mail, mailman as a distributor of messages is ignorant of 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 Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Password protection
On Wed, 2005-09-21 at 09:00 -0500, George Payne wrote: I am trying to post a message to a list of several thousand emails but I want only the poster (moderator or administrator0 to be able to post a message. What I am trying to find out is how do you protect the list. Its in the FAQ 3.11. How do I create a newsletter/announcement/one-way list? http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.011.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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Monthly password reminders not working
On Wed, 2005-09-21 at 10:42 -0400, Darren G Pifer wrote: Hello, I thought this was working when we moved to Mailman 2.1.6b4 in June, (I could be wrong) but the monthly password reminder is not working. I, and a colleague, have tried to manually test the script for a single list but it is not working. The script that runs out of mailman's cron is: # 5 AM on the first of each month, mail out password reminders. 0 5 1 * * /usr/bin/python -S /usr1/mailman/mailman/cron/mailpasswds I tried testing with: $ pwd /usr1/mailman/mailman/cron $ runas -u mailman ./mailpasswds -l testlist It just exits. Nothing in the mail or mailman logs. Other details: Red Hat Enterprise Linux AS release 3 Any suggestions? Have you verified that the list has its password reminder flag set to yes under general options and that the per user option to receive reminders is enabled for at least some members of the 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Monthly password reminders not working
On Wed, 2005-09-21 at 13:44 -0400, Darren G Pifer wrote: On Wed, 2005-09-21 at 12:13, John Dennis wrote: I tried testing with: $ pwd /usr1/mailman/mailman/cron $ runas -u mailman ./mailpasswds -l testlist It just exits. Nothing in the mail or mailman logs. Other details: Red Hat Enterprise Linux AS release 3 Any suggestions? Have you verified that the list has its password reminder flag set to yes under general options and that the per user option to receive reminders is enabled for at least some members of the list? That answer is 'Yes' to both questions. Anything else? Well, if it were me I'd edit the script and throw in a few print statements in a few judicious places to track what it was or wasn't doing since you're not getting any info in the logs. Python print statements are pretty easy, in its simplest form: print value1=%s value2=%s % (value1, value2) each %s is replaced by the matching value inside the parens, just make sure the indentation of the print statement lines 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] command not in docroot
On Sun, 2005-09-18 at 12:05 -0700, Leo A. Notenboom wrote: I've suddenly started getting that error in suexec_log, and as a result no one can confirm or worse, leave, the mailing lists that up until recently had been working fine. This is on Redhat Enterprise w/ Plesk - I suspect a nightly up2date hosed something that mailman cares about. Any thoughts on what to do to correct this problem? 1) Contact SWSoft, the providers of Plesk 2) Provide a more descriptive error message, otherwise no one can possibly debug this for you. My best guess is that something in your apache config file (/etc/httpd/conf/httpd.conf) changed that either has disabled the reading the /etc/httpd/conf.d/mailman.conf file which contains the ScriptAlias and Directory configuration for mailman, which in turn tells apache about the existence of the mailman cgi URL/commands and tells apache it has permission to execute this outside the document root. I believe there is also a global flag in that may be present in httpd.conf that enables or defeats cgi execution outside the document root. But really, this is not a mailman issue, its either an issue with Plesk or your apache configuration (I know very little about how Plesk works but I suspect it has a very strong interaction with apache configuration which is why since Plesk is in the picture you need to consider Plesk interaction). -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] command not in docroot
On Mon, 2005-09-19 at 11:12 -0400, John Dennis wrote: This is on Redhat Enterprise w/ Plesk - I suspect a nightly up2date hosed something that mailman cares about. Any thoughts on what to do to correct this problem? One more suggestion: If up2date installed something that broke your configuration then you might want to go looking for any files under /etc with a .rpmnew or a .rpmsave extension. When rpm installs a new config file for a package and it detects an existing config file that has been modified locally it will respect the local edit of the config file and install the new version of the file with a .rpmnew extension preserving the local edit. If rpm thinks it needs to overwrite a file it will copy the file with a .rpmsave extension. Looking for these files and comparing them may provide a clue as to what changed and induced the new behavior. The existence of either a .rpmnew or a .rpmsave could represent delta in system configuration that needs closer examination. 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] config.pck, apache, permissions and Errno 13
On Wed, 2005-09-14 at 16:08 +0200, Sam Gamgee wrote: I then installed from source with the --with-mail-gid=mailman option. Thats the situation I'm in now - I can mail, but I can't use the web interface properly. What did you specify as --with-cgi-gid? Both mail and cgi have to line up with how your MTA and web server respectively execute sub-programs. Also, being a bit more specific with how the web interface is not working properly would help solve your problem. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] config.pck, apache, permissions and Errno 13
On Wed, 2005-09-14 at 18:45 +0200, Sam Gamgee wrote: yes I have run check_perms several times. I often get wrong group errors such as: /var/lib/mailman/logs/qrunner bad group (has: list, expected mailman) /var/lib/mailman/logs/smtp bad group (has: list, expected mailman) I don't know what keep causing these, but so far they don't seem to have any negative effects. If check_perms is reporting problems you've got problems you need to fix. By default check_perms only reports problems, it does not fix them, to fix them you need to supply the -f argument. If your cgi wrappers are not group mailman then its setgid property is not going to work the way you expect. For instance if its group list then its going to execute as group list and the fact the files it references are -rw-rw mailman:mailman won't help because they are not in the group list. Make sense? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] config.pck, apache, permissions and Errno 13
On Wed, 2005-09-14 at 19:46 +0200, Sam Gamgee wrote: yes yes yes. I know that. but the results are not permanent. My problem is trying to find out why. I'm trying to tell you why :-) Below are the cgi wrappers on my system as a reference point, adjust the path for your installation. The key thing to note here is the wrapper (anything in the mailman/cgi-bin directory) has two critical properties 1) it is in the group mailman 2) it is setgid (the s flag in the group execute field) What this means is when some entity (e.g. your web server, apache) runs one of this cgi-bin programs the OS will note the files is setgid and then run the program as the group the program file belongs to (e.g. mailman). Without setgid sticky bit the OS will run the program as the group belonging to the entity that invoked it (in this case apache) which appears from your description as to what is happening, the group ownerships are getting changed to apache's group. To further expand on what is happening: when one of these cgi-bin wrappers is called the very first thing it does is ask the following question Who called me? If they are not in a group I trust I refuse to execute because I only work on behest of a select set of trusted groups. For the cgi-bin wrappers that set of groups is the set of groups belonging to your web server and what is set via --with-cgi-gid. If the entity that invoked the wrapper is not in the set of trusted groups you get a group mismatch error and the wrapper exits. If the trust test passes the wrapper continues to execute in the group mailman (because the wrapper's file has the setgid sticky bit set and belongs to the group mailman). If either the setgid sticky bit is not set -or- the wrappers file is not group mailman you're going to get the type of permission problems you're seeing. FWIW, the description applies to the mail wrapper and the MTA, just change the names ;-) % ls -l /usr/lib/mailman/cgi-bin/ total 264 -rwxr-sr-x 1 root mailman 18345 Mar 7 2005 admin -rwxr-sr-x 1 root mailman 18349 Mar 7 2005 admindb -rwxr-sr-x 1 root mailman 18349 Mar 7 2005 confirm -rwxr-sr-x 1 root mailman 18349 Mar 7 2005 create -rwxr-sr-x 1 root mailman 18353 Mar 7 2005 edithtml -rwxr-sr-x 1 root mailman 18353 Mar 7 2005 listinfo -rwxr-sr-x 1 root mailman 18349 Mar 7 2005 options -rwxr-sr-x 1 root mailman 18349 Mar 7 2005 private -rwxr-sr-x 1 root mailman 18349 Mar 7 2005 rmlist -rwxr-sr-x 1 root mailman 18349 Mar 7 2005 roster -rwxr-sr-x 1 root mailman 18353 Mar 7 2005 subscribe -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] config.pck, apache, permissions and Errno 13 SOLVED
On Wed, 2005-09-14 at 21:47 +0200, Sam Gamgee wrote: thanks! that did it. the permissions were wrong, and they weren't being corrected by check_perms -f for me it was: /var/lib/mailman/cgi-bin/ which is: /var/lib/mailman/cgi-bin - /usr/lib/cgi-bin/mailman hmm... it's troubling that check_perms -f didn't fix this, it should have. I can only think of two reasons check_perms would miss the cgi-bin files 1) Its a non-standard installation and check_perms was not updated to reflect the new installation. 2) The fact the cgi-bin directory is a symbolic link (but I would expect that to be transparent because links should just be followed). You might want to run check_perms with the -v verbose option (without the -f it won't change anything). With verbose it will tell you exactly what its checking. You could do something like check_perms -v | grep cgi If you don't get something like the output below then you need to file a bug against whoever provided your mailman package for why check_perms is missing your cgi-bin directory. [EMAIL PROTECTED] Mailman]# /usr/lib/mailman/bin/check_perms -v | grep cgi checking gid and mode for /usr/lib/mailman/cgi-bin checking gid and mode for /usr/lib/mailman/cgi-bin/confirm checking gid and mode for /usr/lib/mailman/cgi-bin/admindb checking gid and mode for /usr/lib/mailman/cgi-bin/listinfo checking gid and mode for /usr/lib/mailman/cgi-bin/private checking gid and mode for /usr/lib/mailman/cgi-bin/admin checking gid and mode for /usr/lib/mailman/cgi-bin/roster checking gid and mode for /usr/lib/mailman/cgi-bin/subscribe checking gid and mode for /usr/lib/mailman/cgi-bin/rmlist checking gid and mode for /usr/lib/mailman/cgi-bin/create checking gid and mode for /usr/lib/mailman/cgi-bin/edithtml checking gid and mode for /usr/lib/mailman/cgi-bin/options checking cgi-bin permissions checking set-gid for /usr/lib/mailman/cgi-bin/confirm checking set-gid for /usr/lib/mailman/cgi-bin/admindb checking set-gid for /usr/lib/mailman/cgi-bin/listinfo checking set-gid for /usr/lib/mailman/cgi-bin/private checking set-gid for /usr/lib/mailman/cgi-bin/admin checking set-gid for /usr/lib/mailman/cgi-bin/roster checking set-gid for /usr/lib/mailman/cgi-bin/subscribe checking set-gid for /usr/lib/mailman/cgi-bin/rmlist checking set-gid for /usr/lib/mailman/cgi-bin/create checking set-gid for /usr/lib/mailman/cgi-bin/edithtml checking set-gid for /usr/lib/mailman/cgi-bin/options -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem integrating v2.1.5 into the mail system
On Tue, 2005-09-13 at 09:25 -0700, Rob Tanner wrote: I upgraded from Mailman 2.0.6 to 2.1.5, and I'm having a problem with the aliases. My MTA is Postfix. Here's my problem. Our mail system uses the LDAP server for all the MTA required local aliases. However, on the specific server hosting Mailman, I modified the following line in the Postfix main.cf file to include the Mailman aliases file: alias_database = dbm:/etc/postfix/aliases,dbm:/opt/mailman_2.1.5/data/aliases Apart from hosting Mailman, that server is not part of our regular mail system. When a message is sent to listname@linfield.edu, Postfix, on which ever one of the mail gateway servers that first sees the message, looks up the alias, and then using the mailroutingaddress attribute, re-routes the mail to listname@calvin.linfield.edu, which is the actual name of the host. However, when the mail hits the Mailman server, Postfix reject it with the error: 550 listname@calvin.linfield.edu: User unknown in local recipient table The other pertinent setting in main.cf is: local_recipient_maps = $alias_maps, dbm:/opt/mailman_2.1.5/data/aliases I've played extensively with the various Postfix parameters, and I've not been able to resolve this problem. It probobly is a Postfix settings issue, and I'm hoping someone has had and resolved a similar issue. Here are some things to check: In your main.cf file you've specified a file_type of dbm but I don't see anything in your mail saying you've told Mailman's Postfix.py to use that file format. Have you? It defaults to whatever is the default database type in your postfix installation. You should verify the file types are in fact in harmony with one another. You could take a look at postfix error logging to see if its complaining or use the postmap command to simulate the lookup. Also, it looks like you're performing domain mapping when you re-route to the primary server. If the alias lookup's include domain information you may fail the local_recipient_maps lookup because although the user part of the address is correct it may include a domain part not recognized by the server fielding the request. I would use the postmap command to simulate an alias lookup and see what is returned and make sure domains are not part of the alias or if they are that they match. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman stopped working after upgrade
On Tue, 2005-09-13 at 11:33 -0700, Daevid Vincent wrote: -Original Message- From: John W. Baxter Has Exim lost its setuid bit (and/or its root ownership) in the upgrade? Thanks for the suggestion John, but the perms look correct. Also, other email works fine (incoming/outgoing). It's only mailman... daevid ~ # which exim /usr/sbin/exim daevid ~ # ll /usr/sbin/exim -rws--x--x 1 root root 830012 Jul 7 00:57 /usr/sbin/exim I doubt it can just be mailman. It's failing in the mail wrapper which calls getgid() to get the group its being executed as. Mailman is simply reporting the facts, which is it is not being executed as the group it was intended to be executed as. In your configuration it is exim that is executing mailman wrapper, thus it is exim that needs looking at. Also, please note the error concerns group id not the user id. The error reported says exim executed the mail wrapper as the group mail when it expected it to be group mailman. This means exim invoked the wrapper in the mail group. Sorry, I'm not an exim user so I can't tell you the particulars of exim, but I suspect there is an option when executing the mailman wrapper to elect the group in addition to the user (its the group thats important). Also, its not the setuid or setgid bit of exim that's relevant in this case, that says when that exim executable is run, ignore who is invoking me and run as this user or group instead. Which for exim when invoking mailman on your behalf is not relevant (and may not even be desirable), what is relevant is that when exim invokes the mailman wrapper it calls setgid(mailman) (I'm playing a little loose and fast here, but thats the idea in a nutshell). This probably only happens via an exim configuration parameter tied to mailman invocation. 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman stopped working after upgrade
On Tue, 2005-09-13 at 12:05 -0700, Daevid Vincent wrote: # User and group for Mailman, should match your --with-mail-gid # switch to Mailman's configure script. # Value is normally mailman MM_UID=mailman MM_GID=mailman # # Domains that your lists are in - colon separated list # you may wish to add these into local_domains as well domainlist mm_domains=daevid.com:rollinballzcrew.com:me-racing.com:marq.org # # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # # These values are derived from the ones above and should not need # editing unless you have munged your mailman installation # # The path of the Mailman mail wrapper script MM_WRAP=MM_HOME/mail/mailman Caveat: I don't know exim! But the above does suggest to me that when it invokes MM_WRAP=MM_HOME/mail/mailman will do it as uid=mailman, gid=mailman (because it calls setgid(mailman), is exim running with root privileges? it can't change the group if its not). BUT the mailman wrapper is telling you that is not what is happening, its being executed as group mail. ## #MAIN CONFIGURATION SETTINGS # ## exim_user = mail hmm... very suspicious, looks like this is what is being picked up as the execution context. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Moved mailman, not arhchiving
On Thu, 2005-08-25 at 09:43 -0400, David Clark wrote: Err, sorry I misspoke -- I'm no unix guru. A non-working list shows: drwxrwx---2 root mailman 4096 Aug 2 14:54 database Vs the working list that shows: drwxrws---2 mailman mailman 4096 Aug 24 15:46 database Running check_perms gives no errors.. I think you're problem is with the owner of the file, note the non working file is owned by root while the working version is owned by mailman. check_perms does not check ownership, only groups and modes so it would have missed this. Try this as root: % chown mailman database -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] migrating from sourceforge list archive to mailman
On Fri, 2005-08-19 at 23:57 +0200, Tomasz Chmielewski wrote: I wanted to migrate a list stored on sourceforge.net to mailman kept on my site. It's about 300 messages. It seems that there is no easy way of doing that, and I'll have to open each mail stored on sourceforge.net, copy it's contents, sender, and date, and send it to a new mailman installation (with the appropriate From:, date, and subject/body) - all 300 mails manually. Did anyone already migrate from a list stored on sourceforge.net, and if so, could somebody give me some hints on how to do it best? I assume your need is to archive the previous emails, you are not concerned with member migration. The archive used by mailman is stored in mbox format. If you can somehow grab your existing archive as a flat file (in mbox format or convert it) you could install the mbox file and run mailman/bin/arch to rebuild mailmans archive from the mbox 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] no posts appear on a new list
On Mon, 2005-08-22 at 23:22 +0200, Tomasz Chmielewski wrote: I'm just trying to set up mailman, but I can't make it work. When I send an email to a list, all I can see is this entry in info log of Postfix: Aug 22 23:18:58 mangoo2 postfix/local[12738]: 1BC3EF0021: to=[EMAIL PROTECTED], relay=local, delay=2, status=sent (delivered to command: /opt/mailman/mail/mailman post dupa) and that's it, no Postfix errors nor other entries, no mailman logs, no clue. What should I look for? The postfix log is saying that it gave the message to the mailman wrapper /opt/mailman/mail/mailman asking it to post to the list dupa. All this looks good assuming both the wrapper program /opt/mailman/mail/mailman and the list dupa both exist. I assume also you are not showing any errors in your postfix log file(s). There should have been an entry in one of the mailman logs. Where your mailman logs are located depends on your installation, I'd make a guess in your case its /opt/mailman/log. Are you sure there isn't any entry in any of the mailman logs? It would be suspicious for the mail wrapper to accept a message but not log it. I wonder if your mail wrapper is actually executing. You can try piping a dummy message into the wrapper with the same args as the user your postfix program runs as. Pay particular attention in any of the logs to group mismatch errors. BTW, did you check the system log? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] maximum size of mailman .mbox files
On Fri, 2005-08-19 at 16:17 +0900, Stephen J. Turnbull wrote: Brad At 2:59 PM -0500 2005-08-17, Stephen S Kelley wrote: I'm running mailman 2.1.5 on fedora2 and the box has ample resources. Are there any OS problems a 2GB? Brad Dunno. But you'd be more likely to get an answer to Brad your question if you used resources appropriate to your OS. If John Dennis doesn't show up shortly with an answer, I recommend you write to Red Hat support and ask about large file support in Python. Sorry, I was lurking because I don't have any definitive information at my finger tips. The answer has two components, the max file size of the file system and the max file size python can handle. I'm assuming the installation is on an ext3 partition. The max files size on ext3 depends on the block size, it ranges from 16GB to 4TB on a 32bit CPU. However python and other software has to be able to manage file pointer offsets, which without any direct knowledge I suspect are 32 bit representations on a 32 bit CPU. I suspect that probably limits practical file sizes using python to 4GB. But like I said, I don't know this as a fact, just guessing. Bottom line, I don't think you're likely to have a problem any time soon just based on file sizes. The time to process an archive of that size, the likelyhood of corrupted individual emails in an mbox of that size, and the utility of that much data are other issues. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] how to avoid mailmanSite list creation
On Fri, 2005-08-19 at 11:46 +0300, [EMAIL PROTECTED] wrote: Hello All, 1) I'm implementing web-cyradm installation together with mailman-2.1.4-83.13 on SLES 9. Try to upgrade to mailman 2.1.6 for security reasons. As I understood from the documentation, there must be mailman list for mailman to work properly. Web-cyradm implementing virtual domains with the use of MySQL tables, so my mailman list will look something like haifa.ac.il-mailman where haifa.ac.il is one of the domains I have. After creating this list, I restart mailman and get Starting mailmanSite list is missing: mailman error. Is there any way to avoid this limitation? You need a site list, this does not have to be created via your Web-cyradm tool set, it can be done at the time of mailman installation. 2) When I go to http://myservername.com/mailman/listinfo with the browser, I got this message: Bug in Mailman version 2.1.4 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: Content-type: text/html We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. This is typically a result of python syntax errors introduced by editing mm_cfg.py which is python code that gets executed. A typical reason is not quoting strings. If you can't find the syntax error try running one of the command line scripts in mailman/bin, the python interpreter will probably print the offending file and line number, this is hidden when using the web interface. In my /etc/apache2/default-server.conf I configured it like this: ## ## ## mailman ## ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Directory /usr/lib/mailman/cgi-bin/ AllowOverride None Options FollowSymLinks ExecCGI Order allow,deny Allow from all /Directory ## ## end mailman ## ## Are these config lines sufficient or my bug is from 1) question? Looks fine to me provided your path is correct. See above, you need the site list, you probably have a syntax error in mm_cfg.py. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] how to avoid mailmanSite list creation
On Fri, 2005-08-19 at 12:47 -0400, Julian C. Dunn wrote: On Fri, 2005-08-19 at 12:37 -0400, John Dennis wrote: On Fri, 2005-08-19 at 11:46 +0300, [EMAIL PROTECTED] wrote: Hello All, 1) I'm implementing web-cyradm installation together with mailman-2.1.4-83.13 on SLES 9. Try to upgrade to mailman 2.1.6 for security reasons. As far as I know, Novell has backported all security fixes in 2.1.6 into the SLES 9 2.1.4 Mailman. Please correct me if I'm wrong (and I hope I'm not, because that's the Mailman we're planning on installing) I don't track Novell's patches, but these are the two CVE's you want to make sure are fixed, look to see if the release notes include them. CAN-2005-0202 CAN-2004-1177 Of the two of them, CAN-2005-0202 is the most important. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] list with capital letters in the name and the newlist script
On Wed, 2005-08-10 at 11:19 -0600, Bert Beaudin wrote: Hello all I was hoping that some one could answer the this can I create a list with capital letters in the name of the list using the newlist script? No, it always converts the name to lower case. Not sure why, but that is the behavior. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] check_perms errors
On Tue, 2005-08-09 at 09:30 -0600, Tim DeBoer wrote: timlist. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mailnull, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group mailnull, or re-run configure, providing the command line option `--with-mail-gid=mailman'. ) I think I understand what it's telling me to do here, I just don't know where to change it. Should I make 'mailnull' group part of my mail group which also includes my postfix user? No, you don't want to be changing group membership. You should do what its telling you: This assumes you built and installed mailman yourself, if you didn't you can't perform this step. cd to the mailman source root ./configure --with-mail-gid=mailman make make install Don't forget to add any other configure options you used previously. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Premature End of Script Headers (permissions error?)
On Tue, 2005-08-09 at 14:52 -0400, Chris Mueller wrote: Hi, I'm farily new to Linux administration, but my employer has just asked me to set up some mailing lists. As Mailman seems like a popular and robust piece of software, I decided to give it a try. I have performed the installation of Mailman (on Redhat), but continue to receive 500 Internal Server Errors when I try to access anything in the Mailman cgi-bin, e.g. localhost/mailman/create. The Apache logs show two errors: (13) Permission denied: exec of '/usr/local/mailman/cgi-bin/create' failed. and Premature end of script headers: create. I think the path of least resistance is to install the pre-built mailman rpm from Red Hat rather than trying to perform every piece of obscure configuration yourself. The rpm package is designed to integrate with existing Red Hat packages and configuration. If you do start with the rpm it won't mean you'll be free from any configuration issues but you'll avoid a number of headaches. If you do go this route please be sure to follow the instructions 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman error when sending to test-subscribe
On Tue, 2005-08-09 at 14:24 -0500, Mike Hanby wrote: Ok, I reinstalled, here are the steps that I followed (btw I'm using Slackware 10). As root, I created the mailman user and mailman group. I have mailman temporarily set up to allow shell access (so I can install as mailman). You do not need to be mailman to install mailman, to install mailman you should be root. The mailman user and group will need to exist prior to installation so that the installed components can be assigned that identity. # cd /usr/local # tar -zxvf ./mailman-2.1.6.tgz # chgrp -R mailman ./mailman-2.1.6 # chmod -R a+rx,g+ws ./mailman-2.1.6 # ln -s ./mailman-2.1.6 ./mailman # su - mailman None of this is necessary (except for untaring) % cd /usr/local/mailman % ./configure --with-mail-gid=nogroup % make install ./mailman-install.log 21 ouch. you're building in the install area before you've installed, sounds like a recipe for disaster. :-) You've also installed as the user mailman, not root. Think of your build area as a staging area that is used to construct what will be placed into the the install area by the root user. By trying to point the install at your build you're going to step all over what you've built as it installs. It's equivalent to trying to copy a file onto itself :-( I still don't see the ./scripts/subscribe script. The subscribe script is just a copy of the join script (unsubscribe is a copy of leave). The part of install that copied the existing scripts worked, the part that installed copies of join and leave did not. I'm not sure why that part of the install failed but installing into the build area and not being root during the install are likely culprits. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman error when sending to test-subscribe
On Tue, 2005-08-09 at 16:11 -0400, John Dennis wrote: ouch. you're building in the install area before you've installed, This probably was not clear because I omitted an important but somewhat hidden fact, /usr/local/mailman is the default installation directory. Had you typed ./configure --help you would have seen this: Installation directories: --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local/mailman] You could override the prefix or have picked another build area, but the two should not be identical because they will collide. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Digest Sending Questions
On Thu, 2005-07-28 at 07:03 -0500, David Scribner wrote: I am currently running a test list on Mailman (2.1.5) on OSX Tiger (10.4.2) and seem to have some problems with the sending of Digests. I have the list set that it will bunch traffic in Digests. And I have the option Should a digest be dispatched daily when the size threshold isn't reached? set to YES. But it is not sending out a Daily Digest although there are posts in the queue. It only seems to be sending out a digest when the Threshold is reached. What can I do to make Mailman send out the Digest Daily even if there are only a couple of posts for that Digest? I have even tried to toggle the Daily Sending option to NO and then back to YES but that doesn't seem to work to force a Daily Digest. Also, I don't see anything where I can set the time that a Daily Digest is sent out. On my current LetterRipPro list server I have the Digests for the lists that have a digest option to send for each list at a different time, actually about a half an hour apart just to lessen the amount of out-going traffic when the Digests get sent. Is it possible to do that same with Mailman? The timed delivery of digests is implemented via a cron job that runs the mailman/cron/senddigests script. If your digests are not being sent the first thing to check is if the cron jobs are enabled. You can set the time this cron job runs so you can control when they are sent out. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Is this a mailman or postfix error?
On Thu, 2005-07-28 at 16:28 -0500, roy vinner wrote: Greetings! I have a problem that any address which is supposed to be resolved with the path-to-mailman/data/aliases produces a message undeliverable error. I've also discovered that if I run an alias expansion from the command line aliases: .. # STANZA START: try # CREATED: Mon Jul 25 17:19:03 2005 try: |/usr/local/mailman/mail/mailman post try try-admin: |/usr/local/mailman/mail/mailman admin try try-bounces: |/usr/local/mailman/mail/mailman bounces try try-confirm: |/usr/local/mailman/mail/mailman confirm try try-join:|/usr/local/mailman/mail/mailman join try try-leave: |/usr/local/mailman/mail/mailman leave try try-owner: |/usr/local/mailman/mail/mailman owner try try-request: |/usr/local/mailman/mail/mailman request try try-subscribe: |/usr/local/mailman/mail/mailman subscribe try try-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe try # STANZA END: try .. [EMAIL PROTECTED] mailman-2.1.6]$ /usr/local/mailman/mail/mailman request try Failure to find group name mailman. Try adding this group to your system, or re-run configure, providing an existing group name with the command line option --with-mail-gid. I have re-run mailman's configure as requested by the above message and group mailman does exist on my machine. I am clueless as to what is awry here with postfix aliases? Is this a postfix or mailman problem? Let me know if you need any more information for logs or config files. There are two immediate things to check: 1) I know you said it, but please verify the mailman uid and gid: # id mailman 2) Postfix has a feature which is it will run the commands found in an alias file under the identity of the alias file. What is the owner/group of the alias file: # ls -l path-to-mailman/data/aliases if its group does not match what the mailman wrapper is configured for you'll get group mismatch problems because postfix will attempt to run the mailman alias commands under the group belonging to the alias file, not to the mail_owner in postfix's main.cf file. I think I recall a config variable to turn the postfix behavior off, but you should not do that because mailman should be creating the alias file and hence it should match the uid/gid, but if you hand created it, then all bets are off. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] apache and mailman
On Wed, 2005-07-27 at 15:54 -0500, roy vinner wrote: Greetings! Which settings are there to tweak so that apache set with group=apache can still run mailman? creating a group web with no such user and mailman and apache in it did not do the job. You need to rebuild mailman using the configure option --with-cgi-gid=apache BTW, this is in 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Incoming messages are not received in Mailman + Postfix
On Mon, 2005-07-25 at 18:50 -0500, roy vinner wrote: Greetings! I am having a problem with receiving any mail by the web server. On the other hand, outgoing mail is deliver okay. I suspect that it may be due to a misconfigured postfix. I'm sorry, but this does not make sense, perhaps its vocabulary. One never receives mail via a web server. I think what you're trying to say is that if someone attempts to send mail to your SMTP server (postfix) it fails, correct? If so make sure your SMTP server is listening for outside connectons: inet_interfaces = $myhostname, localhost Make sure your local_recipient_maps is correctly configured, you can turn it off this way for now: local_recipient_maps = Make sure your firewall is passing port 25 (SMTP) Then from another machine try this (replace mymachine.mynetwork with your DNS address): % telnet mymachine.mynetwork.com 25 Does postfix answer? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Incoming messages are not received in Mailman+ Postfix
On Tue, 2005-07-26 at 10:17 -0500, roy vinner wrote: I tried 'ping'ing and received no answer for 128.252.27.164 . My system admin tested it and reported that nothing is listening on that port: -- [EMAIL PROTECTED] telnet nrg.wustl.edu 25 Trying 128.252.27.164... telnet: Unable to connect to remote host: Connection refused [EMAIL PROTECTED] BTW, this really isn't a mailman issue, its postfix, its best to move this discussion to a postfix list or better yet visit www.postfix.org and read their doc. But let me give you one last set of suggestions: Connection refused typically means the port you're trying to connect to (port 25) is blocked by a firewall. It can be blocked in a variety of places, either on the machine you're running the server on or by any other router in between. BTW, connection refused does not mean nothing is listening on the port. To see if something is listening on the port you must go the local machine the server is running and either try to connect locally # telnet localhost 25 -or- examine who is listening on the port using any of a variety of networking utilities, such as: # netstat -l -n | grep :25 or # netstat -l | grep smtp Using the first example: # netstat -l -n | grep :25 tcp0 0 127.0.0.1:250.0.0.0:* LISTEN tcp0 0 192.168.0.0:25 0.0.0.0:* LISTEN This says port 25 is being listened on the localhost (loopback) because your loopback is 127.0.0.1 and its listening on 192.168.0.0 which is 192.168.0.0 (ficticious net addr). If nothing is listening on the external interface, then is postfix running? If so did you restart it after modify inet_interfaces to include the external interface? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] No such list mailman after creating list - Possibly Solved?
On Tue, 2005-07-26 at 11:18 -0400, Josh Simoneau wrote: So, my last challenge is to figure out why Apache is looking to /var/mailman where I can't find anything in the config to tell it to look there. Maybe its somewhere else. For a workaround I just renamed the /var/mailman directory and created a symbolic link from /var/mailman to /usr/local/mailman. It works, but I still want to know how to get Apache to look to the right spot. Did you look in: /etc/httpd/conf.d? That directory has config files, typically one per web service with the name of the service. Is there a mailman.conf file in that directory? If not grep all the files there looking for one that contains 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman not sending - Solved(?)
On Fri, 2005-07-22 at 11:27 -0700, [EMAIL PROTECTED] wrote: Thanks for your corrections and tips. I made the changes, and it still didn't work. I read the thread you referenced, and verified that my permissions and users were correct. I then went back to look at my dns and machine settings, and found that my host name had reverted back to the machine name, not the full name I changed to it to previously that fixed the problem. So it wasn't that it was working for just one list and not others, it was that the fix that I previously made reverted before I tested other mailing lists. When I changed it back again, all the files in the retry queue flushed and I got a bunch of messages delivered on serveral lists. I'm running SuSE 9.2; maybe there's a process running somewhere that is doing this. I know there are processes that keep permissions and other settings in sync. If this reverts again, I think the logical solution would be to find where SuSE is deciding what hostname to use and change it, or to change mm-cfg to match the hostname that SuSE wants to use. I can't speak for SuSE nor do I know how you changed your hostname, but I can tell you this, if you used the plain hostname command that change will not persist across reboots. See the hostname man page on your system for how to make a permanent change. Also, if your machine is being assigned a permanent IP address via a local DHCP server you will likely have to make that change in the DHCP configuration. 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman / Postfix Question on Tiger Server
On Fri, 2005-07-22 at 16:56 -0700, Mark Sapiro wrote: David Scribner wrote: My questions is how do I set Postfix on the OSX box to only receive on the SMTP Submit Port of 587? And then if I do that how do I set Mailman to send to that port rather than the default SMTP port? I don't offhand know the Postfix incantations to tell it on which port(s) to listen, but on the Mailman sending side the relevant mm_cfg.py variables are SMTPHOST and SMTPPORT - read the descriptions in Defaults.py. Perhaps this will be of help: http://www.macosxhints.com/article.php?story=2004122809382235 -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] -1 list moderator request(s) waiting
On Tue, 2005-07-19 at 12:09 -0400, Joshua ChaitinPollak wrote: Hello, I have an odd problem and I can't find it documented anywhere. I have a list administrator on my system who keeps getting messages (below) telling him that he has -1 messages waiting to be moderated. Logging in to the pending tasks page shows nothing to do. We have 6 lists on our server, this only happens on 2 of them. All of the lists are new as of a few days ago, and they all seem to work fine. Mailman FAQ Entry 3.38. Why am I receiving moderation requests that read ...mailing list has -1 request(s) waiting... ? http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.038.htp Note: the 2.1.6 version has this fixed. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Private archive file not found
On Fri, 2005-07-15 at 15:24 +0200, Ákos Maróy wrote: I have the following problem with a new installation of mailman on CentOS Linux 4.1. CentOS :-( I created my first list, and set the archives to be private. but when I try to access the archives, I get: Private archive file not found in the browser. moreover, in the mailman error log, I get the following: Jul 15 10:22:25 2005 (14959) Private archive file not found: /var/lib/mailman/archives/private/proba/ but it's all very strange, as the archives are actually there: $ ls -l /var/lib/mailman/archives/private/proba/ total 48 drwxrwsr-x 2 mailman mailman 4096 Jul 14 13:08 2005-July -rw-rw-r-- 1 mailman mailman 229 Jul 14 13:08 2005-July.txt -rw-rw-r-- 1 mailman mailman 232 Jul 15 03:27 2005-July.txt.gz drwxrws--- 2 mailman mailman 4096 Jul 14 13:08 database -rw-rw-r-- 1 rootmailman 1025 Jul 14 13:08 index.html -rw-rw 1 mailman mailman 845 Jul 14 13:08 pipermail.pck and also, if I set the archives to be public, they are accessible through the link to myserver.com/pipermail/... what could be the issue here? It might be an SELinux policy violation. Take a look in your /var/log/messages (or /var/log/audit/audit.log) file after you get the failure and see if there is avc message denying access (grep for avc:). I seem to recall a bug in an early version of selinux-policy-targeted related to private archives which was fixed a while ago by us. If you do see such a message the solution is to upgrade the selinux-policy-targeted rpm (or as a test you could put SELinux into permissive mode, but you really don't want to run an open server in permissive mode). -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing the path of cgi-bin
On Wed, 2005-07-13 at 14:42 -0400, Forrest Aldrich wrote: Right, exactly. But what' the best way to do this with Mailman. Pick a new location of your chosing, move the cgi-bin directory to it, then edit your httpd ScriptAlias entry for 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] CGI account shouldn't be part of mailman group, but...
On Tue, 2005-07-12 at 17:34 -0400, Poster wrote: Ok, according to the docs, if the account that runs CGI scripts is a member of the mailman group, then private archives can be seen by everyone. This is a bad thing. However, in order for apache to update files in the mailman paths (like locks and such), these files have to be writable by the CGI user. So either the CGI user is a member of the mailman group, or the directory is left readable, writable, and executable by members not of the group! Hopefully, I'm missing something. Any ideas? I think you might be missing something. The account that runs CGI scripts is *NOT* a member of the mailman group, rather the cgi wrapper transitions to the mailman group via setgid, thus its only mailman operations that are executing as group mailman. In addition private mailman archives are authenticated by mailman. I don't think the problem you're concerned about exists, unless perhaps I've misunderstood you. You might find this FAQ helpful: 6.16. Understanding group mismatch errors - how mailman implements security http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=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=showamp;file=faq01.027.htp
Re: [Mailman-Users] CGI account shouldn't be part of mailman group, but...
Just to expand a bit on something I should have elaborated: There is exactly one member of the mailman group, the user mailman. When the MTA or web server want to perform a mailman operation it invokes what is called a wrapper. The wrappers are group mailman and are setgid, this means the wrapper executes as the group mailman even if the MTA or web server invoked it. The wrapper performs a security check on the process that invoked it to assure only permitted users have permission to invoke the wrapper, only the MTA is allowed to invoke the mail wrapper, only the web server is allowed to invoke the CGI wrapper. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] CGI account shouldn't be part ofmailman group, but...
On Tue, 2005-07-12 at 19:20 -0400, Poster wrote: OK. If I'm following this correctly, Mailman is run as setgid Mailman, so whatever calls it acts as though it were in the Mailman group. To prevent abuse of this, Mailman allows only those who pass its security check to call it. I'm running SUSE, which uses a mailman-cgi-gid file, instead of compiling this option into Mailman itself. If I've got this right, Mailman compares this file with the GID of the process calling it. If they match, then the process goes ahead. My mailman-cgi-gid file contains one number -- 8, which is the user nobody. In order to prevent Mailman from crashing with horrendous permissions problems on locks and such, I had to change many files to be owned by nobody. I can't speak for SuSE, but I think your mailman-cgi-gid file should have been modified to have the uid that apache (or whatever httpd server you're running) runs as. You shouldn't need to modify the owner/group/permissions of any of the mailman files (or any other files). But like I said I'm not a SuSE expert they may have done something different, but my expectation is they replaced the configure option --with-cgi-gid with a file read of malman-cgi-gid so its not hardcoded into the wrapper. I suppose that nobody doesn't have to be part of the mailman group, and that's where I went off the path? Yes, I believe that would be a mistake and you may need to go back and undo those file changes :-( mailman_install_dir/bin/fix_perms might be helpful, the -f option will fix the files. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] E-Mail to some users get lost or are very late
On Mon, 2005-07-11 at 16:38 +0200, Götz Reinicke wrote: Hi, we run mailman mailman-2.1.5-33.rhel4 on a RHEL 4 Clone (Tao Linux 4, kernel 2.6.9-11.ELsmp). Some days ago, some users noticed, that they dont get all mails send to the mailinglists they are subscribed to or that they get the mails with a delay from some days or weeks :-( I checked the quota, forward, alias and mailman settings for thouth users, but everything seams O.K. for me. We use sendmail as MTA and dovecot as imap server. Any ideas what to check? Or waht info to provide? You're going to have to identify one of the delayed emails and look at it's headers to see where it was held up. You might also look at /var/log/maillog and the /var/log/mailman/smtp logs to see if and when the suspect messages were processed. Missing mail may have also bounced. Once your MTA hands off a set of mail to a destination SMTP server a whole host of things can happen to it that has nothing to do with your server. Your best bet is to verify from the logs the mail left your server when you expected it to. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Bug in Mailman 2.1.6b4
On Fri, 2005-07-08 at 11:54 +0900, Jim Tittsler wrote: On Jul 8, 2005, at 04:59, Darren G Pifer wrote: [...] from a version of Mailman we upgraded to recently. I tried to look in the logs but could not find anything. We will be upgrading Did you look in your Apache error logs? There may be a Python traceback there that would narrow down the problem. I'm pretty sure that 2.1.6b (as well as 2.1.6) have enabled stealth mode. This prevents stack traces from being visible on the web page for security reasons (you used to be able to see the stack traces). To analyze what caused a bug you'll need the stack trace. Although the stack trace is no longer visible it is logged on the system hosting mailman, I believe in the mailman error.log file, its location will be installation dependent (/var/log/mailman, /usr/local/mailman/log are common locations). -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Bug in Mailman 2.1.6b4
On Fri, 2005-07-08 at 12:08 -0400, Darren G Pifer wrote: Thanks for the information. You are correct, I have not seen anything in the Apache logs, however, I have not seen anything logged to mailman's logs either. Is there a way to disable stealth mode? I know this could cause security implications but may need to do this temporarily to find and fix the problem. We will be upgrading to Mailman 2.1.6 in the next week but am not feeling that this will fix the problem. You may want to read the doc here: http://www.list.org/faq.html and search for STEALTH. I spoke in error, the local logging is not to your mailman error log but rather to syslog. Please note syslog is handled differently on different systems, you may have to tweak your syslog configuration to log the mailman errors. The only way I know of to disable STEALTH_MODE is to change its hardcoded setting in the driver script, you will have to locate this file and edit it. However, if you can, it really would be better to get your syslog working, you do want these errors logged and it really is better to keep sensitive information out of the public eye. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problems with Mailman on Fedora Core 3 system
On Fri, 2005-07-01 at 12:37 -0400, Matt Singerman wrote: Hi Mark, Thanks for posting this - I didn't even know this filed existed! I think I've located the problem - mailmanctl isn't running. However, when I try to start it (with /usr/lib/mailman/bin/mailmanctl start), nothing happens. I tried to su as user mailman to check the crontab and try and run it from there, but when I do, I get the following error: [EMAIL PROTECTED] ~]# su - mailman This account is currently not available. The user definitely exists, but it has no login. Any ideas here? Sorry I didn't respond sooner, I've been on vacation and just returned with the typical 3,000+ emails in my inbox after a week of absence :-( The doc in /usr/share/doc/mailman-* is your friend, in particular the file INSTALL.REDHAT. In there is information on starting the mailman service. FWIW, the install of the mailman RPM does not do the following for good reasons. * It does not start the service * It does not add mailman to the list of services * It does not create a mailman login account. Why? Because it is common practice for people to just install a bunch of RPM's because they want them available. The installation of an RPM is independent of wanting to run the service (if the rpm is a system service which mailman is). Red Hat policy is if you want to run a service you must make a conscious decision to run the service, this has a lot to do with security issues (the INSTALL.REDHAT doc will tell you how to run the service). When the rpm installs it creates a mailman user and group, this is necessary for mailman to run. It is not necessary for a mailman login account to exist to run mailman (it is sometimes a convenience). Along the same lines as why we don't start a service when a package is installed we don't create login accounts. This too is a security issue. What password would be given to the account? It would have to be the same for every installed mailman RPM on Red Hat systems, and this is a security hole wide enough to drive a truck through :-) If you want a mailman login account it's very easy using system-config-users to edit the mailman user and give mailman a login account. Finally, you do not want to be running mailmanctl directly. You do want to use the interface established for controlling system services (e.g. init scripts in /etc/init.d). The init script does important things you won't want to bypass. This also makes the mailman service on Red Hat consistent with every other system service, once again this is covered in the doc. Also, please note that as of mailman 2.1 cron is not necessary to run basic mailman, as of 2.1 mailman is a service (e.g. daemon). Also, the init.d script plays an integral role in managing cron usage for the parts of mailman that still depend on cron. HTH, if you still have problems feel free contact me. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] aliases assistant
On Wed, 2005-06-15 at 15:06 +1000, Diana Huang wrote: Hi Mark, Thx for your email. Actually I tried that method, but I got some errors /usr/bin/sudo: /usr/local/sbin/mailman.aliases: command not found Traceback (most recent call last): File /usr/local/mailman/bin/genaliases, line 116, in ? main() File /usr/local/mailman/bin/genaliases, line 106, in main MTA.create(mlist, nolock=True, quiet=quiet) File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in create _update_maps() File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/bin/sudo /usr/local/sbin/mailman.aliases /usr/local/mailman/data/aliases (status: 1, Operation not permitted) Any comments? I suspect /usr/local/sbin/mailman.aliases is either not executable or not executable by the user/group the command is running under (what user/group that is depends on how you did your installation) What does ls -l /usr/local/sbin/mailman.aliases say? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Red Hat FHS packaging
On Wed, 2005-06-15 at 08:05 +0100, Andy Heath wrote: A plea to Redhat - if you are going to purloin mailman and do it with FHS then a file that accompanies the mailman distribution that explains how to do a manual build that conforms to the way RH does it would be very useful - a how to manually build for FC (which ends up with files in the same places as FC has them). There is indeed a file that recreates the build, it's the src rpm and it's readily available. The src rpm contains the virgin tarball, all the current patches, and the mailman.spec spec file that controls the build. Users familiar with distributions utilizing rpm as the packaging tool (of which Red Hat / Fedora is only just one example) routinely download src rpms, tweak them for their own use and rebuild. This is standard practice. Since you need to be following the development and dealing with that issue anyway I can't see that it is any extra work to write up the method and keep that up to date and contributed to the mm distribution. It's not appropriate for the mailman project to maintain rpms, this is the domain of distributions which repackage upstream. This has been the working model of open source development almost since its inception. As its not extra cost the only reason I can see that RH would NOT do that is to lock persons in to RH. Everything you have asked for is available, free, and transparent. I suspect your conclusions are driven by a lack of familiarity with how to find what you are looking for rather than anything devious. To suggest disingenuous lock in by Red Hat is utter nonsense. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] aliases assistant
On Wed, 2005-06-15 at 08:13 -0700, Mark Sapiro wrote: RuntimeError: command failed: /usr/bin/sudo /usr/local/sbin/mailman.aliases /usr/local/mailman/data/aliases (status: 1, Operation not permitted) seems to say that the commands in /usr/local/sbin/mailman.aliases, the first of which is presumably /bin/cp /usr/local/mailman/data/aliases /etc/mailman.aliases are being executed and it is this first command which fails, but since this is executed via sudo as root, why would it be 'not permitted'? I agree with Mark, it could permission problems either with the script or with the commands the script executes. I sometimes get fooled by the misconception root can do anything too, but in fact it can't, permissions are still checked. The most common example of this is a file whose permissions are granted only to a non-root owner. Root is denied in this case. However root can su to that owner and then perform the operation. Also, the complete absence of execute permission is not something root can compensate for. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with a new install...
On Wed, 2005-06-15 at 14:33 -0400, Michael D. Smith wrote: I'm installing Mailman 2.1.6 on a RHEL 4.0 server... I was having trouble with the smrsh, but worked that out... Now however, when I post to a test list I get the following... - Transcript of session follows - Traceback (most recent call last): File /home/mailman/scripts/post, line 69, in ? main() File /home/mailman/scripts/post, line 64, in main tolist=1, _plaintext=1) File /home/mailman/Mailman/Queue/Switchboard.py, line 126, in enqueue fp = open(tmpfile, 'w') IOError: [Errno 13] Permission denied: '/home/mailman/qfiles/in/1118859566.129771+f526306b132c44862f163e9fbf3e65bea7258162.pck.tmp' 554 5.3.0 unknown mailer error 1 Any ideas? The qfile cannot be opened for writing. This is either a permission problem or SELinux is denying access. You need to: 1) Verify the user/group the MTA is executing the post command under, then look at the permissions on the directory and file. 2) Examine /var/log/messages and/or /var/log/audit for avc messages, these log SELinux denials. 3) Try turning SELinux off (/usr/sbin/setenforce Permissive) 4) Contact me off list for a trial 2.1.6 rpm (I've created the rpm but have not tested it yet, you could be the guinna pig :-) BTW, the RHEL 4 mailman rpm already has the security patches that prompted the 2.1.6 release, but 2.1.6 has some other new stuff as well. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] 2.1.5 fedora core 3 prevent mailbody problem
On Tue, 2005-06-14 at 09:50 +0100, Andy Heath wrote: If someone could do an ls -R or ls -lR (if there are links) of a 2.1.5 mailman directory and post it it would help figure out where fedora puts all the pieces (I'll build a list of links from it so it looks like a normal mailman directory and I can work with it more easily). There are two much easier ways to get this information: 1) read the documentation (/usr/share/doc/mailman-*/INSTALL.REDHAT) 2) rpm -ql mailman (-ql prints a package file list) OFF-TOPIC below: Standards compliance (fedora) is one thing (I work in standards) but when everyone already has a fine standard (put it in the mailman user directory) and the community has no plans to change that then i find it very silly to just throw that away The directory change was dictated by the need to integrate with the SELinux security policy. This is a positive technology advancement. Adhering to the FHS (Filesystem Hierarchy Standard) is a stated goal and appreciated by many. Most people prefer distributions that integrate packages into a coherent system that follow established rules. Individual package defaults are not a standard. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Red Hat FHS packaging
On Tue, 2005-06-14 at 21:38 +0100, Andy Heath wrote: Is there guidance in the standard mailman distributions on how to build for FC starting with a tar.gz ? To the best of my knowledge the install document provided in the tar ball applies equally well to Fedora thus it is not necessary to have special Fedora instructions. -- 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=showamp;file=faq01.027.htp
[Mailman-Users] chroot jails (Was: First-time poster...)
On Tue, 2005-06-07 at 02:42 -0700, Bill Landry wrote: Doh, ended up being a chroot issue in master.cf. Thanks John, Mark, and Dan for the responses, and my apologies to the list for the noise... Glad you got it fixed. I'd like to take this opportunity to make a few comments about chroot jails, this is not directed at you or your choice to use them but rather as a general comment of interest to the wider community. For what its worth I see this as a prime example of why I no longer recommend people run postfix (and other services) in a chroot jail. We stopped shipping postfix chrooted several years ago after observing the inordinate amount of problems it created for a marginal security win. Postfix is now often configured to interact with a host of other software components (SASL, TLS, SQL databases, LDAP directories, mailing list managers, spam filters, challenage/response authentcation methods, etc.) and as such its tenticles reach deep and wide. Trying to keep all these diverese elements in sync in a jail is a headache and a source of numerous problems often ascribed as bugs but which aren't. Even Wietse Venema the author of postfix no longer recommends the use of chroot jails although this was a design center of the original postfix security model. Chroot jails can be broken out of. Even without chroot jails postfix maintains a fairly robust security profile because of its design. Finally, with the advent of SELinux (yes, postfix, mailman, and apache are under the control of SELinux on Red Hat systems) the value of a jail is greatly diminished in favor of the vastly more robust security model inherent in SELinux. In fact it might be a reasonable statement that SELinux is itself a system wide jail enforced at the kernel level for every process and every object (e.g. files, sockets, devices, etc.). It is a Mandatory Access Control (MAC) sytem which means it cannot be defeated and offers great granularity (and unforuntely its own set of new headaces as the wrinkles in the security policy are ironed out ;-) -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
On Mon, 2005-06-06 at 11:46 -0700, Mark Sapiro wrote: Bill Landry wrote: Jun 6 10:52:07 lists postfix/local[20108]: warning: cannot find alias database owner for hash:/usr/local/mailman/data/aliases(0,34100) In any case, this appears to be a postfix configuration issue. A google search for cannot find alias database owner turns up two links to a postfix module alias.c, the relevant piece of which is: I don't think this is a postfix configuration issue, but rather a problem with user lookup's. What the code in question is doing is getting the user id (uid) of the owner of of the alias file and then mapping it to an account. For some reason that's failing. On the machine that postfix is running on you should verify the mailman account exists. (what does the command id mailman return?). Are you running postfix and mailman on the same machine. Do you have any of the files on an NFS mount? It seems very odd that ls -l prints out mailman as the owner but postfix can't perform the same lookup. Are you running a NSCD (Name Service Cache Daemon)? If so, maybe the cache isn't refreshed. Have you tried restarting postfix? Is mailman in /etc/shadow on the machine postfix is running 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
On Mon, 2005-06-06 at 12:48 -0700, Mark Sapiro wrote: And did that say anything about a group mismatch error? Or is there anything in Mailman's 'error' log? If you're getting group mismatch errors, see FAQ article 6.16 FWIW, I don't think this problem will manifest itself as a mailman group mismatch error, but I could be wrong. Thinking about this a bit more I suspect Bill may have modified the user/group on the alias file and/or modified the mailman account information while postfix was running, but did not restart postfix. I haven't looked at the postfix code but I wouldn't be surprised if postfix when it starts gets file information on all its input files referenced in main.cf and stores that information. If that information was altered while postfix was running it would likely get confused because it may be using id's that no longer exist. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
On Mon, 2005-06-06 at 13:00 -0700, Bill Landry wrote: O.K. the other things I suggested you check all seem fine. Is mailman in /etc/shadow on the machine postfix is running on? grep mailman /etc/shadow mailman:!!:12327:: Actually /etc/passwd maybe more relevant in this instance. If postfix does not have permission to read /etc/passwd it's look up is going to fail (a non-readable /etc/group may also provoke this). Recall that postfix typically does not run as root for very good reasons. What postfix runs as is configurable. You want to make sure whatever user postfix is running as has permission to read these /etc files. Also typically /etc/passwd and /etc/group are readable by everybody. The only other thing I can think of for you to check is to assure /etc/passwd and /etc/group are readable by the postfix process. Short of that the only other things I can think of would be to strace (assuming you're on a system with strace, e.g. Linux) the postfix process and seeing where the failure occurs and/or to look at the postfix code that performs the lookup and see exactly what c lib functions it's calling and what triggers it to return a failure. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Monitor qrunner
Mark Sapiro wrote: If it is running, you will find its pid in data/master-qrunner.pid and there will also be two files in locks/, one named master-qrunner and containing the line master-qrunner.host.example.com.pid And the second named master-qrunner.host.example.com.pid and having the same contents where host.example.com is the actual host name and pid is the actual pid of the master qrunner process. Thus there are three files that if present will give you the pid of the master qrunner. Of course, if it died a horrible death, the files might be left behind, so you also have to check if the pid is running and is a mailmanctl process. If the files are missing or the pid doesn't exist or is not a python process invoked with a mailmanctl command, then the master qrunner isn't running. Mark's point about the presence of the file not being a definitive metric of mailman health should not be ignored. You really have to ascertain the status of the process. If mailman is abnormally aborting, which is what started this thread, then there is a high degree of probably the lock files will be left behind and testing them will give false positives. In the Red Hat mailman RPM's we've modified mailmanctl so that it can be asked the status of the mailman process as an unprivledged user and return the result as status to the shell as well as printing a message. Since mailmanctl knows how to locate the process and communicate with the process via signals it makes mailmanctl the optimal reporter of status. It was probably an oversight mailmanctl never had this facility. We have also integrated this with the mailman init.d script so that one can perform the standard service mailman status command. The init.d script depends on the exit status of mailmanctl status. These two changes probably represent a more robust and standard way to determine status. I'm attaching our patch for this in case someone finds it useful. On Wed, 2005-05-25 at 08:13 -0700, Robert Haack wrote: What would happen if during the check you told mailman to stop first? Could this mess things up or would it be fine? Yes you could do that, it is essentially the same thing as service mailman restart if you're running on an OS that supports sysV style service management. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] can't make a new list from the GUI
On Wed, 2005-05-25 at 10:13 -0700, Bo Gusman wrote: I am certain that SELinux is disabled, but how can I verify that? /usr/sbin/getenforce -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] can't make a new list from the GUI
On Wed, 2005-05-25 at 10:36 -0700, Bo Gusman wrote: John Dennis wrote: On Wed, 2005-05-25 at 10:13 -0700, Bo Gusman wrote: I am certain that SELinux is disabled, but how can I verify that? /usr/sbin/getenforce Says disabled - whew. So the question remains, why no new list? I suppose I can live with creating lists from the command line as there will not likely be very many lists, but it'd sure be nice if I knew why the web interface failed. Everything else seems to work just fine. That is as much as I can help you with at the moment in the absence of any error messages in any of the logs. Given the problem you were seeing sounded a lot like a known issue with one version of the FC3 security policy it sounded at first like I might know what was going on, but since SELinux is off it can't be that issue. Sorry I can't be of more help. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Monitor qrunner
On Wed, 2005-05-25 at 19:39 +0200, Brad Knowles wrote: At 11:44 AM -0400 2005-05-25, John Dennis wrote: I'm attaching our patch for this in case someone finds it useful. The attachment was stripped. Could you post it as a patch at the SourceForge page instead? Yeah, I should have known it would have been stripped. Patch id is 1208685. -- 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=showamp;file=faq01.027.htp
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=showamp;file=faq01.027.htp
Re: [Mailman-Users] /bin/sh: mailman: command not found
Kris Vassallo wrote: I am getting emails with the following error in the body of emails being sent to the list owner: /bin/sh: mailman: command not found The subject reads as follows: [Mailman] Cron [EMAIL PROTECTED] mailman /usr/lib/mailman/cron/gate_news Somehow you've got crontab entries enabled with a non-crontab file. Reading the section on cron in /usr/share/doc/mailman-*/INSTALL.REDHAT may help you understand better. But the short answer is the cron file supplied in the rpm you installed has an extra field in it at position 6, the mailman user. It is to be installed in /etc/cron.d. However please note this is automatically done for you by the init.d script when you start and stop mailman, please use the the init script to start and stop mailman (e.g. /sbin/service mailman start|stop). If you installed this cron file with crontab its is going to be very confused by the extra 6th field. Please make sure you do not have any mailman crontab entries and remember crontab != cron. The rpm you installed is supposed to remove any pre-existing mailman crontab entries in favor of the newer methodology. If one got left behind after the rpm install then the %post section of the rpm is failing somehow. -- 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=showamp;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=showamp;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=showamp;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=showamp;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=showfile=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=showamp;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=showamp;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=showamp;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=showfile=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=showamp;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=showamp;file=faq01.027.htp
