Mailman 3 April 2003 - Mailman-coders

[ mailman-Bugs-704912 ] Invitation bug
by SourceForge.net 07 Apr '03

07 Apr '03

Bugs item #704912, was opened at 2003-03-17 05:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=704912&group_i… Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Invitation bug Initial Comment: There seems to be a bug in parsing the confirmation of an invitation to join a mailing list. I suspect this has something to do with MIME decoding of the Subject: header. When sending a reply to the autogenerated invitation (in my case, using pine), with this header: Subject: Re: =?iso-8859-1?q?confirm_55ed0163ec2f0a56ac257f708b 470b6a892935f2?= nothing happened. But when sending a reply with this header (which was the case if I used Netscape Mail or Evolution): Subject: Re: confirm 9924a8cb2e31d2f1605ca6228ff210901ff17aba I was subscribed. Maybe Mailman doesn't decode the Subject: before parsing it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=704912&group_i…

1 0

[ mailman-Bugs-715581 ] plain text digest bug in appending messages
by SourceForge.net 07 Apr '03

07 Apr '03

Bugs item #715581, was opened at 2003-04-04 16:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_i… Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: plain text digest bug in appending messages Initial Comment: Sometimes, messages are incorrectly appended in the plain digests, which cause 2 or more messages to be attached to 1. For example, I got a digest which mentions one message in the Topic list, but at the end of this message, the next message is "glued" to the bottom of it: (...top of first message...) --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!From EMAILADDR(a)aol.com Fri Mar 28 14:04:32 2003 Return-Path: <EMAILADDR(a)aol.com> Delivered-To: fans(a)list.miss-janet.com (...second message continues with all it's headers and content) As you can see, the "From..." of the second message starts directly after the last character of the first message. Here's a second example: (... top of first message...) peace out: -oscarFrom EMAILADDR(a)aol.com Tue Apr 1 15:04:42 2003 Return-Path: <EMAILADDR(a)aol.com> Delivered-To: fans(a)list.miss-janet.com (..second message continues...) Again, the "From..." from the next message is glued to the previous message. Is this a simple missing end of line issue or is it more complicated? I can't seem to see a good pattern in it... Ricardo. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_i…

1 0

[ mailman-Bugs-685040 ] mailmanctl reopen does not reopen all log files
by SourceForge.net 06 Apr '03

06 Apr '03

Bugs item #685040, was opened at 2003-02-11 20:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=685040&group_i… Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl reopen does not reopen all log files Initial Comment: In Mailman 2.1: The help for mailmanctl reopen says that it causes all log files to be closed, and reopened the next time they are used. However, it does not seem to cover the qrunner and error logs. After running this command, lsof shows: [root@dp logs]# lsof -p 9207 .... mailmanct 9207 root 0u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 1u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 2u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 3u REG 8,1 116944 2130090 /var/mailman/logs/error.1 mailmanct 9207 root 4u REG 8,1 649 2130251 /var/mailman/logs/qrunner After running it again: [root@dp logs]# lsof -p 9214 .... python 9214 mailman 0u CHR 136,7 9 /dev/pts/7 python 9214 mailman 1u CHR 136,7 9 /dev/pts/7 python 9214 mailman 2u CHR 136,7 9 /dev/pts/7 python 9214 mailman 3u REG 8,1 116944 2130090 /var/mailman/logs/error.1 python 9214 mailman 4u REG 8,1 116944 2130090 /var/mailman/logs/error.1 python 9214 mailman 5u REG 8,1 649 2130251 /var/mailman/logs/qrunner The same is true for the qrunner child processes. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-06 19:44 Message: Logged In: YES user_id=12800 This works for me. The fd output from lsof might be misleading. I'll bet the fds are getting reused. Checking the actual files shows that it works properly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=685040&group_i…

1 0

[ mailman-Bugs-683833 ] Traceback on checkdbs
by SourceForge.net 06 Apr '03

06 Apr '03

Bugs item #683833, was opened at 2003-02-10 04:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_i… Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-06 19:32 Message: Logged In: YES user_id=12800 I believe this has been fixed in a slightly different way for 2.1.1 or 2.1.2 (cvs). ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-18 06:53 Message: Logged In: YES user_id=483131 Patching worked without any errors, and so does the checkdbs script now. Well done! :-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-18 06:12 Message: Logged In: YES user_id=67709 OK, somehow ^L has disappeared during genrating diff from cvs. I am uploading new patch using non-cvs diff. (You might be able to report error in patch command execution) ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-18 03:11 Message: Logged In: YES user_id=483131 Unfortunately, there's no difference :-( ... [mailman@styx mailman]$ python - S /home/mailman/cron/checkdbs Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 138, in ? main() File "/home/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/home/mailman/cron/checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-17 06:45 Message: Logged In: YES user_id=67709 stdivjak> [mailman@styx cron]# ./checkdbs you should type python -S /path/to/checkdbs ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-17 00:48 Message: Logged In: YES user_id=483131 [mailman@styx cron]# ./checkdbs Traceback (most recent call last): File "./checkdbs", line 138, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 06:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 05:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_i…

1 0

[ mailman-Bugs-672649 ] canonstr -> unicode usernames
by SourceForge.net 06 Apr '03

06 Apr '03

Bugs item #672649, was opened at 2003-01-22 14:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_i… Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: canonstr -> unicode usernames Initial Comment: Cgi.subscribe.process_form gets a unicode value for fullname, from Utils.canonstr() (return unicode(newstr, charset, 'replace') This came to my attention because it broke OwnerNotification when the email Message couldn't "flatten" itself with the unicode payload. Suspect that's only the beginning of the trouble that will be caused, so I'm hoping we really don't want unicode usernames values as a rule. I fixed it in subscribe.py with fullname = fullname.encode('iso8859-1'), but note that canonstr is used elsewhere like this. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-06 19:31 Message: Logged In: YES user_id=12800 I think this bug has been fixed in 2.1.1 or 2.1.2 (cvs). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 06:37 Message: Logged In: YES user_id=67709 If your users choose to input latin-1 charcters in fullname, it will be better to set iso-8859-1as english charset. in mm_cfg.py, def _(s): return s LC_DESCRIPTIONS['en'] = (_('English (USA)'), 'iso-8859-1') del _ ---------------------------------------------------------------------- Comment By: Pat Carr (pcarr) Date: 2003-02-12 23:05 Message: Logged In: YES user_id=710070 I stumbled over the same bug, but in my case it was bailing only in the confirm.py script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_i…

1 0

[ mailman-Bugs-671303 ] bin/arch --start and --end argument handling
by SourceForge.net 06 Apr '03

06 Apr '03

Bugs item #671303, was opened at 2003-01-20 13:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671303&group_i… Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch --start and --end argument handling Initial Comment: bin/arch says (among other things): -s N --start=N Start indexing at article N, where article 0 is the first in the mbox. Defaults to 0. -e M --end=M End indexing at article M. This script is not very efficient with respect to memory management, and for large archives, it may not be possible to index the mbox entirely. For that reason, you can specify the start and end article numbers. However, using --end=[some #] or --start=[some #] results in these errors: % bin/arch --wipe --end=25000 test [...] option --end must not have an argument % bin/arch --wipe --start=25001 test [...] option --start must not have an argument Using --end [some #] or --start [some #] (ie with no =) works fine. So either the help output of bin/arch needs to be amended to remove the ='s, or the argument handling needs to be tweaked to understand ='s. I'm unsure which is preferable. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671303&group_i…

1 0

[ mailman-Patches-713522 ] Spambayes integration
by SourceForge.net 06 Apr '03

06 Apr '03

Patches item #713522, was opened at 2003-04-01 22:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_i… Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Spambayes integration Initial Comment: Here's a patch I developed in Jan 2003 to integrate Spambayes http://spambayes.sf.net into Mailman. It's very experimental but provide here for fun. If people like it I could see it becoming part of Mailman 2.2 or 3.0 You need to separately download the spambayes distutils tarball and drop it in Mailman's misc directory. Check that the version value in misc/Makefile.in matches. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2003-04-07 00:41 Message: Logged In: YES user_id=227443 I'm attaching a safe patch solving all the problems on Barry's one. It must be used together with #715248 (for spambayes 1.0a2) see http://sourceforge.net/tracker/index.php?func=detail&aid=715248&group_id=61… There are still missing functionalities, e.g. training on false negatives for non-moderated lists. Now I'm working on functionality enhancements. ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:59 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:58 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-01 23:49 Message: Logged In: YES user_id=227443 LOL! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 23:19 Message: Logged In: YES user_id=12800 Oh please gawds of SF, accept my burnt offering of a patch as my supplication to your greatness. I have Checkethed the Holy CheckBox and Fillethed in the Holy TextBox. Now I go to Submitteth this Update. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_i…

1 0

[ mailman-Bugs-715581 ] plain text digest bug in appending messages
by SourceForge.net 04 Apr '03

04 Apr '03

Bugs item #715581, was opened at 2003-04-04 21:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: plain text digest bug in appending messages Initial Comment: Sometimes, messages are incorrectly appended in the plain digests, which cause 2 or more messages to be attached to 1. For example, I got a digest which mentions one message in the Topic list, but at the end of this message, the next message is "glued" to the bottom of it: (...top of first message...) --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!From EMAILADDR(a)aol.com Fri Mar 28 14:04:32 2003 Return-Path: <EMAILADDR(a)aol.com> Delivered-To: fans(a)list.miss-janet.com (...second message continues with all it's headers and content) As you can see, the "From..." of the second message starts directly after the last character of the first message. Here's a second example: (... top of first message...) peace out: -oscarFrom EMAILADDR(a)aol.com Tue Apr 1 15:04:42 2003 Return-Path: <EMAILADDR(a)aol.com> Delivered-To: fans(a)list.miss-janet.com (..second message continues...) Again, the "From..." from the next message is glued to the previous message. Is this a simple missing end of line issue or is it more complicated? I can't seem to see a good pattern in it... Ricardo. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_i…

1 0

[ mailman-Bugs-714929 ] Incorrect relative path in user options unsubscribe button
by SourceForge.net 03 Apr '03

03 Apr '03

Bugs item #714929, was opened at 2003-04-03 22:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714929&group_i… Category: Web/CGI Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Matt Noble (mathia-sf) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect relative path in user options unsubscribe button Initial Comment: I'm am using mailman 2.0.13. The monthly subscription reminder gives the URL http://my.server.com/mailman/options/listname/user@mail.com for changes in the users account. If the user follows this link and clicks the unsubscribe button they get directed to http://my.server.com/mailman/options/handle_opts/listname/user@mail.com and get the error "no such list handle_opts". If the user goes to http://my.server.com/mailman/listinfo/listname and clicks on edit options and then does the unsubscribe they get directed to http://my.server.com/mailman/handle_opts/listname/user@mail.com and it works. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714929&group_i…

1 0

[ mailman-Patches-713522 ] Spambayes integration
by SourceForge.net 03 Apr '03

03 Apr '03

Patches item #713522, was opened at 2003-04-01 22:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_i… Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Spambayes integration Initial Comment: Here's a patch I developed in Jan 2003 to integrate Spambayes http://spambayes.sf.net into Mailman. It's very experimental but provide here for fun. If people like it I could see it becoming part of Mailman 2.2 or 3.0 You need to separately download the spambayes distutils tarball and drop it in Mailman's misc directory. Check that the version value in misc/Makefile.in matches. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:59 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:58 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-01 23:49 Message: Logged In: YES user_id=227443 LOL! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 23:19 Message: Logged In: YES user_id=12800 Oh please gawds of SF, accept my burnt offering of a patch as my supplication to your greatness. I have Checkethed the Holy CheckBox and Fillethed in the Holy TextBox. Now I go to Submitteth this Update. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_i…

1 0