Re: [Mailman-Users] How to stop sendmail from spewing messages one itstarts?
Paul Williams wrote: 1). A user added a large number of subscribers by uploading an Excel spreadsheet. Mailman accepted the file and addresses appeared reasonable when viewed with IE but not so good with mozilla (each alpha char was followed by a box). I was able to remove the names using the remove_members command by removing all members. It seems that it might be a good check when importing a list of users, for mailman to make sure it is a text file so users don't mess things up inadvertantly. What Mailman version is this? Current Mailman (2.1.6) is pretty good about weeding out addresses with non-printable ascii characters. In particular, it won't accept whatever characters were displaying as a 'box'. We are using mailman 2.1.5. Is 2.1.6 that much better? 2). The second problem that developed is that the user has set notification on subscribing to yes and so she and her boss bere getting several thousand emails. I finally had to completely delete the list. Is there a better way to tell mailman to stop sending email from a specific list? If that is possible, I have not bumped into an explanation how mailman works so I would be able to stop it sending emails. Mass subscribe allows subscribing with or without notifications regardless of list settings. The notifications are created and placed in Mailman's virgin queue (qfiles/virgin/) and then processed by VirginRunner and placed in the out queue (qfiles/out). They are then picked up by OutgoingRunner and delivered to the outgoing MTA. You can stop Mailman (bin/mailmanctl stop) and then simply delete files from the queues. You can use bin/show_qfiles to examine qfiles if you are in doubt about what to delete. Of course, none of this deals with messages that have already been delivered to the MTA and are queued there. paulw -- 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 complie errors again
In a flurry of recycled electrons, Elvis Fernandes wrote: I am compiling mailman-2.1.5 on Solaris10 (SPARC) with gcc 3.3.2 When I do make install, I get the following fatal error: Mailman compiles itself. Are you compiling -python-? (That's what it looks like.) Sort of out of scope for this list, but you might want to take a look at: http://www.python.org/download/download_other.html /usr/include/sys/siginfo.h:432: error: parse error before k_siginfo_t /usr/include/sys/siginfo.h:437: error: parse error before '}' token In file included from /usr/include/sys/procset.h:24, from /usr/include/sys/wait.h:25, from /usr/include/stdlib.h:22, from /usr/local/include/python2.4/Python.h:39, from src/_japanese_codecs.c:12: Also check the python FAQs. z! -- 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
[Mailman-Users] Monthly password reminders not going out
Apologies if this is a duplicate message; I sent it yesterday afternoon but never saw it show up on the list. I have about a dozen lists running on Mailman 2.1.4 on an XServe with OSX 10.3.9; all but one are set to send out monthly password reminders, but none are going out. Other than that, Mailman is running perfectly the last 2-1/2 months -- messages, digest, archives, all working as they should be. Any suggestions as to why the monthly reminders aren't being sent? The initial notices with the password when someone subscribes do go out okay. Bob -- 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 complie errors again
I installed the python binaries. But I am building mailman on this solaris10 box. So I am sure that this error is from the mailman make install. Elvis On 12/9/05, Carl Zwanzig [EMAIL PROTECTED] wrote: In a flurry of recycled electrons, Elvis Fernandes wrote: I am compiling mailman-2.1.5 on Solaris10 (SPARC) with gcc 3.3.2 When I do make install, I get the following fatal error: Mailman compiles itself. Are you compiling -python-? (That's what it looks like.) Sort of out of scope for this list, but you might want to take a look at: http://www.python.org/download/download_other.html /usr/include/sys/siginfo.h:432: error: parse error before k_siginfo_t /usr/include/sys/siginfo.h:437: error: parse error before '}' token In file included from /usr/include/sys/procset.h:24, from /usr/include/sys/wait.h:25, from /usr/include/stdlib.h:22, from /usr/local/include/python2.4/Python.h:39, from src/_japanese_codecs.c:12: Also check the python FAQs. z! -- 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] Permissions problem accessing commands via php
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. Dave Bevis -- 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] Permissions problem accessing commands via php
On Fri, 9 Dec 2005, John Dennis wrote: 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. I'm giving serious thought to writing a mailman 'server', sort of like an SQL server process. It would let a cgi authenticate, then issue commands. Today it could just call the CLI programs, someday -- it could be the actual way MailMan does its work, with the other programs calling it. Drifting off topic . . . I've done mostly thinking about this because I don't know a lick of python, but it seems to me MailMan and the developers might benefit from breaking it up into more of a frontend/backend system. A 'server' process that accepts messages, sends them from the queue, manages users, etc. Then the web stuff would be one front end to this. There could then be other front ends -- integrating with packages like PostNuke, shopping carts, etc. The Unix way is small programs that do one job well. :-) Am I the only one who thinks this is a good idea ? I'm willing to help how I can, and have zero interest in starting a fork. :-) -Chris == Chris Candreva -- [EMAIL PROTECTED] -- (914) 967-7816 WestNet Internet Services of Westchester http://www.westnet.com/ -- 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 complie errors again
I fixed the mailman compile problem now. Just re-build the box with Solaris8! Thanks much Elvis On 12/9/05, Elvis Fernandes [EMAIL PROTECTED] wrote: I installed the python binaries. But I am building mailman on this solaris10 box. So I am sure that this error is from the mailman make install. Elvis On 12/9/05, Carl Zwanzig [EMAIL PROTECTED] wrote: In a flurry of recycled electrons, Elvis Fernandes wrote: I am compiling mailman-2.1.5 on Solaris10 (SPARC) with gcc 3.3.2 When I do make install, I get the following fatal error: Mailman compiles itself. Are you compiling -python-? (That's what it looks like.) Sort of out of scope for this list, but you might want to take a look at: http://www.python.org/download/download_other.html /usr/include/sys/siginfo.h:432: error: parse error before k_siginfo_t /usr/include/sys/siginfo.h:437: error: parse error before '}' token In file included from /usr/include/sys/procset.h:24, from /usr/include/sys/wait.h:25, from /usr/include/stdlib.h:22, from /usr/local/include/python2.4/Python.h:39, from src/_japanese_codecs.c:12: Also check the python FAQs. z! -- 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] Unable to create new mail list from browser.
Elvis Fernandes wrote: I changed the site passwd using bin/mmsitepass. And now when I try creating a new mail list thru the browser, it comes back with: Error: Illegal list name. Are these problems/errors documented somewhere? Is there something that I am missing? The error messages aren't documented in detail anywhere. They are *supposed* to be self explanitory. The only way to get more information is to look at the scripts themselves. In this case, the message is supposed to be Error: Illegal list name: list_posting_address Where list_posting_address is [EMAIL PROTECTED], and the error is issued because this is not a valid email address according to Utils.ValidateEmail which means either it contained one or more spaces or the emailhost part did not contain at least two dot-separated pieces, i.e., [EMAIL PROTECTED] is OK, [EMAIL PROTECTED] is not. emailhost depends on the setting of VIRTUAL_HOSTS_OVERVIEW and is either DEFAULT_EMAIL_HOST or the email host corresponding to the url host of the create page fron the VIRTUAL_HOSTS dictionary. -- 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] How to stop sendmail from spewing messages oneitstarts?
Paul Williams wrote: Mark Sapiro wrote: What Mailman version is this? Current Mailman (2.1.6) is pretty good about weeding out addresses with non-printable ascii characters. In particular, it won't accept whatever characters were displaying as a 'box'. We are using mailman 2.1.5. Is 2.1.6 that much better? Yes. it is better in this respect. It disallows octal codes 000 through 037 and 177 which were allowed in 2.1.5 (200 through 377 are disallowed in both). It also has some security fixes, a Python 2.4 compatability fix and several other features and fixes. See http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/NEWS?rev=2.43.2.51view=markup for more info. -- 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] High usage -- making Mailman nice
John Dennis wrote: 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. Mailman, via SMTPDirect sends all the delivery chunks for a message before returning control to the outgoing runner. Assuming we're not VERPing or personalizing, it sends the 'MAIL FROM' command followed by SMTP_MAX_RCPTS 'RCPT TO' commands, followed by 'DATA' and the message. After receiving the response to the 'DATA', it (normally, but depends on SMTP_MAX_SESSIONS_PER_CONNECTION) sends the 'MAIL FROM' for the next chunk on the same connection. It may throw in another HELO/EHLO between transactions. This is in the Python smtplib, and I haven't looked in detail. If the client waits for the transaction to complete they of course you're right. The client (Mailman) waits for the response to the 'DATA' command for each chunk. This doesn't mean the mail has been sent, but it has been accepted and queued within the MTA. How many queues the MTA uses at this point to actually send the mail is up to the MTA, not Mailman. -- 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 complie errors again
Carl Zwanzig wrote: In a flurry of recycled electrons, Elvis Fernandes wrote: I am compiling mailman-2.1.5 on Solaris10 (SPARC) with gcc 3.3.2 When I do make install, I get the following fatal error: Mailman compiles itself. Are you compiling -python-? (That's what it looks like.) Sort of out of scope for this list, but you might want to take a look at: http://www.python.org/download/download_other.html /usr/include/sys/siginfo.h:432: error: parse error before k_siginfo_t /usr/include/sys/siginfo.h:437: error: parse error before '}' token In file included from /usr/include/sys/procset.h:24, from /usr/include/sys/wait.h:25, from /usr/include/stdlib.h:22, from /usr/local/include/python2.4/Python.h:39, from src/_japanese_codecs.c:12: Actually, this comes from the installation of the japanese codecs in mailman. The src/_japanese_codecs.c file is in the Mailman 2.1.5 distribution in the misc/JapaneseCodecs-1.4.10 directory. This is one of several compilations of c programs/modules in the Mailman make install process. Note however that Mailman 2.1.5 is not fully compatible with Python 2.4. I don't know if it would fix this problen, but if you're running Python 2.4 (or even if you're not) you would do well to install Mailman 2.1.6 or later. I see from a later post, Elvis 'fixed' the problem by falling back to Solaris 8. It's hard to say what's really going on in the case that fails, but it looks like there is some compatibility issue between the header files in /usr/include/sys/ and gcc 3.3.2 on Solaris 10. Presumably, the Python header file /usr/local/include/python2.4/Python.h is included in many Python modules and thus this whole include path was exercised during the original compile of Python for Solaris 10 (maybe with some other c compiler). -- 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] Monthly password reminders not going out
Bob Bergey wrote: I have about a dozen lists running on Mailman 2.1.4 on an XServe with OSX 10.3.9; all but one are set to send out monthly password reminders, but none are going out. Other than that, Mailman is running perfectly the last 2-1/2 months -- messages, digest, archives, all working as they should be. Any suggestions as to why the monthly reminders aren't being sent? The initial notices with the password when someone subscribes do go out okay. Is the cron to run cron/mailpasswds at 5 a.m. on the first of the month (or other time) actually scheduled? -- 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] Permissions problem accessing commands via php
Dave B wrote: 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? The mail list Save() method effectively moves the current config.pck to config.pck.last and saves a new one (it's more complicated than this for safety, but this is the effect). Thus, every time any list attribute is changed and saved (i.e. whenever a post is processed or the admin or admindb interfaces are changed or a member changes options, etc., etc.), a new config.pck is created with 'standard' permissions. -- 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
