Mailman 3 April 2006 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Aug. 19, 2022

Aug. 19, 2022

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: 7 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-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…

2 1

[ mailman-Bugs-1256272 ] NNTP gatewaying trashes Message-IDs
by SourceForge.net April 29, 2006

April 29, 2006

Bugs item #1256272, was opened at 2005-08-11 00:47 Message generated for change (Comment added) made by kateturner You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256272&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: nntp/news Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kate Turner (kateturner) Assigned to: Nobody/Anonymous (nobody) Summary: NNTP gatewaying trashes Message-IDs Initial Comment: when a message is relayed to NNTP, the NewsRunner unconditionally replaces the existing Message-ID with its own. this breaking threading when reading a list via news, and when an NNTP user replies to a list message. a better solution would be either: 1) do not rewrite the message-id unless the NNTP server reports an error when posting it (duplicate ID); or 2) optionally, always rewrite posters' message-ids into a mailman-generated ID, and use this ID for both mail and news. i have implemented the former at our site and it appears to work, but it's so ugly i'd not feel comfortable submitting a patch for it. ---------------------------------------------------------------------- >Comment By: Kate Turner (kateturner) Date: 2006-04-29 15:44 Message: Logged In: YES user_id=1116721 the conflicts occur when a user cross-posts a message to two lists. the newsrunner won't turn it into a cross-post, instead it tries to post it separately to both groups, and the news server rejects the second one for a duplicate message-id (tested with innd). of course, you could say this behaviour is a bug too :) i'm not sure what the best way to group cross-posted messages is, since they won't be received by the same mailman instance. (cancelling the first and re-posting to both groups might work, but i don't know if inn will still record the message-id and not allow it to be reused.) ---------------------------------------------------------------------- Comment By: Ian Z. (nobrowser) Date: 2006-04-20 06:13 Message: Logged In: YES user_id=1192798 Finally! I thought I was the only one who noticed this. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346413 Why would the mail message-id ever cause a conflict with the NNTP server? message-ids are supposed to be globally unique and there is a convention (in RFC 2822?) that ensures it (put in the FQDN and something unique to the generating software). So I think 1) is not ugly but correct :) 2) wouldn't completely solve the problem. I can post one copy of a message to a mailman list and another directly to another recipient, including myself. (I actually Cc myself on all mail I send). If mailman does 2), the extra recipient will still be confused. Ian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256272&group_…

1 0

[ mailman-Bugs-1471487 ] ASCII decoding error in membership management
by SourceForge.net April 28, 2006

April 28, 2006

Bugs item #1471487, was opened at 2006-04-16 16:32 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1471487&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Andreas Thienemann (ixsnet) Assigned to: Nobody/Anonymous (nobody) Summary: ASCII decoding error in membership management Initial Comment: When opening the list membership management view in the admin interface, a notice about hitting a bug in 2.1.7 appears. The error log has some more information: admin(31507): [----- Mailman Version: 2.1.7 -----] admin(31507): [----- Traceback ------] admin(31507): Traceback (most recent call last): admin(31507): File "/opt/mailman-2.1.7/scripts/driver", line 101, in run_main admin(31507): main() admin(31507): File "/opt/mailman-2.1.7/Mailman/Cgi/admin.py", line 197, in main admin(31507): show_results(mlist, doc, category, subcat, cgidata) admin(31507): File "/opt/mailman-2.1.7/Mailman/Cgi/admin.py", line 497, in show_results admin(31507): form.AddItem(membership_options(mlist, subcat, cgidata, doc, form)) admin(31507): File "/opt/mailman-2.1.7/Mailman/Cgi/admin.py", line 869, in membership_options admin(31507): all = [_m.encode() for _m in mlist.getMembers()] admin(31507): UnicodeError: ASCII decoding error: ordinal not in range(128) admin(31507): [----- Python Information -----] admin(31507): sys.version = 2.2.3 (#1, Nov 11 2003, 17:44:56) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] admin(31507): sys.executable = /usr/bin/python2 admin(31507): sys.prefix = /usr admin(31507): sys.exec_prefix = /usr admin(31507): sys.path = /usr admin(31507): sys.platform = linux2 ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-04-28 15:42 Message: Logged In: YES user_id=1123998 > Would an illegal address such as this be filtered nowadays? Yes, such an address couldn't be added in the first place. ---------------------------------------------------------------------- Comment By: Andreas Thienemann (ixsnet) Date: 2006-04-28 14:32 Message: Logged In: YES user_id=1450459 It seems, the problem is caused by an illegal email address "marionmÃ¼ller(a)t-online.de". And yes, this was an upgrade from 2.0.x. Would an illegal address such as this be filtered nowadays? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-04-16 18:51 Message: Logged In: YES user_id=1123998 Did you just upgrade from Mailman 2.1.2 or older? It appears that this list has one or more members with (invalid?) non-ascii characters in their email address. I think any version from 2.1.3 on would throw this exception, and no recent version would allow the address to be added. You might try something like bin/list_members listname | egrep '[^[:alnum:]@.-]' to find the offending address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1471487&group_…

1 0

[ mailman-Bugs-1471487 ] ASCII decoding error in membership management
by SourceForge.net April 28, 2006

April 28, 2006

Bugs item #1471487, was opened at 2006-04-16 23:32 Message generated for change (Comment added) made by ixsnet You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1471487&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Andreas Thienemann (ixsnet) Assigned to: Nobody/Anonymous (nobody) Summary: ASCII decoding error in membership management Initial Comment: When opening the list membership management view in the admin interface, a notice about hitting a bug in 2.1.7 appears. The error log has some more information: admin(31507): [----- Mailman Version: 2.1.7 -----] admin(31507): [----- Traceback ------] admin(31507): Traceback (most recent call last): admin(31507): File "/opt/mailman-2.1.7/scripts/driver", line 101, in run_main admin(31507): main() admin(31507): File "/opt/mailman-2.1.7/Mailman/Cgi/admin.py", line 197, in main admin(31507): show_results(mlist, doc, category, subcat, cgidata) admin(31507): File "/opt/mailman-2.1.7/Mailman/Cgi/admin.py", line 497, in show_results admin(31507): form.AddItem(membership_options(mlist, subcat, cgidata, doc, form)) admin(31507): File "/opt/mailman-2.1.7/Mailman/Cgi/admin.py", line 869, in membership_options admin(31507): all = [_m.encode() for _m in mlist.getMembers()] admin(31507): UnicodeError: ASCII decoding error: ordinal not in range(128) admin(31507): [----- Python Information -----] admin(31507): sys.version = 2.2.3 (#1, Nov 11 2003, 17:44:56) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] admin(31507): sys.executable = /usr/bin/python2 admin(31507): sys.prefix = /usr admin(31507): sys.exec_prefix = /usr admin(31507): sys.path = /usr admin(31507): sys.platform = linux2 ---------------------------------------------------------------------- >Comment By: Andreas Thienemann (ixsnet) Date: 2006-04-28 21:32 Message: Logged In: YES user_id=1450459 It seems, the problem is caused by an illegal email address "marionmÃ¼ller(a)t-online.de". And yes, this was an upgrade from 2.0.x. Would an illegal address such as this be filtered nowadays? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-04-17 01:51 Message: Logged In: YES user_id=1123998 Did you just upgrade from Mailman 2.1.2 or older? It appears that this list has one or more members with (invalid?) non-ascii characters in their email address. I think any version from 2.1.3 on would throw this exception, and no recent version would allow the address to be added. You might try something like bin/list_members listname | egrep '[^[:alnum:]@.-]' to find the offending address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1471487&group_…

1 0

[ mailman-Feature Requests-1234579 ] hiding e-mail addresses in public archive
by SourceForge.net April 26, 2006

April 26, 2006

Feature Requests item #1234579, was opened at 2005-07-08 05:13 Message generated for change (Comment added) made by eht16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1234579&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: None Priority: 5 Submitted By: Abracode (abracode) Assigned to: Nobody/Anonymous (nobody) Summary: hiding e-mail addresses in public archive Initial Comment: I would love to see an option to hide e-mail addresses of senders in the public archive - only in the archive and only e-mails, not names. Simple e-mail obfuscation (like joe at schmo.com) is not good enough nowadays with more and more advanced/malicious e-mail harvesters. Thanks, Tom ---------------------------------------------------------------------- Comment By: eht16 (eht16) Date: 2006-04-26 14:57 Message: Logged In: YES user_id=1117045 As a workaround I modified some code in HyperArch.py. The patch is available at http://www.uvena.de/patches/mailman_hide_email.patch. Surely, it can be made better, but I'm no python hacker and it just works for the moment. I patched mailman version 2.1.5. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-04-19 20:38 Message: Logged In: YES user_id=12800 Please add this as a comment to the Mailman 2.2 wiki page: http://wiki.list.org/display/DEV/Mailman+2.2 The idea is to implement all archive access as a dynamic process (cgi) and then we'll be able to modify the obfuscation algorithm on the fly as older methods become obsolete. ---------------------------------------------------------------------- Comment By: eht16 (eht16) Date: 2006-04-19 20:29 Message: Logged In: YES user_id=1117045 I also need this feature. Are there any news about it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1234579&group_…

1 0

[ mailman-Feature Requests-1156871 ] Facilitate delivery of membership lists to listowners
by SourceForge.net April 23, 2006

April 23, 2006

Feature Requests item #1156871, was opened at 2005-03-04 11:00 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1156871&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Willie McKemie (mckemie) Assigned to: Nobody/Anonymous (nobody) Summary: Facilitate delivery of membership lists to listowners Initial Comment: Seemingly, customers of hosting services that offer MailMan have no convenient way to backup list memberships. list_members is generally not accessible. A email delivered "who" command does not deliver addresses that are hidden. Addresses can not be globally un-hidden. Web page presented membeship lists are available only in small batches. Possible solutions: 1) a "who" command or replacement that deliveries the entire membershiip list 2) a, possiblly temorary, global "un-hiding" of addresses so that "who" will supply the entire membership list 3) a web page option that will delivery the entire list by email or other means. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-04-23 11:32 Message: Logged In: YES user_id=1123998 Note that there are scripts available for "screen scraping" the admin Membership pages to get a complete list including if desired, all the members settings except language. See the FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.062.htp I understand this isn't an implementation of the request, but it does provide a work around. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2005-03-15 02:36 Message: Logged In: YES user_id=564396 another (in my opinion: good) idea would be the ability to additionally extract the per-list settings of the subscribed users (e.g. if they have set their "no-mail" flag) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1156871&group_…

1 0

[ mailman-Patches-943827 ] true virtual hosting patch for 2.1
by SourceForge.net April 22, 2006

April 22, 2006

Patches item #943827, was opened at 2004-04-29 02:57 Message generated for change (Comment added) made by tbble You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Nobody/Anonymous (nobody) Summary: true virtual hosting patch for 2.1 Initial Comment: [copy of the mail sent to -developpers@] We developped a reliable solution for running lists with the same name on different domains on the same Mailman installation. I implemented that on top of the Mailman 2.1.1-5.1 Debian stable package. All that is needed is to patch 2 files (bin/newlist, Mailman/MailList.py) in the mailman install, and here is the patch: http://bugs.koumbit.net/file_download.php?file_id=3&type=bug There's only one caveat right now: Mailman/Cgi/create.py might need to get patched too, but I haven't got around looking at it yet, and it "just works", for now. I don't know what's the current status of virtual hosting support on Mailman, but this patch is a simple hack that should bring joy in the homes of all Mailman admins around the world. :) I got my inspiration and part of the code from: http://mithrandr.moria.org/blog/139.html All it does is to add the domain to the internal_name() of a list. The real_name is kept as is, and the getListAddress() does the Right Thing. This makes Mailman generate aliases like: list-example.com: "|/var/lib/mailman/mail/mailman post list-example.com" Care will have to be taken on the MTA side to map those list-example.com to list(a)example.com. We are using alternc.org to manage our server, so we are using LDAP, so everything went pretty smoothly. :) But I guess it will require some magic on the Postfix side or something... Cheers, A. PS: for those wanting to see more, you can come to our Wiki: http://koumbit.net/wiki/VirtualMailman You'll probably have a little trouble finding your way if you don't read french though. :) Babelfish might help, haven't tried. ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2006-04-22 21:48 Message: Logged In: YES user_id=87909 Crud, wrapping... The changes are all on one line. ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2006-04-22 21:47 Message: Logged In: YES user_id=87909 minfrin, create it as listname-domain or try this patch: diff -urNad mailman-2.1.5/Mailman/Cgi/create.py /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py --- mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22 20:58:10.324872941 +1000 +++ /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22 21:13:31.596133649 +1000 @@ -184,7 +184,7 @@ oldmask = os.umask(002) try: try: - mlist.Create(listname, owner, pw, langs, emailhost) + mlist.Create("%s@%s" % (listname,hostname), owner, pw, langs, emailhost) finally: os.umask(oldmask) except Errors.EmailAddressError, s: Which will add the '@domain' to the listname before passing it to mlist.Create, which the patch changes to deal with '@' the way we want. ---------------------------------------------------------------------- Comment By: Graham Leggett (minfrin) Date: 2006-03-18 07:39 Message: Logged In: YES user_id=129704 I tried the patch at http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch and it applied cleanly to mailman as provided by RHEL4. I tried to create a list called "list(a)domain1.com", but this failed with the error "Error: List name must not include "@"". Does this patch have any sort of instructions anywhere? ---------------------------------------------------------------------- Comment By: Arnaud Lavrard (arnaudlavrard) Date: 2005-07-20 23:52 Message: Logged In: YES user_id=1315788 I ported the patch to mailman 2.1.5 : http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2005-03-17 07:40 Message: Logged In: YES user_id=246797 I have ported the patch to 2.1.4, no news on 2.1.5 yet. I have also put the patch in a seperate CVS server. Fetch all the goods there: http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-vi… http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-vi… I've also updated the 2.1.1 patch to fix the list-id, so I delete the attachment, fetch the patch straight from our CVS for the latest fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i…

1 0

[ mailman-Patches-943827 ] true virtual hosting patch for 2.1
by SourceForge.net April 22, 2006

April 22, 2006

Patches item #943827, was opened at 2004-04-29 02:57 Message generated for change (Comment added) made by tbble You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Nobody/Anonymous (nobody) Summary: true virtual hosting patch for 2.1 Initial Comment: [copy of the mail sent to -developpers@] We developped a reliable solution for running lists with the same name on different domains on the same Mailman installation. I implemented that on top of the Mailman 2.1.1-5.1 Debian stable package. All that is needed is to patch 2 files (bin/newlist, Mailman/MailList.py) in the mailman install, and here is the patch: http://bugs.koumbit.net/file_download.php?file_id=3&type=bug There's only one caveat right now: Mailman/Cgi/create.py might need to get patched too, but I haven't got around looking at it yet, and it "just works", for now. I don't know what's the current status of virtual hosting support on Mailman, but this patch is a simple hack that should bring joy in the homes of all Mailman admins around the world. :) I got my inspiration and part of the code from: http://mithrandr.moria.org/blog/139.html All it does is to add the domain to the internal_name() of a list. The real_name is kept as is, and the getListAddress() does the Right Thing. This makes Mailman generate aliases like: list-example.com: "|/var/lib/mailman/mail/mailman post list-example.com" Care will have to be taken on the MTA side to map those list-example.com to list(a)example.com. We are using alternc.org to manage our server, so we are using LDAP, so everything went pretty smoothly. :) But I guess it will require some magic on the Postfix side or something... Cheers, A. PS: for those wanting to see more, you can come to our Wiki: http://koumbit.net/wiki/VirtualMailman You'll probably have a little trouble finding your way if you don't read french though. :) Babelfish might help, haven't tried. ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2006-04-22 21:47 Message: Logged In: YES user_id=87909 minfrin, create it as listname-domain or try this patch: diff -urNad mailman-2.1.5/Mailman/Cgi/create.py /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py --- mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22 20:58:10.324872941 +1000 +++ /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22 21:13:31.596133649 +1000 @@ -184,7 +184,7 @@ oldmask = os.umask(002) try: try: - mlist.Create(listname, owner, pw, langs, emailhost) + mlist.Create("%s@%s" % (listname,hostname), owner, pw, langs, emailhost) finally: os.umask(oldmask) except Errors.EmailAddressError, s: Which will add the '@domain' to the listname before passing it to mlist.Create, which the patch changes to deal with '@' the way we want. ---------------------------------------------------------------------- Comment By: Graham Leggett (minfrin) Date: 2006-03-18 07:39 Message: Logged In: YES user_id=129704 I tried the patch at http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch and it applied cleanly to mailman as provided by RHEL4. I tried to create a list called "list(a)domain1.com", but this failed with the error "Error: List name must not include "@"". Does this patch have any sort of instructions anywhere? ---------------------------------------------------------------------- Comment By: Arnaud Lavrard (arnaudlavrard) Date: 2005-07-20 23:52 Message: Logged In: YES user_id=1315788 I ported the patch to mailman 2.1.5 : http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2005-03-17 07:40 Message: Logged In: YES user_id=246797 I have ported the patch to 2.1.4, no news on 2.1.5 yet. I have also put the patch in a seperate CVS server. Fetch all the goods there: http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-vi… http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-vi… I've also updated the 2.1.1 patch to fix the list-id, so I delete the attachment, fetch the patch straight from our CVS for the latest fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i…

1 0

[ mailman-Feature Requests-1472242 ] search user subscription lists
by SourceForge.net April 21, 2006

April 21, 2006

Feature Requests item #1472242, was opened at 2006-04-18 04:58 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1472242&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: alcarobe (alcarobe) Assigned to: Nobody/Anonymous (nobody) Summary: search user subscription lists Initial Comment: mailman now allows to find all or a dedicated mailing list another useful search facility should be added to allow people to find all the lists where they are subscribed to ---------------------------------------------------------------------- Comment By: alcarobe (alcarobe) Date: 2006-04-20 05:03 Message: Logged In: YES user_id=1504579 the "List my other subscriptions" search was indeed what I was looking for, thanks for the fast reply ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-04-18 12:16 Message: Logged In: YES user_id=1123998 If you are asking for something other that the "List my other subscriptions" search that currently exists on the user options page, please clarify what it is you want. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1472242&group_…

1 0

[ mailman-Feature Requests-1474203 ] A junk Mail button would be great
by SourceForge.net April 21, 2006

April 21, 2006

Feature Requests item #1474203, was opened at 2006-04-21 09: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=1474203&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Narishkup (mikekatz) Assigned to: Nobody/Anonymous (nobody) Summary: A junk Mail button would be great Initial Comment: I would love a junk mail button in the administrators review of defered messages section. That button would with one click delete the message and put the senders domain on the rejected domain list. Currently it is a 4 click proccess to put each ban people but domains are even harder to restrict. This should be a button in addition to the existing choices so that less drastic action could also be taken. Thanks so mucch fo a great product. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1474203&group_…

1 0