[Mailman-Developers] [ mailman-Bugs-662127 ] Race condition with summary modification screen
Bugs item #662127, was opened at 2003-01-04 14:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662127&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Race condition with summary modification screen Initial Comment: I just upgraded to 2.1 and noticed an interesting race condition with the summary version of the moderation page. Take this timeline: 1) [EMAIL PROTECTED] sends 3 messages to the list 2) moderator visits summary moderation page and sees the 3 messages 3) [EMAIL PROTECTED] sends another message to the list 4) moderator clicks "discard" and submits The end result is that Mailman discards 4 messages, including the latest one that the moderator did not get to see. This does not happen with the old-style "details" version of the moderation page. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662127&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-662163 ] Autoreplies confirm subscription invitations
Bugs item #662163, was opened at 2003-01-04 11:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662163&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Autoreplies confirm subscription invitations Initial Comment: I'm not sure of the exact circumstances (maybe personalization needs to be on), bu t i fyou "invite" people to join a mailing list, or, presumably, if someone sends a message to list-join, and there is an autoresponder at that address, the address is subscribed to the list without the subscriber being aware of it. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662163&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] Strangely broken list discovered
I have a list that is one of about ten in a particular domain. The list has been unused for about 8 months (it's a seasonal thing), but someone sent a message to it, and the moderator message I got had the wrong URL in it. The list is at the domain , but some poking around at it showed that the admindb part thought that it was at . Everything else about it seemed ok, but I couldn't handle any admin requests because all the links on the admindb pages were pointing to the www host. I dumped the list out with config_list, but there was no mention of in there. Not having any other ideas, I deleted and recreated the list, and now all is well. I still have the list files on a backup if someone (i.e. Barry) wants to take a look at this. Since I don't know what version of Mailman created the list, possibly a 2.0 variant or early 2.1 beta, I can't say whether this is a real bug, but I wanted this to go on record in case it happens to someone else. - Stoney -- Stonewall Ballard [EMAIL PROTECTED] http://stoney.sb.org/ ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Feature Requests-662277 ] Encryption feature
Feature Requests item #662277, was opened at 2003-01-04 18:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Encryption feature Initial Comment: A feature that would allow a listmember to submit a PGP/GnuPG key to Mailman and thereafter all mail sent to that listmember would be encrypted with that key. Obviously, this would imply individual mail delivery to that user as it would no longer be possible to send the same mail to everyone. Also obviously, this would only really be possible for list servers with some spare CPU cycles... -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Feature Requests-662277 ] Encryption feature
Feature Requests item #662277, was opened at 2003-01-04 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Encryption feature Initial Comment: A feature that would allow a listmember to submit a PGP/GnuPG key to Mailman and thereafter all mail sent to that listmember would be encrypted with that key. Obviously, this would imply individual mail delivery to that user as it would no longer be possible to send the same mail to everyone. Also obviously, this would only really be possible for list servers with some spare CPU cycles... -- Comment By: Matthew Davis (big-dog) Date: 2003-01-04 13:59 Message: Logged In: YES user_id=34240 Take a look at http://sourceforge.net/tracker/index.php?func=detail&aid=645297&group_id=103&atid=300103 I think it's for one of the beta's. But it should get you pointed in the right direction. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-645297 ] Add PGP support
Patches item #645297, was opened at 2002-11-28 14:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Ben Laurie (benl) Assigned to: Nobody/Anonymous (nobody) Summary: Add PGP support Initial Comment: Support PGP encrypted lists using GnuPG. -- Comment By: David Shaw (dmshaw) Date: 2003-01-04 19:59 Message: Logged In: YES user_id=606006 Another vote of support. I actually submitted an enhancement request earlier today for exactly this. -- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:37 Message: Logged In: YES user_id=147905 Adding a vote of support for this patch. Please add it as soon as it's appropriate! I've been waiting a long time for this functionality and I'd hate to see the patch bitrot. :-) Adam. -- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-12 03:56 Message: Logged In: YES user_id=12800 I have to defer this patch until after MM2.1 since we're about ready for the first release candidate. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Feature Requests-662324 ] Per-user anonymous posting
Feature Requests item #662324, was opened at 2003-01-04 20:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662324&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Per-user anonymous posting Initial Comment: It would be useful for list members to have the ability to post anonymously to the list. This would entail mangling the "From" address in some way (pushing it through SHA-1?), and possibly searching the message body for the member's email address for similar mangling. Obviously this would not be complete anonymitity, as Mailman and the list admin needs to know what the real address for the user is, but it would be sufficient to keep the list members anonymous from each other. This is similar to the current anonymous_list feature, but different in that anonymous users and non-anonymous users can interact on the same list. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662324&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Feature Requests-662334 ] Remove additional recpientsfrom postings
Feature Requests item #662334, was opened at 2003-01-04 16:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662334&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Remove additional recpients from postings Initial Comment: I have a serious problem with people cc'ing lists along with other recipients. It's a bad idea for those other recipients to have their email addresses exposed via the lists, and it's a lot of trouble to get people to re-send messages with the other recpients stripped out. Lists should have a configuration flag that removes all recpients from the TO and CC headers except for the list address. This must happen before archiving. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662334&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders
At 11:49 +0100 1/3/2003, Fil wrote: >> SB> I've recently discovered that vacation autoresponders will >> SB> subscribe recipients to Mailman lists when they get "invited". >> >> Dang. This is because the From address contains the confirmation >> cookie encoded in the address. This might kill this idea for >> ease-of-use confirmations. > >I would imagine that, if the autoresponder is set to answer emails coming >with a 'Precedence: list' header, the bug is with them, not with Mailman. >You don't want to kill a good functionality just because most autoresponders >are very poorly written - avoiding loops is enough ;) Well, there are different needs for different Mailman sites. If you have to convince your provider that every address in your list truly wanted to be there, it's "unhandy" for there to be such a simple example of involuntary subscription, which the provider can demonstrate at will. Same for sites which choose to block phoney "opt in" schemes, and which contain members of your list. --John -- John Baxter [EMAIL PROTECTED] Port Ludlow, WA, USA ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-662472 ] scrubber arbitrary extension change forattachments
Bugs item #662472, was opened at 2003-01-04 23:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662472&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jorge Becerra (jlbpcuba) Assigned to: Nobody/Anonymous (nobody) Summary: scrubber arbitrary extension change for attachments Initial Comment: the archiver scrubber seems to honor the mimetypes, but not the file extensions. He change the extension other , even when use some that have the same mimetypes and don´t keep the same, he changes to the first with the same mimetypes taked from mimetypes.py or some other order. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662472&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-662490 ] not mimetype return
Bugs item #662490, was opened at 2003-01-05 01:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662490&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jorge Becerra (jlbpcuba) Assigned to: Nobody/Anonymous (nobody) Summary: not mimetype return Initial Comment: Attachments acces using the Mailman cgi-wrapper (private) don´t get the proper mimetype -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662490&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-662504 ] Mailman Admin Notification Racing
Bugs item #662504, was opened at 2003-01-05 02:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662504&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ian Wilson (tacgeek) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman Admin Notification Racing Initial Comment: Hi folks; When a non-list member sends a message to a list, I start to receive emails in a race format...up to about 20 a minute in some instances. Here's how to replicate problem (for those who need to know, and please understand I'm not being a smartbutt, but someone who is just confused with this behavior). 1.) Create new list 2.) Add your email in list administrator's area 3.) Save 4.) Send an email to list from a non-subscribed list 5.) Watch the fireworks on your Admin Email I'm having to go in, stop qrunner, then delete the request.db file before starting qrunner before the race condition stops. Any help would be appreciated! Ian [EMAIL PROTECTED] -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662504&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
