Mailman 3 September 2003 - Mailman-coders

[ mailman-Feature Requests-808626 ] ability to allow postings from all users from *@domain.com
by SourceForge.net 21 Sep '03

21 Sep '03

Feature Requests item #808626, was opened at 2003-09-18 11:13 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808626&group_i… Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Felicia Berryman (felicia) Assigned to: Nobody/Anonymous (nobody) Summary: ability to allow postings from all users from *(a)domain.com Initial Comment: Ability to allow *(a)domain.com. I administer a list that is automatically posted to in order to give developers cvs updates. I only want the automatic posters to have access from the list. It would be nice if I could allow any postings from a particular machine/IP. For example, all users from with @domain.com. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-21 21:07 Message: Logged In: YES user_id=12800 Mailman 2.1 already has this feature. Privacy options -> sender filters -> accept_these_nonmembers (and other variables) accept Python regular expressions. See the details for details. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808626&group_i…

1 0

[ mailman-Feature Requests-808642 ] ability to specify digested "waiting for approval" messages.
by SourceForge.net 18 Sep '03

18 Sep '03

Feature Requests item #808642, was opened at 2003-09-18 10:23 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=808642&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Felicia Berryman (felicia) Assigned to: Nobody/Anonymous (nobody) Summary: ability to specify digested "waiting for approval" messages. Initial Comment: I'd like the ability to specify digested "waiting for approval" messages. If I get 30 messages waiting my approval per day, then I get 30 notifications plus reminders that messages are waiting. I'd like the ability to get these messages in daily and weekly digests. Furthermore, it might be nice to only have particular messages digested, such as the messages with the explaination "Non-members are not allowed to post messages to this list.". All other posts would then come to me right away. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808642&group_i…

1 0

[ mailman-Feature Requests-808626 ] ability to allow postings from all users from *@domain.com
by SourceForge.net 18 Sep '03

18 Sep '03

Feature Requests item #808626, was opened at 2003-09-18 10:13 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=808626&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Felicia Berryman (felicia) Assigned to: Nobody/Anonymous (nobody) Summary: ability to allow postings from all users from *(a)domain.com Initial Comment: Ability to allow *(a)domain.com. I administer a list that is automatically posted to in order to give developers cvs updates. I only want the automatic posters to have access from the list. It would be nice if I could allow any postings from a particular machine/IP. For example, all users from with @domain.com. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808626&group_i…

1 0

[ mailman-Patches-807016 ] dutch translation breaks e-mail confirmation instructions
by SourceForge.net 16 Sep '03

16 Sep '03

Patches item #807016, was opened at 2003-09-16 09:14 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=807016&group_i… Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ward Vandewege (ward) Assigned to: Nobody/Anonymous (nobody) Summary: dutch translation breaks e-mail confirmation instructions Initial Comment: The Dutch translation in templates/nl/invite.txt translates the 'confirm' command for e-mail replies to an invitation by list owners into Dutch. Mailman does not respond to Dutch commands, so this breaks Mailman. The attached patch fixes this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=807016&group_i…

1 0

[ mailman-Bugs-805630 ] mail to foo-bar@ list languishes in maildir
by SourceForge.net 13 Sep '03

13 Sep '03

Bugs item #805630, was opened at 2003-09-13 11:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=805630&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: mail to foo-bar@ list languishes in maildir Initial Comment: Mail to a list with a hyphen in its name languishes forever in qfiles/maildir. The culprin might be in MaildirRunner.py # We only care about the listname and the subq as in listname@ or # listname-request@ lre = re.compile(r""" ^ # start of string (?P<listname>[^-@]+) # listname@ or listname-subq@ (?: # non-grouping - # dash separator (?P<subq>[^-+@]+) # everything up to + or - or @ )? # if it exists """, re.VERBOSE | re.IGNORECASE) How about list-name@? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=805630&group_i…

1 0

[ mailman-Patches-804162 ] Bug: unsubscription confirmation from Web bypasses approval
by SourceForge.net 10 Sep '03

10 Sep '03

Patches item #804162, was opened at 2003-09-11 12:53 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=804162&group_i… Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: Bug: unsubscription confirmation from Web bypasses approval Initial Comment: When a member submit unsubscription request from Web UI (options) without logging in then submit confirmation from Web UI (confirm), s/he can be unsubscribed without moderator approval. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=804162&group_i…

1 0

[ mailman-Bugs-803871 ] 2.1.2/Solaris 8 Problems with OutgoingRunner
by SourceForge.net 10 Sep '03

10 Sep '03

Bugs item #803871, was opened at 2003-09-10 13:17 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803871&group_i… Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Charles Gagnon (charlesg) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.2/Solaris 8 Problems with OutgoingRunner Initial Comment: Mailman 2.1.2, Solaris 8 and Python 2.2.2 seem to be a bad combo. The "qrunner --runner=OutgoingRunner:0:1 -s" process starts okay and stays okay to send one message (either confirmation or post) and than is just hangs. After downgrading the Python version to 2.1.3 on the same Solaris 8 server, everything seems okay. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803871&group_i…

1 0

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net 10 Sep '03

10 Sep '03

Patches item #657951, was opened at 2002-12-23 19:17 Message generated for change (Comment added) made by wookiew 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: Michael Weber (wookiew) Date: 2003-09-10 16:29 Message: Logged In: YES user_id=863445 So far the patch is included (by the way: i hope that Defaults.py.in in the patch *means* Defaults.py ) and mailman get a restart. Hopefully i add the two lines in listinfo.html ( /de/ because we have german speaking lists) and take a look for the xml file). After search the whole device (only to be sure) i can say: There is no file like this. Is another patch need before? Another setup to make? I cant find any hint here... so i have to ask. But the idea is great... if it work on my lists its genious... regards, Michael running version 2.1.1 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-02 04:15 Message: Logged In: YES user_id=12800 Bumping priority. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 18: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-11 01:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-11 00: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 15: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 11: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 11: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 22: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 21: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-18 01: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 20: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 19: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 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19: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

[ mailman-Bugs-803729 ] LookupError: unknown encoding: X-UNKNOWN
by SourceForge.net 10 Sep '03

10 Sep '03

Bugs item #803729, was opened at 2003-09-10 15:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ervin Németh (nemethe) Assigned to: Nobody/Anonymous (nobody) Summary: LookupError: unknown encoding: X-UNKNOWN Initial Comment: Our site encounters the following problem. mailman-2.1.2 installed from OpenBSD ports. Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_i…

1 0

[ mailman-Bugs-803045 ] mailman breaks PGP/MIME messages
by SourceForge.net 09 Sep '03

09 Sep '03

Bugs item #803045, was opened at 2003-09-09 12:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803045&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Enno Rehling (eressea) Assigned to: Nobody/Anonymous (nobody) Summary: mailman breaks PGP/MIME messages Initial Comment: When sending PGP/MIME messages to mailman, mailman tries to wrap the message by packaging it into its own message. To quote the enimgamil developers: "The message from mailman, however, has a Content- Type: multipart/mixed, where the signed message is packed into the first part of that message (there is an additional part with some footer message). This is not compliant to the PGP/MIME standard, no tool will be able to read such a message." I originally filed this bug with the enigmail developers, but agree with them that the bug is on mailman's side. Original bug report (including attachments of example mail) can be read at http://mozdev.org/bugs/show_bug.cgi?id=4601 This is with the mailman 2.1.2-6 deian package ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803045&group_i…

1 0