Bugs item #1904737, was opened at 2008-02-29 07:14
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1904737&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: command line scripts
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Lars Köller (wlanguy2)
>Assigned to: Mark Sapiro (msapiro)
Summary: ban_list entry breaks bulk member import
Initial Comment:
Mailman 2.1.9 (python 2.4.4) on Solaris 8 SPARC:
When an email address, e.g. dummy(a)example.com is inserted into the ban_list and the same member is tried to become a regular member, an error is triggered.
The is really critical, cause automatically generated bulk imports fail.
echo "dummy(a)example.com" | /usr/local/mailman/current/fhbi/bin/add_members -a n -w n -r - verteiler-zv
Traceback (most recent call last):
File "/usr/local/mailman/current/fhbi/bin/add_members", line 255, in ?
main()
File "/usr/local/mailman/current/fhbi/bin/add_members", line 235, in main
addall(mlist, nmembers, 0, send_welcome_msg, s)
File "/usr/local/mailman/current/fhbi/bin/add_members", line 135, in addall
mlist.ApprovedAddMember(userdesc, ack, 0)
File "/usr/localhost/mailman/current/fhbi/Mailman/MailList.py", line 958, in ApprovedAddMember
raise Errors.MembershipIsBanned, pattern
Mailman.Errors.MembershipIsBanned: dummy(a)example.com
Please fix as fast as possible.
many thanks and best regards
Lars
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2008-02-29 09:35
Message:
Logged In: YES
user_id=1123998
Originator: NO
Fixed by the attached patch which also fixes sync_members and
clone_member.
File Added: patch.txt
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1904737&group_…
Bugs item #1904737, was opened at 2008-02-29 16: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=1904737&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: command line scripts
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Lars Köller (wlanguy2)
Assigned to: Nobody/Anonymous (nobody)
Summary: ban_list entry breaks bulk member import
Initial Comment:
Mailman 2.1.9 (python 2.4.4) on Solaris 8 SPARC:
When an email address, e.g. dummy(a)example.com is inserted into the ban_list and the same member is tried to become a regular member, an error is triggered.
The is really critical, cause automatically generated bulk imports fail.
echo "dummy(a)example.com" | /usr/local/mailman/current/fhbi/bin/add_members -a n -w n -r - verteiler-zv
Traceback (most recent call last):
File "/usr/local/mailman/current/fhbi/bin/add_members", line 255, in ?
main()
File "/usr/local/mailman/current/fhbi/bin/add_members", line 235, in main
addall(mlist, nmembers, 0, send_welcome_msg, s)
File "/usr/local/mailman/current/fhbi/bin/add_members", line 135, in addall
mlist.ApprovedAddMember(userdesc, ack, 0)
File "/usr/localhost/mailman/current/fhbi/Mailman/MailList.py", line 958, in ApprovedAddMember
raise Errors.MembershipIsBanned, pattern
Mailman.Errors.MembershipIsBanned: dummy(a)example.com
Please fix as fast as possible.
many thanks and best regards
Lars
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1904737&group_…
Patches item #1902402, was opened at 2008-02-26 13:28
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1902402&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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Updated README
Initial Comment:
The README hasn't been touched in a while; it encourages the user to download Python 2.3.3, points to a now-404 /mailman-21/ URL, and refers to the inactive mailman3-dev list and to public CVS.
The attached patch modernizes the README. I think I have commit privs so I could commit it, but wanted to get the changes double-checked.
----------------------------------------------------------------------
>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2008-02-26 13:50
Message:
Logged In: YES
user_id=12800
Originator: NO
Andrew, how about creating a bzr branch with these changes and pushing
them to Launchpad? :) I'd love to review a branch more than a patch!
----------------------------------------------------------------------
Comment By: A.M. Kuchling (akuchling)
Date: 2008-02-26 13:38
Message:
Logged In: YES
user_id=11375
Originator: YES
Attaching another patch, for UPGRADING.
File Added: UPGRADING.diff
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1902402&group_…
Patches item #1902402, was opened at 2008-02-26 13:28
Message generated for change (Comment added) made by akuchling
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1902402&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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Updated README
Initial Comment:
The README hasn't been touched in a while; it encourages the user to download Python 2.3.3, points to a now-404 /mailman-21/ URL, and refers to the inactive mailman3-dev list and to public CVS.
The attached patch modernizes the README. I think I have commit privs so I could commit it, but wanted to get the changes double-checked.
----------------------------------------------------------------------
>Comment By: A.M. Kuchling (akuchling)
Date: 2008-02-26 13:38
Message:
Logged In: YES
user_id=11375
Originator: YES
Attaching another patch, for UPGRADING.
File Added: UPGRADING.diff
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1902402&group_…
Patches item #1902402, was opened at 2008-02-26 13:28
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=1902402&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: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Updated README
Initial Comment:
The README hasn't been touched in a while; it encourages the user to download Python 2.3.3, points to a now-404 /mailman-21/ URL, and refers to the inactive mailman3-dev list and to public CVS.
The attached patch modernizes the README. I think I have commit privs so I could commit it, but wanted to get the changes double-checked.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1902402&group_…
Bugs item #1845459, was opened at 2007-12-06 04:11
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1845459&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: command line scripts
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Gerry Murphy (gjmurphy)
Assigned to: Nobody/Anonymous (nobody)
Summary: cron/checkdbs produces traceback - buggy french translation
Initial Comment:
The following is produced when checkdb expires held messages AND the list preferred language is 'fr'. Patch which fixes this is attached.
--start--
Traceback (most recent call last):
File "/usr/local/mailman/cron/checkdbs", line 203, in ?
main()
File "/usr/local/mailman/cron/checkdbs", line 107, in main
text = _(
File "/usr/local/mailman/Mailman/i18n.py", line 90, in _
return tns % dict
ValueError: unsupported format character 'a' (0x61) at index 34
--end--
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2008-02-20 15:01
Message:
Logged In: YES
user_id=1123998
Originator: NO
I posted your patch to the Mailman-i18n list in December. See
<http://mail.python.org/pipermail/mailman-i18n/2007-December/001532.html>.
I am still hoping to get an updated translation in time for the 2.1.10
final release, but in case I don't, I'm applying the patch to the current
message catalog. The next beta/rc release of 2.1.10 will have it.
----------------------------------------------------------------------
Comment By: Gerry Murphy (gjmurphy)
Date: 2008-02-20 02:56
Message:
Logged In: YES
user_id=1890069
Originator: YES
This bug was originally found in Mailman 2.1.9. This bug is still present
in Mailman 2.1.10b3. This patch works with version 2.1.10b3.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1845459&group_…
Feature Requests item #1104433, was opened at 2005-01-18 04:44
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&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: 3
Private: No
Submitted By: Ross Golder (rossigee)
Assigned to: Nobody/Anonymous (nobody)
Summary: Configurable per-user/per-subscription subject prefix
Initial Comment:
I've had a request from a list member who would like us
to add a subject prefix to all the lists on our server
(mail.gnome.org), as his mail client can't do any kind
of automatic filtering. We are obviously reluctant to
change the status quo, as many people (e.g. PDA/mobile
users) would then respond asking us to remove them.
Instead, I decided to file this feature request to make
it (per-subscription) configurable. It would have one
of three possible values; use the default list setting,
override on or override off. This would allow users to
please themselves, and in some cases overcome problems
caused by limitations in their mailclient.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2008-02-20 06:59
Message:
Logged In: YES
user_id=1123998
Originator: NO
This discussion should continue on Mailman-Developers(a)python.org
<http://mail.python.org/mailman/listinfo/mailman-developers>.
Please keep in mind that this is unlikely to be accepted for the 2.1
maintenance branch, primararily because of the changes to user options and
the corresponding i18n implications.
----------------------------------------------------------------------
Comment By: Kenneth Porter (scratchmonkey)
Date: 2008-02-19 21:43
Message:
Logged In: YES
user_id=29401
Originator: NO
It looks like the default subject prefix mangling happens in the main
pipeline after the message is accepted, in CookHeaders. Per-user processing
(like VERP) appears to be done in the queue runners. I guess OutputRunner
would need to be the one to do this, and would need to break up the
recipient list into groups based on what per-recipient munging needs to be
done.
----------------------------------------------------------------------
Comment By: Kenneth Porter (scratchmonkey)
Date: 2008-02-19 16:03
Message:
Logged In: YES
user_id=29401
Originator: NO
Nothing seems to have happened with this in the last 3 years. I just saw
this conflict come up again on the Subversion mailing list, and it seems to
come up regularly on any list that has the prefixes disabled (my personal
preference).
Before I start looking at the code, are there any design constraints that
argue against implementing this, or implementing it in a particular way?
----------------------------------------------------------------------
Comment By: Ross Golder (rossigee)
Date: 2005-01-19 00:43
Message:
Logged In: YES
user_id=20872
Some lists use prefixes, some don't. Some users that
subscribe to many lists want consistency, but we don't want
to have to determine and enforce a site-wide policy and deal
with all the ensuing arguments. This feature shifts the
decision from the list/site managers to the individuals
users. Basic headache prevention.
The main argument for prefixes seems to be 'I can quickly
identify what the mail is about in my inbox', where users
haven't got or don't use their client's header filtering
features.
The main argument against prefixes seems to be 'I just get a
screenful of list prefixes when I try to view my list
folders', where users are trying to use mail clients in a
low screen resolution (e.g. old VGA screen, palm/PDA device,
mobile phone, small desktop window whatever).
Sorry for misfiling it. Haven't used SF for a while -
forgot that feature requests and bugs aren't mixed like in
bugzilla.
----------------------------------------------------------------------
Comment By: Tokio Kikuchi (tkikuchi)
Date: 2005-01-18 18:45
Message:
Logged In: YES
user_id=67709
This should be submitted as Feature Request.
BTW, many mailing list users are happy with subject
prefixes. Why not GNOME users? ;-)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_…
Bugs item #1845459, was opened at 2007-12-06 13:11
Message generated for change (Comment added) made by gjmurphy
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1845459&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: command line scripts
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Gerry Murphy (gjmurphy)
Assigned to: Nobody/Anonymous (nobody)
>Summary: cron/checkdbs produces traceback - buggy french translation
Initial Comment:
The following is produced when checkdb expires held messages AND the list preferred language is 'fr'. Patch which fixes this is attached.
--start--
Traceback (most recent call last):
File "/usr/local/mailman/cron/checkdbs", line 203, in ?
main()
File "/usr/local/mailman/cron/checkdbs", line 107, in main
text = _(
File "/usr/local/mailman/Mailman/i18n.py", line 90, in _
return tns % dict
ValueError: unsupported format character 'a' (0x61) at index 34
--end--
----------------------------------------------------------------------
>Comment By: Gerry Murphy (gjmurphy)
Date: 2008-02-20 11:56
Message:
Logged In: YES
user_id=1890069
Originator: YES
This bug was originally found in Mailman 2.1.9. This bug is still present
in Mailman 2.1.10b3. This patch works with version 2.1.10b3.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1845459&group_…
Feature Requests item #1897575, was opened at 2008-02-20 07:16
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=1897575&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: Ross Golder (rossigee)
Assigned to: Nobody/Anonymous (nobody)
Summary: Patch to help report spam in moderator queue
Initial Comment:
You're moderating one of your lists, looking at the 'admindbsummary' page. You're already ticked 'accept' to all the non-spam entries and clicked submit. You're now left with a queue consisting only of spam.
Some days, you feel calm and rational and just delete the rest using the handy 'discard all deferred' tickboxes and move on. Other times, you have spam-rage and feel frustrated that it's not trivial to forward all this spam on to a reporting service, such as Spamcop or Knujon (or whatever else comes along) and help those who do have more time and resources to hunt down and shut down these bastards. The problem is that you'd have to go through the list, ticking 'forward to' and cutting'n'pasting your spam submission address(es) in for the whole list manually before you can submit it.
One solution would be to add another tickbox like 'report all deferred' and do some server-side patching to act on the tickbox. A quicker (dirtier?) solution is just to add a few lines of Javascript to the 'admindbsummary' page to automate the task client-side. I added the following to the template on my home server:
<script type="text/javascript"><!--
function sendspamto() {
email = document.getElementById("fwdspamto").value;
for (elnum in document.forms[1].elements) {
elem = document.forms[1].elements[elnum];
name = elem.name;
if(name.substr(0, 14) == 'senderforward-') {
elem.checked = true;
}
if(name.substr(0, 16) == 'senderforwardto-') {
elem.value = email;
}
}
}
--></script>
<form method="GET" action="javascript: sendspamto(); return false;">
<p><b>Forward spam</b> to : <input id="fwdspamto" value="knujon(a)coldrain.net"/> <input type="submit" value="Set" onclick="sendspamto()"/></p>
</form>
If someone wants to take the above, polish it or whatever and use it in upstream mailman that'd make my (and probably a few thousands other moderators) lives a little easier :)
Otherwise, please feel free to put it in the FAQ for others to use as they wish.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1897575&group_…
Feature Requests item #1104433, was opened at 2005-01-18 04:44
Message generated for change (Comment added) made by scratchmonkey
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&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: 3
Private: No
Submitted By: Ross Golder (rossigee)
Assigned to: Nobody/Anonymous (nobody)
Summary: Configurable per-user/per-subscription subject prefix
Initial Comment:
I've had a request from a list member who would like us
to add a subject prefix to all the lists on our server
(mail.gnome.org), as his mail client can't do any kind
of automatic filtering. We are obviously reluctant to
change the status quo, as many people (e.g. PDA/mobile
users) would then respond asking us to remove them.
Instead, I decided to file this feature request to make
it (per-subscription) configurable. It would have one
of three possible values; use the default list setting,
override on or override off. This would allow users to
please themselves, and in some cases overcome problems
caused by limitations in their mailclient.
----------------------------------------------------------------------
Comment By: Kenneth Porter (scratchmonkey)
Date: 2008-02-19 21:43
Message:
Logged In: YES
user_id=29401
Originator: NO
It looks like the default subject prefix mangling happens in the main
pipeline after the message is accepted, in CookHeaders. Per-user processing
(like VERP) appears to be done in the queue runners. I guess OutputRunner
would need to be the one to do this, and would need to break up the
recipient list into groups based on what per-recipient munging needs to be
done.
----------------------------------------------------------------------
Comment By: Kenneth Porter (scratchmonkey)
Date: 2008-02-19 16:03
Message:
Logged In: YES
user_id=29401
Originator: NO
Nothing seems to have happened with this in the last 3 years. I just saw
this conflict come up again on the Subversion mailing list, and it seems to
come up regularly on any list that has the prefixes disabled (my personal
preference).
Before I start looking at the code, are there any design constraints that
argue against implementing this, or implementing it in a particular way?
----------------------------------------------------------------------
Comment By: Ross Golder (rossigee)
Date: 2005-01-19 00:43
Message:
Logged In: YES
user_id=20872
Some lists use prefixes, some don't. Some users that
subscribe to many lists want consistency, but we don't want
to have to determine and enforce a site-wide policy and deal
with all the ensuing arguments. This feature shifts the
decision from the list/site managers to the individuals
users. Basic headache prevention.
The main argument for prefixes seems to be 'I can quickly
identify what the mail is about in my inbox', where users
haven't got or don't use their client's header filtering
features.
The main argument against prefixes seems to be 'I just get a
screenful of list prefixes when I try to view my list
folders', where users are trying to use mail clients in a
low screen resolution (e.g. old VGA screen, palm/PDA device,
mobile phone, small desktop window whatever).
Sorry for misfiling it. Haven't used SF for a while -
forgot that feature requests and bugs aren't mixed like in
bugzilla.
----------------------------------------------------------------------
Comment By: Tokio Kikuchi (tkikuchi)
Date: 2005-01-18 18:45
Message:
Logged In: YES
user_id=67709
This should be submitted as Feature Request.
BTW, many mailing list users are happy with subject
prefixes. Why not GNOME users? ;-)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_…