[Mailman-Users] Approve subscription requests via mail
Hi, when someone subscribes to my mailman mailinglist I get a subscription request (like I configured it): [..] At your convenience, visit: http://www.etc.example.org/foo/bar [..] Hm, this is not the convenience I imagined. Is it possible to configure mailman in such a way, that the admin is able to approve such subscription requests via mail? E.g. mailman could send some hash with the request and I would simply reply adding an approve/deny command string to it. Btw, it looks like the subject of the subscription request is localized according to the users language choice. The body is localized to the admin language choice. (I am using mailman 2.1.5-9ubuntu4.) Best regards Georg Sauthoff PS: Is it ok, if I submit a subscribtion request for this list to www.gmane.org (a nntp gateway and web-archive of mailinglists)? PPS: Perhaps you could remove the direct link to this list from http://www.gnu.org/software/mailman/lists.html (in the left row) - because the list requires subscription. pgpp7UAF7Bh5E.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
Re: [Mailman-Users] scripts/owners not setting list domain
Mark Sapiro [EMAIL PROTECTED] probably said: Peter Radcliffe wrote: Utils.get_site_email() with no hostname which goes through get_domain() to get where it's looking for... which pulls the hostname out of mm_cfg.DEFAULT_URL_HOST. Yes, but then it looks that up in VIRTUAL_HOSTS I've got what the Defaults file and the FAQ says is the default setting for virtual hosts for my url/email hosts. My mm_cfg.py section is thus; -- DEFAULT_EMAIL_HOST = 'list.pir.net' DEFAULT_URL_HOST = 'www.pir.net' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) -- I can't see a way to configure that to get what I think is the right answer from hostname = mm_cfg.VIRTUAL_HOSTS.get(get_domain(), get_domain()) but perhaps I'm missing something. The above says call get_domain() and use the result as a key to be looked up in VIRTUAL_HOSTS and return the value associated with that key or if the key is not found, return the result of get_domain(). So get_domain() should return DEFAULT_URL_HOST which when looked up in VIRTUAL_HOSTS should return DEFAULT_EMAIL_HOST. I'd say that if that even given a misconfiguration, if the VIRTUAL_HOSTS lookup fails it should be falling back to DEFAULT_EMAIL_HOST, not returning DEFAULT_URL_HOST which it seems to be to me. I suspect since this is a Mailman 2.0.x upgrade that you may still have a setting for DEFAULT_URL in mm_cfg.py. If so, remove it, and any setting for DEFAULT_HOST_NAME. These are deprecated and if present will override DEFAULT_URL_HOST in get_domain(). Nope, I checked quite specificly through the upgrade instructions and the config code and removed all the old config options. Still couldn't get it to use the DEFAULT_EMAIL_HOST. # fgrep DEFAULT_URL ~mailman/Mailman/mm_cfg.py DEFAULT_URL_HOST = 'www.pir.net' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_URL_PATTERN = 'https://%s/mailman/' # fgrep DEFAULT_HOST_NAME ~mailman/Mailman/mm_cfg.py # My names config section is as I listed above, the rest is smtp, archive, qrunners, etc, settings, which all seem to give the desired results. Your patch is OK, but it shouldn't be necessary and it affects bounce processing which is tricky for owners anyway. If it shouldn't be necessary then I'm missing something since I can't get that chunk of code to output the right answer... admittedly my python is a bit rusty, though. Ta, P. -- pir -- 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] request.pck does not match heldmsg-Listname files
Well, if mailman do not provide such a tool, there is lots of quick ways
to find such a files: Lets assume that any given .pck file must have at
least 5 lines to be considered a `good one'. So you can find those files
who have less than 5 lines, then you can delete it
Simple python oneliner for finding .pck files fewer than 5 lines:
cd ~mailman/data
python
import glob
'\n'.join([x[0] for x in [(open(y).name, len(open(y).readlines()))
for y in glob.glob('*.pck')] if x[1] 5])
## the (if x[1] 5) at the end is the total lines for each file.
Try it and watch. If you like it, you can save it as
find_orphaned_files.py and do
./find_orphaned_files.py | xargs ~mailman/bin/discard
Or something like this. Its just an idea, hope to be helpfull.
Bye!
Gerardo
Hello,
I've noticed heldmsg-ListName-* files in mailman/data, which the
request.pck file for the given list isn't aware of (the pickle only has a
version string).
Is there something which others have used to iterate the request.pck
file of all lists, and determine orphaned files in the mailman/data
directory so they can be deleted?
Thanks,
Ivan Fetch.
--
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/gherzig%40fmed.uba.ar
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] Too Many Lists?
Greetings, I've been happily converting text/aliases based lists to mailman (Tru64 Unix v5.1b, Sendmail 8.13.7, Apache Server version: Apache/2.0.54, Mailman version: 2.1.9) and everything has been working great. I have ~150 lists with ~16,000 addresses distributed among them. Most of the lists are 100 with a few 2000. I find when I add another list things get goofy. I can get to a list's admin page fine but when I click on another link, even a documentation or logout link, I get a web page not found browser message. At this point I cannot even logout from the admin page. When I remove the additional list operation returns to normal. I've checked_perms, restarted apache mailman, and searched the FAQ all with no luck. I seem to be on the border of some system limit. I also copied the installation to a similar, backup system and got the same results. Any ideas? Todd Seeleman I'm happily running 239 Mailman lists, the largest of which has /5/970 at the moment on mailman 2.1.9. //I have previously run mailman lists with 200K addresses on them on earlier versions of Mailman. I've not see this issue. I did have an issue similar to this when my url was not being set successfully and all of the links were trying to go to a non-existent domain./ / -- Anne -- 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] IncomingRunner reached maximum restart
You are correct. This was SuSE Linux 10.1, which appears to be 2.1.7 with a lot of patches. I went ahead and installed 2.1.9 and it seemed to resolve the issue. I'm guessing the problem was RFC-2231 file names that spanned multiple lines. The outbound message had REALLY long file names. Once I installed 2.1.9, the person was able to send the message. Mark Sapiro wrote: Tokio Kikuchi wrote: George Sexton wrote: When the IncomingRunner dies, the new message appears in the qfiles/in folder with an extension of .bak. I've tried deleting and re-creating the list and it still dies. If I remove the .bak message and re-start Mailman, then any queued messages are sent or discarded. I've filed a bug report and a patch in the sourceforge tracker. http://sourceforge.net/tracker/index.php?func=detailaid=1598087group_id=103atid=100103 It may not apply cleanly to the 2.1.7 version but the point is deleting lines starting from 'except...' and to the next 'try:' line. The errorneous messages should be shunted and you can check them in qfiles/shunt directory. Two things: If this is really 2.1.7, it is someones package with 2.1.9 backports, because .bak files in qfiles directories were only implemented in 2.1.9. I disagree with Tokio about how to fix this. I have attached a comment and an alternative patch to Tokio's bug report. -- George Sexton MH Software, Inc. Voice: +1 303 438 9585 URL: http://www.mhsoftware.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] Approve subscription requests via mail
Georg Sauthoff sent the message below at 02:47 11/17/2006: PS: Is it ok, if I submit a subscribtion request for this list to www.gmane.org (a nntp gateway and web-archive of mailinglists)? End original message. - There was a rather drawn out, and sometimes heated discussion about this recently. IIRC, the outcome of that discussion was that the owner and maintainers of this list do not want the content of this list carried on the gmane service at this time. I don't recall exactly the specific reasons for this but a search of this list's archives should turn it up in no time. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- 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] Approve subscription requests via mail
At 11:47 AM +0100 11/17/06, Georg Sauthoff wrote: PS: Is it ok, if I submit a subscribtion request for this list to www.gmane.org (a nntp gateway and web-archive of mailinglists)? Uh, no -- please don't. Please see the archives for the background on this issue. PPS: Perhaps you could remove the direct link to this list from http://www.gnu.org/software/mailman/lists.html (in the left row) - because the list requires subscription. The list does require subscription, but the archives are public. IMO, people should be able to figure out for themselves that they will need to subscribe before posting. But Barry is the one who has the final word on that subject. -- Brad Knowles, [EMAIL PROTECTED] Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. -- 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] IncomingRunner reached maximum restart
Tokio Kikuchi wrote: George Sexton wrote: When the IncomingRunner dies, the new message appears in the qfiles/in folder with an extension of .bak. I've tried deleting and re-creating the list and it still dies. If I remove the .bak message and re-start Mailman, then any queued messages are sent or discarded. I've filed a bug report and a patch in the sourceforge tracker. http://sourceforge.net/tracker/index.php?func=detailaid=1598087group_id=103atid=100103 It may not apply cleanly to the 2.1.7 version but the point is deleting lines starting from 'except...' and to the next 'try:' line. The errorneous messages should be shunted and you can check them in qfiles/shunt directory. Two things: If this is really 2.1.7, it is someones package with 2.1.9 backports, because .bak files in qfiles directories were only implemented in 2.1.9. I disagree with Tokio about how to fix this. I have attached a comment and an alternative patch to Tokio's bug report. -- 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] Approve subscription requests via mail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 17, 2006, at 11:53 AM, Brad Knowles wrote: PPS: Perhaps you could remove the direct link to this list from http://www.gnu.org/software/mailman/lists.html (in the left row) - because the list requires subscription. The list does require subscription, but the archives are public. IMO, people should be able to figure out for themselves that they will need to subscribe before posting. But Barry is the one who has the final word on that subject. I agree with Brad. I'd like to keep the link. I /would/ still like to find a better way for non-subscribers to get help, but I think that's a larger issue than how this list is configured. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRV3zjHEjvBPtnXfVAQJsHwP+PbNEET91ee1iobfNmtQFPMqpXR9wGNUC 5U8QbdPpBaDh545E/RIGR/peKbyEmzidthh0SNXztPd/tKFmuA2i4JMOhO7kfITx 9elSIa+upwWD+hwRwngfCWZzNqmO3ZtyhSi/waCIIgZ2HSC/BkwFGH4F/ysHV6wV vFNiwA92t4c= =nZOa -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] Too Many Lists?
Todd Seeleman wrote: I find when I add another list things get goofy. I can get to a list's admin page fine but when I click on another link, even a documentation or logout link, I get a web page not found browser message. At this point I cannot even logout from the admin page. When I remove the additional list operation returns to normal. Are you saying that lista, listb, etc. all work fine in the admin interface and then you create listz and lista, listb, etc. all start failing and you remove listz and the other lists start working again? What happens to the actual links on the pages? Do they change? What is in the apache logs for these failed attempts? -- 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] IncomingRunner reached maximum restart
George Sexton wrote: I went ahead and installed 2.1.9 and it seemed to resolve the issue. I'm guessing the problem was RFC-2231 file names that spanned multiple lines. The outbound message had REALLY long file names. Once I installed 2.1.9, the person was able to send the message. Yes, 2.1.9 contains email 2.5.8 which fixed some issues with RFC 2231 headers. However, while it appears less urgent in your case, I advise applying my suggested patch from http://sourceforge.net/tracker/index.php?func=detailaid=1598087group_id=103atid=100103 to prevent some other unparseable message from causing the same problem. -- 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] scripts/owners not setting list domain
Peter Radcliffe wrote:
If it shouldn't be necessary then I'm missing something since I can't
get that chunk of code to output the right answer... admittedly my
python is a bit rusty, though.
Try the following tests:
$ bin/withlist -i
No list name supplied.
Python info ...
(InteractiveConsole)
from Mailman import Utils
Utils.get_domain()
(should return 'www.pir.net')
Utils.get_site_email()
(should return '[EMAIL PROTECTED]')
from Mailman import mm_cfg
mm_cfg.VIRTUAL_HOSTS
(should return {'www.pir.net': 'list.pir.net'}
--
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] scripts/owners not setting list domain
Mark Sapiro [EMAIL PROTECTED] probably said:
Try the following tests:
Utils.get_domain()
(should return 'www.pir.net')
Utils.get_site_email()
(should return '[EMAIL PROTECTED]')
mm_cfg.VIRTUAL_HOSTS
(should return {'www.pir.net': 'list.pir.net'}
All return as they should. Even this returns correctly:
from Mailman.Utils import get_domain
mm_cfg.VIRTUAL_HOSTS.get(get_domain(), get_domain())
'list.pir.net'
Now if I back out my patch and retry sending mail to owners it works
just fine.
Makes me really puzzled. My best guess is I changed the mm_cfg.py file
from when I had the bad entries in, post-upgrade, and afterwards only
processes not in the mailman group that couldn't write to
Mailman/mm_cfg.pyc were run until I was done testing... but my MTA is
in mailman group and runs the wrapper as mailman/malman so that
doesn't make much sense.
Very odd. Thanks for the debugging help, though.
P.
--
pir
--
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] scripts/owners not setting list domain
Peter Radcliffe wrote: Makes me really puzzled. Me too. My best guess is I changed the mm_cfg.py file from when I had the bad entries in, post-upgrade, and afterwards only processes not in the mailman group that couldn't write to Mailman/mm_cfg.pyc were run until I was done testing... This wouldn't be the explaination. If the .py is newer than the .pyc, the .py should always be used whether or not the .pyc can be updated. but my MTA is in mailman group and runs the wrapper as mailman/malman so that doesn't make much sense. Very odd. Thanks for the debugging help, though. I'm glad it is working as it should. -- 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] identifying dormant lists
I'm curious on how to tell if lists are inactive or dormant ... I have 200+ lists and would like to get rid of lists that are no longer wanted or utilized. It is a rare user that asks to have something deleted ;) Thanks in advance! Ellen Gurganious Computing Services 910.962.4227 [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] Default options for list
I was setting my system defaults for a new installation of mailman and seem to have run across a stumbling block. I can set the generic_member_moderation to yes, but there doesn't seem to be a way in mm_cfg.py to set default member_moderation_action or default member_moderation_notice...or am I missing something? I don't see any defaults for those in Defaults.py and when I try DEFAULT_MEMBER_MODERATION_ACTION = 1 DEFAULT_MEMBER_MODERATION_NOTICE = You do not have permission to post to this list, Please contact the list owner with any issues it seems to have no effect. How do I set a system default for these? -- Anne -- 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] Difficulties with mailman 2.1.5
Hi, Brad, I've been silent, uncourteously not thanking you for your helpful message, because I wanted to act on your suggestions before replying. I have been in touch with the tech staff at PatriotNet(to whom I'm cc-ing this, and they have responded that they are running Debian, with its well-known system of upgrades, security fixes, etc. I run Debian at home, so I know a little about this. On Sat, Nov 11, 2006 at 08:08:39PM -0600, Brad Knowles wrote: At 3:47 PM -0500 11/11/06, Alan McConnell wrote: 1. It often takes two or more repetitions to log on to the administrative page. I am always careful about typing my password. On first blush, this sounds a lot like the problem discussed in FAQ I now can log in without repeating the process. 2. When I go to the Membership Management/mass subscription page to subscribe a new member, this subscription often does not take. I get a nice screen saying X is successfully . . . . My guess is that this is related to issue #1 above, and if you can get that problem fixed then this one seems that it would be likely to also go away. I haven't added anyone recently. I'll monitor this. 3. Worst of all: I want messages sent by our members to be sent also to the member that sent them. This is not at present occurring. I have _not_ checked the button in . . . I'm not sure what to tell you. You've checked the two things I know of to check, and yet you're seeing precisely the kind of behaviour we would expect when these features are used. I couldn't test this, but a PatriotNet sysadmin checked this; he sent a TEST message, and assures me that he got it back. One thing that would help is if your ISP was running the latest version of Mailman -- we're now on version 2.1.9. There have been a Yes. My question, addressed to you, or to any Debian experts here is: using the Debian upgrade/update system, will the improvements of 2.1.9 by now have propagated to the PatriotNet system? Debian puts a big focus on security. But, as I indicated above, it does seem that the system is better now. (However the bottom LH corner of the admin screens still say version 2.1.5 ! ? ) Any comments from you or other experts would be much appreciated. Again, thanks for your help! Alan -- Alan McConnell : http://patriot.net/users/alan The intelligence and facts were being fixed around the policy. Impeachment proceedings should be started immediately. -- 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 issue downloading full raw archive
Jared Nyland wrote: Great Thanks for the help on this issue. I have added that code to my private.py and now I am getting this error. Traceback: Traceback (most recent call last): File /usr/lib/mailman/scripts/driver, line 88, in run_main sys.__stdout__.write(tempstdout.getvalue()) MemoryError You can try the following change to /usr/lib/mailman/scripts/driver. locate the code try: try: sys.stderr = logger sys.stdout = tempstdout main() sys.__stdout__.write(tempstdout.getvalue()) finally: sys.stderr = sys.__stderr__ sys.stdout = sys.__stdout__ and change it to try: try: sys.stderr = logger sys.stdout = tempstdout main() tempstdout.seek(0) line = tempstdout.readline() while line: sys.__stdout__.write(line) line = tempstdout.readline() finally: sys.stderr = sys.__stderr__ sys.stdout = sys.__stdout__ This and the prior change are really only a stopgap. I now see the issue is twofold. The output of the CGI is written to an in-memory string and then ultimately copied to the real stdout. The base code actually copies things in a way that at times there are two full copies of the file in memory at once. These changes do the copy a line at a time so that there is only one file copy in memory plus a line which should avoid the problem for now, but eventually, the file will grow large enough so that even one copy won't fit in memory, but before that, perhaps the browsers receiving this file will choke. -- 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] identifying dormant lists
Gurganious, Ellen wrote: I'm curious on how to tell if lists are inactive or dormant ... I have 200+ lists and would like to get rid of lists that are no longer wanted or utilized. It is a rare user that asks to have something deleted ;) If the lists have archives, look at them. If there are no archives, you can use bin/withlist to look at the list attribute last_post_time. e.g. $ bin/withlist listname Loading list listname (unlocked) The variable `m' is the listname MailList instance import time time.ctime(m.last_post_time) 'Thu Sep 28 09:44:31 2006' (control-D entered here) Finalizing $ Or create a script to print the list name and last_post_time for all lists or some subset. -- 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] Default options for list
Anne Ramey wrote: I was setting my system defaults for a new installation of mailman and seem to have run across a stumbling block. I can set the generic_member_moderation to yes, but there doesn't seem to be a way in mm_cfg.py to set default member_moderation_action or default member_moderation_notice...or am I missing something? You can set the default value for default_member_moderation for new lists via DEFAULT_DEFAULT_MEMBER_MODERATION The default values for member_moderation_action and member_moderation_notice are hard coded in Mailman/MailList.py to 'Hold' and empty respectively. I don't see any defaults for those in Defaults.py and when I try DEFAULT_MEMBER_MODERATION_ACTION = 1 DEFAULT_MEMBER_MODERATION_NOTICE = You do not have permission to post to this list, Please contact the list owner with any issues it seems to have no effect. You can't add any setting to mm_cfg.py that isn't in Defaults.py. Mailman won't see it. If it did look for it and it wasn't defined in Defaults.py, it would produce an error. How do I set a system default for these? You could change Mailman/MailList.py to use mm_cfg.DEFAULT_MEMBER_MODERATION_ACTION and mm_cfg.DEFAULT_MEMBER_MODERATION_NOTICE instead of the current hard coded 0 and '', and then you could put them in mm_cfg.py. Or you could put the two lines member_moderation_action = 1 member_moderation_notice = You do not have permission to post to this list, Please contact the list owner with any issues in a file and run bin/config_list with this file as input on the new lists. -- 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 issue downloading full raw archive
That did the trick for this issue Thanks again Jared On 11/17/06, Mark Sapiro [EMAIL PROTECTED] wrote: Jared Nyland wrote: Great Thanks for the help on this issue. I have added that code to my private.py and now I am getting this error. Traceback: Traceback (most recent call last): File /usr/lib/mailman/scripts/driver, line 88, in run_main sys.__stdout__.write(tempstdout.getvalue()) MemoryError You can try the following change to /usr/lib/mailman/scripts/driver. locate the code try: try: sys.stderr = logger sys.stdout = tempstdout main() sys.__stdout__.write(tempstdout.getvalue()) finally: sys.stderr = sys.__stderr__ sys.stdout = sys.__stdout__ and change it to try: try: sys.stderr = logger sys.stdout = tempstdout main() tempstdout.seek(0) line = tempstdout.readline() while line: sys.__stdout__.write(line) line = tempstdout.readline() finally: sys.stderr = sys.__stderr__ sys.stdout = sys.__stdout__ This and the prior change are really only a stopgap. I now see the issue is twofold. The output of the CGI is written to an in-memory string and then ultimately copied to the real stdout. The base code actually copies things in a way that at times there are two full copies of the file in memory at once. These changes do the copy a line at a time so that there is only one file copy in memory plus a line which should avoid the problem for now, but eventually, the file will grow large enough so that even one copy won't fit in memory, but before that, perhaps the browsers receiving this file will choke. -- 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] Rate limit by domain/mx
I know this isn't really a mailman issue, but I was just curious, those that need rate limiting, what are you using? I really need this set up, we have one list in paticular that has almost 1500 AOL subscribers, which is an announce only list, but the owner sends out about 6 announcements at the same time flooding AOL with 9,000 messages, and as fast as our MTA can handle. Right now we are using sendmail 8.13.8. Thanks -Rob -- 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: how to display subject and date for archives when listingof archives?
Jana Nguyen wrote: How do I get the archive list to display the subject, author and date when I go to list archives? For example: ArchiveView by:Downloadable version 11 May 2006: [ Next Meeting for Workshop] [Jana Nguyen] [11 May 2006] [ Text 1 KB ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060511.txt The default that comes with mailman display the heading and we don't want this (see below). You can get more information about this list http://birn-holly.ucsd.edu/mailman/listinfo/bcc-internal. ArchiveView by:Downloadable version 11 May 2006: [ Thread ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060511/thread.html [ Subject ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060511/subject.html [ Author ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060511/author.html [ Date ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060511/date.html [ Text 1 KB ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060511.txt 5 May 2006:[ Thread ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060505/thread.html [ Subject ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060505/subject.html [ Author ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060505/author.html [ Date ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060505/date.html [ Text 438 bytes ] http://birn-holly.ucsd.edu/mailman/private/bcc-internal/20060505.txt This got lost in my inbox, partly because I don't understand the question. It appears from the examples above that you start new archive volumes weekly. The first example is a particular weeks index page and the second example is the overall table of contents. I don't know what you are asking. Are you asking how to get the message date on a particular weeks index page, or how to skip the overall table of contents and have one big index page, or something else? -- 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] Difficulties with mailman 2.1.5
At 3:10 PM -0500 11/17/06, Alan McConnell wrote: Hi, Brad, I've been silent, uncourteously not thanking you for your helpful message, because I wanted to act on your suggestions before replying. Not a problem. I appreciate your attention to detail. I have been in touch with the tech staff at PatriotNet(to whom I'm cc-ing this, and they have responded that they are running Debian, with its well-known system of upgrades, security fixes, etc. I run Debian at home, so I know a little about this. While I don't consider myself a Linux person, I have some familiarity with Debian, and I understand the desire to have software fully checked out before upgrading as well as wanting to have the upgrade process be as bullet-proof as possible. I was the Sr. Internet Mail Administrator for AOL for a couple of years, and I know what it's like to manage hundreds of systems with a small staff. I only managed our small piece of the overall system, but I worked closely with the configuration management guys, so I understand what that's like. On first blush, this sounds a lot like the problem discussed in FAQ I now can log in without repeating the process. Cool. That's good to hear. My guess is that this is related to issue #1 above, and if you can get that problem fixed then this one seems that it would be likely to also go away. I haven't added anyone recently. I'll monitor this. If you have any further problems, please let us know. One thing that would help is if your ISP was running the latest version of Mailman -- we're now on version 2.1.9. There have been a Yes. My question, addressed to you, or to any Debian experts here is: using the Debian upgrade/update system, will the improvements of 2.1.9 by now have propagated to the PatriotNet system? Debian puts a big focus on security. But, as I indicated above, it does seem that the system is better now. (However the bottom LH corner of the admin screens still say version 2.1.5 ! ? ) I'm most certainly not a Debian expert, so in that respect I'm not sure I can answer this question. I do know that there have been some issues in the past with getting the updates pushed out to some sites running Debian, especially if they're running older Debian releases for which new packages are not being built. Moreover, Debian has made a number of changes to the code they ship out with our name on it, and we can't be responsible for them. This process is getting better, and we have recently started having the Debian package maintainers contributing the relevant portions of their changes back to us, for future inclusion in our code base. There will be at least some convergence, at least in the future. In the meanwhile, if you're still having issues, then I don't see many alternatives. You can either choose to run the Debian package version of Mailman (in which case we're not going to be able to help you with certain classes of problems), or you can run the version installed directly from our source tarballs. If you do choose to stick with the Debian package version, then your first level of support should be from the Debian community and especially the Debian package maintainer(s). If you're having certain problems and they can prove that those problems are not a result of the code changes they've made, then we might be able to help. But the only version of Mailman that we can officially support is the version we provide in our tarballs from our official sites. We can make a best effort to try to support other versions of Mailman as modified by other organizations, but there's going to be a limit to what we can do in that regard. I'm sorry I don't have a better answer for you. -- Brad Knowles, [EMAIL PROTECTED] Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. -- 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
