Mailman 3 December 2004 - Mailman-Developers

salam
by VAEZ(daneshjooye sharif) 01 Jan '05

01 Jan '05

momkene ye nafar az iranihaa be man komak kone? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 1

hi all
by VAEZ(daneshjooye sharif) 01 Jan '05

01 Jan '05

thank you for suffering --------------------------------- Do you Yahoo!? Send a seasonal email greeting and help others. Do good.

1 0

hi all
by VAEZ(daneshjooye sharif) 01 Jan '05

01 Jan '05

thank you for suffering. --------------------------------- Do you Yahoo!? The all-new My Yahoo! � What will yours do?

1 0

Excessive unsubscriptions
by Luke Hilton 01 Jan '05

01 Jan '05

Hi All, I am very new to Linux, but will tell you what I can. I am trying to diagnose a problem on a. Linux Redhat server Mailman version 2.1.4 Spamassassin Squirrelmail The particular mailing list has over 20,000 members. The list is being sent to on a on a monthly basis one way. A mass mail (80k - html) was sent out to the 20,000 members approximately 2 weeks ago. All seemed to go fine. I was alerted that the server performance had dropped dramatically so I checked the obvious and then bounced it. The following day I received approx. 3000 unsubscribe notices. This is highly irregular as in the past only a few unsubscribe notices come in per month. I checked these entries in the Membership list and they are still there, but the 'nomail' box is now checked and reason 'B' displayed. A colleague of mine restarted the server again yesterday and I have just received another huge amount of unsubscribe notices again. I followed the following faq yesterday in an attempt to diagnose. http://www.python.org/cgi-bin/faqw-mm.py?req=show <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.014.htp> &file=faq03.014.htp 1. Permissions seemed fine 2. Cron daemon was running 3. Aliases are in /etc/aliases + did a 'newaliases' 4. I checked the mailman/locks and there are a number of locks from around the time the list was sent 5. I checked to see if the processes are still around for the above locks and they are Should I delete the locks? If so how do I do this safely? Has anyone heard of this type of problem happening before? I want to make sure there are no pending mailman tasks to complete and that if another restart occurs I won't get bombarded by another wad of unsubscribes. I have a copy of the membership list and was thinking I could create 3 new mailing lists and divide the 20000 people over the 4 lists. Is this worth it? Should mailman be able to send 20,000 mails easily? Any help with this would be fantastic. Luke

3 6

new feature request (was: Re: setting a list for no daily reminders?)
by Mark 01 Jan '05

01 Jan '05

Thanks to everyone who responded. Please forgive this crosspost to the developers group. Seeing that there is no way to do this without changing the code, and that many Mailman users are not Python programmers or do not have the permission to make such changes on the server they are using, I think it would be best if this was made an option that could be set through the web interface for each list. That way administrators could choose immediate notifications, daily summaries, or both. THANX!! :) On 11/20/04, Mark Sapiro put forth: >Mark wrote: > > > >I am running a list set to immediately send administrative requests > >(admin_immed_notify set to yes), but I am getting daily notices as > >well. I don't want to receive daily notices. The immediate notices > >are sufficient. Nor do I see the logic in filling my inbox with > >daily notices when I'm not around or haven't had a chance to process > >the immediate notices that are already sitting there. > > > >Is there any way to change this?? > >You could delete the checkdbs entry from crontab, but this would affect >all lists and also would have the side effect of never clearing stale >entries from hold_and_cmd_autoresponses[] (I don't think this is >serious because I don't think there is ever more than one entry per >user - stale entries get "reused"). > >The only other way and the only way to do it per list is to change the >code in checkdbs.

3 5

Re: [Mailman-Developers] Need to reset passwords en masse, pls help
by Barry Warsaw 31 Dec '04

31 Dec '04

On Thu, 2004-12-30 at 22:04, hhart(a)blue.weeg.uiowa.edu wrote: > Thanks for cc'ing me on this, Hugh. Does this mean all those subscribed ot > the recount lsits will get new passwords automatically sent to them? You'll have to run cron/mailpasswds manually to get the new passwords sent out. This is the script that normally runs once a month to send out password reminders. You might want to edit templates/en/cronpass.txt to some more relevant message before you run cron/mailpasswds manually. -Barry

2 2

Need to reset passwords en masse, pls help
by Hugh Esco 31 Dec '04

31 Dec '04

Hey folks: I and a cohort wrote a script to facilitate list subscriptions to multiple lists provided by our campaign. (for details, check out: http://cgi.votecobb.org/supporters.cgi?function=subscribe). As a part of this, my friend developed a perl module which he describes in the perldoc notes saying: "The MailingList class is not yet a generic mailing-list subscription engine, but hopefully it will move in that direction." It provides an object oriented methods to subscribe to lists for not just mailman, but also majordomo, yahoo, sympa, etc. After collecting the data from our form, the script uses wget to post web form submissions against the mailman subscription forms, which generates a confirmation message sent back to the user. The script generates a random password for the form, using a perl script, pw (copyright by University of Illinois) which generates output looking like: Of/QiBDZ OfUmuOXfjg2to Those first eight letters are the password. The rest of the string after the space is an encrypted hash of those first eight characters. I wrote a subroutine to generate the password, using this pw script, which truncates the output using a substring function to pull those first eight characters. However, instead of calling the subroutine which returns the eight characters, I made a shell call directly to the pw script and used the password+hash string instead. That setup was used to subscribe over 3,000 folks to various lists. Now that space in the middle is giving me fits. No one can log in or change their password to something that will permit a login. I have command line access as root in a BSD jail to this installation. I need to know: is there anyway I can automate the resetting of every password for every subscriber on this installation, with the new password sent out in an email to the subscriber, and causing as little confusion and disruption as possible? All help is appreciated. Thanks, -- Hugh Esco

3 3

Mailman contractors
by Barry Warsaw 28 Dec '04

28 Dec '04

From time to time I get requests for Mailman installation or customization help, often for compensation. This is not something I do so I usually have to turn people down cold, or tell them to email these two mailing lists. However, such requests are coming in more often these days, so I wonder if it makes sense to try to collect a list of people willing to provide Mailman services. I would not be willing to recommend anyone specifically, but I would be happy to point such requests at say, a wiki page where people can self-register. What do you think? We can either use the FAQ or we can use the Python.org wiki. I'd rather not be in the loop so I don't want to use the static list.org pages. I think we as a community can self-regulate this list. -Barry

2 1

Custom Welcome Message
by Grant Bowman 28 Dec '04

28 Dec '04

Hello, I'm looking for feedback about the attached one line patch, It uses existing capabilities to allow the editing of subscribeack.txt. If this is the right approach I would be happy to follow up with additional patches to help support this capability. The first thing that comes to mind adjusting the text of the HTML selection page. If this isn't the right approach to provide this capability then what are the alternatives? Thanks, -- -- Grant Bowman <grantbow(a)grantbow.com> --- Mailman/Cgi/edithtml.py.orig 2001-11-30 00:00:18.000000000 -0800 +++ Mailman/Cgi/edithtml.py 2004-12-10 12:09:31.000000000 -0800 @@ -42,6 +42,7 @@ template_data = ( ('listinfo.html', _('General list information page')), ('subscribe.html', _('Subscribe results page')), + ('subscribeack.txt', _('Welcome email text file')), ('options.html', _('User specific options page')), )

2 2

Handling potential security bugs
by Florian Weimer 28 Dec '04

28 Dec '04

Hi, where should I submit security bugs? There are two more in my queue (minor ones, admittedly, as no server-side code execution is involved). Shall I post them to this mailing list, and notify full-disclosure &c at the same time? (Terri will prove that these two bugs are non-issues as well, and propose to defer fixing them to 3.0 anyway, so I doubt that I private discussion would get us anywhere.) Florian

3 4