Re: Are some es-discuss submissions automatically blocked?
We use Google Postini in concert with Mailman. Postini needs to be told sometimes. If you don't see mail get through, mail es-discuss-ow...@mozilla.org about it. /be While that has helped usually, in this particular case my email to es-discuss-owner (19.10.2011) also disappeared without reply. As did another attempt to reach you directly (22.10.2011). So the system seems to have more serious issues at the moment. How many es-discuss-owners are left, and do they all use the same filters as es-discuss? Do they check their spam folders (perhaps weekly), or is spam deleted automatically/unseen? Claus ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Are some es-discuss submissions automatically blocked?
Le 06/11/2011 15:37, Axel Rauschmayer a écrit : Claus Reinke could not submit his js-tools discussion group announcement (interestingly, I could do it for him). And the email I appended underneath my signature never got through. Can someone explain the blocking criteria? I have experienced similar problems at some point. I don't know what the blocking criteria is. Maybe an anti-spam trying to be smarter than it is? David Thanks! Axel -- Dr. Axel Rauschmayer a...@rauschma.de mailto:a...@rauschma.de home: rauschma.de http://rauschma.de twitter: twitter.com/rauschma http://twitter.com/rauschma blog: 2ality.com http://2ality.com Subject: Fixing one last quirk With Allen's decoupling [ ] and property access for collections [1], all of the JavaScript quirks that I can think of will be fixed in ECMAScript.next (including, hopefully, typeof null). Except for one: solving dynamic `this` is still in limbo (as far as I can tell). It would be really nice if it could be fixed for ES.next, it is surprisingly easy to get it wrong. Any thoughts? For me, lambda blocks would do the trick. Will those be in ES.next? Could functions adopt their semantics of picking up the `this` of the surrounding scope when not invoked as methods? It seems like that could work in strict mode where no one expects `this` to have a value. ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Are some es-discuss submissions automatically blocked?
On 11/7/11 2:48 PM, David Bruant wrote: Le 06/11/2011 15:37, Axel Rauschmayer a écrit : Claus Reinke could not submit his js-tools discussion group announcement (interestingly, I could do it for him). And the email I appended underneath my signature never got through. Can someone explain the blocking criteria? I have experienced similar problems at some point. I don't know what the blocking criteria is. Maybe an anti-spam trying to be smarter than it is? I’ve had this happen, too. -FG ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Are some es-discuss submissions automatically blocked?
Claus Reinke could not submit his js-tools discussion group announcement (interestingly, I could do it for him). And the email I appended underneath my signature never got through. Can someone explain the blocking criteria? I have experienced similar problems at some point. I don't know what the blocking criteria is. Maybe an anti-spam trying to be smarter than it is? That would be my guess, too. -- Dr. Axel Rauschmayer a...@rauschma.de home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Are some es-discuss submissions automatically blocked?
We use Google Postini in concert with Mailman. Postini needs to be told sometimes. If you don't see mail get through, mail es-discuss-ow...@mozilla.org about it. /be On Nov 7, 2011, at 12:48 PM, David Bruant wrote: Le 06/11/2011 15:37, Axel Rauschmayer a écrit : Claus Reinke could not submit his js-tools discussion group announcement (interestingly, I could do it for him). And the email I appended underneath my signature never got through. Can someone explain the blocking criteria? I have experienced similar problems at some point. I don't know what the blocking criteria is. Maybe an anti-spam trying to be smarter than it is? David Thanks! Axel -- Dr. Axel Rauschmayer a...@rauschma.de home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com Subject: Fixing one last quirk With Allen’s “decoupling [ ] and property access for collections” [1], all of the JavaScript quirks that I can think of will be fixed in ECMAScript.next (including, hopefully, typeof null). Except for one: solving dynamic `this` is still in limbo (as far as I can tell). It would be really nice if it could be fixed for ES.next, it is surprisingly easy to get it wrong. Any thoughts? For me, lambda blocks would do the trick. Will those be in ES.next? Could functions adopt their semantics of picking up the `this` of the surrounding scope when not invoked as methods? It seems like that could work in strict mode where no one expects `this` to have a value. ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Are some es-discuss submissions automatically blocked?
Claus Reinke could not submit his js-tools discussion group announcement (interestingly, I could do it for him). And the email I appended underneath my signature never got through. Can someone explain the blocking criteria? Thanks! Axel -- Dr. Axel Rauschmayer a...@rauschma.de home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com Subject: Fixing one last quirk With Allen’s “decoupling [ ] and property access for collections” [1], all of the JavaScript quirks that I can think of will be fixed in ECMAScript.next (including, hopefully, typeof null). Except for one: solving dynamic `this` is still in limbo (as far as I can tell). It would be really nice if it could be fixed for ES.next, it is surprisingly easy to get it wrong. Any thoughts? For me, lambda blocks would do the trick. Will those be in ES.next? Could functions adopt their semantics of picking up the `this` of the surrounding scope when not invoked as methods? It seems like that could work in strict mode where no one expects `this` to have a value. ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss