[Mailman-Users] New Mailman Server Setup
I have just compiled and installed a copyof mailman-2.1.3 with python-2.2.3 running on a Solaris 8 machine with and apache server every thing appears to be ok except that when i connect to the webser/mailman/ i get a 403 forbidden error with the message You don't have permission to access /mailman/ on this server. this also appears to happen for the public archives as well, although i have not created any lists as yet to have any archives i would like to get this resolved before creating any lists and getting to far into the configuration of the server please not that webserver/mailman/listinfo is working ok my apache configuration is as follows: ServerRoot /usr/local/apache PidFile /usr/local/apache/logs/httpd.pid ScoreBoardFile /usr/local/apache/logs/httpd.scoreboard TypesConfig /usr/local/apache/conf/mime.types IfModule mod_mime_magic.c MIMEMagicFile /usr/local/apache/conf/magic /IfModule ServerName mailman.globalgraphics.com Port 80 Listen 172.16.19.105:80 User www Group www ServerAdmin [EMAIL PROTECTED] Directory / AllowOverride None Options Indexes FollowSymlinks Allow from all /Directory Directory /usr/local/mailman/archives/public Options FollowSymlinks /Directory DirectoryIndex index.html index.htm AccessFileName .htaccess ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ Alias /pipermail/ /usr/local/mailman/archives/public/ any help with this will apreciated, i have run check_perms and the permissions are ok so i do not know what the problem is. i played with an earlier version of mailman previously and did not have these problems Thanks James Osbourn -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] restarting a blocked list
i'm actually working with 2.1.3 (always the latest version is good ;-) ) No problems found with checkperms. Now, i'm going to write my little experiment with mailman, i don't know if somebody did it before, look the /usr/local/mailman in machine1 bash-2.03$ cd /usr/local/mailman/ bash-2.03$ ls -la total 54 drwxrwsr-x 18 mailman mailman 512 Oct 22 10:42 . drwxr-xr-x 11 root other512 Sep 19 12:00 .. lrwxrwxrwx 1 root mailman 26 Jul 3 12:50 archives - /dirarcon/mailman/archives drwxrwsr-x 2 root mailman 1024 Oct 7 12:23 bin drwxrwsr-x 2 root mailman 512 Oct 7 12:23 cgi-bin -rw-r- 1 root mailman 4133 Oct 22 10:42 config.pck drwxrwsr-x 2 root mailman 512 Oct 7 12:25 cron drwxrwsr-x 2 root mailman 2048 Oct 21 12:09 data drwxrwsr-x 2 root mailman 512 Oct 7 12:23 icons lrwxrwxrwx 1 root mailman 23 Jul 3 12:50 lists - /dirarcon/mailman/lists drwxrwsr-x 2 root mailman 512 Oct 23 13:25 locks drwxrwsr-x 2 root mailman 512 Oct 1 08:26 logs drwxrwsr-x 2 root mailman 512 Oct 7 12:23 mail drwxrwsr-x 11 root mailman 1536 Oct 7 12:23 Mailman drwxrwsr-x 24 root mailman 512 Oct 7 11:27 messages drwxrwsr-x 6 root mailman 512 Jul 1 12:41 pythonlib drwxrwsr-x 11 root mailman 512 Oct 7 11:34 qfiles drwxrwsr-x 2 root mailman 512 Oct 7 12:42 scripts drwxrwsr-x 2 root mailman 512 Jul 1 12:40 spam drwxrwsr-x 26 root mailman 512 Oct 7 11:27 templates drwxrwsr-x 4 root mailman 512 Oct 7 12:23 tests As you can see mailman is working in machine1 and writting the lists information into a networkapplyant (dirarcon) Now, machine2 has another mailman writting into dirarcon too, with same lists, and in DNS i put machine1 and machine2 with one name, mailmans.domain.es... so roundrobin of DNS sometimes send messages to lists by machine1 and sometimes by machine2... no problem... all work fine but the most traffic lists ([EMAIL PROTECTED]) sometimes stops (once per a couple of weeks)... theory of unix says that two diferents tasks can open and write a file at same time, so i thought that was posible... Now machine2 is stoped, and DNS only has a mailmans.domain.es - machine1, at momment [EMAIL PROTECTED] is working good, so i'm beginning to think that theory of unix is my problem, and if only one machine is working with mailman, comunicaciones @cedex.es won't stop... anyway, i'll study qfiles, thank you very much jonc, and hope you to enjoy my experiment :-) Jon Carnes wrote: On Tue, 2003-10-21 at 05:40, javier wrote: hello... one of the ten lists i have working stoped sending messages,. Ok, at moment i have to rmlist blocked list, saving the config file, and i have to create the same new list again, with same config file, and without removing archives... but... i don't know if i could solve this problem better... i can't find why the list stops sending messages, may the cron process of sending digest is the reason, i've send a HELP message yesterday with the output cron command. thank you very much Javier, Look in the FAQ for Mailman (3.14) might be helpful. If you are not running the latest version of your Mailman branch, then you should consider upgrading: For 2.0. that would be 2.0.13 For 2.1 that would be 2.1.3 In general, check for a locking file problem first, then check the qfiles to see what is stuck in the queue. It may be that one of your users on that list has a do-it-yourself email program that is sending out corrupt headers. You should NEVER need to delete the existing list. If this solves the problem for you, then try running check_perms -f and see if that finds any problems. This will check the rights on most of the key files needed for Mailman to run properly. Good Luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/b.englefield%40uel.ac.uk -- Javier Romero Casado tel.913357274 Dep. Comunicaciones CEDEX -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New Mailman Server Setup
It looks like you are going to the wrong url. try www.myserver.com/mailman/admin [EMAIL PROTECTED] 10/23/03 07:25AM I have just compiled and installed a copyof mailman-2.1.3 with python-2.2.3 running on a Solaris 8 machine with and apache server every thing appears to be ok except that when i connect to the webser/mailman/ i get a 403 forbidden error with the message You don't have permission to access /mailman/ on this server. this also appears to happen for the public archives as well, although i have not created any lists as yet to have any archives i would like to get this resolved before creating any lists and getting to far into the configuration of the server please not that webserver/mailman/listinfo is working ok my apache configuration is as follows: ServerRoot /usr/local/apache PidFile /usr/local/apache/logs/httpd.pid ScoreBoardFile /usr/local/apache/logs/httpd.scoreboard TypesConfig /usr/local/apache/conf/mime.types IfModule mod_mime_magic.c MIMEMagicFile /usr/local/apache/conf/magic /IfModule ServerName mailman.globalgraphics.com Port 80 Listen 172.16.19.105:80 User www Group www ServerAdmin [EMAIL PROTECTED] Directory / AllowOverride None Options Indexes FollowSymlinks Allow from all /Directory Directory /usr/local/mailman/archives/public Options FollowSymlinks /Directory DirectoryIndex index.html index.htm AccessFileName .htaccess ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ Alias /pipermail/ /usr/local/mailman/archives/public/ any help with this will apreciated, i have run check_perms and the permissions are ok so i do not know what the problem is. i played with an earlier version of mailman previously and did not have these problems Thanks James Osbourn -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/griswld%40cio.sc.gov -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] umbrella lists
We've had probs with nested lists in the past. I think the issue had to do with private lists (ie only members can post) for both the sublist(s) and the umbrella list. If set, how could a member of a sublist post to the umbrella list unless either the umbrella list was unrestricted or the user was also on the umbrella list? As I understand it, an umbrella list should *ONLY* be a list of lists and have no users. But that still wont allow a sublist member from posting to the umbrella, right? So one option we've entertained is to wipe and rebuild superlists each night (ie dump sublist member addresses, wipe and reload them into superlist instead of having nested list). This also makes employee-exit procedures harder (how to find all lists a person is a member. I wrote a script that lists_lists and recursivesly list_members and greps, kinda slow for many lists. OTOH, superlists guarantee someone isn't on two sublists and thus gets two iterations of lists. What have others done on this issue? Another concern is; what happens if someone sends to a superlist during a list rebuild? Is sync_members robust enough to at least always keep one list of addresses around? TIA =-=-=-=-=-=-=-=-=-=-=-=- generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=-=-= David SternUniversity of Maryland Institute for Advanced Computer Studies -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] umbrella lists
On Thu, 2003-10-23 at 10:14, Dave Stern - Former Rocket Scientist wrote: We've had probs with nested lists in the past. I think the issue had to do with private lists (ie only members can post) for both the sublist(s) and the umbrella list. If set, how could a member of a sublist post to the umbrella list unless either the umbrella list was unrestricted or the user was also on the umbrella list? A user does not have to be a member of a list to post. Posting privileges can be added either individually or via a regular expression. I generally go the route of hourly sync's to do master lists formed from sub-lists, so that isn't a problem I deal with regularly. As I understand it, an umbrella list should *ONLY* be a list of lists and have no users. But that still wont allow a sublist member from posting to the umbrella, right? So one option we've entertained is to wipe and rebuild superlists each night (ie dump sublist member addresses, wipe and reload them into superlist instead of having nested list). This also makes employee-exit procedures harder (how to find all lists a person is a member. Nope. Look at the remove_members command in Mailman. --fromall Removes the given addresses from all the lists on this system regardless of virtual domains if you have any. This option cannot be used with -a/--all. Also, you should not specify a listname when using this option. I wrote a script that lists_lists and recursivesly list_members and greps, kinda slow for many lists. OTOH, superlists guarantee someone isn't on two sublists and thus gets two iterations of lists. You also might want to look at the find_member command. What have others done on this issue? Another concern is; what happens if someone sends to a superlist during a list rebuild? Is sync_members robust enough to at least always keep one list of addresses around? No problems. Lists are locked during changes, so the sent email will simply be queued until the lock is removed. Hope that's helpful - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Major problems after major problems...
So we had some problems with disk space on the box which houses mailman...we ran out. As a solution, we moved /mailman-2.0.13/archives to /home/mailman-2.0.13/archives -/home resides on a different partition and has plenty of free space. I created and symlink in /mailman-2.0.13 for the archives directory and i have double-checked all of the permissions in /home/mailman-2.0.13/archives -initially there were issues. Now I am have some problems with subscriptions and in viewing some public archives. there are a couple of issues: Logging into admin mylist yields the admin pages but i get this at the bottom of the page: Bug in Mailman version 2.0.13 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Looking into the /mailman-2.0.13/logs/error, i see this: Oct 23 10:33:04 2003 admin(24579): admin(24579): [- Mailman Version: 2.0.13 -] admin(24579): [- Traceback --] admin(24579): Traceback (most recent call last): admin(24579): File /mailman-2.0.13/scripts/driver, line 96, in run_main admin(24579): main() admin(24579): File ../Mailman/Cgi/admin.py, line 175, in main admin(24579): mlist.Save() admin(24579): File /mailman-2.0.13/Mailman/MailList.py, line 861, in Save admin(24579): self.CheckHTMLArchiveDir() admin(24579): File /mailman-2.0.13/Mailman/Archiver/Archiver.py, line 256, in CheckHTMLArchiveDir admin(24579): makelink(privdir, pubdir) admin(24579): File /mailman-2.0.13/Mailman/Archiver/Archiver.py, line 42, in makelink admin(24579): os.symlink(old, new) admin(24579): OSError: [Errno 13] Permission denied ... I have seen this error multiple times for multiple actions. Most trouble of which is when a user attempts to subscribe via the web to a list and this happens in the error log: Oct 19 05:53:36 2003 admin(27587): admin(27587): [- Mailman Version: 2.0.13 -] admin(27587): [- Traceback --] admin(27587): Traceback (most recent call last): admin(27587): File /mailman-2.0.13/scripts/driver, line 96, in run_main admin(27587): main() admin(27587): File ../Mailman/Cgi/subscribe.py, line 76, in main admin(27587): process_form(mlist, doc) admin(27587): File ../Mailman/Cgi/subscribe.py, line 187, in process_form admin(27587): mlist.AddMember(email, pw, digest, remote) admin(27587): File /mailman-2.0.13/Mailman/MailList.py, line 983, in AddMember admin(27587): cookie = Pending().new(name, password, digest) admin(27587): File ../Mailman/Pending.py, line 74, in new admin(27587): self.__save(db) admin(27587): File ../Mailman/Pending.py, line 111, in __save admin(27587): fp = open(self.db_path, w) admin(27587): IOError: [Errno 13] Permission denied: '/mailman/data/pending_subscriptions.db' Any idea as far as what i should be looking at here? i have checked permissions all over the place and it seems like something simple but i cannot seem to find it. Ideas? Any help is much appretiated. Thanks. -- ___ Mike Neuharth ADCS Technology Specialist http://www.umn.edu/adcs === E-Mail : [EMAIL PROTECTED] Page Mail : [EMAIL PROTECTED] ___ What is important, it seems to me, is not so much to defend a culture whose existence has never kept a man from going hungry, as to extract, from what is called culture, ideas whose compelling force is identical with that of hunger. -Antonin Artaud -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Perl API
Hi, I need to write a few custom management frontends to mail man and they need to be in perl. Is there a perl API[module] for mailman ? Jeff. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Address matching behavior
Hi all, I've been running a bunch of mailman lists for about two years now, and a couple of months ago I upgraded to version 2.1 from 2.0. Since the change, every message sent to any one of our members-only lists is being held for approval. The problem appears to be a change in mailman's address matching behavior. Previously, if [EMAIL PROTECTED] was subscribed, email from [EMAIL PROTECTED] would be accepted as well. The new mailman, however, doesn't think [EMAIL PROTECTED] is a member, and so holds the message for approval. This is a huge pain. Is there a way I can get back the old behavior? I searched all over google and Usenet, and it seems like no one else has commented on this before... Thanks, -- -Vijay -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] strange bounce notification
Hello -- One of our lists owners has received a very strange uncaught bounce notification. I can't figure out where it's coming from... here is the message: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 23, 2003 2:36 PM To: [EMAIL PROTECTED] Subject: Uncaught bounce notification The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). For more information see: http://lists.olin.edu/mailman/admin/it-student-wg/bounce Subject: New subscription request to list It-student-wg [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Thu, 23 Oct 2003 14:35:54 -0400 To: [EMAIL PROTECTED] Your authorization is required for a mailing list subscription request approval: For: [EMAIL PROTECTED] List: [EMAIL PROTECTED] At your convenience, visit: http://lists.olin.edu/mailman/admindb/it-student-wg to process the request. How would this bounce? Where was it sent to? -- Aaron Bennett UNIX Administrator Franklin W. Olin College of Engineering -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Address matching behavior
On Thursday, October 23, 2003, at 08:50 pm, Vijay G. Bharadwaj wrote: Hi all, I've been running a bunch of mailman lists for about two years now, and a couple of months ago I upgraded to version 2.1 from 2.0. Since the change, every message sent to any one of our members-only lists is being held for approval. The problem appears to be a change in mailman's address matching behavior. See: http://www.mail-archive.com/[EMAIL PROTECTED]/msg11701.html Previously, if [EMAIL PROTECTED] was subscribed, email from [EMAIL PROTECTED] would be accepted as well. The new mailman, however, doesn't think [EMAIL PROTECTED] is a member, and so holds the message for approval. This is a huge pain. Is there a way I can get back the old behavior? I searched all over google and Usenet, and it seems like no one else has commented on this before... Thanks, -- -Vijay --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Address matching behavior
On Thu, Oct 23, 2003 at 03:50:44PM -0400, Vijay G. Bharadwaj wrote: I've been running a bunch of mailman lists for about two years now, and a couple of months ago I upgraded to version 2.1 from 2.0. Since the change, every message sent to any one of our members-only lists is being held for approval. The problem appears to be a change in mailman's address matching behavior. Previously, if [EMAIL PROTECTED] was subscribed, email from [EMAIL PROTECTED] would be accepted as well. The new mailman, however, doesn't think [EMAIL PROTECTED] is a member, and so holds the message for approval. I believe that this is the intended behavior. You need to determine if you want outgoing mail to be [EMAIL PROTECTED] or [EMAIL PROTECTED] - you should not use both. The 2 e-mail addresses are different, and I think you need to fix the outgoing mail to masquerade [EMAIL PROTECTED] to [EMAIL PROTECTED] I would think the 2.0 behavior, as you specified, is a bug. How would you expect it to work if [EMAIL PROTECTED] and [EMAIL PROTECTED] are different users? From an outsider's point of view, the most certainly are. [EMAIL PROTECTED] is also different than [EMAIL PROTECTED] - in some cases at my site, they are (root for example). IMO, 2.1 is doing the right thing and you need to fix your outgoing mail behavior. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] New Zealand
Is there anyone from NZ out there I could ring for some help with mailman? Richard Davis Communications Advisor and Webmaster Presbyterian Church of Aotearoa New Zealand PO Box 9049, Wellington, New Zealand Phone: +64.4.801600; Fax: +64.4.8016001 Direct: +64.4.3818285 Mob: 027.4048656 http://www.presbyterian.org.nz/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Address matching behavior
Thanks for the replies. I realize that adding the host name is not-so-desirable behavior (which is why you won't see hostnames in my outgoing email :)). It is, however, very common, and I don't have any control over the large number of users and mail servers that would need to be fixed in order for it to go away. Ed - the 2.0 behavior was a config option, not a bug. I know that someone who controls a host can give themselves any username they want - this is just one of the many easy ways to forge a from address. However, most users don't do this, and many are either unable or not knowledgable enough to fix their clients or servers to canonicalize the outgoing address. As such, SMART_MATCH provided a useful service to some of us harrowed admins. I think I will take a closer look at the membership adapter. It doesn't seem that hard to hack the functionality back in at first glance, and it sure beats having to nag at all the (mostly external) users who have the problem. -- -Vijay -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman CGI not working
Hello, I'm a newbie, and have just installed mailman on Red Hat 9, with the apache web server. None of it was done with rpm, I downloaded, configured and compiled from both apache.org and the mailman site. I've created the 'mailman' list, after having gone through all install docs. Mailman's cgi does not work, however. The documentation said to check the apache group setting, which is at the default right now #-1, but I have changed it to gid 99, to no avail. Default cgi group is apparently www in mailman, although the username is nobody in apache (gid 99 in redhat) for httpd. How do I get the mailman cgi to work? I've set the scriptalias directive in apache to /mailman/ /usr/local/mailman/cgi-bin I also tried re-running the configure script using the --with-cgi-id , but no matter what it seems to use www. The first mailing from the mailman list went to my email ok, returning the link myserver.vcd.hp.com/mailman/admin/mailman, but all that is returned is the object not found - the requested URL was not found on this server Any help is greatly appreciated. Thanks, Randy Foo Unix System Administrator The Kemtah Group at Hewlett Packard -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Good win32 mailing list manager server?
Does anyone know of a no-cost mailing list manager application that runs on Win2k? I saw the FAQ entry for mailman and have googled around for quite awhile now, but can't seem to find any. I would think this would be obvious somewhere, but I can only find a handful of commercial implementations that I've never heard of before. Is anyone working on a win32 port of mailman, or has anyone put together a howto to get it running under Win2K? I'd set up a linux box but I think our IT people would freak out... Regards, Glen Starrett -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] AOL now bouncing ALL email from ALL mailman systems
Serious issue for those with aol subscribers. I'm currently whitelisted with aol and usually have no problem with mail delivery. Currently running 2.1.3 This morning I noticed aol bouncing just about all of the emails from my mailman server with one or the other of the following bounce messages: Oct 23 09:39:34 myserver postfix/smtp[5615]: 974515884F8: to=[EMAIL PROTECTED], relay=mailin-04.mx.aol.com[64.12.138.152], delay=1, status=bounced (host mailin-04.mx.aol.com[64.12.138.152] said: 500 SYNTAX ERROR, COMMAND UNRECOGNIZED) Oct 23 09:39:34 myserver postfix/smtp[6435]: 1ED73588177: to=[EMAIL PROTECTED], relay=mailin-01.mx.aol.com[64.12.137.89], delay=0, status=bounced (host mailin-01.mx.aol.com[64.12.137.89] said: 554 TRANSACTION FAILED) I spoke with the aol postmaster support line and they confirmed that the problem is due to the form of the mailman reply-to address to process bounces: [EMAIL PROTECTED] They don't like the = in the address. Again this appears to be due to a recent change in aol's mail server software. I'll update once I hear back from aol -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] AOL now bouncing ALL email from ALL mailman systems
I meant to say that the issue is with the mailman form of Sender: and Errors-to: Not Reply-to -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] AOL now bouncing ALL email from ALL mailman systems
Is there anything we can do to remedy this in our own installations of Mailman? It'd be nice if AOL would fix it, but I don't think we can count on that. It's clearly not a situation any of us can live with. So what shall we do? Allan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] AOL now bouncing ALL email from ALL mailman systems
Someone emailed me to point out that this form of Sender: and Errors to: address is only used if you have personalization turned on. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] AOL now bouncing ALL email from ALL mailman systems
Someone emailed me to point out that this form of Sender: and Errors to: address is only used if you have personalization turned on. I couldn't live without personalization now that I have it on. Would removing the RFC 2369 headers make any difference to AOL? Allan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Where is 'reject' message stored
One of my associates set up content filters to reject attachments and other things. He created a custom message to explain this. Now he wants to change the message, but I cannot locate which file in /mailman holds the text (and I did look at all of them). Can somebody tell me how I could find it. I do know text fragments. Thanks!!! --Warren -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] restarting a blocked list
On Thu, 2003-10-23 at 07:37, javier wrote: i'm actually working with 2.1.3 (always the latest version is good ;-) ) theory of unix says that two diferents tasks can open and write a file Do you have the ~mailman/locks directory shared as well? That should do a fair job of keeping the processes (even on multiple machines) from writing to the files simultaneously. at same time, so i thought that was posible... Now machine2 is stoped, and DNS only has a mailmans.domain.es - machine1, at momment [EMAIL PROTECTED] is working good, so i'm beginning to think that theory of unix is my problem, and if only one machine is working with mailman, comunicaciones @cedex.es won't stop... anyway, i'll study qfiles, thank you very much jonc, and hope you to enjoy my experiment :-) Cool. I've used LVS to do something similar. In my case, I run a separate process in the background that keeps the background servers synchronized (and creates a lock file during the sync). In the end, I think that is a simpler setup, as each server can operate independently. Originally I set it up so that only one of the background servers handled the Web-requests - that removed any latency issues from users who expect to see the changes instantly propagated. Good Luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: AOL now bouncing ALL email from ALL mailman systems
Links at Momsview.com wrote: Someone emailed me to point out that this form of Sender: and Errors to: address is only used if you have personalization turned on. I must differ with the subject heading. I have four Mailman 2.1.2 lists with personalization on, and I am not getting bounces from AOL. In fact I just sent a message to one, and it went to my AOL test account just fine. Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Where is 'reject' message stored
On Thu, 2003-10-23 at 23:10, Warren Hoffman wrote: One of my associates set up content filters to reject attachments and other things. He created a custom message to explain this. Now he wants to change the message, but I cannot locate which file in /mailman holds the text (and I did look at all of them). Can somebody tell me how I could find it. I do know text fragments. Thanks!!! --Warren for i in `find /var/mailman/ -type f` do; grep -H fragment $i; done This will search through every file in every subdirectory of /var/mailman and look for the word fragment. If it finds a match, it prints out the files name. Good Luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
