http://permalink.gmane.org/gmane.mail.mailman.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.mail.mailman.user/75046 <pre> See the script at &lt;http://www.msapiro.net/scripts/change_member_address.py&gt;. </pre> Mark Sapiro 2013-05-17T19:27:35 http://permalink.gmane.org/gmane.mail.mailman.user/75045 <pre>We are going to change one of the domain names we have. I have a few lists where members of these lists will need to have their email addresses changed. member1&lt; at &gt;old-domain.com -&gt; member1&lt; at &gt;new-domain.com I am aware of a few ways I could do this. One is pipe the list's members into a file, delete the list, and recreate the members. Or just do an add-the-new and delete-the-old. Is there any way other than this? Thanks steve campbell ------------------------------------------------------ Mailman-Users mailing list Mailman-Users&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org </pre> Steve Campbell 2013-05-17T18:04:54 http://permalink.gmane.org/gmane.mail.mailman.user/75044 <pre> I just updated them to include a warning about the scrub_nondigest situation. </pre> Mark Sapiro 2013-05-17T17:54:07 http://permalink.gmane.org/gmane.mail.mailman.user/75043 <pre> They are as good as any. The issue here is that bin/arch --wipe will fix the links to attachments scrubbed during the archiving process. However, for attachments scrubbed during incoming message processing because scrub_nondigest is Yes, the situation is different. The attachment was saved in the attachments directory and replaced by a link in the actual message body. Thus, the LIST.mbox file contains only the link in the body and the only place the scrubbed attachment exists is in the attachments directory on the old server. The only way to fix this is to move the actual files from the attachments directory on the old server and update the links manually or possibly with some programmatic process. </pre> Mark Sapiro 2013-05-17T17:34:53 http://permalink.gmane.org/gmane.mail.mailman.user/75042 <pre>An update... On May 16, 2013, at 14:48 PM, Matthew Needham &lt;mneedham&lt; at &gt;hdfgroup.org&gt; wrote: The URL in the archives is updated for attachments that were received when scrubbing is OFF. For attachments that were received when scrubbing is ON, the URL is not rewritten and still points to the old list. Incidentally, message headers report that this is Mailman 2.1.15. Thanks. </pre> Matthew Needham 2013-05-17T15:45:40 http://permalink.gmane.org/gmane.mail.mailman.user/75041 <pre>Hey list, I'm not sure if anyone has done this before (probably), but I figured I'd run my solution by those more knowledgeable of the inner workings of GNU Mailman. My Python 3 / PyGI / Gtk+ application, among other things, prompts a user for their name, email, and password, and then submits an http POST request to a hard coded remote GNU Mailman server. So far, the code appears to work and I'll request a peer review by anyone kind enough: &lt;http://rod.gs/Cbq&gt; One potential concern I've found is that it is difficult to machine parse the server response to reliably distinguish a successful subscription from a failure. A successful subscription returns an http code 200, but so do many failed ones (e.g. bad formatted email address is still code 200). The most reliable brute force method I could come up with was to check the message body of the returned HTML document for the substring "Your subscription request has been received". Great, except since Mailman is i18n capable, its gettext could return som</pre> Kip Warner 2013-05-17T08:50:49 http://permalink.gmane.org/gmane.mail.mailman.user/75040 <pre> I have a mailman install under cPanel, and I need to move my lists from listname&lt; at &gt;bigdata.org to listname&lt; at &gt;lists.bigdata.org. I've read quite a few webpages about how to move lists and rename lists, and I've done a lot of testing. I feel like I'm very close to getting this to work. The only problem that remains is scrubbed attachments. I've followed the directions at http://wiki.list.org/pages/viewpage.action?pageId=4030617, and while it says that "links to scrubbed attachments [that] point to the oldlist" can be fixed with "bin/arch --wipe newlist", this doesn't work for me. the command completes without error, but when I look at an archived message, the I still see "URL: &lt;http://mail.bigdata.org/mailman/private/listname_bigdata.org/attachments/20130513/5d587194/attachment.obj&gt; I have two questions. 1. For the situation I described, are the instructions on that FAQ (moving the files) the ones I should be following? 2. Should the arch --wipe command really be fixing the links to the scrubbed attachments</pre> Matthew Needham 2013-05-16T19:48:01 http://permalink.gmane.org/gmane.mail.mailman.user/75039 <pre>On 5/15/2013 10:45 AM, Dave Jones wrote, in part: Since Mark did not respond to this, I will. Mailman is not listserv. "Listserv" is a registered trademark of L-soft, and is one of a number of Mailing List Management software packages available. Mailman is another MLM software package. (I first met the founder of L-soft when he was still a student in Paris.) --Barry Finkel ------------------------------------------------------ Mailman-Users mailing list Mailman-Users&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org </pre> Barry S. Finkel 2013-05-17T14:24:46 http://permalink.gmane.org/gmane.mail.mailman.user/75038 <pre>Hi all, thanks for your help, it is much appreciated. Mark wrote: Wow - ancient indeed. Must have been around the time i played text-based adventures in my local mailbox here. Whoops, memories coming up :-) And here Stephen is completely correct in assuming: Mailman doesn't change anything in the body as such, however I get reports from multiple users that their MUAs do not show the picture as an attachment if there is a MIME object behind. At least the following MUAs seem to be affected: - Thunderbird 17.0.4 - Outlook 11 - Outlook 14 Outlook 14 (= MS Office 2010, if I remember correctly) is also the one producing the uuencoding. Google revealed that this seems to be a known issue and does indeed happen with attachments to plaintext-mails if the respective switch in outlook is set. So I will have that user correct his setting and all should be fine then. The fact that this did not happen before migrating to the current mailman version could (in this light) be due to a possible re-installation or</pre> Jan Lausch 2013-05-17T09:25:11 http://permalink.gmane.org/gmane.mail.mailman.user/75037 <pre> &gt; On 05/16/2013 01:48 AM, Jan Lausch wrote: &gt; &gt; Is that a correct MIME-set? As Mark says, it's conformant to MIME in that a MIME conforming MUA is perfectly happy to process that encoded file as part of the message body's text, completely oblivious to the fact that it's really an image. It's incorrect in that it doesn't do what the users expect. &gt; &gt; But still this malformatted mail does work if sent directly to &gt; &gt; recipient (not via mailman) and still does NOT have the delimiter &gt; &gt; then. It only breaks when sent via mailman. Obviously things &gt; &gt; stop working when mailman adds the delimiter consisting the &gt; &gt; msg_footer. &gt; &gt; Which is the part I don't understand. Mailman's msg_footer comes after &gt; the "end" of the uuencoded data, so what's the problem? I would guess that some recipient MUA readded uuencode support only as a bug fix without really thinking about what they were doing, and it's only supported at the end of a message in the MIME trailer. &gt; &gt; Does anyone have an idea on what to</pre> Stephen J. Turnbull 2013-05-17T01:46:19 http://permalink.gmane.org/gmane.mail.mailman.user/75036 <pre> This is a pre-MIME uuencoded attachment. Mailman does not understand that the uuencoded data is an "attachment". To Mailman, it is just part of the plain text message body. However, I don't understand why adding msg_footer to the body would "break" the mail. Mailman should not be changing anything in the body between the begin and end delimiters so the uuencoded data chould be intact. [...] No. It is an obsolete method of adding a uuencoded file to an email message and predates MIME. Which is the part I don't understand. Mailman's msg_footer comes after the "end" of the uuencoded data, so what's the problem? Tell your user to upgrade to a MIME compliant MUA. Yes, msg_footer can be empty and Mailman won't add anything. </pre> Mark Sapiro 2013-05-16T17:19:16 http://permalink.gmane.org/gmane.mail.mailman.user/75035 <pre> --On May 16, 2013 10:48:31 +0200 Jan Lausch &lt;Jan.Lausch&lt; at &gt;gmx.de&gt; wrote: That's an ancient pre-MIME encoding called uuencode. I am amazed that any modern software would create it. Joseph Brennan Columbia University Information Technology ------------------------------------------------------ Mailman-Users mailing list Mailman-Users&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org </pre> Joseph Brennan 2013-05-16T17:17:08 http://permalink.gmane.org/gmane.mail.mailman.user/75034 <pre>Dear all, I've got a strange problem that I'd ask for help with. I tried to word it as easy I could. Abstract: Some MUAs send picture-attachments not seperated by MIME-delimiters, but by "begin" and "end". Mailman adding the list footer with a MIME-delimiter breaks these mails. Detailed description:  Since migrating a list to a new server (mailman 2.1.12), mails with attachments (pictures) coming from one of the subscribers come with the picture not as picture but as plaintext within the mail. However the same mail, sent directly (not over list) looks fine. It seems the extra MIME element (list footer) added by mailman, breaks the MIME set. As I said: with the old server (older mailman) this did not happen. Let's look at the details:   Example what a broken mail looks like: ------------ This is the body of the email blablabla begin 666 examplepicture.jpg M_]C_X `02D9)1&lt; at &gt;`!`0$`2 !(``#_X0_^17AI9&lt; at &gt;``34T`*&lt; at &gt;````&lt; at &gt;`"&lt; at &gt;$/``(` M```&amp;````A&lt; at &gt;$0``(````)````C $2``,````!``$```$:``4````!````E&lt; at &gt;$; M``4````!````G&lt; at &gt;$H``,````</pre> Jan Lausch 2013-05-16T08:48:31 http://permalink.gmane.org/gmane.mail.mailman.user/75033 <pre> If the MTA (Postfix) is returning a 4xx status for the domain not found, Mailman will move the queue entry to the retry queue and it will be retried (moved back to the out queue) every DELIVERY_RETRY_WAIT seconds (default 1 hour) until it is DELIVERY_RETRY_PERIOD (default 5 days) old at which time the remaining undelivered recipients will be treated as a bounce. If that is too long to wait, you can shorten the time by setting DELIVERY_RETRY_PERIOD = days(1) or maybe DELIVERY_RETRY_PERIOD = hours(12) or whatever in mm_cfg.py, or since the deliverable addresses should have been delivered, simply remove the .pck file from the queue. To be more selective about which recipients to remove, see &lt;http://www.msapiro.net/scripts/remove_recips&gt; Then this is not what you want as it would affect all mail. Further, it just moves the problem to Postfix which probably keeps retrying at intervals until its expiration time elapses. </pre> Mark Sapiro 2013-05-16T03:48:33 http://permalink.gmane.org/gmane.mail.mailman.user/75032 <pre>I'm having problems with DOMAIN not found errors. Is there anyway to edit/remove them from the qfiles/out .pck files? They don't seem to be getting purged by mailman and hang around way too long. I'm using postfix and mailman 2.1.12 under ubuntu 8.04. I found item 4.20 in the FAQ, but I'm not sure if it would work and still working on learning postfix as my normal admin is ill. I'd only want it to work for mailman and not for other users regarding this problem. I'm disabled due to vision problems so I did look through the archives until my eyes went buggy. Thanks ------------------------------------------------------ Mailman-Users mailing list Mailman-Users&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org </pre> Richard Shetron 2013-05-16T00:02:16 http://permalink.gmane.org/gmane.mail.mailman.user/75031 <pre> That's a side-effect that we don't want. This looks reasonable. I think this is sufficiently useful to justify supporting without patching, but this patch isn't hard to carry. Thanks for your detailed answer. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org </pre> Jed Brown 2013-05-15T20:36:18 http://permalink.gmane.org/gmane.mail.mailman.user/75030 <pre> I guess that depends on what you call a configuration option. You could put this in mm_cfg.py GLOBAL_PIPELINE.remove('AvoidDuplicates') That would just remove the Handler so every list member that is a direct recipient would receive both the list and the direct copy regardless of her avoid duplicates setting, or you could apply the attached patch to Mailman/Handlers/AvoidDuplicates.py, or you could patch the module but name the patched module say Mailman/Handlers/MyAvoidDuplicates.py and put GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('AvoidDuplicates'), 'MyAvoidDuplicates') GLOBAL_PIPELINE.remove('AvoidDuplicates') im mm_cfg.py. See the FAQ at &lt;http://wiki.list.org/x/l4A9&gt;. Note: the first line is wrapped but it doesn't matter because of Python's implies continuation inside parens. Also note that this latter method is preferable to simple patching AvoidDuplicates.py for reasons mentioned in the FAQ. </pre> Mark Sapiro 2013-05-15T20:24:31 http://permalink.gmane.org/gmane.mail.mailman.user/75029 <pre> Okay, thanks. I'll talk with the others here and decide what to do. Yeah, I saw that, but I don't care how long the Cc list gets. I would rather allow people to filter aggressively and not worry about missing posts that may be relevant to them. It's common on other lists (evidently not those managed by mailman, vger.kernel.org is a high-profile example) to by convention, always Cc everyone that is likely to be interested. Asking recipients to write rules in terms of thread ancestry isn't sufficient either: when we later do more work that is somehow related, we might start a new thread and Cc everyone from prior threads that were related. If the list chronically drops Cc, it can be hard to figure out everyone that should be Cc'd in a new topic. Anyway, can I interpret your response as being that mailman always drops Cc and there is no configuration option? ------------------------------------------------------ Mailman-Users mailing list Mailman-Users&lt; at &gt;python.org http://mail.python.org/mailman/listinf</pre> Jed Brown 2013-05-15T19:47:10 http://permalink.gmane.org/gmane.mail.mailman.user/75028 <pre> The Message-ID of the post is in the HTML page containing the post, but it is only in an In-Reply-To= fragment of a mailto: URL that isn't indexed in htdig. Also, it's URL encoded so &lt;, &gt; and &lt; at &gt; are %3C, %3E and %40 respectively. The actual Message-ID: headers are in the periodic *.txt files. This leads to a few possibilities such as teaching htdig to index the .txt files (may be tricky, I just spent a couple of minutes looking at this and didn't see it), changing the noindex start and end tags in the list's archives/private/LIST/htdig/LIST.conf file so that everything in the HTML files including the URL encoded Message-ID is indexed or writing a separate CGI search script to search the .txt files for the Message-ID. Or, use mail-archive.com which is probably simplest. I've learned a lot in the last 7 years ;) The reason is to keep the Cc: list from growing excessively long in long threads involving many people (see the subsequent post(s) in that thread). </pre> Mark Sapiro 2013-05-15T19:33:27 http://permalink.gmane.org/gmane.mail.mailman.user/75027 <pre>... I'm sorry, you're correct, Mark. I forgot you told me earlier how to write such a handler which I implemented successfully. You said: So I guess the real question is "how do I postpone that handler until AFTER the check for whether the poster is a member?" After reviewing the original implementation instructions I think I can fix the problem. Consider the problem solved unless I run into problems. Thanks so much! Best regards, -Tom ------------------------------------------------------ Mailman-Users mailing list Mailman-Users&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org </pre> Tom Browder 2013-05-15T19:08:06 http://permalink.gmane.org/gmane.mail.mailman.user/75026 <pre> Mailman can do this, but it requires a custom handler &lt;http://wiki.list.org/x/l4A9&gt;. Alternatively, you could use header_filter_rules with a regexp like "^From:(.|\n)*^From:" to detect multiple From: headers and reject the post. </pre> Mark Sapiro 2013-05-15T18:21:35 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.mail.mailman.user