Community
Participate
Working Groups
I got this today trying to send a message to EMF, EMFT, GMF, M2T, MDT, and M2M dev lists: Your mail to 'm2t-dev' with the subject Today's RC4 build schedule Is being held until the list moderator can review it for approval. The reason it is being held: Too many recipients to the message Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: https://dev.eclipse.org/mailman/confirm/m2t-dev/045425084efd3f0f50c1e2ab4c539eff31c740d0 --- Problem is that these lists don't have moderators, so they never get moderated. Why does sending a message to 7 mailing lists at the same time (to coordinate the Modeling projects' releases) cause this prevention of information services?
Maybe we need a modeling-dev@eclipse.org list?
(In reply to comment #1) > Maybe we need a modeling-dev@eclipse.org list? +1
(In reply to comment #0) > Why does sending a message to 7 mailing lists at the same time (to coordinate > the Modeling projects' releases) cause this prevention of information services? Mailing 7 lists is a bit of an exception, and the mailing list software has no idea that this is exactly what you want to do, so it's trying to uphold information services by avoiding a potential mail bomb to what could be zillions of innocent people. Indeed, a modeling-dev list covering all projects is likely what is best suited here.
I wonder if modeling-dev could simply have all the modeling-*-dev lists. Can a list be a member of a list?
(In reply to comment #4) > Can a list be a member of a list? I was going to ask you the same question.
Matt, Karl, do you know if a list can be a member of a list?
(In reply to comment #6) > Matt, Karl, do you know if a list can be a member of a list? Yes, they can. It's called an "umbrella list". We could definitely do this if that's what's needed.
I'd say it's needed, and with Rich's +1 it sounds like a great idea for coordinating the tail end of Ganymede (if your time permits) or else subsequent releases (if you're otherwise busy -- and who isn't?) :) So, here's what I'd propose should be under the umbrella for now: modeling-dev@ ------------- m2m-dev@ m2t-dev@ emft-dev@ emf-dev@ gmf-dev@ tmf-dev@ mdt.dev@ (note that this one is .dev, not -dev, because MDT wanted one mailing list per component [1]. I'd be thrilled if it got standardized -- Kenn, how much traffic do the MDT component lists get?) [1]http://www.eclipse.org/mail/index_project.php (ctrl-f for "mdt") Later, as they join the common releng fold, we can add: mddi-dev@ gmt-dev@ Or, if you prefer, we could do all 9 at once.
Don't forget amalgam, which is easy to forget given that it's absent from the home page, but that's another issue.
(In reply to comment #9) > Don't forget amalgam, which is easy to forget given that it's absent from the > home page, but that's another issue. Right. We should add amalgam-dev@ and gmt-dev@ too, but mddi-dev@ is not required as they're apparently being boxed for storage. http://dev.eclipse.org/mhonarc/lists/modeling-pmc/msg00719.html
I've set up modeling-dev@eclipse.org. If you're subscribed to any of its sub-lists, you shouldn't need to subscribe to it to post. From the mailman docs: One thing to note is that if a single subscriber is subscribed to more than one of the "sub" lists, they will receive multiple copies of any messages posted to the "umbrella" list. They will need to use a local mail filter to avoid multiple copies of the same post.
Denis, thanks for doing that!
Seems like it's not working yet. (In reply to comment #11) > I've set up modeling-dev@eclipse.org. If you're subscribed to any of its > sub-lists, you shouldn't need to subscribe to it to post. You must subscribe to mailing lists before you can post to them, using the same e-mail address as the one you're using to send e-mail. ... If you are a member of this list and you think that your messages are being rejected in error, contact the mailing list owner at modeling-dev-owner@eclipse.org. To subscribe to this list, or to any list, please go to http://www.eclipse.org/mail/ Subject: test post (see bug 236300) From: Nick Boldt <codeslave@ca.ibm.com> Date: Mon, 23 Jun 2008 17:22:02 -0400 To: modeling-dev@eclipse.org Content-Transfer-Encoding: 7bit Return-Path: <nickboldt@gmail.com> X-Original-To: modeling-dev@eclipse.org Delivered-To: modeling-dev@eclipse.org Received: from hs-out-0708.google.com (hs-out-0708.google.com [64.233.178.241]) by mail.eclipse.org (Postfix) with SMTP id AAB343E2E4 for <modeling-dev@eclipse.org>; Mon, 23 Jun 2008 17:22:36 -0400 (EDT) Received: by hs-out-0708.google.com with SMTP id x43so416751hsb.0 for <modeling-dev@eclipse.org>; Mon, 23 Jun 2008 14:22:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding:sender; bh=4cPh7EKlywJfei288k2k5nKmBKPKsoNE8RTUelNK06s=; b=jdPevBc2fSEKQpnTfvVoXvTgFGdnaC7o9K5iv1b9vMWvsbwnW3z7crIcvSkE4vjgKp 7R1UFX/MsIE5oqJ8eRylBrSc1m4Xk2YVJ1k7JT0W7d53/dNQnLt/v0OkasbDkUOvcl3x GFq6T1WlogQLG3nbhiNrxATQykoV6NcsrmLd4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:sender; b=aEfK8RpUdUQ7lrS4+SMbDYvpkhKtNeWkcHaz0KvCW6o7RfMfEOFOgtUjdygh9gcS35 7FJjHSCEbvbLQ8Ao9pojXksMhGa4CmEmhrMd97DFLJ71AM81s/JFTkI5CoVBAKBFkMje 0S8zBrkPox9bOhPWrNZe9evLC74yTlMYTGWX0= Received: by 10.100.41.15 with SMTP id o15mr14044599ano.48.1214256156373; Mon, 23 Jun 2008 14:22:36 -0700 (PDT) Received: from ?192.168.2.130? ( [99.244.57.240]) by mx.google.com with ESMTPS id d21sm14174933and.0.2008.06.23.14.22.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Jun 2008 14:22:35 -0700 (PDT) Message-ID: <486013FA.70202@ca.ibm.com> User-Agent: Mozilla-Thunderbird 2.0.0.6 (X11/20071113) MIME-Version: 1.0 Sender: Nick Boldt <nickboldt@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Tried again today and got told, once again, that I need to subscribe first. So, I signed up again, and never got the confirmation email re: signup. This says one of two things is broken: a) if we need to subscribe to modeling-dev@ to send to it and distribute from there to the child lists, then the subscription process needs to actually send me a note so I can confirm the subscription b) if we don't need to subscribe to modeling-dev@ in order to send to its children, then a switch needs to be flipped so that the list knows subscription is not required (as it'll be handled by the individual child lists' subscriptions, eg., if I'm not subscribed to tmf-dev@, but all the others, then I'll get one "you must be subscribed first" note and the rest will go thru sans problème)
Any chance we'll see some closure here? I sent a note to the various Modeling lists yesterday and it bounced as follows: Your mail to 'emft-dev' with the subject Re: Final Daze and Modeling Is being held until the list moderator can review it for approval. The reason it is being held: Too many recipients to the message
Ok, I've dug around in the documentation and settings and I think we now have a working solution that doesn't require you to sign up to modeling-dev. -M.
(In reply to comment #16) > Ok, I've dug around in the documentation and settings and I think we now have a > working solution that doesn't require you to sign up to modeling-dev. Look solution > What? Examine solution > The solution is flawless, and elegant in its simplicity. Unfortunately, it's in another castle, and thus cannot be documented here. Deducing the solution will be left as an exercise for the reader. Eat a peach > You don't see Princess Peach here. Maybe she's in another castle too?
I wasn't aware that the big N made text adventure games. The solution is to essentially auto-include everyone on the sub lists in the permitted senders section of modeling-dev. We update this nightly when we rebuild a bunch of other lists. According to the online docs the next new version of mailman is set to allow a 'simpler' solution to this problem. Stomp Bug > What? Jump bug > You jump directly on the bug. There is a disturbing sound as what used to be inside the bug covers the outside of your shoes. -M.
(In reply to comment #18) > I wasn't aware that the big N made text adventure games. https://bugs.eclipse.org/bugs/show_bug.cgi?id=198042#c2 > > You jump directly on the bug. There is a disturbing sound as what used to be inside the bug covers the outside of your shoes. So, to test this, I fired yet another email at modeling-dev@... and got this: You must subscribe to mailing lists before you can post to them, using the same e-mail address as the one you're using to send e-mail. However, technical questions and discussions about using eclipse and eclipse-based tools, and developing plug-in tools should be posted to the newsgroups at http://www.eclipse.org/newsgroups/ . Mailing list suffixed with -dev, such as eclipse-dev and platform-dev are intended for use by developers actually working on or otherwise contributing to day-to-day development. The development mailing lists are the way design and implementation issues are discussed and decisions voted on by the committers. If you are a member of this list and you think that your messages are being rejected in error, contact the mailing list owner at modeling-dev-owner@eclipse.org. To subscribe to this list, or to any list, please go to http://www.eclipse.org/mail/ Alternatively, you may subscribe to lists, and find list archives and RSS feeds at: http://dev.eclipse.org/mailman/listinfo/modeling-dev. Subject: This is a test of the modeling-dev@eclipse.org notification system From: Nick Boldt <nickboldt@gmail.com> Date: Mon, 22 Jun 2009 12:00:32 -0400 To: modeling-dev@eclipse.org This is a test of the modeling-dev@eclipse.org notification system. There is no need to reply, unless you didn't receive this email. If working correctly, this address will forward to emf-dev, emft-dev, m2m-dev, m2t-dev, mdt.dev (yes, "."), gmf-dev, & tmf-dev... and possibly amalgam-dev@. If not, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=236300 This has been a test of the modeling-dev@eclipse.org notification system. -- Nick Boldt :: http://nick.divbyzero.com Release Engineer :: Eclipse Modeling & Dash Athena
You enter a cubical room with no doors or windows, and wonder briefly how you got in. There is an email here. > Examine room You can see no way out. A bug scampers across the floor towards the email. > Examine email The email bears today's date, with a 2:18pm timestamp. It's from Webmaster Matt to modeling-dev@ and m2m-dev@. The headers suggest this email was received from the m2m-dev@ mailing list (cc:'d on the addressee list), not from modeling-dev@. > Shake 8-ball You shake your 8-ball. > 8-ball, is this bug fixed? Signs point to no. > Stomp bug. The bug disappears under your foot. When you lift it back up, it scampers away, seemingly unscathed. Evidently you will need more than a mere stomp to squash *this* bug. > Score Your score is still zero, after 19 turns. > Inventory You are carrying an email, an 8-ball and patience. Lots of patience.
Actually I was referring to Nintendo, based on your princess peach comment. From the gmf-dev inbox: <snip> Date: Mon, 22 Jun 2009 16:33:09 -0400 From: "Webmaster(Matt Ward)" <webmaster@eclipse.org> To: modeling-dev@eclipse.org Cc: Subject: [gmf-dev] [modeling-dev] Test Message #2 </snip> So it should be working. You may find you get multiple copies if you're on multiple child lists, but that seems to be unavoidable at this time(http://wiki.list.org/pages/viewpage.action?pageId=4030540). -M.
Created attachment 140304 [details] full email message bounce Still broken. Maybe I'm not subscribed using nickboldt@gmail.com, but nickboldt+bugzilla@gmail.com? Can you check who's subscribed to modeling-dev@?
Both are. I think the issue is the ';' that the script was using as a termination character between entries. Can you try your post again? -M.
This is sorta working. On July 7 I sent a note to modeling-dev@eclipse.org called "emft.eclipse.org is going down permanently in 8 days: Wednesday July 15 at 9:00am GMT-5 (EST)". Checking the archives, I see that it was sent to some lists, but not all: Found: http://dev.eclipse.org/mhonarc/lists/tmf-dev/2009/Jul/index.php http://dev.eclipse.org/mhonarc/lists/gmf-dev/2009/Jul/index.php http://dev.eclipse.org/mhonarc/lists/mdt.dev/2009/Jul/index.php http://dev.eclipse.org/mhonarc/lists/m2t-dev/2009/Jul/index.php http://dev.eclipse.org/mhonarc/lists/m2m-dev/2009/Jul/index.php http://dev.eclipse.org/mhonarc/lists/gmt-dev/2009/Jul/index.php Not found: http://dev.eclipse.org/mhonarc/lists/emf-dev/2009/Jul/index.php http://dev.eclipse.org/mhonarc/lists/emft-dev/ (no archives for June or July) http://dev.eclipse.org/mhonarc/lists/mddi-dev/ (no archives since Aug 2008!)
As an added bonus, it seems as though people who are on one of the modeling lists can send to modeling-dev@ via reply so all lists are copied on the thread. This is certainly a plus... now we just just emf-dev@ and emft-dev@ to be included in the loop. :)
EMF-dev should be ok now, there was a typo in on of the required settings fields. And I think I've finally nailed down the problem with emft-dev. Essentially we are experiencing: https://bugs.launchpad.net/mailman/+bug/266332 . After digging around for a while I found that Ed had posted a message that was getting 'stuck' in the digest queue. I've updated the digest mbox and my second test message came through. I'll see what I can do about getting the shunted messages back. As for MDDI-dev according to our project DB they're inactive, and I can't find an active list called 'mddi*' -M.
