Re: [Mailman-Developers] any interest in a new built-in web-archive? (i.e. pipermail replacement)

or whenever it was, but I conclude that the much bigger problem than building this ship is choosing a destination. It needs to start with clear goals, because the wrong implementation is easy. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago ___

Re: [Mailman-Developers] VM for Mailman development

public ec2 AMI? A sponsoring foundation could even host an account with "IAM" (Amazon IDM) to run them under and pay for the AMI storage. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago ___ Mailman-Developers ma

Re: [Mailman-Developers] [Mailman Confluence] Development > Web UI Mockups

* On 05 Aug 2010, Anna Granudd wrote: > > Other people having suggestions/ideas/thoughts on the design are more than > welcome to post them. We might start with this view in a few days so the > more feedback we can get on the design before starting the better. I have a couple of suggestions on t

Re: [Mailman-Developers] Proposed: remove address-obfuscation code from Mailman 3

* On 31 Aug 2009, Barry Warsaw wrote: > > Mailman will always still collect the raw data for messages sent to > the list. There are legitimate uses for allowing outsiders access > to that data (say, the list is moving and you want to migrate the > archives), so I think we always want to support

Re: [Mailman-Developers] MM command prefix and-or single mm-admin CLI frontend

> I like the idea of a master command, and quite naturally I would choose > 'mailman'. I didn't know that Trac did this, but lots of other programs > do, and I would look at the Bazaar code to see if there's anything we can > steal there too. If there's a Cheeseshop package we can just use, a

Re: [Mailman-Developers] LMTP delivery (was Re: ANNOUNCE: GNU Mailman 3.0a1 (Leave That Thing Alone))

> Okay. BTW, wouldn't you think that the majority of messages sent to a > Mailman list will have exactly one RCPT? Cross-posting is relatively > rare for most sites, isn't it? Just another data point: I don't have experience at most sites, but here cross-posting is extremely common. For exa

Re: [Mailman-Developers] mm-handler2.1.10(was:beforenextrelease:disable backscatter in defaultinstallation)

> mm-handler parses its arguments from sendmail and builds a list of > recipients and then processes that list in a loop. If it is really the > case that a message addressed to, e.g., more than one list will be > passed from sendmail to mm-handler as one invocation with multiple > recipients, then

Re: [Mailman-Developers] mm-handler 2.1.10 (was:beforenextrelease:disable backscatter in default installation)

> As I understand it (possibly wrong), the way this > > if ($DEBUG) { > $to = join(',', @to); > print STDERR "to: $to\n"; > print STDERR "sender: $sender\n"; > print STDERR "server: $server\n"; > exit(-1); > } > > w

Re: [Mailman-Developers] mm-handler 2.1.10 (was: beforenextrelease:disable backscatter in default installation)

> I don't have any preference. My version does depend on the presence of the > syslog module, and I don't know how commonly-installed that is. But I don't > know under what systems the debugging to stderr is supposed to work. Is > that a Sun thing? IIRC stderr is captured by sendmail and logged

Re: [Mailman-Developers] mm-handler 2.1.10 (was: before nextrelease:disable backscatter in default installation)

> Sorry for the bugs and such, and thanks for working it out. I feel bad about posting and abandoning, but I actually have no infrastructure to test this anymore. When I first contributed that script I only knew enough Python to debug Ma

Re: [Mailman-Developers] before next release: disable backscatter in default installation

> # Prevent backscatter for unapproved actions? > $BounceUnapproved = 0; > > # Prevent backscatter for undefined lists? > $BounceNonlist = 1; > > The comment seems to be logically backwards from the variable name. Should > it really read "allow", not "prevent"? Does 0 or 1 mean backscatter? Goo

Re: [Mailman-Developers] before next release: disable backscatter in default installation

> > 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by > > default. Nearly everyone uses web based signup. > > How, exactly, does one do these? In particular, how do you remove the > aliases when using mm-handler to process mail from sendmail? (I'd be happy > to start the wiki

Re: [Mailman-Developers] Batch-level list configuration

* On 2007.05.02, in <[EMAIL PROTECTED]>, * "Jeff Kunzelman (DHL)" <[EMAIL PROTECTED]> wrote: > > Is there a way that I can use the withlist command to change the display > name of a mailman list? You can, but you must write valid python code that manipulates properties of the list object.

[Mailman-Developers] Re: Multi-slice qrunners to be fixed for 2.1.6? (Re: SF Patch 1008983)

* On 2004.10.21, in <[EMAIL PROTECTED]>, * "Brad Knowles" <[EMAIL PROTECTED]> wrote: > > MTA configuration, but it certainly sounds like the ability to have > multiple qrunners going at the same time would allow the MTA a better > chance to maximize the potential overall mailing list throu

[Mailman-Developers] Re: New command-line tool...

* On 2004.07.16, in <[EMAIL PROTECTED]>, * "Brad Knowles" <[EMAIL PROTECTED]> wrote: > At 7:55 PM -0500 2004-07-16, David Champion wrote: > > > I don't have a new-enough mailman to judge this, and I don't see a link > > for the full versi

[Mailman-Developers] Re: New command-line tool...

* On 2004.07.16, in <[EMAIL PROTECTED]>, * "Brad Knowles" <[EMAIL PROTECTED]> wrote: > > A modified version of the "discard" tool has been created and > uploaded to > . > > I believe that this

[Mailman-Developers] Re: interface dreams

* On 2004.07.15, in <[EMAIL PROTECTED]>, * "Fil" <[EMAIL PROTECTED]> wrote: > > As a list admin, I dream of a roster interface that would help me go fast > when I have 10 people to subscribe and 10 to remove because they don't know > better than "Reply"-ing to me. > > I can make it up with

[Mailman-Developers] Re: skinning mailman pages...

* On 2004.07.06, in <[EMAIL PROTECTED]>, * "Chuq Von Rospach" <[EMAIL PROTECTED]> wrote: > > someone please tell me I'm not crazy. I remember a set of patches that > could be added to mailman that allowed defining header/footer for > mailman without having to hack everything -- and now, I

[Mailman-Developers] Re: Cloning listsZ

* On 2004.04.02, in <[EMAIL PROTECTED]>, * "Mike Porter" <[EMAIL PROTECTED]> wrote: > Make the new list, then perhaps use config_list to dump the > variables of the list to clone from, make changes, and then import > into the new list, making the new list look a lot like the old > list? The

[Mailman-Developers] Re: bugtraq submission warning: email address harvesting exploit

* On 2003.11.27, in <[EMAIL PROTECTED]>, * "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > > downloading the listname.mbox file that has all the unmunged addresses > > still in it) > > I'd consider turning this off for 2.1.4 if people agree. Perhaps making > it available only through a site con

[Mailman-Developers] Re: bugtraq submission warning: email address harvesting exploit

* On 2003.11.25, in <[EMAIL PROTECTED]>, * "Bernhard Kuemel" <[EMAIL PROTECTED]> wrote: > > While this approach may work in individual cases it is trivially > and quite likely defeatet when the prize is 100,000 mailing lists > with 1 to 5 million (!) high quality email addresses. > ... > I

[Mailman-Developers] Re: "Turing test" to reject email harvesting bots

* On 2003.11.16, in <[EMAIL PROTECTED]>, > > This test may disable users of non graphical web browers or email > only subscribers to subscribe. I've generally found that encoding the address as HTML character entities works fine. I've had a bait address on my web page for quite some time, and it

[Mailman-Developers] Re: Requirements for a new archiver

* On 2003.10.28, in <[EMAIL PROTECTED]>, * "Chuq Von Rospach" <[EMAIL PROTECTED]> wrote: > > because once you leave the niche of dealing with your fellow geeks, > that's what users are going to want. browser access. NNTP is simply a It's the "non-geeks" I'm trying to help: I support 25,00

[Mailman-Developers] Re: Requirements for a new archiver

* On 2003.10.27, in <[EMAIL PROTECTED]>, * "Barry Warsaw" <[EMAIL PROTECTED]> wrote: > > Which does point to an alternative direction -- maybe we don't need any > direct connection to an html archive. Maybe the archiver should just be > a separate process that reads messages from the NNTP i

[Mailman-Developers] Re: Requirements for a new archiver

> exhaustion. Or you could store everything in an mbox file with a file > offset index. Or perhaps store everything to an nntp server (Twisted > would make a nice platform for this ). > ... > Also, I really want the next generation archiver to do everything > through cgi (or equivalent programmat

[Mailman-Developers] feature idea

Forgive me if this is already in there and I haven't noticed, but occasionally there's a situation where I think it would be useful for Mailman to support an address that would expand to all addresses currently listed as mailing list administrators. (It wouldn't be obligatory; you could just disabl

[Mailman-Developers] Re: checkdbs UnicodeError

* On 2003.02.06, in <[EMAIL PROTECTED]>, * "Daniel Buchmann" <[EMAIL PROTECTED]> wrote: > The patch solved the problem. Thanks! :) > > Over to something else: > Is there anyone out there that has written a script to flush (discard) > the entire request db for a specified list? > I need it ba

[Mailman-Developers] Re: I hate the 1st of the month.

* On 2003.02.01, in <[EMAIL PROTECTED]>, * "Ron Jarrell" <[EMAIL PROTECTED]> wrote: > > Just venting. I'm in my monthly "God, I *hate* the password reminder > scheme" phase. I get over it in a few days. But for the next 48 hours > or so I'm dealing with a stream of people who reply to mailman

Re: [Mailman-Developers] usage() going to stderr

* On 2002.10.21, in <[EMAIL PROTECTED]>, * "Chuq Von Rospach" <[EMAIL PROTECTED]> wrote: > >Most of the scripts in the bin/ directory send their usage() output to > >sys.stderr. Unfortunately, this makes it difficult to pipe the usage > >output to a program such as more(1) (without redirecti

[Mailman-Developers] Re: i18n support for Archiver

* On 2002.09.03, in <[EMAIL PROTECTED]>, * "Dan Mick" <[EMAIL PROTECTED]> wrote: > > Oh, that's brilliant! Thank you David; I love Joerg's software, > but that just hit home... I rely on his CD software, and for the most part it's quite good, but it was just too funny to let lie when I fo

[Mailman-Developers] Re: i18n support for Archiver

* On 2002.08.27, in <[EMAIL PROTECTED]>, * "Bob Puff@NLE" <[EMAIL PROTECTED]> wrote: > > Easier to use one of the extended CDROM formats which supports long > > filenames > > A few months ago I went through this with a customer who wanted a copy > of the archives on CDROM from their list. Th

[Mailman-Developers] Re: Anti-spam "killer app"?

* On 2002.08.22, in <[EMAIL PROTECTED]>, * "Daniel Buchmann" <[EMAIL PROTECTED]> wrote: > > Let's say 99.99% of all spam is in english (which is my experience), and > my mother tongue is norwegian. ;) Funny: my experience is that 60% of all spam is in Chinese, Spanish, or Turkish. :) > L

[Mailman-Developers] Re: bin/arch: a bug or not?

* On 2002.08.13, in <[EMAIL PROTECTED]>, * "Simone Piunno" <[EMAIL PROTECTED]> wrote: > > it could be a mitigating factor for people forced to rebuild the > archive, becase having the old messages in place you can still serve > people coming through external search engines (at the cost of w

[Mailman-Developers] Re: bounces going to wrong list's admin

* On 2002.08.09, in <[EMAIL PROTECTED]>, * "Barry A. Warsaw" <[EMAIL PROTECTED]> wrote: > > >>>>> "DC" == David Champion <[EMAIL PROTECTED]> writes: > > DC> https://listhost.uchicago.edu/mailman-files/mailman-ignor

Re: [Mailman-Developers] bounces going to wrong list's admin

* On 2002.08.09, in <[EMAIL PROTECTED]>, * "Gary Casterline" <[EMAIL PROTECTED]> wrote: > > Ahh. In the meantime, if the sorting is alpha, perhaps I > should create a bogus public list -- alist -- like > taxi cab listings in the yellow pages? See my message from Monday, Aug. 5, "Pass

[Mailman-Developers] Re: Opening up a few can o' worms here...

* On 2002.07.18, in <[EMAIL PROTECTED]>, * "Jay R. Ashworth" <[EMAIL PROTECTED]> wrote: > > You obviously have not been following the activities of Senator > Hollings, D-Disney, whose SSSCA indeed wants to make the very *design* > of Linux illegal. How does this conflict with the design of

[Mailman-Developers] Re: A RELEASED Mailman 2.1 beta 2

Just a quickie while I'm in between crises: * On 2002.05.06, in <[EMAIL PROTECTED]>, * "Chuq Von Rospach" <[EMAIL PROTECTED]> wrote: > I would, by the way, do two of these: a pre-filter and a post-filter. The Delivery filter and archiving filter? A little clearer in intent. Good idea. A

[Mailman-Developers] Re: Python-2.2 disaster

On 2002.03.05, in <514667500.1015300858@[192.168.0.1]>, "Carson Gaspar" <[EMAIL PROTECTED]> wrote: > OK, I "fixed" the _socket problem by hacking setup.py to change how it > found ssl_incs and ssl_libs, and by adding 'runtime_library_dirs = > ssl_libs' to the exts.append clause. > > Can

[Mailman-Developers] Re: [Zest-devel] Re: Pipermail replacement? Zest!

On 2002.02.26, in <[EMAIL PROTECTED]>, "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote: > > Er, all of them? Search engines don't do authentication, webservers > do. Or at the very least, webservers can do enough kinds of > authentication that you should be able to find one you like. I

[Mailman-Developers] Re: [Zest-devel] Re: Pipermail replacement? Zest!

On 2002.02.26, in <[EMAIL PROTECTED]>, "Jay R. Ashworth" <[EMAIL PROTECTED]> wrote: > > ... and a generic web search engine, running locally on that machine, > with access to the messages, will serve that purpose fine, and can > still be hidden behind whatever authentication you like. Ma

[Mailman-Developers] Re: [Zest-devel] Re: Pipermail replacement? Zest!

On 2002.02.26, in <[EMAIL PROTECTED]>, "Jay R. Ashworth" <[EMAIL PROTECTED]> wrote: > > Searching doesn't belong inside of a list archiver that has a web > interface -- why do the same work twice? There are half a dozen or > more web search engine packages which can be pointed at that in

[Mailman-Developers] Re: Interesting study -- spam on postedaddresses...

On 2002.02.18, in <[EMAIL PROTECTED]>, "Daniel J. Cody" <[EMAIL PROTECTED]> wrote: > Speaking of tradeoffs, it's my opinion that hiding archives behind a > password protection scheme for fear that the administrator, who probably > deals with oodles of email anyways and is probably the *m

[Mailman-Developers] Re: Style Sheet (CSS) support

On 2002.01.17, in <[EMAIL PROTECTED]>, "David Champion" <[EMAIL PROTECTED]> wrote: > > I contributed a number of patches in this thread to the SourceForge "Thread"? There's a misleading word. How about "vein"? > My patches cared

Re: [Mailman-Developers] Style Sheet (CSS) support

On 2002.01.17, in <[EMAIL PROTECTED]>, "Dan Rich" <[EMAIL PROTECTED]> wrote: > I figure this question is probably better suited for this list than > mailman-users. > > Has anyone looked at adding style sheet support to mailman? I've hacked > it into my installtion, since I really need th

[Mailman-Developers] Re: New Pipermail hacks (was Re: Ok, it works! ...)

On 2001.10.26, in <[EMAIL PROTECTED]>, "Ben Gertzfield" <[EMAIL PROTECTED]> wrote: > > Sure, but duplicates will come in quite quickly; it will be pretty > useless as soon as 40 people send in "map.gif", don't you think? We'd > have to do filename munging in any case, and that's sticky.

Re: [Mailman-Developers] New Pipermail hacks (was Re: Ok, it works! ...)

On 2001.10.25, in <[EMAIL PROTECTED]>, "Ben Gertzfield" <[EMAIL PROTECTED]> wrote: > > Here's a patch that actually throws out all-HTML emails, but just > removes HTML parts. > > Actually, why don't we just decode HTML attachments like any other, > and let the user beware if they want

[Mailman-Developers] Re: Reply-To: handling

On 2001.10.20, in <[EMAIL PROTECTED]>, "J C Lawrence" <[EMAIL PROTECTED]> wrote: > > BTW: Have you checked Mutt's behaviour yet? Could/would someone > check Outlook's behaviour? Jay's using a truly old version of mutt, so I'm going to jump in here. Mutt 1.3.23, the current development

[Mailman-Developers] Re: handling duplicate mails

On 2001.10.16, in <[EMAIL PROTECTED]>, "Marc MERLIN" <[EMAIL PROTECTED]> wrote: > > Ben's attacks the problem by ensuring that an individual only > > gets delivered one copy of an email (based on the message ID) > > (ie at the delivery stage) > > This is indeed what I need. > (it apparent

[Mailman-Developers] Re: Creation/deletion of lists through-the-web

On 2001.05.09, in <[EMAIL PROTECTED]>, "Jay R. Ashworth" <[EMAIL PROTECTED]> wrote: > > that you typically have to do some manual and difficult crud like edit > > an /etc/aliases file and run `newaliases' (as root!). I've figured a > > way around this with Postfix, and of course Exim can

[Mailman-Developers] Re: Dates

On 2001.05.01, in <[EMAIL PROTECTED]>, "Barry A. Warsaw" <[EMAIL PROTECTED]> wrote: > > Phew! A little thing like dates gets us geeks in an uproar. > Whodathunk? :) Well, we're touching on a matter of fidelity of a record, which is what gets me concerned about it. I guess that's a kind

[Mailman-Developers] Re: Dates

On 2001.05.01, in <[EMAIL PROTECTED]>, "Jay R. Ashworth" <[EMAIL PROTECTED]> wrote: > > correct. How would it possibly know? You're discussing ways to make a > > correct guess in most cases, but not a way to ensure correct > > information in all cases. > > Stipulated. But we're not rew

[Mailman-Developers] Re: Dates

On 2001.05.01, in <[EMAIL PROTECTED]>, "Jay R. Ashworth" <[EMAIL PROTECTED]> wrote: > > If that date is *wrong*, it's *wrong*. That it was applied by the > sending MUA does *not* make it automatically authoritative; timestamps > are an absolute -- there *is* a standard. But it's not the