Re: [Mailman-Users] The newaliases command
No. newaliases is for sendmail. The equivalent Postfix command is postalias. I use newaliases with Postfix, as Postfix supplies a newaliases script for those who are used to the sendmail commands. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- 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] Permission problem in handling moderator requests; also archive queries
Sekhar Ramakrishnan wrote: I have three questions - two general, and one about a particular problem. 1) Is there a plan to offer a search function for private archives? See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.011.htp for links to current solutions. This is a highly requested feature and something will eventually be done to provide an archive search, but at this point there is no timeframe. 2) One of our lists has monthly archives. Is there a way to combine older archives (more than a year or two old) into yearly archives? It's probably a manual process and possibly not a good idea, since any existing URLs such as those in one archived post pointing to another or those in a FAQ or those saved by individuals will be invalidated by such a change. That said, you could do it by something like the following: 1) stop Mailman to prevent new mail from being archived 2) set the list's archive_volume_frequency to yearly 3) remove all the 'old' monthly directories and .txt files from archives/private/listname. also, remove the 'old' subdirectories from archives/private/listname/attachments and the 'old' database files from archives/private/listname/database 4) figure out the message number of the last 'old' message in the archives/private/listname.mbox/listname.mbox file or the first and last of the 'old' monthly messages if you've done this before. 5) run bin/arch with the appropriate --end (and --start) options as determined in step 4). do NOT use the --wipe option. 6) set the list's archive_volume_frequency back to monthly. 7) start Mailman. 3) I administer a few Mailman lists (version 2.1.9.cp2) on a cPanel X account that I control as well. I have a problem with the Tend to pending moderator requests page. Everything works normally as long as I am able to approve, reject, discard, etc on the main adminb page. But if I click on view all messages from to deal with messages from a single person, I get a page with that person's messages but, whatever I do, I get an error message, given below. This is a creeping problem. I saw it first on one list, and I didn't worry since I was about to delete the list. But for the past few weeks, I have the problem on my main list. Before posting this, I set up a new list with just one member and posted a message big enough to be held up for moderation. I had no problem clicking on view all messages from and disposing of the message. It didn't matter whether or not the list name had a hyphen, in case that is relevant. Thanks in advance. Sekhar Ramakrishnan Error message: Forbidden You don't have permission to access /mailman/admindb/list_domain on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Apache/1.3.37 Server at insaf.net Port 80 First see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp. That said what additional information is in the Apache error_log? Is http://server.name//mailman/admindb/list_domain the correct URL for this list's admindb page (Is server.name the same as domain)? Look at the 'page source' for the 'view all messages from'. Is the action URL in the form tag correct? I'm really grasping at straws here because all admindb pages should generate the same form tag with the same action URL so it should either work or not from any of the admindb pages. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Mailing List - people say their e-mails neverappear
Patrick M.wrote: Please forgive me, as I'm very new to Mailman. While I know my way around Postfix, troubleshooting Mailman is another issue. I can see that e-mail gets sent and delivered to the particular mailing list in question, but sometimes people tell me their e-mails never get posted to the mailing list. Other people say they submit their post, and it eventually gets there, after 10 or so minutes. Since I don't know how to troubleshoot Mailman, I can only suspect that is has something to do with the NFS, although another part of me is telling me that it can't be. Can you folks push me in the right direction? What should I be troubleshooting? Is there anything I can provide so that you folks can help me troubleshoot further? Brad has given lots of good advice already in this thread including a reference to http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.078.htp. I want to emphasise that, as the thread seems to be concentrating more on NFS. In particular, look at Mailman's 'smtp' log and correlate that with your MTA logs. Normally, you will see in your MTA log that a post has been delivered to Mailman at some time and then you will see an entry Mailman's 'smtp' log x seconds later which says message-id smtp for n recips, completed in y seconds. Normally x is only slightly larger (less than 2 seconds) than y. y is the time for all the SMTP transactions to deliver the mail to the n list recipients, and y-x is the sum of the times the message was queued in Mailman's in and out queues and Mailman's non-SMTP processing time. Also, are the 'missing' posts in the list's archive? Do the delayed posts appear in the archive without delay? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Adding the list aliases
But are the command -o not removed in the newest mailman versions? -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Barry Finkel Skickat: den 7 september 2007 14:30 Till: Mailman-Users@python.org Ämne: Re: [Mailman-Users] Adding the list aliases Eh i try i understand But the command newaliases -o ??? Or Should i run newaliases -oA/etc/aliases assuming that that is the name of your aliases file. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- 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/jonsson%40mj1.mine.nu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Adding the list aliases
Eh i try i understand But the command newaliases -o ??? Or Should i run newaliases -oA/etc/aliases assuming that that is the name of your aliases file. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- 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] Adding the list aliases
mattias wrote: But after i have created a list with newlist Wil the aliases be displayed? I believe so (but it's been a long time since I created a list without using the nice Postfix integration that handles this automatically, so I could be wrong). And wil all this commands work iven if i install with apt-get install in ubuntu Or yum in fedora I don't know about ubuntu, but in Fedora (and Red Hat), mailman is installed in different locations than the default Mailman tarball would install things. The details of the changes are included in the file INSTALL.REDHAT, located in /usr/share/doc/mailman-2.1.9. I mentioned this in reply to your question on the fedora users list just yesterday (along with answers and links to the Postfix integration instructions). -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Every side I get up on is the wrong side of bed. If it weren't so expensive, I'd wish I were dead. -- signed Unhappy pgpPERm41CNSy.pgp Description: PGP signature -- 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] pdf-attachments in archives stored as attachment.obj
Hi list, i'm new to the list and i've got a problem with that pipermail-archives. Every attachment is listed under the Messages with it's size an filename etc. All the files are stored with the file-extension as they are send to the list, except *.pdf-files. They are stored as attachment.obj instead of attachment.pdf. it seems that pipermail / scrubber or another candidate doenst get it's mime-type in the archiving-process. Any suggestions how to fix that? Maybe there is a relation from my /etc/mime.types to that problem? Greets, René -- 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] Adding the list aliases
mattias [EMAIL PROTECTED] wrote: Eh i try i understand But the command newaliases -o ??? Or Should i run and I replied: newaliases -oA/etc/aliases assuming that that is the name of your aliases file. and mattias replied: But are the command -o not removed in the newest mailman versions? The newaliases command is a sendmail and/or Postfix command. It is supplied by those packages, not by Mailman. The command takes /etc/aliases and creates /etc/aliases.dir /etc/aliases.pag These two files are internal database formats of the aliases file so that the sendmail/Postfix can search the alias file/database more quickly. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- 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] admin user passwords
Chris Waltham wrote: Is there an easy way to change a list admin's password in 2.0.x? My version (2.0.12) lacks a change-pw command. I have no experience with Mailman prior to 2.1.4, but from the code, it appears that you change the password at the bottom of the General Options page in the web admin interface. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] pdf-attachments in archives stored as attachment.obj
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 de ren0r wrote: All the files are stored with the file-extension as they are send to the list, except *.pdf-files. They are stored as attachment.obj instead of attachment.pdf. it seems that pipermail / scrubber or another candidate doenst get it's mime-type in the archiving-process. Any suggestions how to fix that? Maybe there is a relation from my /etc/mime.types to that problem? There are a few possible of solutions. 1) you can set SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True in mm_cfg.py to use the extension of the attachment filename instead of guessing the extension from the content-type. 2) you can try to make sure that all the clients that send pdf attachments give them a content-type of application/pdf. 3) if SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION is False, scrubber calls the Python library mimetypes.guess_all_extensions() function to map the content-type to an extension. This module in turn supplements its built in list by attempting to read several files (depending on Python version) including /etc/mime.types so if the issue is due to some content-type other than application/pdf, associating that content-type with the pdf extension in /etc/mime.types may work. - -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFG4WOWVVuXXpU7hpMRAkO7AKDhZcVr2O4lpjJ34jIP9bByOTuBSgCfTJRX 6mRUm9M+ZlQzKoc2nhHaI00= =8UHf -END PGP SIGNATURE- -- 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] Mailing Lists and Outlook
Brian Canty wrote: I was wondering if anyone has experienced the problem I am having with outlook. It seems every time someone sends an email to my lists that contain HTML, outlook put the email into a file. Does anyone know of a way to tell outlook to let the email be shown with putting it into a file. If you mean that Outlook is showing the body of the mail as an attachment, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.039.htp. If you mean something else, please try to be more specific about what is actually happening. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Cleaning up Mailman log files
Does Mailman need to be stopped before cleaning up the log files or can I just cat /dev/null error -- We've Got Your Name @ www.mail.com!!! Get a FREE E-mail Account Today - Choose From 100+ Domains -- 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 in chrooted OpenBSD
Patrick Valencia wrote: I need help setting up mailman in a chrooted OpenBSD environment. I've copied the /usr/local/lib/mailman and /var/spool/mailman directories to /var/www/mailman, as well as the modules it needed, but now I'm getting an error that says: Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Failure to find group name for GID 67. Mailman expected the CGI wrapper to be executed as group www, but the system's web server executed the wrapper as GID 67 for which the name could not be found. Try adding GID 67 to your system as www, or tweak your web server to run the wrapper as group www. I believe that a chrooted apache drops the user name and just holds onto the user id. Can anyone help me out with this? I really need this installed and kinda need to keep the chroot. If I need to start over with a fresh installation of mailman, that's not a problem. Any and all help would be GREATLY appreciated! I suggest you try install Mailman from source http://sourceforge.net/projects/mailman and configure it with --prefix=/var/www/mailman and --with-cgi-gid=67 as well as the appropriate --with-mail-gid. Alternatively, there may be a way to set the expected cgi group in whatever package you installed and you might be able to set that to 67. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Mailing Lists and Outlook
Hello Everyone - I was wondering if anyone has experienced the problem I am having with outlook. It seems every time someone sends an email to my lists that contain HTML, outlook put the email into a file. Does anyone know of a way to tell outlook to let the email be shown with putting it into a file. Thanks in advance. Brian Canty Manager Computer Information Services American Psychoanalytic Association 212-752-0450 x17 -- 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] We're sorry, we hit a bug!
I'm hoping someone can help me figure out a problem that I've been having for some time now. For some of my lists when I try to log in and approve/discard posts using the admin function I get the following error. This is obviously a cpanel version of mailman. I am also trying to get support through my hosting company on this. 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. Looking at the error log for this particular error shows the following: Sep 07 07:56:13 2007 (19565) Uncaught runner exception: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Traceback (most recent call last): File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py, line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/ Switchboard.py, line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ __init__.py, line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 240, in _parsebody msgobj = self.parsestr(part) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 265, in _parsebody msg = self.parse(fp) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 206, in _parsebody raise Errors.BoundaryError( BoundaryError: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Ignoring unparseable message: 1173539747.1827431+c4b30a10b02f512f3aa88e8038d6f17843cdb81b Sep 07 07:56:13 2007 (19565) Uncaught runner exception: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Traceback (most recent call last): File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py, line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/ Switchboard.py, line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ __init__.py, line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 240, in _parsebody msgobj = self.parsestr(part) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 265, in _parsebody msg = self.parse(fp) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 206, in _parsebody raise Errors.BoundaryError( BoundaryError: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Ignoring unparseable message: 1187578207.7474239+de47fddadb334d46d06c9248df89448cf2a433ce Sep 07 07:58:41 2007 admin(25812): admin(25812): [- Mailman Version: 2.1.9.cp2 -] admin(25812): [- Traceback --] admin(25812): Traceback (most recent call last): admin(25812): File /usr/local/cpanel/3rdparty/mailman/scripts/ driver, line 101, in run_main Thanks, J.R. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ:
Re: [Mailman-Users] We're sorry, we hit a bug!
J.R. Constance wrote: I'm hoping someone can help me figure out a problem that I've been having for some time now. For some of my lists when I try to log in and approve/discard posts using the admin function I get the following error. This is obviously a cpanel version of mailman. I am also trying to get support through my hosting company on this. 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. Looking at the error log for this particular error shows the following: Sep 07 07:56:13 2007 (19565) Uncaught runner exception: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Traceback (most recent call last): File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py, line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/ Switchboard.py, line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ __init__.py, line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 240, in _parsebody msgobj = self.parsestr(part) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 265, in _parsebody msg = self.parse(fp) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 206, in _parsebody raise Errors.BoundaryError( BoundaryError: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Ignoring unparseable message: 1173539747.1827431+c4b30a10b02f512f3aa88e8038d6f17843cdb81b Sep 07 07:56:13 2007 (19565) Uncaught runner exception: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Traceback (most recent call last): File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py, line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/ Switchboard.py, line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ __init__.py, line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 240, in _parsebody msgobj = self.parsestr(part) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 265, in _parsebody msg = self.parse(fp) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 206, in _parsebody raise Errors.BoundaryError( BoundaryError: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Ignoring unparseable message: 1187578207.7474239+de47fddadb334d46d06c9248df89448cf2a433ce The above two 'errors' and tracebacks just coincidently occurred about the same time as your 'we hit a bug' error. The above errors are due to malformed (unparseable) messages which almost certainly were spam sent to your lists (probably the same message sent to two lists). Sep 07 07:58:41 2007 admin(25812): admin(25812): [- Mailman Version: 2.1.9.cp2 -] admin(25812): [- Traceback --] admin(25812): Traceback (most recent call last):
Re: [Mailman-Users] Cleaning up Mailman log files
[EMAIL PROTECTED] wrote:
Does Mailman need to be stopped before cleaning up the log files or can I just
cat /dev/null error
It is best to do
bin/mailmanctl reopen
following any logfile changes done while Mailman is running.
Why not use logrotate? A typical config excerpt for logrotate is
something like
list of paths to mailman's logs {
missingok
sharedscripts
postrotate
/path/to/bin/mailmanctl reopen /dev/null 21 || true
endscript
}
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Exporting Subscribers...
Hi Everyone, I was wondering if it was possible to export the subscribers list to a text file of some sort. Anyone know how? Thanks! -Jeff -- 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] Exporting Subscribers...
Jeff Shepherd wrote: I was wondering if it was possible to export the subscribers list to a text file of some sort. Anyone know how? See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.062.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] thanks
I will only say Thanks for all help Now my mailman works fine -- 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] Exporting Subscribers...
/usr/lib/mailman/bin/list_members -f -p name of your list and if you want more support you call the list_members program with the flag -h : /usr/lib/mailman/bin/list_members -h: List all the members of a mailing list. Usage: ./list_members [options] listname Where: --output file -o file Write output to specified file instead of standard out. --regular / -r Print just the regular (non-digest) members. --digest[=kind] / -d [kind] Print just the digest members. Optional argument can be mime or plain which prints just the digest members receiving that kind of digest. --nomail[=why] / -n [why] Print the members that have delivery disabled. Optional argument can be byadmin, byuser, bybounce, or unknown which prints just the users who have delivery disabled for that reason. It can also be enabled which prints just those member for whom delivery is enabled. --fullnames / -f Include the full names in the output. --preserve / -p Output member addresses case preserved the way they were added to the list. Otherwise, addresses are printed in all lowercase. --invalid / -i Print only the addresses in the membership list that are invalid. Ignores -r, -d, -n. --unicode / -u Print addresses which are stored as Unicode objects instead of normal string objects. Ignores -r, -d, -n. --help -h Print this help message and exit. listname is the name of the mailing list to use. Note that if neither -r or -d is supplied, both regular members are printed first, followed by digest members, but no indication is given as to address status. Jeff Shepherd wrote: Hi Everyone, I was wondering if it was possible to export the subscribers list to a text file of some sort. Anyone know how? Thanks! -Jeff -- 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/msilva%40nmcourts.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mario Silva Systems Administrator Supreme Court of New Mexico Judicial Information Division 2905 Rodeo Park Dr. East, Bldg. #5 Santa Fe, NM 87505 Phone: (505) 476-6959 / Mobil: (505) 660-1026 Fax:(505) 476-6952 Website: http://www.nmcourts.gov mailto: [EMAIL PROTECTED] LEGAL DISCLAIMER: The content of this data transmission is not considered as an offer, proposal, understanding, or agreement unless it is confirmed in a document signed by a legal representative of Supreme Court of the State of New Mexico or the Judicial Information Division. The content of this data transmission is confidential and it is intended to be delivered only to the addresses, therefore, it shall not be distributed and/or disclosed through any mean without the original sender's previous authorization. If you are not the addressee you are forbidden to use it, either totally or partially, for any purpose. AVISO LEGAL: El contenido de este mensaje de datos no se considera oferta, propuesta o acuerdo, sino hasta que sea confirmado en documento por escrito que contenga la firma autógrafa del apoderado legal de La Suprema Corte del Estado de Nuevo Mexico o de la Division de Informatica del Estado. El contenido de este mensaje de datos es confidencial y se entiende dirigido y para uso exclusivo del destinatario, por lo que no podrá distribuirse y/o difundirse por ningún medio sin la previa autorización del emisor original. Si usted no es el destinatario, se le prohíbe su utilización total o parcial para cualquier fin. -- 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] who command issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Running Mailman 2.1.9 lists at Dreamhost (if that matters). It seems that, under the heading: - - Results: Non-digest (regular) members: The email who command is showing digest and regular members. I looked for a bit for discussion of the who command but did not find any mention of this. Where did I miss it? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRuHN8dN2DJl/zagkAQLt7Qf/YYceRSsAfETXi19EtWHhk5xZOwLNlx6u sqlTwFFBigdLjv3SvdSYd9NsyLU+oBhOSD03QO0dsitrC8zoljcoJt2V01hY20rU hHpE4K1LUorsXfsiwLCaqnvtSGhjss+dtgKKRHf1WCH9IJtxtfPvzbHBgG6bzbUd 80ZrjEbETsRs6OP/2KpwMXkcGDgXv5GRNzOqJvAaFxtd6GwoNiLPQGlEkrN1xEKE n3ylIabpCteFnOFoBRH6bdltCf2M7rXCndnSod5RkvfAOhzt/oANVnLcCZONHI2l hlnP/fvecGSNi6P7sbzhA0RdhNjlFqhTsP8/ttKsZNSXqxeBtcv0Cg== =CNjl -END PGP SIGNATURE- -- 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] who command issue
Brandon Sussman wrote: Running Mailman 2.1.9 lists at Dreamhost (if that matters). It may. They have their own modifications. It seems that, under the heading: - - Results: Non-digest (regular) members: The email who command is showing digest and regular members. I looked for a bit for discussion of the who command but did not find any mention of this. Where did I miss it? I don't see what you describe. When I send the 'who command' I get something like - Results: Non-digest (regular) members: [EMAIL PROTECTED] (Mark Sapiro) ... Digest members: [EMAIL PROTECTED] (Mark (mime digest) Sapiro) [EMAIL PROTECTED] (Mark (digest) Sapiro) ... Perhaps it is a Dreamhost issue. Have you asked them? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] who command issue
Mark Sapiro wrote: I don't see what you describe. When I send the 'who command' I get something like - Results: Non-digest (regular) members: [EMAIL PROTECTED] (Mark Sapiro) ... Digest members: [EMAIL PROTECTED] (Mark (mime digest) Sapiro) [EMAIL PROTECTED] (Mark (digest) Sapiro) ... Note however that if there are no regular members, the entire Non-digest (regular) members: section including the heading is omitted and similarly if there are no digest members. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] who command issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Sapiro wrote: Brandon Sussman wrote: Perhaps it is a Dreamhost issue. Have you asked them? Not yet - I wanted to make sure I did not miss a true Mailman issue. - -- - - |/\/\ /\/\ /\/\ Webster Ridge Farm |http://WebsterRidge.com | |\oo/ \--/ \--/ Brandon and Mary Sussman | (603)648-2595 | |=\/= =\/= =\/= 1482 Pleasant St.| N 43.32558 W 71.70835 | | Sleep Well... Webster, NH, 03303-7613 |19TBJ800015 | - - |Lamb, Poultry, Eggs, Quilts and Web Sites |Think Locally, Buy Locally! | - - -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRuHfQtN2DJl/zagkAQIeKwf/cSr61EVe0c/j8nLmz3fX6khNPVUHwrcq /jCe0nfR9Zbxfw/hLEbLYuJT/ZIi+0rpHxbAPr4R05+EgRglv0kKgTzegmgwz9vQ o7kv+X7Cn53xOK5Dr+i/Hd//XfjsoChQFxwDzLSwyq8nZJnKaIVlvIC8I0hYLeCB iNqItPmAgnzWpuBR0tKDaDLGL0+ZUujC4DtdAk7oacf7icxIikwYPlOFTPPtmb43 SH3Mos4yRyYRu+JaYL0M0MgnoxrMOAed2eJ/n/kLsNBhEIh/OiF3nPup3y83ZWIZ Tclmu5rSqcT/C6JJrJCEUinJqeZKFUwDcyokEEcQiytmQG5lAqXj6A== =LtiY -END PGP SIGNATURE- -- 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 in chrooted OpenBSD
I configured it as such: ./configure --prefix=/var/www/mailman --with-mail-gid=67 --with-cgi-gid=67 --with-username=_mailman --with-groupname=_mailman (using the _mailman user group from the port install) and I still get the same error: Failure to find group name for GID 67. Mailman expected the CGI wrapper to be executed as group www, but the system's web server executed the wrapper as GID 67 for which the name could not be found. Try adding GID 67 to your system as www, or tweak your web server to run the wrapper as group www. I was pretty sure that this would force mailman to look for '67' as the group, but it seems to still be looking for 'www'. On 9/7/07, Mark Sapiro [EMAIL PROTECTED] wrote: Patrick Valencia wrote: I need help setting up mailman in a chrooted OpenBSD environment. I've copied the /usr/local/lib/mailman and /var/spool/mailman directories to /var/www/mailman, as well as the modules it needed, but now I'm getting an error that says: Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Failure to find group name for GID 67. Mailman expected the CGI wrapper to be executed as group www, but the system's web server executed the wrapper as GID 67 for which the name could not be found. Try adding GID 67 to your system as www, or tweak your web server to run the wrapper as group www. I believe that a chrooted apache drops the user name and just holds onto the user id. Can anyone help me out with this? I really need this installed and kinda need to keep the chroot. If I need to start over with a fresh installation of mailman, that's not a problem. Any and all help would be GREATLY appreciated! I suggest you try install Mailman from source http://sourceforge.net/projects/mailman and configure it with --prefix=/var/www/mailman and --with-cgi-gid=67 as well as the appropriate --with-mail-gid. Alternatively, there may be a way to set the expected cgi group in whatever package you installed and you might be able to set that to 67. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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 in chrooted OpenBSD
Matter of fact, when I configure it, the DCGI_GROUP=\www\ and so does the DMAIL_GROUP. I think it's taking the 67 as a gid and finding the group it belongs to. I'm still not exactly sure how it can't see the gid when it goes to run the cgi script I thought it would be able to, especially since the set_gid bit is enabled. Would it help if I added a /var/www/etc/group file with 67 mapped to 'www'? On 9/7/07, Patrick Valencia [EMAIL PROTECTED] wrote: I configured it as such: ./configure --prefix=/var/www/mailman --with-mail-gid=67 --with-cgi-gid=67 --with-username=_mailman --with-groupname=_mailman (using the _mailman user group from the port install) and I still get the same error: Failure to find group name for GID 67. Mailman expected the CGI wrapper to be executed as group www, but the system's web server executed the wrapper as GID 67 for which the name could not be found. Try adding GID 67 to your system as www, or tweak your web server to run the wrapper as group www. I was pretty sure that this would force mailman to look for '67' as the group, but it seems to still be looking for 'www'. On 9/7/07, Mark Sapiro [EMAIL PROTECTED] wrote: Patrick Valencia wrote: I need help setting up mailman in a chrooted OpenBSD environment. I've copied the /usr/local/lib/mailman and /var/spool/mailman directories to /var/www/mailman, as well as the modules it needed, but now I'm getting an error that says: Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Failure to find group name for GID 67. Mailman expected the CGI wrapper to be executed as group www, but the system's web server executed the wrapper as GID 67 for which the name could not be found. Try adding GID 67 to your system as www, or tweak your web server to run the wrapper as group www. I believe that a chrooted apache drops the user name and just holds onto the user id. Can anyone help me out with this? I really need this installed and kinda need to keep the chroot. If I need to start over with a fresh installation of mailman, that's not a problem. Any and all help would be GREATLY appreciated! I suggest you try install Mailman from source http://sourceforge.net/projects/mailman and configure it with --prefix=/var/www/mailman and --with-cgi-gid=67 as well as the appropriate --with-mail-gid. Alternatively, there may be a way to set the expected cgi group in whatever package you installed and you might be able to set that to 67. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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 in chrooted OpenBSD
Patrick Valenciawrote: I configured it as such: ./configure --prefix=/var/www/mailman --with-mail-gid=67 --with-cgi-gid=67 --with-username=_mailman --with-groupname=_mailman (using the _mailman user group from the port install) and I still get the same error: Failure to find group name for GID 67. Mailman expected the CGI wrapper to be executed as group www, but the system's web server executed the wrapper as GID 67 for which the name could not be found. Try adding GID 67 to your system as www, or tweak your web server to run the wrapper as group www. I was pretty sure that this would force mailman to look for '67' as the group, but it seems to still be looking for 'www'. I too thought that would be the case, but closer examination of configure says that when you give it --with-cgi-gid=numeric, it looks up the group name that corresponds to the numeric gid and uses the name. Also, the specific Failure to find group name for GID 67 message from the wrapper comes from the inability to find a group name for the numeric gid under which it was invoked, and the expected group www is the compiled in group name that came from looking up 67 at configure time. The bottom line is I think you have two options. Figure out how to make the web server (cgi-gid) and the MTA (mail-gid) invoke the respective wrappers with some gid that can be resolved to a name inside the chroot jail, and configure those as the expected groups, or modify the code in src/common.c to either bypass the group tests or change them to something that will work. You might also look at http://mail.python.org/pipermail/mailman-users/2007-August/058157.html and the containing thread and the results of http://www.google.com/search?hl=ensafe=offq=site%3Amail.python.org++inurl%3Amailman++chroot. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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 in chrooted OpenBSD
Patrick Valencia wrote: Matter of fact, when I configure it, the DCGI_GROUP=\www\ and so does the DMAIL_GROUP. I think it's taking the 67 as a gid and finding the group it belongs to. That's right. See my other reply. I'm still not exactly sure how it can't see the gid when it goes to run the cgi script I thought it would be able to, especially since the set_gid bit is enabled. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.htp. The setgid bit sets the effective group, but for security reasons the wrapper checks the original group by resolving the original gid to a name and seeing if that name matches what it was told to expect. If it can't resolve the original gid to a name, it gives the error. Would it help if I added a /var/www/etc/group file with 67 mapped to 'www'? If that would allow the wrapper to resolve gid 67 to the name www, then yes, that would do it. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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 in chrooted OpenBSD
Ok, so the /var/www/etc/group file works, but now it's giving me another error: No such file or directory. It mentions storing the output into a syslog, but from checking apache's error_log and access_log, I don't see anything useful. It shows /mailman/admin getting a 200 response, which means OK, but that's all it says. And since it's chrooted, I'm pretty sure it can't reach whatever syslog it's trying to. If I knew which log it was, I could make an entry in the chroot jail, and check, but I'm not sure what files it would be needing outside the chroot anyway. BTW, I really appreciate your help Mark! On 9/7/07, Mark Sapiro [EMAIL PROTECTED] wrote: Patrick Valencia wrote: Matter of fact, when I configure it, the DCGI_GROUP=\www\ and so does the DMAIL_GROUP. I think it's taking the 67 as a gid and finding the group it belongs to. That's right. See my other reply. I'm still not exactly sure how it can't see the gid when it goes to run the cgi script I thought it would be able to, especially since the set_gid bit is enabled. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.htp. The setgid bit sets the effective group, but for security reasons the wrapper checks the original group by resolving the original gid to a name and seeing if that name matches what it was told to expect. If it can't resolve the original gid to a name, it gives the error. Would it help if I added a /var/www/etc/group file with 67 mapped to 'www'? If that would allow the wrapper to resolve gid 67 to the name www, then yes, that would do it. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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 in chrooted OpenBSD
Patrick Valencia wrote: Ok, so the /var/www/etc/group file works, but now it's giving me another error: No such file or directory. Where do you see this error? Is there an entry in Mailman's error log (/var/www/mailman/logs/error I think in your case)? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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
