Mailman 3 March 2004 - 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-Patches-871062 ] A MemberAdaptor for LDAP-based membership
by SourceForge.net March 31, 2004

March 31, 2004

Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by fubarobfusco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- >Comment By: K. A. Krueger (fubarobfusco) Date: 2004-03-30 22:59 Message: Logged In: YES user_id=944208 Well, Mailman does a lot more than just keep track of who's subscribed -- for instance, restricted posters, list moderation, archiving. LDAPMemberships is not meant to be useful for Internet mailing lists with people signing up for them, but rather for institutional or enterprise lists. These have a lot of the same requirements (moderation etc.) as Internet lists, but don't need subscription/unsubscription -- since employees are usually required to be on them. My workplace is using this (well, actually a later version than the one I've uploaded here) as a replacement for an LDAP mailing-list feature in Netscape SuiteSpot now that we have migrated away from that system. We -also- use LDAP-based aliases (in Postfix, not Sendmail, actually) -- but for some things we need the moderation and other facilities that Mailman has. For instance, we have an announcements list that goes to all regular employees. A simple alias would allow anyone to send stuff to it, and certain senior scientists would love to send big PDFs to everyone. A Mailman list with LDAPMemberships can have sender restrictions so that only our IT Director and our mail systems admin can approve posts to it. Archiving is also quite useful for announcements lists. ---------------------------------------------------------------------- Comment By: Chris Drumgoole (cdrum) Date: 2004-03-30 22:38 Message: Logged In: YES user_id=429400 why use this when you can just use Sendmail's LDAP -> Alias functions? No need for a mailing list program like mailman.. right? ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-26 15:35 Message: Logged In: YES user_id=944208 Yet another new version (0.3) of LDAPMemberships.py. This one fixes some ambiguities with LDAP record handling, particularly for users with multiple "cn" values, and those who send mail as their "mailalternateaddress" field address rather than their "mail" field. If anyone is actually using this, please email me and let me know :) ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 11:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i…

1 0

[ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership
by SourceForge.net March 31, 2004

March 31, 2004

Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by cdrum You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- Comment By: Chris Drumgoole (cdrum) Date: 2004-03-30 22:38 Message: Logged In: YES user_id=429400 why use this when you can just use Sendmail's LDAP -> Alias functions? No need for a mailing list program like mailman.. right? ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-26 15:35 Message: Logged In: YES user_id=944208 Yet another new version (0.3) of LDAPMemberships.py. This one fixes some ambiguities with LDAP record handling, particularly for users with multiple "cn" values, and those who send mail as their "mailalternateaddress" field address rather than their "mail" field. If anyone is actually using this, please email me and let me know :) ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 11:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i…

1 0

[ mailman-Bugs-926034 ] Crashes on encoding errors
by SourceForge.net March 30, 2004

March 30, 2004

Bugs item #926034, was opened at 2004-03-30 16:06 Message generated for change (Comment added) made by heikkilevanto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=926034&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Heikki Levanto (heikkilevanto) Assigned to: Nobody/Anonymous (nobody) Summary: Crashes on encoding errors Initial Comment: I have seen crashes on some Danish-speaking lists, where users put Danish characters in the headers. It seems to depend on the encoding used. I do not have much statistical material, as I can not produce the crash myself, but have to ask some of the "troublemakers" to post a test message every time I need to see the crash. Here is a traceback: Mar 30 15:17:03 2004 (339) Uncaught runner exception: unknown encoding Mar 30 15:17:03 2004 (339) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 75, in process prefix_subject(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject h.append(s, c) File "/home/mailman/pythonlib/email/Header.py", line 285, in append s = s.encode(outcodec, errors) LookupError: unknown encoding The sad thing is that these mails just disappear, and my users wonder why they can not post to the list. Even a bounce would be to prefer, or at least something in the log that tells whom I could send apologies to... Here are the headers of one offending message, as sent directly to my mailbox: >From cfb(a)pikobryg.dk Tue Mar 30 15:47:23 2004 Return-path: <cfb(a)pikobryg.dk> Envelope-to: heikki(a)indexdata.dk Delivery-date: Tue, 30 Mar 2004 15:47:23 +0200 Received: from smtp020.tiscali.dk ([212.54.64.104]) by bagel.index with esmtp (Exim 3.35 #1 (Debian)) id 1B8JaM-0003l8-00 for <heikki(a)indexdata.dk>; Tue, 30 Mar 2004 15:47:22 +0200 Received: from pikobryg.dk (213.237.80.191.adsl.vbr.worldonline.dk [213.237.80.191]) by smtp020.tiscali.dk (8.12.10/8.12.10) with ESMTP id i2UDlKsm001688 for <heikki(a)indexdata.dk>; Tue, 30 Mar 2004 15:47:20 +0200 (MEST) Message-ID: <40697A66.5030604(a)pikobryg.dk> Date: Tue, 30 Mar 2004 15:47:18 +0200 From: "Christian F. Behrens" <cfb(a)pikobryg.dk> Reply-To: cfb(a)pikobryg.dk Organization: Pikobryg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: da, en-us, en MIME-Version: 1.0 To: heikki(a)indexdata.dk Subject: Korrektion af =?windows-1252?Q?sukkerm=E6ngde_til_den_sids?= =?windows-1252?Q?te_nadver?= Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp020.tiscali.dk id i2UDlKsm001688 Note that the subject line carries encoding "windows-1252", which comes from Mime-Autoconversion at tiscali.dk. The sender claims (and I believe him) that in his end the subject line looks something like this: Subjekt: Test mail encoded =?ISO-8859-1?Q?=5B=E6=F8=E5_=C6=C5=D8=5D?= I am not asking mailman to support mysterious windows code pages, but if it could handle unknown encodings better (ie without crashing) I would be much happier. I am also sending a polite letter to tiscali.dk, asking them to get their act together. ---------------------------------------------------------------------- >Comment By: Heikki Levanto (heikkilevanto) Date: 2004-03-30 16:51 Message: Logged In: YES user_id=854974 Sorry, forgot to specify that I run on a Debian/Stable, with hand-installed mailman 2.1.2 from June 2003. It may also be that the original mail in my example was written in MS-Word, and pasted from there to Mozilla. Maybe that has something to do with the encoding, perhaps more than tiscali.dk's autoconversion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=926034&group_i…

1 0

[ mailman-Bugs-926034 ] Crashes on encoding errors
by SourceForge.net March 30, 2004

March 30, 2004

Bugs item #926034, was opened at 2004-03-30 16:06 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=926034&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Heikki Levanto (heikkilevanto) Assigned to: Nobody/Anonymous (nobody) Summary: Crashes on encoding errors Initial Comment: I have seen crashes on some Danish-speaking lists, where users put Danish characters in the headers. It seems to depend on the encoding used. I do not have much statistical material, as I can not produce the crash myself, but have to ask some of the "troublemakers" to post a test message every time I need to see the crash. Here is a traceback: Mar 30 15:17:03 2004 (339) Uncaught runner exception: unknown encoding Mar 30 15:17:03 2004 (339) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 75, in process prefix_subject(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject h.append(s, c) File "/home/mailman/pythonlib/email/Header.py", line 285, in append s = s.encode(outcodec, errors) LookupError: unknown encoding The sad thing is that these mails just disappear, and my users wonder why they can not post to the list. Even a bounce would be to prefer, or at least something in the log that tells whom I could send apologies to... Here are the headers of one offending message, as sent directly to my mailbox: >From cfb(a)pikobryg.dk Tue Mar 30 15:47:23 2004 Return-path: <cfb(a)pikobryg.dk> Envelope-to: heikki(a)indexdata.dk Delivery-date: Tue, 30 Mar 2004 15:47:23 +0200 Received: from smtp020.tiscali.dk ([212.54.64.104]) by bagel.index with esmtp (Exim 3.35 #1 (Debian)) id 1B8JaM-0003l8-00 for <heikki(a)indexdata.dk>; Tue, 30 Mar 2004 15:47:22 +0200 Received: from pikobryg.dk (213.237.80.191.adsl.vbr.worldonline.dk [213.237.80.191]) by smtp020.tiscali.dk (8.12.10/8.12.10) with ESMTP id i2UDlKsm001688 for <heikki(a)indexdata.dk>; Tue, 30 Mar 2004 15:47:20 +0200 (MEST) Message-ID: <40697A66.5030604(a)pikobryg.dk> Date: Tue, 30 Mar 2004 15:47:18 +0200 From: "Christian F. Behrens" <cfb(a)pikobryg.dk> Reply-To: cfb(a)pikobryg.dk Organization: Pikobryg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: da, en-us, en MIME-Version: 1.0 To: heikki(a)indexdata.dk Subject: Korrektion af =?windows-1252?Q?sukkerm=E6ngde_til_den_sids?= =?windows-1252?Q?te_nadver?= Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp020.tiscali.dk id i2UDlKsm001688 Note that the subject line carries encoding "windows-1252", which comes from Mime-Autoconversion at tiscali.dk. The sender claims (and I believe him) that in his end the subject line looks something like this: Subjekt: Test mail encoded =?ISO-8859-1?Q?=5B=E6=F8=E5_=C6=C5=D8=5D?= I am not asking mailman to support mysterious windows code pages, but if it could handle unknown encodings better (ie without crashing) I would be much happier. I am also sending a polite letter to tiscali.dk, asking them to get their act together. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=926034&group_i…

1 0

[ mailman-Bugs-781977 ] Attempt to invoke directory as as script
by SourceForge.net March 30, 2004

March 30, 2004

Bugs item #781977, was opened at 2003-08-02 14:46 Message generated for change (Comment added) made by winnegan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=781977&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: Attempt to invoke directory as as script Initial Comment: Package: mailman Version: 2.1.2-7 Log entries like the following appear with some regularity. ,----[ Excerpt from: /var/log/apache-ssl ] [Fri Aug 1 15:54:12 2003] [error] [client 128.242.232.130] attempt to invoke directory as script: /usr/lib/cgi-bin/mailman `---- -- System Information Debian Release: 3.0 Kernel Version: Linux lists 2.4.20-bf2.4 #1 Wed Dec 25 13:17:08 UTC 2002 i686 GNU/Linux Versions of the packages mailman depends on: ii cron 3.0pl1-72 management of regular background processing ii debconf 1.0.32 Debian configuration management system ii libc6 2.3.1-17 GNU C Library: Shared libraries and Timezone ii logrotate 3.5.9-8 Log rotation utility ii pwgen 2.03-1 Automatic Password generation ii python 2.2.3-3 An interactive high-level object-oriented la ii ucf 0.18 Update Configuration File: preserves user ch exim Not installed or no info ii postfix 2.0.13-2003070 A high-performance mail transport agent ^^^ (Provides virtual package mail-transport-agent) apache Not installed or no info ii apache-ssl 1.3.27.0-2 Versatile, high-performance HTTP server with ^^^ (Provides virtual package httpd) ---------------------------------------------------------------------- Comment By: Bernd S. Brentrup (winnegan) Date: 2004-03-30 10:33 Message: Logged In: YES user_id=168018 Has this been submitted to the Debian BTS? I can't find any reference. (I'm a co-maintainer of Debian's mailman package) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=781977&group_i…

1 0

[ mailman-Bugs-925337 ] quoted-printable encoding in web archive
by SourceForge.net March 29, 2004

March 29, 2004

Bugs item #925337, was opened at 2004-03-29 16:55 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=925337&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: quoted-printable encoding in web archive Initial Comment: Mailman 2.1.2 received a mail with charset windows-1252 and Content-Transfer-Encoding: quoted-printable The email is attached in mbox format. In the web archive at http://intevation.de/pipermail/mapserver-de/2004-March/000176.html some characters are still in their =XY encoding. Other mails with windows-1252 or quoted-printable work fine, but I don't have another example of both in a single mail. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=925337&group_i…

1 0

[ mailman-Bugs-925319 ] SMTP error code 550 not seen as bounce
by SourceForge.net March 29, 2004

March 29, 2004

Bugs item #925319, was opened at 2004-03-29 09:15 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=925319&group_i… Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Cashwell (cashwell) Assigned to: Nobody/Anonymous (nobody) Summary: SMTP error code 550 not seen as bounce Initial Comment: >From the collection of uncaught bounces I'm dealing with it seems that Mailman does not treat an unknown user account as a fatal error (despite the 5xx code). This must be a bug. It's a real headache as these clearly fatal errors constitute more than 80% of the unchaught bounces I must wade through. Here are several examples (and I have many more if you need them!): From: E500_SMTP_Mail_Service(a)lists.sld.tld Date: March 25, 2004 11:06:51 PM EST To: <thelist-bounces(a)lists.sld.tld> Subject: Returned Mail - Error During Delivery ------ Failed Recipients ------ <baduser(a)pop400.gsfc.nasa.gov>: Requested action not taken: mailbox unavailable. [SMTP Error Code 550] -------- Returned Mail -------- ..... From: "InterScan MSS Notification" <interscan(a)gao.gov> Date: March 25, 2004 11:08:25 PM EST To: <thelist-bounces(a)lists.sld.tld> Subject: Mail could not be delivered This message was AUTO GENERATED. Please DO NOT RESPOND to this EMAIL. Sent <<< RCPT TO:<baduser.sro(a)gao.gov> Received >>> 550 5.1.1 <baduser.sro(a)gao.gov>... user unknown Unable to deliver message to <baduser.sro(a)gao.gov> (and other recipients in the same domain). ..... From: "InterScan MSS Notification" <interscan(a)gao.gov> Date: March 25, 2004 11:08:25 PM EST To: <thelist-bounces(a)lists.sld.tld> Subject: Mail could not be delivered This message was AUTO GENERATED. Please DO NOT RESPOND to this EMAIL. Sent <<< RCPT TO:<baduser.nsiad(a)gao.gov> Received >>> 550 5.1.1 <baduser.nsiad(a)gao.gov>... user unknown Unable to deliver message to <baduser.nsiad(a)gao.gov> (and other recipients in the same domain). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=925319&group_i…

1 0

[ mailman-Patches-923428 ] VERP subscription confirmations
by SourceForge.net March 25, 2004

March 25, 2004

Patches item #923428, was opened at 2004-03-25 15:16 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=923428&group_i… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Gordon Rowell (gordonr) Assigned to: Nobody/Anonymous (nobody) Summary: VERP subscription confirmations Initial Comment: From: Gordon Rowell <gordonr(a)gormand.com.au> To: mailman-developers(a)python.org [...] On Thu, Feb 05, 2004 at 09:44:05PM -0500, Gordon Rowell <gordonr(a)gormand.com.au> wrote: > If I enable VERP_CONFIRMATIONS and "Invite" > someone from the admin page, I get a VERP > invite and a "nice" Subject line: > [...] > It appears that the VERP confirmations are only > partially implemented, but maybe I've missed > something. > [...] The attached patch seems to DTRT for me. Gordon ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=923428&group_i…

1 0

[ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option
by SourceForge.net March 25, 2004

March 25, 2004

Feature Requests item #923122, was opened at 2004-03-25 14:01 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=923122&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl(a)freefriends.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i…

1 0