Mailman 3 February 2005 - Mailman-Developers

Re: Please confirm your message
by Ian Eiloart 11 Feb '05

11 Feb '05

--On February 11, 2005 05:02:00 -0500 Bob Puff <bob(a)nleaudio.com> wrote: > Hello iane(a)sussex.ac.uk, > > ** IMPORTANT! Please Read! ** > In an effort to reduce spam, a message filtering service called TMDA has > been implemented on this mailbox. Bob, Can you please remove your TMDA protected email address from this list. Imagine if everyone on a thousand member list used TMDA. Every time you posted a message, you'd get a thousand requests to click on a link. For the list to work properly, a million clicks would be required, followed by another two thousand for every new member. > The purpose of this message is to verify that you, a live human, did > indeed sent a message (shown below) to this mailbox. > > It is IMPORTANT that you do one of the following two things: > > > 1. Simply reply to THIS message (you don't need to type anything, just > send a blank message), or > > 2. Click on this link: > http://nleaudio.com/cgi-bin/tmda.cgi?501.1108116120.3176.21a674 > > > After doing so, your messages will go through automatically, and you will > not see this message again. If you do not reply to this email within > three weeks, your original message may be lost. > > Thank you for your patience. This one small step saves this user from a > ton of spam. > -- Ian Eiloart Servers Team Sussex University ITS

1 0

www.python.org back online...
by Brad Knowles 11 Feb '05

11 Feb '05

Folks, The power problem has been resolved. It turns out that the machine itself was not down, but the switch it was connected to was. So, as far as it was concerned, it was the rest of the world that went away. ;) Anyway, www.python.org now points back to the original server, and everything should be as it was. Sorry for any confusion that may have been caused. -- Brad Knowles <brad(a)python.org> Python.org Postmaster Team

1 0

Website www.python.org down...
by Brad Knowles 10 Feb '05

10 Feb '05

Folks, Just to let you know, the machine that normally provides service for www.python.org is currently down. The facility that provides the co-location is having power problems, and they are working on solving it. We have temporarily moved the www.python.org hostname to a different machine, which does not include any of the original content from www.python.org, and ftp.python.org and other non-mail or mailing list related services are still down. However, the temporary home for www.python.org does have a list of known mirrors, so you should hopefully be able to access the content you need from one of them. I'll post more information as I get it. -- Brad Knowles, <brad(a)stop.mail-abuse.org> "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See <http://www.sage.org/> for more info.

1 0

Re: [Mailman-Developers] mailman email harvester
by Thien Vu 10 Feb '05

10 Feb '05

[whoops, meant to send to the whole list] def roster_privatize(mlist): mlist.private_roster = 1 m.Save() m.Unlock() Put that into your mailman/bin/roster_privatize.py and then run withlist -a -l -r roster_privatize Yeah I haven't tested that code but that's the rough idea. Take a look at setting mm_cfg.DEFAULT_PRIVATE_ROSTER also. Thien On Thu, 10 Feb 2005 19:08:51 +0100, Brad Knowles <brad(a)stop.mail-abuse.org> wrote: > At 11:40 AM -0500 2005-02-10, Tobias Eigen wrote: > > > Is there a way to change the setting to restrict access to the roster for > > all lists, globally? > > That should be possible to do using "withlist". However, I don't > know the specifics of how to do that. > > -- > Brad Knowles, <brad(a)stop.mail-abuse.org> > > "Those who would give up essential Liberty, to purchase a little > temporary Safety, deserve neither Liberty nor Safety." > > -- Benjamin Franklin (1706-1790), reply of the Pennsylvania > Assembly to the Governor, November 11, 1755 > > SAGE member since 1995. See <http://www.sage.org/> for more info. > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers > 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-developers/thien.vu%40gmail.… >

1 0

Critical security update for Mailman 2.1.5 and earlier
by Barry Warsaw 10 Feb '05

10 Feb '05

There is a critical security flaw in Mailman 2.1.5 and earlier Mailman 2.1 versions which can allow remote attackers to gain access to member passwords under certain conditions. The extent of the vulnerability depends on what version of Apache you are running, and (possibly) how you have configured your web server. However, the flaw is in Mailman and has been fix in CVS and will be included in the Mailman 2.1.6 release. This issue has been assigned CVE number CAN-2005-0202. We currently believe that Apache 2.0 sites are not vulnerable, and that many if not most Apache 1.3 sites are. In any event, the safest approach is to assume the worst and take the remediation steps indicated below as soon as possible. The quickest fix is to remove the /usr/local/mailman/cgi-bin/private executable. This will disable all access to all private archives on your system. While this is the quickest and easiest way to close the hole, it will also break all your private archives. If all the lists on your site only run public archives, this won't matter to you. Until Mailman 2.1.6 is released, the longer term fix is to apply this patch: http://www.list.org/CAN-2005-0202.txt For additional piece of mind, it is recommended that you regenerate your member passwords. Instructions on how to do this, and more information about this vulnerability are available here: http://www.list.org/security.html My thanks to Tokio Kikuchi, Mark J Cox, and the folks on vendor-sec. This issue was found by Marcus Meissner. -Barry

3 3

Fwd: [SourceForge.net Release] m2f : m2f
by Tobias Eigen 09 Feb '05

09 Feb '05

fyi - maybe I was wrong.. release candidate of m2f has been released today. Begin forwarded message: > From: "SourceForge.net" <noreply(a)sourceforge.net> > Date: February 9, 2005 8:22:13 PM EST > To: noreply(a)sourceforge.net > Subject: [SourceForge.net Release] m2f : m2f > > Project: mail2forum (m2f) > Package: m2f > Date : 2005-02-09 22:22 > > Project "mail2forum" ('m2f') has released the new version of package > 'm2f'. > You can download it from SourceForge.net by following this link: > <https://sourceforge.net/project/showfiles.php? > group_id=68964&release_id=303790> > or browse Release Notes and ChangeLog by visiting this link: > <https://sourceforge.net/project/shownotes.php?release_id=303790> > > You receive this email because you requested to be notified when new > versions > of this package were released. If you don't wish to be notified in the > future, > please login to SourceForge.net and click this link: > <https://sourceforge.net/project/filemodule_unmonitor.php? > filemodule_id=67748> > If you lost your SourceForge.net login name or password, refer to this > document: > <https://sourceforge.net/docman/display_doc.php?docid=760&group_id=1> > > Note that you may receive this message indirectly via one of your > mailing list > subscriptions. Please review message headers before reporting > unsolicited > mailings. > -- Tobias Eigen Executive Director Kabissa - Space for Change in Africa http://www.kabissa.org * Kabissa's vision is for a socially, economically, politically, and environmentally vibrant Africa, supported by a strong network of effective civil society organizations. *

1 0

Re: [Mailman-Users] Subject_prefix doesn't get added for posts from one domain - Solved
by Chris Malatesta 09 Feb '05

09 Feb '05

So here is the answer, The domain that I used to setup the mailman server used to be managed by the domain/server that was sending the problem posts. They still had this domain in the virtualdomain file for their qmail server. Now why the email was even getting out of their qmail server and actually posted to the list is beyond me as these are 2 different servers on different networks, but just removing this domain from virtualdomains solved the problem. Thanks, Chris On 2/7/05 11:51 AM, "Mark Sapiro" <msapiro(a)value.net> wrote: > Chris Malatesta wrote: > >> So here is the issue, posts from this one domain don't get mailman header >> information added to the email, although they get posted to the list. >> >> What would cause a post to go to the list and not get header info and the >> Subject_prefix added to that post? > > The message is not being processed by CookHeaders which is the module > that adds the subject prefix and headers X-BeenThere, > X-Mailman-Version, Precedence and maybe others depending on list > options. > > CookHeaders must be in the list pipeline since it is there for messages > from other domains. I can't see how it would be avoided for just the > messages from this one domain. Presumably the rest of the pipline is > processed since without CalcRecips and ToOutgoing or at least > ToDigest, the message wouldn't be sent to anyone. > > This is really puzzling. > > -- > Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >

1 0

Fwd: Volunteer sought to code Mailman/Plesk integration script for use by African organizations
by Tobias Eigen 08 Feb '05

08 Feb '05

Dear Mailman developers - Below is a message I attempted to post to the Python jobs board, but which never appeared there. As it is directly relevant to Mailman, I hope you don't mind that I also share it with you all directly. I am quite keen on solving this problem as soon as possible. Please let me know if you're interested and I'll give you the gory details. Any useful scripts or lessons learned shared back to the community, of course. Cheers, Tobias +1-202-265-6116 -- Tobias Eigen Executive Director Kabissa - Space for Change in Africa http://www.kabissa.org * Kabissa's vision is for a socially, economically, politically, and environmentally vibrant Africa, supported by a strong network of effective civil society organizations. * Begin forwarded message: > From: Tobias Eigen <tobias(a)kabissa.org> > Date: January 12, 2005 6:21:46 AM EST > To: jobs(a)python.org > Subject: Volunteer sought to code Mailman/Plesk integration script for > use by African organizations > > `Kabissa - Space for Change in Africa <http://www.kabissa.org>`_ > (Washington DC, USA) > =================================================================== > > **Job Description**: Volunteer sought to code Mailman/Plesk > integration script for use by African organizations > > Kabissa helps African organizations to put the Internet to > work for the people they serve. A key aspect of this is > maintaining a server which our member organizations in > Africa use to host Websites, mailboxes - and mailing lists. > > We need one-off help from a Linux/open source coder, > which might turn into more regular volunteering if there is > interest, to write code that integrates our existing > Mailman (http://www.list.org) installation with the new > version of Plesk (http://www.plesk.com) server > administration tool. The goal is to empower our members > to use Plesk to create, manage and then delete their own > lists autonomously. > > We know it is possible and have tested it on a manual > basis on specific lists, but need some additional coding > done to make it work on a turnkey basis for all lists on the > server. > > Any work done to be released (with credit where due) to > the open source community. > > You will need to have your own testing server. > > **What Python is used for**: Mailman. The integration script could be > a python script but doesn't need to be. > > * **Contact**: Tobias Eigen > * **E-mail contact**: tobias(a)kabissa.org > * **Other Contact Info**: +1-202-265-6116 > * **Web**: http://www.kabissa.org > >

3 4

MACE, Internet2, mailing lists etc
by J C Lawrence 07 Feb '05

07 Feb '05

Middleware-Enabled Mailing List Working Group (MACE-MLIST): http://middleware.internet2.edu/mlist/ --<cut>-- Charter The I2 MACE-MLIST working group intends to address the following sets of issues: - The WG will research the issues surrounding middleware-enablement of mailing list services. Where possible, the WG will document how to perform this integration and provide forums where people can learn and help each other in addressing these integration issues within campus contexts. Where appropriate, the WG will collaborate with open source communities to consider needed modifications or other techniques for achieving better integration with the enterprise/federation. - The WG will consider and implement a survey of current university mailing list users to identify favorite features, needed improvements, and notable warts. We will map existing mailing list capabilities to a matrix of available functionality. - The WG will include persons who are actively working on integration with the enterprise/federation using non-proprietary technology; experiences will be shared regarding application designs best supporting infrastructure. Working group members will test-drive pilot/prototype solutions. Outcomes / Deliverables 1. Survey results, identifying best features, absent features, and desired improvements from users of mailing list software, along with a mapping of this feature set to existing mailing list software. 2. A simple model of mailing list management software operations, with middleware enablement points identified. 3. At least one open-source list software prototype (Sympa is a likely candidate) using federated authN/Z. 4. Documentation describing methods for modifying open source list software for use in federated environments. --<cut>-- -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Subject_prefix doesn't get added for posts from one domain
by Chris Malatesta 07 Feb '05

07 Feb '05

I posted this to the mailman-users list and no one seemed to have any idea, so I thought I'd give you all a shot. Appreciate anything that you come up with... Chris ------ Forwarded Message > From: Chris Malatesta <chris(a)digital-waves.net> > Date: Fri, 04 Feb 2005 20:17:03 -0800 > To: "mailman-users(a)python.org" <mailman-users(a)python.org> > Subject: Subject_prefix doesn't get added for posts from one domain > > Hopefully someone has an answer for this one, I haven¹t been able to find it > anywhere... > > I have setup a new mailman server for a client (RHE3/netmail 1.0.5/Mailman > 2.1.5) when people from one domain running qmail post to a newly created list > with the default options, the subject_prefix doesn¹t get added to the subject > line, but it does for everyone else??? > > The only thing I can think could be different is the header of the email, > There are some differences with mail from this domain, but I don¹t believe > they are necessarily wrong, but it is the only thing I can see would be different... > > Any ideas would be appreciated. > > Chris > > > I.e. Here is a header from this domain, with the actual address names and ip's > changed. > > Received: from domain.com ([55.255.255.255]) by otherdomain.com with Microsoft > SMTPSVC(6.0.3790.211); > Wed, 2 Feb 2005 17:30:07 -0800 > Received: (qmail 508 invoked by uid 14282); 3 Feb 2005 01:33:53 -0000 > Received: from user(a)domain.com by domain.com by uid 505 with > qmail-scanner-1.22 > (avp: 5.0.2.0. f-prot: 3.12/. Clear:RC:1(10.250.100.83):. > Processed in 0.557572 secs); 03 Feb 2005 01:33:53 -0000 > Received: from in.domain.com (HELO usersname) (10.250.100.83) > by 0 with SMTP; 3 Feb 2005 01:33:53 -0000 > Reply-To: <user(a)domain.com> > From: "First Last" <user(a)domain.com> > To: "'First Last'" <sender(a)domain.com> > Subject: Same Problem > Date: Wed, 2 Feb 2005 17:34:44 -0800 > Organization: Company Name > > Message-ID: <012b01c50990$8cf42bc0$a764fa0a@usersname> > > MIME-Version: 1.0 > Content-Type: multipart/mixed; > boundary="----=_NextPart_000_012C_01C5094D.7ED0EBC0" > X-Priority: 3 (Normal) > X-MSMail-Priority: Normal > X-Mailer: Microsoft Outlook, Build 10.0.2627 > Importance: Normal > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 > X-Bogosity: No, tests=bogofilter, spamicity=0.500000, version=0.17.5 > Return-Path: user(a)domain.com > X-OriginalArrivalTime: 03 Feb 2005 01:30:08.0062 (UTC) > FILETIME=[E53905E0:01C5098F] > ------ End of Forwarded Message

1 0