Mailman 3 February 2005 - Mailman-coders

[ mailman-Bugs-649112 ] " #" in mail address confuses mailman
by SourceForge.net 14 Feb '05

14 Feb '05

Bugs item #649112, was opened at 2002-12-05 19:59 Message generated for change (Comment added) made by effbot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649112&group_i… Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Fredrik Lundh (effbot) Assigned to: Nobody/Anonymous (nobody) Summary: "#" in mail address confuses mailman Initial Comment: someone recently managed to subscribe himself to the python.org image-sig mailing list, using an add- ress looking a bit like this one: prefix#user(a)some.com unfortunately, the web interface doesn't escape the "#" character, so the web pages for this user cannot be accessed: http://mail.python.org/mailman/options/image- sig/prefix#user--at--some.com (the browser strips off the "#" and everything after it before sending the URL to mailman...). I'm not sure what version python.org is running, but I suspect that the Barry person might be able to figure that out. cheers /F ---------------------------------------------------------------------- >Comment By: Fredrik Lundh (effbot) Date: 2005-02-14 23:16 Message: Logged In: YES user_id=38376 (if this has been fixed, feel free to close this report) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649112&group_i…

1 0

[ mailman-Bugs-1122131 ] Can't configure Reply-To: to include Poster *and* List
by SourceForge.net 14 Feb '05

14 Feb '05

Bugs item #1122131, was opened at 2005-02-13 22:14 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=1122131&group_… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Seth Teller (seth_teller) Assigned to: Nobody/Anonymous (nobody) Summary: Can't configure Reply-To: to include Poster *and* List Initial Comment: Regarding Mailman 2.1.5, in use at MIT CSAIL. I administer a class, and a mailing list "help" to which students in the class can email problem reports. The reports go to the course staff. I would like Mailman to provide the default behavior that the staff's replies go to the list (so the rest of the staff sees them) *and* to the student (so that the student sees the solution!). Yet Mailman does not seem to be able to support this behavior. My choices are to set reply-to to Poster or to List. If I set to Poster, then the default Reply behavior excludes the List. If I set to List, then neither Reply or Reply-All includes the original Poster (i.e., the student). I submit that Mailman should support a third option: Reply-To: Poster *and* List. thanks, seth teller. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1122131&group_…

1 0

[ mailman-Patches-1121257 ] adding html banners, user_id, list_id
by SourceForge.net 12 Feb '05

12 Feb '05

Patches item #1121257, was opened at 2005-02-12 08:14 Message generated for change (Comment added) made by binworkers You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1121257&group_… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: binworkers (binworkers) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: adding html banners, user_id, list_id Initial Comment: Html header/footer patch. Add to mailman 2.1.5 functionality for add html and text banners to mime messages. Added new option for these to Non-Digest category on List admin panel. Adding list_id user_id and personalize it, so they may be included in text/html footers/headers. Added script for handle unsubscribe requests which contain user_id, list_id, password. ---------------------------------------------------------------------- >Comment By: binworkers (binworkers) Date: 2005-02-12 08:34 Message: Logged In: YES user_id=1217687 authors: Main ideas and testing: adrian(a)tasdevil.com Implementation: binworkers(a)dcemail.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1121257&group_…

1 0

[ mailman-Patches-1121257 ] adding html banners, user_id, list_id
by SourceForge.net 12 Feb '05

12 Feb '05

Patches item #1121257, was opened at 2005-02-12 08: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=1121257&group_… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: binworkers (binworkers) Assigned to: Nobody/Anonymous (nobody) Summary: adding html banners, user_id, list_id Initial Comment: Html header/footer patch. Add to mailman 2.1.5 functionality for add html and text banners to mime messages. Added new option for these to Non-Digest category on List admin panel. Adding list_id user_id and personalize it, so they may be included in text/html footers/headers. Added script for handle unsubscribe requests which contain user_id, list_id, password. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1121257&group_…

1 0

[ mailman-Bugs-1120477 ] Traceback in private.py after security patch
by SourceForge.net 11 Feb '05

11 Feb '05

Bugs item #1120477, was opened at 2005-02-10 19:39 Message generated for change (Comment added) made by rgoun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_… Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Roger H. Goun (rgoun) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in private.py after security patch Initial Comment: I applied the patch at http://www.list.org/CAN-2005-0202.txt to a Mailman 2.1.4 installation and restarted the Web server. The first time I tried to access the archives for a private list using an email address that's *not* subscribed to the list, I got the traceback below. I backed out the patch and restarted the Web server. I now get the correct "Authorization failed." message. Note that for the sake of paranoia I've obfuscated my email address, changed the names of private lists, and flipped a few bits in the cookie data and remote address below. -- Roger --------------- Bug in Mailman version 2.1.4 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/private.py", line 124, in main password, username): File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: roger-no(a)spam-bcah.com Python information: Variable Value sys.version 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] sys.executable /usr/bin/python2.2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /dfnh-foo/ HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://mail.democracyfornewhampshire.com/mailman/private/dfnh-foo/ SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_python/2.7.8 Python/1.5.2 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 mod_throttle/3.1.2 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/private SERVER_ADMIN roger-no(a)spam-bcah.com SCRIPT_NAME /mailman/private SERVER_SIGNATURE Apache/1.3.27 Server at democracyfornewhampshire.com Port 80 REQUEST_METHOD POST HTTP_HOST mail.democracyfornewhampshire.com HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/private/dfnh-foo/ CONTENT_LENGTH 63 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_COOKIE dfnh-board+user+roger-no--at--spam-bcah.com=280200000069caae0b42732800000063346130393963653330656239633862643737356337626437396561663334363862343563643536; dfnh-members+admin=280200000069dcee0b42732800000033353539613836343166396565376030323966663963313435646564633734303837666366666230 SERVER_NAME democracyfornewhampshire.com REMOTE_ADDR 24.35.177.35 REMOTE_PORT 38224 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /home/roger/democracyfornewhampshire.com/html/dfnh-foo/ SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 199.125.75.14 DOCUMENT_ROOT /home/roger/democracyfornewhampshire.com/html ---------------------------------------------------------------------- >Comment By: Roger H. Goun (rgoun) Date: 2005-02-11 06:32 Message: Logged In: YES user_id=3950 I deleted cookies and tried again. This time I got the "Authorization failed." message. Sorry for the false alarm. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-10 20:33 Message: Logged In: YES user_id=67709 The security patch should have nothing to do with the trace back. Will you please try again after deleting cookies of this site? (not disable but delete existing cookies) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_…

1 0

[ mailman-Feature Requests-1120700 ] ReturnMail from max_message_size, configure attachment?
by SourceForge.net 11 Feb '05

11 Feb '05

Feature Requests item #1120700, was opened at 2005-02-11 11:58 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=1120700&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rickard Persson (ripop) Assigned to: Nobody/Anonymous (nobody) Summary: ReturnMail from max_message_size, configure attachment? Initial Comment: Hi I have a problem with "max_message_size", not the actual variable itself. My problem is with the message sent back to the admin of the list. This message has the original message included, and for me this is not a good solution. I sit on a slow connection and I guess you understand what happens :( I have lookt around but haven't found anything about it before in lists or documentations. So here comes the question: Is it possible to have a configuration option where the admin can chose if the complete original message should be attached to the message? Thus not needing to download the complete mail with the big atatchment? Tanks for all the hard work you have allready done Rickard Persson Sweden/Lappland/Lycksele ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1120700&group_…

1 0

[ mailman-Bugs-1120477 ] Traceback in private.py after security patch
by SourceForge.net 11 Feb '05

11 Feb '05

Bugs item #1120477, was opened at 2005-02-11 00:39 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Roger H. Goun (rgoun) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in private.py after security patch Initial Comment: I applied the patch at http://www.list.org/CAN-2005-0202.txt to a Mailman 2.1.4 installation and restarted the Web server. The first time I tried to access the archives for a private list using an email address that's *not* subscribed to the list, I got the traceback below. I backed out the patch and restarted the Web server. I now get the correct "Authorization failed." message. Note that for the sake of paranoia I've obfuscated my email address, changed the names of private lists, and flipped a few bits in the cookie data and remote address below. -- Roger --------------- Bug in Mailman version 2.1.4 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/private.py", line 124, in main password, username): File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: roger-no(a)spam-bcah.com Python information: Variable Value sys.version 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] sys.executable /usr/bin/python2.2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /dfnh-foo/ HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://mail.democracyfornewhampshire.com/mailman/private/dfnh-foo/ SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_python/2.7.8 Python/1.5.2 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 mod_throttle/3.1.2 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/private SERVER_ADMIN roger-no(a)spam-bcah.com SCRIPT_NAME /mailman/private SERVER_SIGNATURE Apache/1.3.27 Server at democracyfornewhampshire.com Port 80 REQUEST_METHOD POST HTTP_HOST mail.democracyfornewhampshire.com HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/private/dfnh-foo/ CONTENT_LENGTH 63 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_COOKIE dfnh-board+user+roger-no--at--spam-bcah.com=280200000069caae0b42732800000063346130393963653330656239633862643737356337626437396561663334363862343563643536; dfnh-members+admin=280200000069dcee0b42732800000033353539613836343166396565376030323966663963313435646564633734303837666366666230 SERVER_NAME democracyfornewhampshire.com REMOTE_ADDR 24.35.177.35 REMOTE_PORT 38224 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /home/roger/democracyfornewhampshire.com/html/dfnh-foo/ SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 199.125.75.14 DOCUMENT_ROOT /home/roger/democracyfornewhampshire.com/html ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-11 01:33 Message: Logged In: YES user_id=67709 The security patch should have nothing to do with the trace back. Will you please try again after deleting cookies of this site? (not disable but delete existing cookies) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_…

1 0

[ mailman-Bugs-1120477 ] Traceback in private.py after security patch
by SourceForge.net 11 Feb '05

11 Feb '05

Bugs item #1120477, was opened at 2005-02-10 19:39 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=1120477&group_… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Roger H. Goun (rgoun) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in private.py after security patch Initial Comment: I applied the patch at http://www.list.org/CAN-2005-0202.txt to a Mailman 2.1.4 installation and restarted the Web server. The first time I tried to access the archives for a private list using an email address that's *not* subscribed to the list, I got the traceback below. I backed out the patch and restarted the Web server. I now get the correct "Authorization failed." message. Note that for the sake of paranoia I've obfuscated my email address, changed the names of private lists, and flipped a few bits in the cookie data and remote address below. -- Roger --------------- Bug in Mailman version 2.1.4 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/private.py", line 124, in main password, username): File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: roger-no(a)spam-bcah.com Python information: Variable Value sys.version 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] sys.executable /usr/bin/python2.2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /dfnh-foo/ HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://mail.democracyfornewhampshire.com/mailman/private/dfnh-foo/ SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_python/2.7.8 Python/1.5.2 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 mod_throttle/3.1.2 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/private SERVER_ADMIN roger-no(a)spam-bcah.com SCRIPT_NAME /mailman/private SERVER_SIGNATURE Apache/1.3.27 Server at democracyfornewhampshire.com Port 80 REQUEST_METHOD POST HTTP_HOST mail.democracyfornewhampshire.com HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/private/dfnh-foo/ CONTENT_LENGTH 63 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_COOKIE dfnh-board+user+roger-no--at--spam-bcah.com=280200000069caae0b42732800000063346130393963653330656239633862643737356337626437396561663334363862343563643536; dfnh-members+admin=280200000069dcee0b42732800000033353539613836343166396565376030323966663963313435646564633734303837666366666230 SERVER_NAME democracyfornewhampshire.com REMOTE_ADDR 24.35.177.35 REMOTE_PORT 38224 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /home/roger/democracyfornewhampshire.com/html/dfnh-foo/ SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 199.125.75.14 DOCUMENT_ROOT /home/roger/democracyfornewhampshire.com/html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_…

1 0

[ mailman-Feature Requests-1120282 ] PASSWORD_REMINDERS_FROM Defaults.py Config Option
by SourceForge.net 10 Feb '05

10 Feb '05

Feature Requests item #1120282, was opened at 2005-02-10 12:37 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=1120282&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Matt (matt_ruzicka) Assigned to: Nobody/Anonymous (nobody) Summary: PASSWORD_REMINDERS_FROM Defaults.py Config Option Initial Comment: As a site that will be running a number of separate lists maintained and containing unrelated addresses it would be nice if there was if there was a config option that allowed an administrator to specify if the monthly password reminders came from the site owner (to retain current message reduction capacities) or the list owner (to allow bounces and responses from the reminders to go to the list owners themselves). Obviously this option would most defintiely end up causing people to get multiple messages from a single Mailman installation, but an administrator might see this as an acceptible trade off to ensure better communication between list members and list owners (as opposed to site owners who may not care to be bothered with messages from list members they are not aware of). My limited brain envisioned something like # This option determines what address the monthly # password reminders is sent from. It is strongly # recommended that you leave this set to site owner # so users subscribed to multiple lists will receive # only one message per month. # # examples are # %(siteowner)s@%(hostname)s - (recommended) # %(listowner)s@%(hostname)s # PASSWORD_REMINDERS_FROM = %(siteowner)s@%(hostname)s Also, not sure if this would actually be better suited for list specific list options so lists with a large number of cross over addresses could still benefit from the single address. Thanks for your time. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1120282&group_…

1 0

[ mailman-Bugs-1023942 ] No "Date:" line in digest header
by SourceForge.net 08 Feb '05

08 Feb '05

Bugs item #1023942, was opened at 2004-09-07 21:55 Message generated for change (Comment added) made by janschlosser You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1023942&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Todd K. Watson (tkdubs) Assigned to: Nobody/Anonymous (nobody) Summary: No "Date:" line in digest header Initial Comment: I am running Mailman-2.1.5. Mailman fails to insert the "Date:" line in the header, which can cause problems for MTA's which do not inject a "Date:" line (such as qmail). Each individual message within the digest has a date line in its header, but the digest itself is missing the Date line. This causes mail readers like Thunderbird to label the message as being sent on Dec. 31, 1969. Most MTA's and MUA's inject a Date line, but I'm using Qmail as an MTA -- which doesn't inject one. It is the job of the MUA (Mailman in this case) to create the Date: line according to RFC-2822. This was fixed for non-digested messages delivered to lists in 2.1-beta-1 of Mailman according to the NEWS file, but has not yet been addressed for delivery of digests. ---------------------------------------------------------------------- Comment By: Jan Schlosser (janschlosser) Date: 2005-02-08 14:26 Message: Logged In: YES user_id=918851 This one is fixed by patch 1116952, although the patch file didn't work without manual rewriting to the ToDigest.py source file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1023942&group_…

1 0