Mailman 3 September 2003 - Mailman-coders

[ mailman-Feature Requests-797436 ] subscription confirmation log access
by SourceForge.net Sept. 2, 2003

Sept. 2, 2003

Feature Requests item #797436, was opened at 2003-08-29 10:58 Message generated for change (Comment added) made by jcdill You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: subscription confirmation log access Initial Comment: Please create a system for mailing list owners to access the logs that prove that subscriptions were confirmed (opt-in confirmation). Ideally, this would be available both via the web administration page and via email, like all other list management tasks. ---------------------------------------------------------------------- >Comment By: JC Dill (jcdill) Date: 2003-09-02 11:34 Message: Logged In: YES user_id=836732 oops, it was spam-l, not nanog. Sorry! ---------------------------------------------------------------------- Comment By: JC Dill (jcdill) Date: 2003-09-02 11:33 Message: Logged In: YES user_id=836732 This was just posted to nanog: From: Vivek Khera <khera(a)KCILINK.COM> Organization: Khera Communications, Inc., Rockville, MD Subject: Re: Media: Fearing 'Spam' Label, Advertisers Wary of E-Mail To: SPAM-L(a)PEACH.EASE.LSOFT.COM Precedence: list X-UIDL: 96919 >>>>> "JD" == JC Dill <spam-l(a)VO.CNCHOST.COM> writes: JD> At 12:27 PM 8/29/2003, Laura Atkins wrote: >> > This is what a list manager server *should* do, if it isn't doing it >> > already then we need to just ask the developers to add this feature in. >> >> A lot of hassle for an extremely limited (if any) benefit. JD> I believe that being able to prove that a subscription was confirmed JD> is going to become increasingly important as legitimate mailing lists JD> are increasingly being asked to prove their legitimacy. Proof means JD> keeping and being able to produce the relevant logs, doesn't it? We have found that by keeping a copy of the confirmation request and upon confirmation the full headers of the incoming message, we cover pretty much any request we've gotten. Nobody has ever asked for more (not to say that they won't in the future). Since we started allowing confirm by click, instead of the return message headers, we keep the details of time, IP address, browser version, and full HTTP request. That seems to have been sufficient, too. We keep this information in the per-subscriber record in our database, so that we can pull it up any time, for as long as the record is in our database (up to 6 months after they unsubscribe). After that time, we'd have to dig thru some CDs to find it, but it is there forever. This is all for our proprietary broadcast-only announcement system, so it was easy to modify to do this... What I'd really like is for Mailman to support this type of record keeping, so the discussion lists we operate for some non-profits can also have this kind of protection. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_i…

1 0

[ mailman-Feature Requests-797436 ] subscription confirmation log access
by SourceForge.net Sept. 2, 2003

Sept. 2, 2003

Feature Requests item #797436, was opened at 2003-08-29 10:58 Message generated for change (Comment added) made by jcdill You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: subscription confirmation log access Initial Comment: Please create a system for mailing list owners to access the logs that prove that subscriptions were confirmed (opt-in confirmation). Ideally, this would be available both via the web administration page and via email, like all other list management tasks. ---------------------------------------------------------------------- >Comment By: JC Dill (jcdill) Date: 2003-09-02 11:33 Message: Logged In: YES user_id=836732 This was just posted to nanog: From: Vivek Khera <khera(a)KCILINK.COM> Organization: Khera Communications, Inc., Rockville, MD Subject: Re: Media: Fearing 'Spam' Label, Advertisers Wary of E-Mail To: SPAM-L(a)PEACH.EASE.LSOFT.COM Precedence: list X-UIDL: 96919 >>>>> "JD" == JC Dill <spam-l(a)VO.CNCHOST.COM> writes: JD> At 12:27 PM 8/29/2003, Laura Atkins wrote: >> > This is what a list manager server *should* do, if it isn't doing it >> > already then we need to just ask the developers to add this feature in. >> >> A lot of hassle for an extremely limited (if any) benefit. JD> I believe that being able to prove that a subscription was confirmed JD> is going to become increasingly important as legitimate mailing lists JD> are increasingly being asked to prove their legitimacy. Proof means JD> keeping and being able to produce the relevant logs, doesn't it? We have found that by keeping a copy of the confirmation request and upon confirmation the full headers of the incoming message, we cover pretty much any request we've gotten. Nobody has ever asked for more (not to say that they won't in the future). Since we started allowing confirm by click, instead of the return message headers, we keep the details of time, IP address, browser version, and full HTTP request. That seems to have been sufficient, too. We keep this information in the per-subscriber record in our database, so that we can pull it up any time, for as long as the record is in our database (up to 6 months after they unsubscribe). After that time, we'd have to dig thru some CDs to find it, but it is there forever. This is all for our proprietary broadcast-only announcement system, so it was easy to modify to do this... What I'd really like is for Mailman to support this type of record keeping, so the discussion lists we operate for some non-profits can also have this kind of protection. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_i…

1 0

[ mailman-Patches-605234 ] Stylesheet support for archives
by SourceForge.net Sept. 2, 2003

Sept. 2, 2003

Patches item #605234, was opened at 2002-09-05 15:57 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 4 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Stylesheet support for archives Initial Comment: This patch adds a stylesheet reference to the pipermail archives, and copies in an empty stylesheet the first time the list is opened and the file doesn't already exist. The patch modifies two files in the Mailman.Archiver package, and the stylesheet should be copied into templates/en/. ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-09-02 13:05 Message: Logged In: YES user_id=3066 Bumped priority a little now that MM2.1 is out. ;) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:04 Message: Logged In: YES user_id=12800 Postponing this to post-MM2.1 :( ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-09-05 16:00 Message: Logged In: YES user_id=3066 Barry volunteered to integrate and test. Yay! ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_i…

1 0

[ mailman-Feature Requests-799248 ] enhanced list of subscriptions
by SourceForge.net Sept. 2, 2003

Sept. 2, 2003

Feature Requests item #799248, was opened at 2003-09-02 13:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=799248&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Nobody/Anonymous (nobody) Summary: enhanced list of subscriptions Initial Comment: After dealing with mailbox quota problems in the aftermath of the Sobig.F worm, I found it would be really nice if the "List my subscriptions" display contained more information. Most importantly, whether email would actually be sent for each subscription. The most valuable information to include could probably be determined by looking for fields that differ for some lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=799248&group_i…

1 0

[ mailman-Patches-799166 ] install-sh doesn't support multiple sources
by SourceForge.net Sept. 2, 2003

Sept. 2, 2003

Patches item #799166, was opened at 2003-09-02 16:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=799166&group_i… Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Joerg Friedrich (jeff42) Assigned to: Nobody/Anonymous (nobody) Summary: install-sh doesn't support multiple sources Initial Comment: Hi, When not having installed a 'install'-programm configure falls back to the provided install-sh. But this Program does'nt support multiple source files. I encountered not installed files in messages (the mo-files) and the icons. Since I had no time to take a look at install-sh I send two patches to the Makefiles. Yours, Joerg ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=799166&group_i…

1 0

[ mailman-Bugs-782024 ] Private archives link error
by SourceForge.net Sept. 2, 2003

Sept. 2, 2003

Bugs item #782024, was opened at 2003-08-02 19:24 Message generated for change (Comment added) made by thomas_ah You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=782024&group_i… Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nicola Soranzo (soranzo) Assigned to: Nobody/Anonymous (nobody) Summary: Private archives link error Initial Comment: If I visit http://domain/mailman/private/listname/ all the links to the Thread, Subject, ... monthly archives are correct, but if the URL is http://domain/mailman/private/listname (without the trailing slash), the links are incorrect, eg.: http://domain/mailman/private/2003-July/thread.html (without the listname between private and the month). ---------------------------------------------------------------------- Comment By: Thomas Arendsen Hein (thomas_ah) Date: 2003-09-02 12:27 Message: Logged In: YES user_id=839582 A quick fix is to add a redirect in your web server. But since the List-Archive mail header points to the link without a trailing slash, this should be done in the cgi script, too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=782024&group_i…

1 0

[ mailman-Bugs-767596 ] mailman list archive links not working with virtual hosts
by SourceForge.net Sept. 2, 2003

Sept. 2, 2003

Bugs item #767596, was opened at 2003-07-08 09:55 Message generated for change (Comment added) made by thomas_ah You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=767596&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nick Hemsley (blackisha) Assigned to: Nobody/Anonymous (nobody) Summary: mailman list archive links not working with virtual hosts Initial Comment: any mailman page with a link to the archives page for a mailing-list on a virtual-host, points to the primary hostname, instead of pointing to the virtual-domain. try this page for an example of the problem http://itomic.com/mailman/listinfo/asaconsultants_itomic.com the Asaconsultants archives link points to http://earth.itomic.com/pipermail/asaconsultants_itomic.com/ which is the primary hostname of the server on which itomic.com resides. it should point to http://itomic.com/pipermail/asaconsultants_itomic.com p.s. this list was recently upgraded to 2.1.2 by make install-ing into a previously existing mailman (2.0.13) directory (it said things in make install about upgrading, so I assumed it was handling ok) ---------------------------------------------------------------------- Comment By: Thomas Arendsen Hein (thomas_ah) Date: 2003-09-02 12:24 Message: Logged In: YES user_id=839582 leftlink: Remove PUBLIC_ARCHIVE_URL from mm_cfg.py since this will be calculated by Defaults.py blackisha (and maybe leftlink, too): You need to use add_virtualhost statements in your mm_cfg.py: DEFAULT_EMAIL_HOST = 'itomic.com' DEFAULT_URL_HOST = DEFAULT_EMAIL_HOST add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) We just stumbled into the same problems here :) ---------------------------------------------------------------------- Comment By: rich cowan (leftlink) Date: 2003-08-26 01:45 Message: Logged In: YES user_id=538509 This bug should renamed: "LIST Archive Links Broken After 2.1 Upgrade." That's because it is one of several problems with updating: it appears that on one machine where the list info is at: domain.org/cgi-bin/mailman/listinfo/nosi-steering the archives link for this list points to: domain.org/pipermail/ i.e. the list name vanishes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=767596&group_i…

1 0

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Sept. 2, 2003

Sept. 2, 2003

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 9 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-02 00:15 Message: Logged In: YES user_id=12800 Bumping priority. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 14:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 21:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 20:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan <danbri(a)w3.org> ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

1 0