From mark at msapiro.net Fri Jan 1 15:31:41 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 01 Jan 2010 14:31:41 -0000 Subject: [Bug 502022] Re: RFE: provide option to email displayed message to email address References: <20100101063551.28125.70819.malonedeb@wampee.canonical.com> Message-ID: <20100101143141.10901.69276.malone@potassium.ubuntu.com> This ability already exists. If the site is configured with ARCHIVER_OBSCURES_EMAILADDRS = Yes (the default), the poster's obscured email address is a mailto: link with the list posting address and appropriate Subject= and In-Reply-To= fragments. Of course, it is up to the MUA that handles the mailto: to understand these. The other issue is that archive threading is by archive index period, so if the archive is indexed by month, a reply in January to a December post will be indexed in January and (in pipermail at least) can't be threaded to the December thread. For your second use-case, you can use the same mailto: link to reply, and if your non-member post arrives in the same index period and is accepted, it will be threaded with the post you replied to. Is there some other reason why you would want an archived post to be mailed to you? Archiving will be enhanced in MM3, and we will keep this request in mind. ** Changed in: mailman Importance: Undecided => Wishlist ** Changed in: mailman Status: New => Triaged -- RFE: provide option to email displayed message to email address https://bugs.launchpad.net/bugs/502022 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From lists at whitehouse.org.nz Fri Jan 1 07:35:51 2010 From: lists at whitehouse.org.nz (Aaron Whitehouse) Date: Fri, 01 Jan 2010 06:35:51 -0000 Subject: [Bug 502022] [NEW] RFE: provide option to email displayed message to email address References: <20100101063551.28125.70819.malonedeb@wampee.canonical.com> Message-ID: <20100101063551.28125.70819.malonedeb@wampee.canonical.com> Public bug reported: Very often, I will come across a new piece of information on a topic that has previously been discussed on the list. I will then search through my email accounts to try and find a copy of an email in that thread and reply to it, so that the message is correctly archived in the list manager etc. Quite a lot of times, I will have deleted the relevant message. I then have to find it on the list, which is not a problem. Because I don't have a copy of the email to reply to, I can't reply to the thread and make it come up as part of the thread. At best, I can create a new email and add a permalink to the original thread. This would not, however, allow people browsing the old thread in the archives to see the newer information. What would be ideal (and which I have seen implemented in other list managers, but cannot remember where) would be if, after finding a post in the archives, one could click a button and enter an email address to have that message (with all thread headers etc.) emailed to that email address again. Then the user could simply reply to the new email to have the threading properly maintained. A second, related use-case is for people who aren't on the list and find a "hanging" thread in the archives. I often Google and find threads that end with something like "I will provide an update on this soon" with no following update. It would be nice, even if I wasn't on the mailing list, to have that one email sent to me so that I could reply and maintain threads. ** Affects: mailman Importance: Undecided Status: New -- RFE: provide option to email displayed message to email address https://bugs.launchpad.net/bugs/502022 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From lists at whitehouse.org.nz Fri Jan 1 23:52:20 2010 From: lists at whitehouse.org.nz (Aaron Whitehouse) Date: Fri, 01 Jan 2010 22:52:20 -0000 Subject: [Bug 502022] Re: RFE: provide option to email displayed message to email address References: <20100101063551.28125.70819.malonedeb@wampee.canonical.com> <20100101143141.10901.69276.malone@potassium.ubuntu.com> Message-ID: <196947f21001011452i218e8477y767f39de8074923a@mail.gmail.com> Thanks Mark for the very quick and helpful response! I hadn't realised that. Perhaps this could be made clearer with an identical link next to the email address saying "(reply to this message)", or something. I also hadn't realised that the threading was limited to single months. That seems a bit of a limitation to me and I hadn't realised it. Perhaps there are a few threads that I haven't seen the end of for this reason and hadn't thought to look at the next month's threads (as there were no more "next in this thread"s). It would be excellent if this could be kept in mind through the MM3 enhancements. If nothing else, having complete threads (including those in following months) prevents threads being reopened by people finding them in the archives. The one use-case that the current method does not work for, and an "email this to me" link would, is actually one that I face at the moment: I am away (and so don't have the originals of the emails) and am using webmail to clear my messages. The machine is set up for somebody else's email (the people I am staying with), so "mailto" links don't work. If it emailed me the message, I could reply to it with webmail. Probably not an uncommon use-case when so many people are using GMail etc. instead of an email client. Please feel free to alter the subject etc. to better fit what remains to be enhanced. -- RFE: provide option to email displayed message to email address https://bugs.launchpad.net/bugs/502022 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Wed Jan 6 16:11:48 2010 From: barry at canonical.com (Barry Warsaw) Date: Wed, 06 Jan 2010 15:11:48 -0000 Subject: [Bug 490602] Re: sourcecode/mailman/configure.in does not support group names with spaces References: <20091201014437.30616.84069.malonedeb@gandwana.canonical.com> Message-ID: <20100106151148.18974.78560.malone@gangotri.canonical.com> This is not worth fixing. Mailman 3 doesn't use the same mechanism, and in all the years of MM2 development, this is the first such complaint about this I've seen. I didn't even know spaces in group names on *nix was allowed . ** Changed in: mailman Status: Confirmed => Won't Fix -- sourcecode/mailman/configure.in does not support group names with spaces https://bugs.launchpad.net/bugs/490602 You received this bug notification because you are a member of Mailman Coders, which is a direct subscriber. From raph+mailman at mankin.org.uk Wed Jan 6 19:14:58 2010 From: raph+mailman at mankin.org.uk (Raphael Mankin) Date: Wed, 06 Jan 2010 18:14:58 -0000 Subject: [Bug 265965] Re: url parse (probably) cannot handle port number References: <20080905192733.27052.47865.launchpad@forster.canonical.com> Message-ID: <20100106181458.12823.41363.malone@potassium.ubuntu.com> In particular, all mails sent from mailman have the port number on the end of the reply address. This causes certain mail servers to reject the messagges. A workaround is to have two web listeners, one on port 80 and one on the real port e.g. 8080. One then redirects all mailman requests on port 80 to the other port. I do this because I have to have my main web server and my mailman web server running as different users. The problem is current in 2.1.12 -- url parse (probably) cannot handle port number https://bugs.launchpad.net/bugs/265965 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Thu Jan 7 04:11:06 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 Jan 2010 03:11:06 -0000 Subject: [Bug 265965] Re: url parse (probably) cannot handle port number References: <20080905192733.27052.47865.launchpad@forster.canonical.com> Message-ID: <20100107031106.19542.34844.malone@palladium.canonical.com> The original bug is invalid. If the site is properly configured with the appropriate port in DEFAULT_URL_PATTERN and PUBLIC_ARCHIVE_URL in mm_cfg.py the web interface works fine. E.g. DEFAULT_URL_PATTERN = 'http://%s:8080/mailman PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:8080/pipermail/%(listname)s' After making such a change in mm_cfg.py, you need to run fix_url to update existing lists. See the FAQs at and . The issue in the comment from Raphael Mankin is probably because the list's host_name attribute has a port. It should not. This in turn probably results from having a port appended to DEFAULT_EMAIL_HOST or the host in an add_virtualhost() directive. This is a misconfiguration. Note that the list's host_name is exposed and can be changed on the list's General Options admin page. ** Changed in: mailman Status: New => Invalid -- url parse (probably) cannot handle port number https://bugs.launchpad.net/bugs/265965 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From raphael.barrois_launchpad at m4x.org Thu Jan 7 15:53:45 2010 From: raphael.barrois_launchpad at m4x.org (=?utf-8?q?Rapha=C3=ABl_Barrois?=) Date: Thu, 07 Jan 2010 14:53:45 -0000 Subject: [Bug 266760] Re: moderation approval should send email notification References: <20080905194239.1806.20962.launchpad@forster.canonical.com> Message-ID: <20100107145345.31612.13809.malone@wampee.canonical.com> I think this functionnality would be quite useful for mailing lists used with "non-tech" users, who don't understand why they aren't notified of their message being approved... -- moderation approval should send email notification https://bugs.launchpad.net/bugs/266760 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From raphael.barrois_launchpad at m4x.org Thu Jan 7 15:54:46 2010 From: raphael.barrois_launchpad at m4x.org (=?utf-8?q?Rapha=C3=ABl_Barrois?=) Date: Thu, 07 Jan 2010 14:54:46 -0000 Subject: [Bug 266760] Re: moderation approval should send email notification References: <20080905194239.1806.20962.launchpad@forster.canonical.com> Message-ID: <20100107145446.14875.7668.malone@gandwana.canonical.com> --- Acknowledge.py.orig 2010-01-07 15:50:01.000000000 +0100 +++ Acknowledge.py 2010-01-07 15:50:43.000000000 +0100 @@ -38,7 +38,8 @@ if not ack: return except Errors.NotAMemberError: - return + if not mlist.notify_nonmembers_post_approved: + return # Okay, they want acknowledgement of their post. Give them their original # subject. BAW: do we want to use the decoded header? origsubj = msgdata.get('origsubj', msg.get('subject', _('(no subject)'))) -- moderation approval should send email notification https://bugs.launchpad.net/bugs/266760 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From daniel.holbach at ubuntu.com Fri Jan 15 10:40:41 2010 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Fri, 15 Jan 2010 09:40:41 -0000 Subject: [Bug 507841] [NEW] show list moderators on listinfo page too References: <20100115094041.3016.71600.malonedeb@gandwana.canonical.com> Message-ID: <20100115094041.3016.71600.malonedeb@gandwana.canonical.com> Public bug reported: It would be nice if the listinfo page wouldn't just show "list is run by X, Y and Z" but also who's moderating it. For a big project this would help to find lists with inactive moderators and admins, but also increase the transparency of the project. As far as I can see this would need to be fixed in Mailman/HTMLFormatter.py. ** Affects: mailman Importance: Undecided Status: New -- show list moderators on listinfo page too https://bugs.launchpad.net/bugs/507841 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Fri Jan 22 05:48:12 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 22 Jan 2010 04:48:12 -0000 Subject: [Bug 266164] Re: Private archive specific message URL lost in authorization References: <20080905192912.27052.10264.launchpad@forster.canonical.com> Message-ID: <20100122044813.13032.8032.malone@gandwana.canonical.com> The original fix released in Mailman 2.1.7 was incomplete. It didn't properly account for http://www.example.com/mailman/private/list- name.mbox/listname.mbox URLs. This oversight has been corrected and committed on the 2.1 branch at rev 1217. ** Changed in: mailman Importance: Medium => Low ** Changed in: mailman Status: Fix Released => Fix Committed ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** Branch linked: lp:mailman/2.1 ** Branch linked: lp:mailman/2.2 -- Private archive specific message URL lost in authorization https://bugs.launchpad.net/bugs/266164 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From petri.koistinen at iki.fi Wed Jan 27 12:38:46 2010 From: petri.koistinen at iki.fi (Petri Koistinen) Date: Wed, 27 Jan 2010 11:38:46 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20100127113846.17424.63981.malone@gangotri.canonical.com> What does this "Declined for Hardy by Thierry Carrez" means, what is the reasoning behind declining this update to hardy (8.04 LTS) release? -- Logrotate is noisy with: Re-opening all log files https://bugs.launchpad.net/bugs/244233 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From petri.koistinen at iki.fi Wed Jan 27 12:44:22 2010 From: petri.koistinen at iki.fi (Petri Koistinen) Date: Wed, 27 Jan 2010 11:44:22 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20100127114422.16538.14754.malone@wampee.canonical.com> Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456954 ** Bug watch added: Debian Bug tracker #456954 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456954 ** Changed in: mailman (Ubuntu) Status: Fix Released => Incomplete ** Changed in: mailman (Ubuntu) Assignee: (unassigned) => Thierry Carrez (ttx) -- Logrotate is noisy with: Re-opening all log files https://bugs.launchpad.net/bugs/244233 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From thierry.carrez at ubuntu.com Wed Jan 27 13:43:14 2010 From: thierry.carrez at ubuntu.com (Thierry Carrez) Date: Wed, 27 Jan 2010 12:43:14 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20100127124314.20523.7495.malone@potassium.ubuntu.com> Bug is fix released in the current development version. Bug was rejected for hardy SRU since stable release updates are here to address "high-impact" bugs, and during review this was not considered to be high-impact. See https://wiki.ubuntu.com/StableReleaseUpdates#When ** Changed in: mailman (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mailman (Ubuntu) Assignee: Thierry Carrez (ttx) => (unassigned) -- Logrotate is noisy with: Re-opening all log files https://bugs.launchpad.net/bugs/244233 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From petri.koistinen at iki.fi Thu Jan 28 11:18:30 2010 From: petri.koistinen at iki.fi (Petri Koistinen) Date: Thu, 28 Jan 2010 10:18:30 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20100128101830.19867.6783.malone@soybean.canonical.com> I think this fits just fine to this definition: * Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel). ** Changed in: mailman (Ubuntu) Status: Fix Released => Incomplete ** Changed in: mailman (Ubuntu) Assignee: (unassigned) => Thierry Carrez (ttx) -- Logrotate is noisy with: Re-opening all log files https://bugs.launchpad.net/bugs/244233 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From thierry.carrez at ubuntu.com Thu Jan 28 13:51:27 2010 From: thierry.carrez at ubuntu.com (Thierry Carrez) Date: Thu, 28 Jan 2010 12:51:27 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20100128125127.24520.92733.malone@palladium.canonical.com> Approved, please follow https://wiki.ubuntu.com/StableReleaseUpdates#Procedure to submit SRU for consideration. ** Changed in: mailman (Ubuntu) Status: Incomplete => Triaged ** Changed in: mailman (Ubuntu) Assignee: Thierry Carrez (ttx) => (unassigned) -- Logrotate is noisy with: Re-opening all log files https://bugs.launchpad.net/bugs/244233 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From petri.koistinen at iki.fi Thu Jan 28 20:22:22 2010 From: petri.koistinen at iki.fi (Petri Koistinen) Date: Thu, 28 Jan 2010 19:22:22 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20100128192222.19867.63869.malone@soybean.canonical.com> It seems that I can't use "Nominate for release" as this has been previously declined for Hardy. ** Changed in: mailman (Ubuntu) Status: Triaged => Fix Released -- Logrotate is noisy with: Re-opening all log files https://bugs.launchpad.net/bugs/244233 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From thierry.carrez at ubuntu.com Thu Jan 28 20:34:27 2010 From: thierry.carrez at ubuntu.com (Thierry Carrez) Date: Thu, 28 Jan 2010 19:34:27 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20100128193427.23719.40954.malone@gandwana.canonical.com> @Petri: I thought I had nominated/approved it. Done now, sorry for the noise. ** Also affects: mailman (Ubuntu Hardy) Importance: Undecided Status: New -- Logrotate is noisy with: Re-opening all log files https://bugs.launchpad.net/bugs/244233 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Fri Jan 29 00:02:46 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 Jan 2010 23:02:46 -0000 Subject: [Bug 514050] [NEW] listinfo.html templates have a misplaced form start tag References: <20100128230247.24613.62377.malonedeb@palladium.canonical.com> Message-ID: <20100128230247.24613.62377.malonedeb@palladium.canonical.com> Public bug reported: The tag which generates the
tag for the subscribe form is in the entry for the language form. This generates invalid HTML which is a problem for at least some browsers. There is also no DOCTYPE directive and other misplaced tags that cause validation errors. ** Affects: mailman Importance: Undecided Status: New -- listinfo.html templates have a misplaced form start tag https://bugs.launchpad.net/bugs/514050 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Fri Jan 29 00:12:01 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 Jan 2010 23:12:01 -0000 Subject: [Bug 514050] Re: listinfo.html templates have a misplaced form start tag References: <20100128230247.24613.62377.malonedeb@palladium.canonical.com> Message-ID: <20100128231201.20625.38136.malone@potassium.ubuntu.com> Fixed at rev 1218 on the 2.1 branch. Previously fixed at rev 1041 on the 2.2 branch. ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1-stable ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** Branch linked: lp:mailman/2.1 ** Branch linked: lp:mailman/2.2 -- listinfo.html templates have a misplaced form start tag https://bugs.launchpad.net/bugs/514050 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Fri Jan 29 04:52:33 2010 From: barry at canonical.com (Barry Warsaw) Date: Fri, 29 Jan 2010 03:52:33 -0000 Subject: [Bug 490114] Re: Mailman should be compliant with the Filesystem Hierarchy Standard References: <20091129221530.31720.38380.malonedeb@potassium.ubuntu.com> Message-ID: <20100129035234.20387.92462.launchpad@potassium.ubuntu.com> ** Summary changed: - Mailman should be compliant with the File System Hierarchy + Mailman should be compliant with the Filesystem Hierarchy Standard ** Also affects: mailman/3.0 Importance: High Status: Triaged ** Changed in: mailman/3.0 Milestone: None => 3.0.0a6 -- Mailman should be compliant with the Filesystem Hierarchy Standard https://bugs.launchpad.net/bugs/490114 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From 490114 at bugs.launchpad.net Fri Jan 29 05:05:22 2010 From: 490114 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 29 Jan 2010 04:05:22 -0000 Subject: [Bug 490114] Re: Mailman should be compliant with the Filesystem Hierarchy Standard References: <20091129221530.31720.38380.malonedeb@potassium.ubuntu.com> Message-ID: <20100129040527.24713.90004.launchpad@loganberry.canonical.com> ** Branch linked: lp:mailman -- Mailman should be compliant with the Filesystem Hierarchy Standard https://bugs.launchpad.net/bugs/490114 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Fri Jan 29 05:05:11 2010 From: barry at canonical.com (Barry Warsaw) Date: Fri, 29 Jan 2010 04:05:11 -0000 Subject: [Bug 490114] Re: Mailman should be compliant with the Filesystem Hierarchy Standard References: <20091129221530.31720.38380.malonedeb@potassium.ubuntu.com> Message-ID: <20100129040511.19780.43590.malone@soybean.canonical.com> r6888 ** Changed in: mailman/3.0 Status: Triaged => Fix Committed ** Changed in: mailman/3.0 Assignee: (unassigned) => Barry Warsaw (barry) -- Mailman should be compliant with the Filesystem Hierarchy Standard https://bugs.launchpad.net/bugs/490114 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From stephen at xemacs.org Sat Jan 30 07:04:32 2010 From: stephen at xemacs.org (Stephen Turnbull) Date: Sat, 30 Jan 2010 06:04:32 -0000 Subject: [Bug 514625] [NEW] Mailman 3 member functions should "guess" address membership References: <20100130060432.12561.63827.malonedeb@gandwana.canonical.com> Message-ID: <20100130060432.12561.63827.malonedeb@gandwana.canonical.com> Public bug reported: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull at sk.domain.tld" is subscribed, then "turnbull at shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname at xemacs.org and lastname at xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull at shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for . [ ] Add as an alias for ." ** Affects: mailman Importance: Undecided Status: New ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull at sk.tsukuba.ac.jp" is subscribed, then "turnbull at shako.sk.tsukuba.ac.jp" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname at xemacs.org and lastname at xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull at shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for . [ ] Add address as an alias for ." + address>. [ ] Add as an alias for ." ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against - the member database. For example, if "turnbull at sk.tsukuba.ac.jp" is - subscribed, then "turnbull at shako.sk.tsukuba.ac.jp" probably is the same + the member database. For example, if "turnbull at sk.domain.tld" is + subscribed, then "turnbull at shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname at xemacs.org and lastname at xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull at shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for . [ ] Add as an alias for ." -- Mailman 3 member functions should "guess" address membership https://bugs.launchpad.net/bugs/514625 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sat Jan 30 23:06:40 2010 From: barry at canonical.com (Barry Warsaw) Date: Sat, 30 Jan 2010 22:06:40 -0000 Subject: [Bug 514625] Re: Mailman 3 member functions should "guess" address membership References: <20100130060432.12561.63827.malonedeb@gandwana.canonical.com> Message-ID: <20100130220641.6549.63050.launchpad@palladium.canonical.com> ** Also affects: mailman/3.0 Importance: Undecided Status: New -- Mailman 3 member functions should "guess" address membership https://bugs.launchpad.net/bugs/514625 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.