Bugs item #1834569, was opened at 2007-11-19 15:48
Message generated for change (Settings changed) made by gjmurphy
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&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.0.x
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: gjmurphy (gjmurphy)
Assigned to: Nobody/Anonymous (nobody)
Summary: core dump when list admin is set to be the list bounce addr
Initial Comment:
A list manager here decided that the list admin email address should be set to the list bounce address.
Later, a message was sent to this address informing the admin that there were requests pending approval/whatever. Mailman then accepted this message and attempted to parse it as a bounce message which, obviously, failed. This failure was then send to the list administrator informing them that a bounce message could not be parsed. This was repeated until python coredumped the bounce queuerunner process.
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2007-11-19 21:38
Message:
Logged In: YES
user_id=1123998
Originator: NO
Fixed in Mailman 2.1.10.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&group_…
Bugs item #1834569, was opened at 2007-11-19 06:48
Message generated for change (Settings changed) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&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.0.x
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: gjmurphy (gjmurphy)
Assigned to: Nobody/Anonymous (nobody)
Summary: core dump when list admin is set to be the list bounce addr
Initial Comment:
A list manager here decided that the list admin email address should be set to the list bounce address.
Later, a message was sent to this address informing the admin that there were requests pending approval/whatever. Mailman then accepted this message and attempted to parse it as a bounce message which, obviously, failed. This failure was then send to the list administrator informing them that a bounce message could not be parsed. This was repeated until python coredumped the bounce queuerunner process.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-11-19 12:38
Message:
Logged In: YES
user_id=1123998
Originator: NO
Fixed in Mailman 2.1.10.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&group_…
Bugs item #1834569, was opened at 2007-11-19 15:48
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=1834569&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.0.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: gjmurphy (gjmurphy)
Assigned to: Nobody/Anonymous (nobody)
Summary: core dump when list admin is set to be the list bounce addr
Initial Comment:
A list manager here decided that the list admin email address should be set to the list bounce address.
Later, a message was sent to this address informing the admin that there were requests pending approval/whatever. Mailman then accepted this message and attempted to parse it as a bounce message which, obviously, failed. This failure was then send to the list administrator informing them that a bounce message could not be parsed. This was repeated until python coredumped the bounce queuerunner process.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&group_…
Bugs item #1834281, was opened at 2007-11-19 00:19
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=1834281&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: Pipermail
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong mailto subject/in-reply-to link in the article page
Initial Comment:
The Archived article page give an oppotunity to reply or to send comments with the mailto link on the poster (or the list address) with the subject and in-reply-to attributes set. But, the subject should have the 'Re:' prefix like the other messages from the user's MUA, and 'In-Reply-To' should be the message-id of the article not the in-reply-to header value of it.
The patch is attached.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834281&group_…
Patches item #1220144, was opened at 2005-06-13 23:29
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&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: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: Jim Tittsler (jtittsler)
Assigned to: Tokio Kikuchi (tkikuchi)
Summary: allow specifying another list in accept_these_nonmembers
Initial Comment:
Add the capability to logically include the addresses
all of the members of another list in the same Mailman
installation to accept_these_nonmembers.
'@listname' checks the poster's address against the
membership of listname.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-11-18 11:58
Message:
Logged In: YES
user_id=1123998
Originator: NO
Patch will be in 2.1.10.
----------------------------------------------------------------------
Comment By: Charles (libertytrek)
Date: 2007-11-18 10:32
Message:
Logged In: YES
user_id=1881071
Originator: NO
Hello,
I'm very interested in using this feature, but I'm not very good at adding
custom patches... any chance of an update on when this will be added to the
core code?
Thanks,
Charles
----------------------------------------------------------------------
Comment By: Tokio Kikuchi (tkikuchi)
Date: 2007-05-04 00:33
Message:
Logged In: YES
user_id=67709
Originator: NO
Because '@' is mandatory in mailman 2.2 listname, I think that
'`listname@domain`' is more preferable. Use of '`' is meaning 'evaluate
this list member'.
I also think we can merge this patch (along with the sibling list patch
#1347962) in the next mailman 2.1.10 because release of 2.2 is delayed
considerably.
Thoughts ?
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2006-12-01 12:30
Message:
Logged In: YES
user_id=1123998
Originator: NO
The patch also applies without change to Mailman 2.1.9.
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2006-07-17 16:09
Message:
Logged In: YES
user_id=1123998
The 2.1.6 patch also applies without change to Mailman 2.1.7
and 2.1.8. Even though there are minor changes in the
patched modules, the patched line numbers and the patch data
are unchanged.
----------------------------------------------------------------------
Comment By: Tokio Kikuchi (tkikuchi)
Date: 2005-11-17 18:37
Message:
Logged In: YES
user_id=67709
Marking as an Mailman 2.2 new feature candidate.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&group_…
Patches item #1220144, was opened at 2005-06-14 02:29
Message generated for change (Comment added) made by libertytrek
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&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: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: Jim Tittsler (jtittsler)
Assigned to: Tokio Kikuchi (tkikuchi)
Summary: allow specifying another list in accept_these_nonmembers
Initial Comment:
Add the capability to logically include the addresses
all of the members of another list in the same Mailman
installation to accept_these_nonmembers.
'@listname' checks the poster's address against the
membership of listname.
----------------------------------------------------------------------
Comment By: Charles (libertytrek)
Date: 2007-11-18 13:32
Message:
Logged In: YES
user_id=1881071
Originator: NO
Hello,
I'm very interested in using this feature, but I'm not very good at adding
custom patches... any chance of an update on when this will be added to the
core code?
Thanks,
Charles
----------------------------------------------------------------------
Comment By: Tokio Kikuchi (tkikuchi)
Date: 2007-05-04 03:33
Message:
Logged In: YES
user_id=67709
Originator: NO
Because '@' is mandatory in mailman 2.2 listname, I think that
'`listname@domain`' is more preferable. Use of '`' is meaning 'evaluate
this list member'.
I also think we can merge this patch (along with the sibling list patch
#1347962) in the next mailman 2.1.10 because release of 2.2 is delayed
considerably.
Thoughts ?
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2006-12-01 15:30
Message:
Logged In: YES
user_id=1123998
Originator: NO
The patch also applies without change to Mailman 2.1.9.
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2006-07-17 19:09
Message:
Logged In: YES
user_id=1123998
The 2.1.6 patch also applies without change to Mailman 2.1.7
and 2.1.8. Even though there are minor changes in the
patched modules, the patched line numbers and the patch data
are unchanged.
----------------------------------------------------------------------
Comment By: Tokio Kikuchi (tkikuchi)
Date: 2005-11-17 21:37
Message:
Logged In: YES
user_id=67709
Marking as an Mailman 2.2 new feature candidate.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&group_…
Bugs item #1833527, was opened at 2007-11-16 21:04
Message generated for change (Comment added) made by twcook
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&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 (stable)
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Tim Cook (twcook)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fails to send own users mail to them.
Initial Comment:
In at least version 2.1.9, in at least two separate installations, I do not receive my own posts even though I ensured that the Yes option is selected. Another user on the same mailing list reported the same issue.
The only similarity I can find in our email addresses are that they are both quite long.
timothywayne.cook(a)gmail.com
and
serefarikan(a)kurumsalteknoloji.com
----------------------------------------------------------------------
>Comment By: Tim Cook (twcook)
Date: 2007-11-16 22:09
Message:
Logged In: YES
user_id=19267
Originator: YES
Thanks. Sorry I missed it in the mailing list archive.
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2007-11-16 22:05
Message:
Logged In: YES
user_id=1123998
Originator: NO
I don't know what the issue is with serefarikan(a)kurumsalteknoloji.com, but
with timothywayne.cook(a)gmail.com, this is a gmail 'feature' that ignores
the post from the list because it is a duplicate of the message in Sent
Mail. This is a gmail issue and Mailman can't do anything about it.
This is noted at
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.042.htp> and
has been noted several times on mailman-users(a)python.org, e.g.,
<http://mail.python.org/pipermail/mailman-users/2005-February/042782.html>.
If you can provide more information about the issue with
serefarikan(a)kurumsalteknoloji.com, we can look into that.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&group_…
Bugs item #1833527, was opened at 2007-11-16 21:04
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&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 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tim Cook (twcook)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fails to send own users mail to them.
Initial Comment:
In at least version 2.1.9, in at least two separate installations, I do not receive my own posts even though I ensured that the Yes option is selected. Another user on the same mailing list reported the same issue.
The only similarity I can find in our email addresses are that they are both quite long.
timothywayne.cook(a)gmail.com
and
serefarikan(a)kurumsalteknoloji.com
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-11-16 22:05
Message:
Logged In: YES
user_id=1123998
Originator: NO
I don't know what the issue is with serefarikan(a)kurumsalteknoloji.com, but
with timothywayne.cook(a)gmail.com, this is a gmail 'feature' that ignores
the post from the list because it is a duplicate of the message in Sent
Mail. This is a gmail issue and Mailman can't do anything about it.
This is noted at
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.042.htp> and
has been noted several times on mailman-users(a)python.org, e.g.,
<http://mail.python.org/pipermail/mailman-users/2005-February/042782.html>.
If you can provide more information about the issue with
serefarikan(a)kurumsalteknoloji.com, we can look into that.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&group_…
Bugs item #1833527, was opened at 2007-11-16 21:04
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=1833527&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 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tim Cook (twcook)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fails to send own users mail to them.
Initial Comment:
In at least version 2.1.9, in at least two separate installations, I do not receive my own posts even though I ensured that the Yes option is selected. Another user on the same mailing list reported the same issue.
The only similarity I can find in our email addresses are that they are both quite long.
timothywayne.cook(a)gmail.com
and
serefarikan(a)kurumsalteknoloji.com
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&group_…
Bugs item #963137, was opened at 2004-05-30 07:12
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=963137&group_i…
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: Paul Rubin (prubin)
Assigned to: Nobody/Anonymous (nobody)
Summary: dumpdb broken
Initial Comment:
In the stable 2.1.5 load dump db is broken:
Traceback (most recent call last):
File "/var/mailman/bin/dumpdb", line 156, in ?
msg = main()
File "/var/mailman/bin/dumpdb", line 126, in main
d = DumperSwitchboard().read(filename)
NameError: global name 'DumperSwitchboard' is not
defined
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-11-12 16:01
Message:
Logged In: YES
user_id=1123998
Originator: NO
Fixed in 2.1.10.
----------------------------------------------------------------------
Comment By: Paul Rubin (prubin)
Date: 2004-05-30 20:33
Message:
Logged In: YES
user_id=91557
Appearently, yo just removed support for .db files. it works
fine on the .pck files...
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=963137&group_i…