Re: [Mailman-Developers] RELEASED: GNU Mailman (core) 3.0b5
On Wed, Jan 7, 2015 at 11:37 PM, Barry Warsaw wrote: I've heard that Debian is working on Ubuntu-like PPAs. That would seem like a fruitful way of providing the entire stack for older distros. What about just a backport of Python 3.4 (and any future mailman3 package)? http://backports.debian.org/ -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman (core) 3.0b5
On Wed, Jan 7, 2015 at 1:48 AM, Tanstaafl wrote: So, wheezy admins will be left out in the cold. I expect Debian jessie will become Debian stable soon enough. -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman (core) 3.0b5
On Wed, Jan 7, 2015 at 3:09 PM, Tanstaafl wrote: Not for those wanting to avoid systemd. systemd is optional and easy to avoid in Debian. -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Deb packages for Mailman 3 suite, beta 1 preview
On Tue, Sep 16, 2014 at 8:08 AM, Chuck Peters wrote: Has anyone been working on Debian/Ubuntu packages? From our discussions at DebConf14 it sounds like Barry Warsaw is working on this but I don't think it will be ready in time. I also think it is far too early to package mailman3 in a stable distro release at this time. -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Git mirror for mailman
git itself has git-remote-bzr that works well so I don't think this is needed, git users can just checkout direct from bzr to git. The only issue I can find with it is that push to launchpad doesn't appear to work right now. https://bugs.debian.org/714038 -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] GSOC Project idea: OpenPGP integration
On Sun, Apr 7, 2013 at 5:19 AM, Abhilash Raj wrote: I am a undergrad student interested in OpenPGP integration in mailman as a GSOC project this summer. Here is a semi-related idea; use OpenPGP instead of passwords for authentication to the web interface, possibly using monkeysphere: http://web.monkeysphere.info/ -- bye, pabs http://wiki.debian.org/PaulWise ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] anti-spam filter
On Mon, Apr 15, 2013 at 1:39 PM, Pratik Sarkar wrote: Is the anti-spam/abuse filter still being seriously considered as a gsoc project this year? One really useful thing to have would be removal of spam from archives. Here are some examples of how it has been done before: The Debian lists server isn't based on mailman but has a collaborative method of removing spam from the archive: https://wiki.debian.org/Teams/ListMaster/ListArchiveSpam Indymedia implemented a mailman 2 patch for this a number of years ago: https://lists.indymedia.org/patches/imc-10-mmid_hide_posts.patch -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] anti-spam filter
On Mon, Apr 15, 2013 at 4:55 PM, Stephen J. Turnbull wrote: That's a great idea (and a great example of why I don't think spam-filtering technology should be embedded in a Mailman handler! :-) I think you might not be thinking expansively enough, it allows more flexibility to do spam filtering in multiple places. Different lists will have different definitions of what is an unwanted message. On the Debian lists we don't want anything about shares, liquidity and financial instruments, but some economists will find messages about source code and copyright law unwanted on their lists. A list for pharmacists will probably want to accept messages containing usually-spammy keywords. A generic mailing-list-hoster hosting all 3 of those will want to allow most mail and add per-list filters. -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] A feature I'd like to emphasize for GSoC ...
On Tue, Apr 16, 2013 at 4:08 AM, Florian Fuchs wrote: This could be something for a HTML(5)/JS/CSS savvy person (to make it *really* convenient). I'm thinking scrollable log views, that interactively append/prepend entries to the view, depending on your position in the log file. Or commenting on log snippets and saving them for further review. As long these are based on progressive enhancement, sounds good. The web interface should continue to work for browsers that don't support CSS, JavaScript, AJAX, images, Flash, SVG or any of the other stuff that was added to HTML. https://en.wikipedia.org/wiki/Progressive_enhancement -- bye, pabs ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Hi from a student interested in a GSoC project
In addition to Augeas, I would encourage you to look at Config::Model. I think you will need the pair of them to do upgrades. There are a number of blog posts on Planet Debian about it and I'm sure the author would be willing to help out. http://planet-search.debian.org/cgi-bin/search.cgi?terms=Config::Model -- bye, pabs http://wiki.debian.org/PaulWise ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] GSOC Project idea: OpenPGP integration
On Sun, Apr 7, 2013 at 5:19 AM, Abhilash Raj wrote: I am a undergrad student interested in OpenPGP integration in mailman as a GSOC project this summer. Cool! I'm not sure about the scope of your project but you may want to review some prior efforts: http://schleuder2.nadir.org/ http://www.synacklabs.net/projects/crypt-ml/ My pet favourite feature from the lurker mail archiver is showing photos from OpenPGP keys in the archive pages. -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] MM3: list disabling/enabling?
On Mon, Jul 11, 2011 at 5:40 PM, Barry Warsaw wrote: It sounds like a lot, but I'd think it's only a day or two of work, and I'm happy to answer questions, review code, etc. I would like to get the design right first, after reading the full thread a couple of times, some thoughts: By bounce I meant SMTP-time rejection, sounds like the LMTP stuff provides that (and mailman 2 doesn't use that IIRC). Temporarily failing lists were not an objective. The design of list objects seems to be heavily similar to how the UI is in mailman 2, I think it should be much more generic. For example: In the web UI turning on emergency moderation should set the first item in the receive pipeline to a hold() function. Disabling a list would set the first item in the receive pipeline to reject_disabled, set the first item in the subscription pipeline to reject_disabled, set the first item in the settings pipeline to admin_read_only etc. List objects should be flexible to support different kinds of lists, but the UI should hide most of that behind simple labels like retired list, public list, private list and the emergency moderation button. PS: Is there a Mailman UI yet? The link on the Mailman branches wiki page points to one with only one commit in it and no working code. PPS: It seems Mailman 3 will be quite different to Mailman 2 so I'm thinking configuration filenames, data directories etc should be named mailman3 instead of mailman. -- bye, pabs ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] MM3: list disabling/enabling?
On Mon, Jul 11, 2011 at 5:40 PM, Barry Warsaw ba...@list.org wrote: I've thought about this on and off over the years and still think it's a good idea. No, MM3 does not have such a thing yet. ... Yep Ok, great. but I'd like to understand the semantics first. Do messages to the list get bounced, and if so, by Mailman or the MTA? Currently, deleting a list does remove its configuration, but (by default) retains its archives, which can be deleted later. A disabled list would always have its archives available I think. With our current setup the disabled (or graveyarded) list is removed from the /var/lib/mailman/lists dir and the aliases regenerated, so the MTA bounces messages to it and the admin interface for it cannot be logged into. Disabled lists are listed in a separate page in the web interface to the normal listinfo page. Some disabled lists might get their archives removed and some not. I think bouncing at the MTA is slightly sub-optimal and that mailman could generate a more informative bounce indicating how to contact the server admin to get the list revived. Probably in the web interface there could be a disabled lists category. Server admins would probably want to be able to login to the disabled lists in the web interface, but maybe not the list admins. I think the core feature would not be too hard to implement, but some specifics would depend on answering the main question above. Here's an outline of what you'd probably need to touch: Thanks for the pointers, I will try that this week. -- bye, pabs ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] MM3: less generic names for scripts in $PATH?
On Mon, Jul 11, 2011 at 5:47 PM, Barry Warsaw ba...@list.org wrote: `master` and `runner` are a bit more problematic because they are pretty handy as separate commands. I don't think they belong under `bin/mailman` and since they're of internal use only, I would never expect them to be installed into /usr/bin. More likely any vendor package would put them under /usr/lib/mailman/bin in an FHS world. I'm not sure MM3 can function with `master` and `runner` under /usr/lib/mailman/bin but I would accept patches that made that work. (Or at least file a bug with a mailman3 tag). I'll take a look at that this week too since currently they are installed in $prefix/bin. -- bye, pabs ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] MM3: less generic names for scripts in $PATH?
Hi all, I was looking at Mailman 3 to see how many of the Indymedia patches for Mailman 2 would be still needed. The first thing that struck me was how generic the files that were installed in $PATH. I would really recommend mm-master, mm-runner, mm-onebounce or similar instead of the current master, runner, onebounce. Could that be changed? -- bye, pabs ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] MM3: list disabling/enabling?
Hi all, For the Indymedia Mailman 2 install, we have a patch that allowed list disabling (and later re-enabling). Disabled lists had their settings/archives saved, did not accept mail and were listed on a separate page to listinfo. For a long-lived large mailman server serving local groups in many locations, management of the complete list life cycle was and still is essential for us. AFAICT Mailman 3 doesn't yet support such a concept, is that the case? If not, would it be acceptable to add that? Any pointers if I were to try and add that? -- bye, pabs ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Install problems for mailman-3.0.0a7 on Debian Squeeze
On Wed, Jul 6, 2011 at 5:32 PM, Pavel Šimerda wrote: Wouldn't it be nice to have some more reasonable way to present this info to the user? Agreed. Does distutils have the equivalent of autoconf for checking for dependencies before starting the build? If so I assume mailman patches for this would be welcome. -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Install problems for mailman-3.0.0a7 on Debian Squeeze
On Fri, Jul 1, 2011 at 11:25 PM, ardeshir ardeshir@gmail.com wrote: Don't know if this will help you, but I got the following errors while installing on my system, Running Squeeze Debian ... src/zope/interface/_zope_interface_coptimizations.c:15:20: error: Python.h: No such file or directory src/zope/interface/_zope_interface_coptimizations.c:16:26: error: structmember.h: No such file or directory You need to install the Python headers (Debian package python-dev). storm/cextensions.c:23:20: error: Python.h: No such file or directory storm/cextensions.c:24:26: error: structmember.h: No such file or directory Same here. -- bye, pabs http://wiki.debian.org/PaulWise ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] pipermail feature request for View by Date
On Wed, Mar 10, 2010 at 11:33 PM, Mark Sapiro m...@msapiro.net wrote: As far as I can tell, patches to implement the feature seen at https://www.redhat.com/archives/fedora-devel-list/2010-January/date.html have never been submitted upstream. AFAICT, those pages are generated by MHonArc, not pipermail. Debian lists are also generated by MHonArc and have the same features. http://lists.debian.org/debian-devel/2010/03/maillist.html -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman 2.x Roadmap
On Tue, Jan 6, 2009 at 1:09 AM, Mark Sapiro m...@msapiro.net wrote: Please don't start (or extend) a list of downstream things to look at in the week before a release. First of all, I'm just compulsive enough to actually look, but even so, the most likely result is I'll be overwhelmed, defer everything and then forget about it. If downstream patches are of general applicability or address bugs in the upstream distribution, they should be reported in the upstream tracker (currently https://bugs.launchpad.net/mailman). My apologies. I'll try and find some time to post bugs and feature requests for mm3, perhaps during LCA if not before then. -- bye, pabs http://wiki.debian.org/PaulWise ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Getting Started with Mailman Development
On Sat, Sep 27, 2008 at 5:10 AM, Barry Warsaw [EMAIL PROTECTED] wrote: Maybe this code could be hosted on Launchpad as a Bazaar branch? What about merging it into the 2.2 or 3.0 branches? Also: Indymedia did a summary of encrypted mailing list options in 2006: http://lists.indymedia.org/pipermail/listwork/2006-February/0203-uh.html -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Getting Started with Mailman Development
On Sat, Sep 27, 2008 at 11:22 AM, Barry Warsaw [EMAIL PROTECTED] wrote: If there were branches on Launchpad that were ready for review, I'd be happy to take a look at them. They should definitely include tests and documentation, and a description of the design should probably be added to the wiki. Perhaps Joost can comment on how ready this is: https://code.launchpad.net/~joostvb/mailman/2.1-pgp-smime -- bye, pabs http://bonedaddy.net/pabs3/ ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Improving the archives
On 7/3/07, Terri Oda [EMAIL PROTECTED] wrote: I'm trying to remember all the things people have suggested for the archives in the past so I can figure out what needs to be done and what might be nice to have, and see if this is doable in the time I have in the foreseeable future. At lists.indymedia.org, we use a patch that provides these: * stable URLs based on a generated message id * URLs to the archived message in the message headers * message hiding http://lists.indymedia.org/patches/imc-10-mmid_hide_posts.patch It poses a bit of a migration issue since all the existing mboxes may or may not have the mmid header in them. We worked around that by having an special place for the old archives. We've been meaning to move to lurker for years, but haven't had the human resources and also there were some showstoppers: * public/private lists - lurker couldn't do that properly when we looked * lack of date-based index to the archives * general navigation issues; stuff like linking between current thread and nearby ones * mailto links (has now been fixed) * the migration nightmare My personal opinion is that pipermail should be removed and mailman should not contain a default archiver since there are plenty of good archivers already (lurker, mhonarc etc). Adding wrappers around them would be simpler than reimplementing them. -- bye, pabs https://docs.indymedia.org/view/Main/PaulWise ___ Mailman-Developers mailing list Mailman-Developers@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-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.027.htp
