Patches item #1696053, was opened at 2007-04-07 07:24
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1696053&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dubi (dovzamir)
Assigned to: Nobody/Anonymous (nobody)
Summary: Hebrew Translation Attached!
Initial Comment:
Attached are the Hebrew files for Mailman 2.1.9
I added a parameter to the LC_DESCRIPTION function, and these are the files that are affected by the addition of 'direction' to the 'LC_DESCRIPTION'
function. They have been changed, and diffs are attached...
./Mailman/Cgi/create.py
./Mailman/Defaults.py.in
./Mailman/Defaults.py
./Mailman/Utils.py
./messages/es/README.es
./messages/ja/README.ja
./messages/ja/doc/Defaults.py.in
./messages/eu/README.eu
Likewise, all translation files are attached.
There is still a problem displaying command line output in the correct direction. Still looking for a solution...
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-06-22 14:34
Message:
Logged In: YES
user_id=1123998
Originator: NO
Replacement didn't help. Uploaded file was 207,802 bytes. When downloaded,
the file is identical except now there are 8 extraneous bytes appended.
Some versions of gunzip including 1.3.5 will report "decompression OK,
trailing garbage ignored", and the resultant file will be fine. Reportedly
there are other gunzip versions and/or .gz expanders that will not process
the file.
If you can't expand the downloaded file, you can try running this python
script to truncate it to the proper length.
>>> f = open('Mailman_2.1.9_he.tar.gz', 'r+b')
>>> f.seek(207802)
>>> f.truncate()
>>> f.close()
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2007-06-22 14:06
Message:
Logged In: YES
user_id=1123998
Originator: NO
Attempt to replace Mailman_2.1.9_he.tar.gz with one that doesn't have 6
extraneous trailing bytes.
Also moved from 'bugs' to 'patches'.
File Added: Mailman_2.1.9_he.tar.gz
----------------------------------------------------------------------
Comment By: Dubi (dovzamir)
Date: 2007-04-26 11:33
Message:
Logged In: YES
user_id=1207589
Originator: YES
File Added: Mailman_2.1.9_he.tar.gz
----------------------------------------------------------------------
Comment By: Dubi (dovzamir)
Date: 2007-04-26 11:30
Message:
Logged In: YES
user_id=1207589
Originator: YES
File Added: Mailman_2.1.9_he.tar.gz
----------------------------------------------------------------------
Comment By: Dubi (dovzamir)
Date: 2007-04-26 11:27
Message:
Logged In: YES
user_id=1207589
Originator: YES
File Added: Mailman_2.1.9_he.tar.gz
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1696053&group_…
Patches item #1696053, was opened at 2007-04-07 07:24
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1696053&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
>Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dubi (dovzamir)
Assigned to: Nobody/Anonymous (nobody)
Summary: Hebrew Translation Attached!
Initial Comment:
Attached are the Hebrew files for Mailman 2.1.9
I added a parameter to the LC_DESCRIPTION function, and these are the files that are affected by the addition of 'direction' to the 'LC_DESCRIPTION'
function. They have been changed, and diffs are attached...
./Mailman/Cgi/create.py
./Mailman/Defaults.py.in
./Mailman/Defaults.py
./Mailman/Utils.py
./messages/es/README.es
./messages/ja/README.ja
./messages/ja/doc/Defaults.py.in
./messages/eu/README.eu
Likewise, all translation files are attached.
There is still a problem displaying command line output in the correct direction. Still looking for a solution...
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-06-22 14:06
Message:
Logged In: YES
user_id=1123998
Originator: NO
Attempt to replace Mailman_2.1.9_he.tar.gz with one that doesn't have 6
extraneous trailing bytes.
Also moved from 'bugs' to 'patches'.
File Added: Mailman_2.1.9_he.tar.gz
----------------------------------------------------------------------
Comment By: Dubi (dovzamir)
Date: 2007-04-26 11:33
Message:
Logged In: YES
user_id=1207589
Originator: YES
File Added: Mailman_2.1.9_he.tar.gz
----------------------------------------------------------------------
Comment By: Dubi (dovzamir)
Date: 2007-04-26 11:30
Message:
Logged In: YES
user_id=1207589
Originator: YES
File Added: Mailman_2.1.9_he.tar.gz
----------------------------------------------------------------------
Comment By: Dubi (dovzamir)
Date: 2007-04-26 11:27
Message:
Logged In: YES
user_id=1207589
Originator: YES
File Added: Mailman_2.1.9_he.tar.gz
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1696053&group_…
Patches item #1740331, was opened at 2007-06-20 15:06
Message generated for change (Comment added) made by rebum
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1740331&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: internationalization
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Martin Matuska (rebum)
Assigned to: Nobody/Anonymous (nobody)
Summary: New translation: Slovak
Initial Comment:
The attached patch adds the slovak translation to Mailman 2.1.9. The included .po file is from SVN trunk.
I would like to become the language champion for the Slovak language.
Thank you,
Martin Matuska
<martin at matuska dot org>
<mm at FreeBSD dot org>
----------------------------------------------------------------------
>Comment By: Martin Matuska (rebum)
Date: 2007-06-20 18:07
Message:
Logged In: YES
user_id=41220
Originator: YES
Updated translation and single mailman.po + templates can be found under:
http://www.matuska.org/martin/mailman
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1740331&group_…
Patches item #1740331, was opened at 2007-06-20 15:06
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=1740331&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: internationalization
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Martin Matuska (rebum)
Assigned to: Nobody/Anonymous (nobody)
Summary: New translation: Slovak
Initial Comment:
The attached patch adds the slovak translation to Mailman 2.1.9. The included .po file is from SVN trunk.
I would like to become the language champion for the Slovak language.
Thank you,
Martin Matuska
<martin at matuska dot org>
<mm at FreeBSD dot org>
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1740331&group_…
Bugs item #1738710, was opened at 2007-06-17 10:00
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738710&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: documentation
Group: 2.1 (stable)
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: David Chase (dr2chase)
Assigned to: Nobody/Anonymous (nobody)
Summary: Out-of-order install instructions (permissions)
Initial Comment:
Quoting:
Warning: You want to be very sure
that the user id under which your
CGI scripts run is not in the
mailman group you created above,
otherwise private archives will
be accessible to anyone.
Problem #1: this is the first point in the
install instructions where this is so clearly
stated, far after the configure and make steps.
Yeah, sure, once upon a time we were supposed
to read all the instructions first before doing
anything, but more people will install and use
the software if you just put the steps in the
right order in the documentation. Lots of other
products manage to get this right.
Problem #2: HOW IS THIS ACCOMPLISHED? This
is important, right? Why not spend a few words
on making sure people get it right?
Problem #3: This looks like exactly the sort
of boring mechanical thing that a computer is
good at. Why is the human installer being
asked to check this?
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-06-17 10:57
Message:
Logged In: YES
user_id=1123998
Originator: NO
Problem #1 - It seems to me this is in the right place. It is under
'setting up your web server' which is where you configure the user under
which Mailman CGIs will run.
Problem #2 - Consult your web server documentation. Normally, your web
server is not running Mailman GGIs as the mailman user anyway unless you go
out of your way to make it do so.
Problem #3 - We have no idea what web server you are running or how to
find and parse its configuration file(s), so how can we check this
mechanically? We do check at run time in the CGI wrapper to be sure that
the wrapper is invoked with the group configured with --with-cgi-gid.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738710&group_…
Bugs item #1738710, was opened at 2007-06-17 13:00
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=1738710&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: documentation
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: David Chase (dr2chase)
Assigned to: Nobody/Anonymous (nobody)
Summary: Out-of-order install instructions (permissions)
Initial Comment:
Quoting:
Warning: You want to be very sure
that the user id under which your
CGI scripts run is not in the
mailman group you created above,
otherwise private archives will
be accessible to anyone.
Problem #1: this is the first point in the
install instructions where this is so clearly
stated, far after the configure and make steps.
Yeah, sure, once upon a time we were supposed
to read all the instructions first before doing
anything, but more people will install and use
the software if you just put the steps in the
right order in the documentation. Lots of other
products manage to get this right.
Problem #2: HOW IS THIS ACCOMPLISHED? This
is important, right? Why not spend a few words
on making sure people get it right?
Problem #3: This looks like exactly the sort
of boring mechanical thing that a computer is
good at. Why is the human installer being
asked to check this?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738710&group_…
Bugs item #1738667, was opened at 2007-06-17 07:54
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738667&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: David Chase (dr2chase)
Assigned to: Nobody/Anonymous (nobody)
Summary: misc/KoreanCodecs-2.0.5/src/hangul.c does not compile
Initial Comment:
SunOS ... 5.10 Generic_118855-36 i86pc i386 i86pc
Python 2.3.5 (#1, Nov 30 2005, 10:43:01) [C] on sunos5
gcc -v yields:
Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs
Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
--------------
Compilation first fails when it attempts to invoke "cc" despite being configured to use the default (which is gcc). Hacking around this with a symbolic link from cc to gcc yields:
src/hangul.c:33: error: syntax error before numeric constant
src/hangul.c:34: error: syntax error before numeric constant
The cause of this is that two of the enums defined in hangul.c
enum { /* Jaeum Codes on U+3100 */
G = 0x3131, GG, GS, N, NJ, NH, D, DD, L, LG, LM, LB,
LS, LT, LP, LH, M, B, BB, BS, S, SS, NG, J, JJ, C, K, T, P, H
};
preprocess to integers (after gcc -E):
enum {
G = 0x3131, GG, 0, N, NJ, NH, D, DD, L, LG, LM, LB,
LS, LT, LP, LH, M, B, BB, BS, S, 18, NG, J, JJ, C, K, T, P, H
};
Presumably this is specific to the python include file version.
Proposed hackaround, inserted before the enums:
#ifdef GS
#undef GS
#endif
#ifdef SS
#undef SS
#endif
It did at least finish the make install after this.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-06-17 08:37
Message:
Logged In: YES
user_id=1123998
Originator: NO
I believe this is a Solaris bug, not a Mailman bug. See
<http://www.google.com/search?hl=en&q=site%3Amail.python.org++inurl%3Amailma…>
including
<http://mail.python.org/pipermail/mailman-users/2007-January/055235.html>
from which I quote
This is due to a bug in Solaris 10 headers. <signal.h> includes
<sys/regset.h> which pollutes the macro "namespace" (if you will)
with definitions for x86 registers, like GS and SS. This is only
on Solaris/x86; Solaris/sparc doesn't have this error.
Regarding the cc/gcc issue see
<http://www.google.com/search?hl=en&safe=off&q=site%3Amail.python.org++inurl…>
including
<http://mail.python.org/pipermail/mailman-users/2007-January/055506.html>
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738667&group_…
Bugs item #1738667, was opened at 2007-06-17 10:54
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=1738667&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: David Chase (dr2chase)
Assigned to: Nobody/Anonymous (nobody)
Summary: misc/KoreanCodecs-2.0.5/src/hangul.c does not compile
Initial Comment:
SunOS ... 5.10 Generic_118855-36 i86pc i386 i86pc
Python 2.3.5 (#1, Nov 30 2005, 10:43:01) [C] on sunos5
gcc -v yields:
Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs
Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
--------------
Compilation first fails when it attempts to invoke "cc" despite being configured to use the default (which is gcc). Hacking around this with a symbolic link from cc to gcc yields:
src/hangul.c:33: error: syntax error before numeric constant
src/hangul.c:34: error: syntax error before numeric constant
The cause of this is that two of the enums defined in hangul.c
enum { /* Jaeum Codes on U+3100 */
G = 0x3131, GG, GS, N, NJ, NH, D, DD, L, LG, LM, LB,
LS, LT, LP, LH, M, B, BB, BS, S, SS, NG, J, JJ, C, K, T, P, H
};
preprocess to integers (after gcc -E):
enum {
G = 0x3131, GG, 0, N, NJ, NH, D, DD, L, LG, LM, LB,
LS, LT, LP, LH, M, B, BB, BS, S, 18, NG, J, JJ, C, K, T, P, H
};
Presumably this is specific to the python include file version.
Proposed hackaround, inserted before the enums:
#ifdef GS
#undef GS
#endif
#ifdef SS
#undef SS
#endif
It did at least finish the make install after this.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738667&group_…
Patches item #1527537, was opened at 2006-07-24 11:06
Message generated for change (Comment added) made by pabs3
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1527537&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Paul Wise (pabs3)
Assigned to: Nobody/Anonymous (nobody)
Summary: prevent and log subscription spamflood (2.1.8)
Initial Comment:
The attached patch for mailman 2.1.8 causes mailman to
ignore subscriptions that already exist in pending.pck
and request.pck. This prevents people from
mass-spamming either the list admin or random email
addresses (depending on the configuration of the list).
----------------------------------------------------------------------
>Comment By: Paul Wise (pabs3)
Date: 2007-06-14 00:47
Message:
Logged In: YES
user_id=35028
Originator: YES
New version that doesn't traceback when there are pending unsubscription
attempts.
File Added: imc-37-stop-subscription-spam.patch
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1527537&group_…
Bugs item #1181161, was opened at 2005-04-11 17:54
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1181161&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 beta
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Jim Tittsler (jtittsler)
Assigned to: Nobody/Anonymous (nobody)
Summary: Approved: only removed from text/plain part
Initial Comment:
If someone uses the "Approved: in the first line of the message"
scheme, the line including the list password is only removed from
the first text/plain part. It might be better to iterate over all text/*
parts.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-06-09 13:03
Message:
Logged In: YES
user_id=1123998
Originator: NO
The fix in 2.1.7 sometimes failed because it didn't decode
quoted-printable and base64 encoded body parts. The fix has now been
enhanced to decode the body part before looking for an Approve(d): line.
This also fixes a related issue of not finding Approve(d): line in the
first text/plain part or getting the password wrong if that part was
encoded.
The fix is in SVN (Mailman/Handlers/Approve.py).
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2005-12-20 19:08
Message:
Logged In: YES
user_id=1123998
Fixed in CVS for 2.1.7rc1 and 2.2. We still require the
Approve(d): <password> to be the first non-blank line in the
first text/plain part (if it's not an actual header), but
once it's found in the first text/plain part, we remove it
from every text/* part in which we can find it.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1181161&group_…