Mailman 3 June 2004 - Mailman-coders

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

19 Aug '22

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-Feature Requests-983002 ] Add names to roster
by SourceForge.net 30 Jun '04

30 Jun '04

Feature Requests item #983002, was opened at 2004-06-30 16:40 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=983002&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason Diceman (jasondiceman) Assigned to: Nobody/Anonymous (nobody) Summary: Add names to roster Initial Comment: On /mailman/roster/listname it would be great to see names beside email email. Also, unless the user is logged in as admin, each subscriber should not link to their admin page. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=983002&group_i…

1 0

[ mailman-Patches-982644 ] command line util for setting member options
by SourceForge.net 30 Jun '04

30 Jun '04

Patches item #982644, was opened at 2004-06-30 10:18 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=982644&group_i… Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: fvm (mfvmheise) Assigned to: Nobody/Anonymous (nobody) Summary: command line util for setting member options Initial Comment: I missed a command line tool for setting user options, so I modified remove_members to fit my needs. The tool won't check whether a list is digestable or not, if it is not and you set digest to 1, the script will fail with an uncaught exception. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=982644&group_i…

1 0

[ mailman-Bugs-981188 ] Cannot cancel subscription on confirmation page
by SourceForge.net 28 Jun '04

28 Jun '04

Bugs item #981188, was opened at 2004-06-28 13:32 Message generated for change (Comment added) made by mranner You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=981188&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: mranner (mranner) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot cancel subscription on confirmation page Initial Comment: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/usr/local/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, Jan 10 2004, 17:19:45) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://secure.inforum.at/mailman/confirm/vinegar-newsletter/c082c7391977d2… SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_gzip/1.3.26.1a DAV/1.0.3 FrontPage/5.0.2.2623 mod_ssl/2.8.18 OpenSSL/0.9.7c PHP/4.3.5 SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE Apache/1.3.31 Server at secure.inforum.at Port 443 REQUEST_METHOD POST PATH_INFO /vinegar-newsletter SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 121 HTTP_ACCEPT_CHARSET iso-8859-15, utf-8;q=0.5, *;q=0.5 HTTP_USER_AGENT Mozilla/5.0 (compatible; Konqueror/3.2; FreeBSD; X11; i386) (KHTML, like Gecko) HTTP_CONNECTION Keep-Alive SERVER_NAME secure.inforum.at REMOTE_ADDR 213.229.17.146 PATH_TRANSLATED /www/virtual/secure.inforum.at/data/vinegar-newsletter SERVER_PORT 443 SERVER_ADDR 195.58.178.86 DOCUMENT_ROOT /www/virtual/secure.inforum.at/data HTTP_PRAGMA no-cache PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/confirm SERVER_ADMIN webmaster(a)inforum.at HTTP_HOST secure.inforum.at HTTPS on HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/confirm/vinegar-newsletter HTTP_ACCEPT text/html, image/jpeg, image/png, text/*, image/*, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 49579 HTTP_ACCEPT_LANGUAGE de, en CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING x-gzip, x-deflate, gzip, deflate UNIQUE_ID QOAAWMM6slYAAD56QB4 ---------------------------------------------------------------------- >Comment By: mranner (mranner) Date: 2004-06-28 13:34 Message: Logged In: YES user_id=1072505 cannot cancel "pending" subscribtion on confirmation page ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=981188&group_i…

1 0

[ mailman-Bugs-981188 ] Cannot cancel subscription on confirmation page
by SourceForge.net 28 Jun '04

28 Jun '04

Bugs item #981188, was opened at 2004-06-28 13:32 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=981188&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: mranner (mranner) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot cancel subscription on confirmation page Initial Comment: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/usr/local/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, Jan 10 2004, 17:19:45) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://secure.inforum.at/mailman/confirm/vinegar-newsletter/c082c7391977d2… SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_gzip/1.3.26.1a DAV/1.0.3 FrontPage/5.0.2.2623 mod_ssl/2.8.18 OpenSSL/0.9.7c PHP/4.3.5 SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE Apache/1.3.31 Server at secure.inforum.at Port 443 REQUEST_METHOD POST PATH_INFO /vinegar-newsletter SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 121 HTTP_ACCEPT_CHARSET iso-8859-15, utf-8;q=0.5, *;q=0.5 HTTP_USER_AGENT Mozilla/5.0 (compatible; Konqueror/3.2; FreeBSD; X11; i386) (KHTML, like Gecko) HTTP_CONNECTION Keep-Alive SERVER_NAME secure.inforum.at REMOTE_ADDR 213.229.17.146 PATH_TRANSLATED /www/virtual/secure.inforum.at/data/vinegar-newsletter SERVER_PORT 443 SERVER_ADDR 195.58.178.86 DOCUMENT_ROOT /www/virtual/secure.inforum.at/data HTTP_PRAGMA no-cache PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/confirm SERVER_ADMIN webmaster(a)inforum.at HTTP_HOST secure.inforum.at HTTPS on HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/confirm/vinegar-newsletter HTTP_ACCEPT text/html, image/jpeg, image/png, text/*, image/*, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 49579 HTTP_ACCEPT_LANGUAGE de, en CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING x-gzip, x-deflate, gzip, deflate UNIQUE_ID QOAAWMM6slYAAD56QB4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=981188&group_i…

1 0

[ mailman-Bugs-979631 ] Better aliases generation for Postfix (webmin)
by SourceForge.net 25 Jun '04

25 Jun '04

Bugs item #979631, was opened at 2004-06-25 12:05 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=979631&group_i… Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christophe Chisogne (wombachi) Assigned to: Nobody/Anonymous (nobody) Summary: Better aliases generation for Postfix (webmin) Initial Comment: The data/aliases file generated by MTA/Postfix.py can be slightly improved, notably when using webmin (little patch below). I didnt check if alias generation with other MTAs have the same problem. Postfix.py generates lines like # STANZA START: <listname> # CREATED: <date> (...) # STANZA END: Problem is the "# CREATED:" line. To disable a mail alias, some admin simply put a '# ' in front of that alias. So that line could be interpreted as a user 'CREATED' that has been disabled. And webmin (v1.150, last one) just do that in the postfix module, displaying wrong infos for postfix aliases. That webmin module use a regex to check these 'disabled' aliases with this Perl code (sorry, not Python:) if (/^(#*)\s*([^:$ \t]+)\s*:\s*(.*)$/) The '# STANZA' lines dont match, so it's ok. But the '# CREATED:' line do match, causing wrong results in webmin. A simple solution is to replace the 'CREATED:' word with two word, by example 'ALIASES CREATED:' MTA/Postfix.py line 108 (mailman-2.1.5) print >> fp, '# CREATED:', time.ctime(time.time()) proposed change print >> fp, '# ALIASES CREATED:', time.ctime(time.time()) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=979631&group_i…

1 0

[ mailman-Bugs-975145 ] Description of -owner field is wrong
by SourceForge.net 24 Jun '04

24 Jun '04

Bugs item #975145, was opened at 2004-06-18 08:20 Message generated for change (Comment added) made by hgerstung You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko (hgerstung) Assigned to: Nobody/Anonymous (nobody) Summary: Description of -owner field is wrong Initial Comment: In the web interface, list administration section "General options" there is a field called "umbrella_member_suffix", which is "-owner" by default. In the detailed help for this field it reads: When "umbrella_list" is set to indicate that this list has other mailing lists as members, then administrative notices like confirmations and password reminders need to not be sent to the member list addresses, but rather to the owner of those member lists. In that case, the value of this setting is appended to the member's account name for such notices. `-owner' is the typical choice. This setting has no effect when "umbrella_list" is "No". The last sentence indicates that this field is not used anywhere when the field umbrella_list is set to No. This is wrong, because the owner address is used in automatic replies sent to non-subscripted users trying to send a mail to the list, which is automatically rejected. So, I see two possibilities: Change the description of the field, saying that this suffix also is used for building the list owner address (e.g. list "xxx" means a xxx-owner@domain mail address) or (my favourite way) introduce a new field for setting up a list owner address AND be able to edit this "your message has been rejected" mail message (e.g. using a template for this), because even when I edit the LC_MESSAGES file, I have no chance to edit the english texts without diving into the sources, which makes upgrades a crap. Great software, keep on! Kind regards, Heiko ---------------------------------------------------------------------- >Comment By: Heiko (hgerstung) Date: 2004-06-24 09:49 Message: Logged In: YES user_id=1009520 Sorry, but I did not get it. Is there any other field which is used to setup the list-owner address used in several messages or procedures? The field "owner" is used to setup "The list administrator email addresses." , so please let me suggest to use this field (e.g. the first entry) instead of the "list-owner" address which - this is unusual for mailman - seems to be hardcoded in sourcecode and can not be altered. This looks like a special requirement for me, but I do not want to have an alias "-owner" for every list I run, a single mail address used to let the list members know where they can get further help would be sufficient for me. So, please consider this as a humble request for feature: Do not use a hardcoded "-owner"-alias for creating reject messages or other types of error/notification messages, use the first "owner" address entry OR Create and use a template for those messages, which could easily be customized by everyone - even for the english language texts (which is not possible for the LC_MESSAGES, at the moment) Thank you very much for taking the time to answer me, kind regards, Heiko ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-06-24 09:21 Message: Logged In: YES user_id=75166 You observation is incorrect because the description is about the use of the field NOT the alias and it is NOT said that the alias specified is used for no other purpose. The -owner alias is defined on all lists and has other uses. The use of the -owner alias for other purposes is not directly related to its use as a target for certain types of message when the list is marked as being an umbrella list. If you do not want the -owner alias used this way when the list is an umbrella list you can define an alternative alias, -stuff for example, setting the field on the GUI accordingly. You can then specify what the incoming MTA is to do with messages addressed to the -stuff alias in whatever way you want (> /dev/null for instance) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_i…

1 0

[ mailman-Bugs-975145 ] Description of -owner field is wrong
by SourceForge.net 24 Jun '04

24 Jun '04

Bugs item #975145, was opened at 2004-06-18 06:20 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko (hgerstung) Assigned to: Nobody/Anonymous (nobody) Summary: Description of -owner field is wrong Initial Comment: In the web interface, list administration section "General options" there is a field called "umbrella_member_suffix", which is "-owner" by default. In the detailed help for this field it reads: When "umbrella_list" is set to indicate that this list has other mailing lists as members, then administrative notices like confirmations and password reminders need to not be sent to the member list addresses, but rather to the owner of those member lists. In that case, the value of this setting is appended to the member's account name for such notices. `-owner' is the typical choice. This setting has no effect when "umbrella_list" is "No". The last sentence indicates that this field is not used anywhere when the field umbrella_list is set to No. This is wrong, because the owner address is used in automatic replies sent to non-subscripted users trying to send a mail to the list, which is automatically rejected. So, I see two possibilities: Change the description of the field, saying that this suffix also is used for building the list owner address (e.g. list "xxx" means a xxx-owner@domain mail address) or (my favourite way) introduce a new field for setting up a list owner address AND be able to edit this "your message has been rejected" mail message (e.g. using a template for this), because even when I edit the LC_MESSAGES file, I have no chance to edit the english texts without diving into the sources, which makes upgrades a crap. Great software, keep on! Kind regards, Heiko ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-06-24 07:21 Message: Logged In: YES user_id=75166 You observation is incorrect because the description is about the use of the field NOT the alias and it is NOT said that the alias specified is used for no other purpose. The -owner alias is defined on all lists and has other uses. The use of the -owner alias for other purposes is not directly related to its use as a target for certain types of message when the list is marked as being an umbrella list. If you do not want the -owner alias used this way when the list is an umbrella list you can define an alternative alias, -stuff for example, setting the field on the GUI accordingly. You can then specify what the incoming MTA is to do with messages addressed to the -stuff alias in whatever way you want (> /dev/null for instance) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_i…

1 0

[ mailman-Bugs-975768 ] senddigests doesn't handle consecutive unparseable messages
by SourceForge.net 19 Jun '04

19 Jun '04

Bugs item #975768, was opened at 2004-06-19 09:07 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=975768&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Andreas Voegele (voegelas) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests doesn't handle consecutive unparseable messages Initial Comment: The following code fragment in send_i18n_digests in Mailman/ Handlers/ToDigest.py doesn't take into account that there could be several consecutive messages that are unparseable: msg = mbox.next() while msg is not None: if msg == '': # It was an unparseable message msg = mbox.next() [...] # Get the next message in the digest mailbox msg = mbox.next() I'm not that familiar with Python but I think that the following code should fix the problem: while 1: msg = mbox.next() if msg is None: break if msg == '': # It was an unparseable message continue [...] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975768&group_i…

1 0

[ mailman-Bugs-975145 ] Description of -owner field is wrong
by SourceForge.net 17 Jun '04

17 Jun '04

Bugs item #975145, was opened at 2004-06-18 08:20 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=975145&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko (hgerstung) Assigned to: Nobody/Anonymous (nobody) Summary: Description of -owner field is wrong Initial Comment: In the web interface, list administration section "General options" there is a field called "umbrella_member_suffix", which is "-owner" by default. In the detailed help for this field it reads: When "umbrella_list" is set to indicate that this list has other mailing lists as members, then administrative notices like confirmations and password reminders need to not be sent to the member list addresses, but rather to the owner of those member lists. In that case, the value of this setting is appended to the member's account name for such notices. `-owner' is the typical choice. This setting has no effect when "umbrella_list" is "No". The last sentence indicates that this field is not used anywhere when the field umbrella_list is set to No. This is wrong, because the owner address is used in automatic replies sent to non-subscripted users trying to send a mail to the list, which is automatically rejected. So, I see two possibilities: Change the description of the field, saying that this suffix also is used for building the list owner address (e.g. list "xxx" means a xxx-owner@domain mail address) or (my favourite way) introduce a new field for setting up a list owner address AND be able to edit this "your message has been rejected" mail message (e.g. using a template for this), because even when I edit the LC_MESSAGES file, I have no chance to edit the english texts without diving into the sources, which makes upgrades a crap. Great software, keep on! Kind regards, Heiko ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_i…

1 0