Dear Co- chairs, I fully support Roelof ’s request, with the addition that all SOIs should be reviewed and attendance monitored. Can I make a further suggestion, as we move full steam ahead to Marrakesh. Would it possible to create separate accountability-cross-community@icann.org /// emails to the list based on separate threads/ topics. Would the ICANN Female Quartet ( Alice,Hilary, Grace and Brenda) be able to coordinate. As Roelof says we all have day jobs ( that pays for ICANN volunteering). I personally simply do not have the time to read emails to which I have no expertise, no professional knowledge. Regards,
Phil Phil Buckingham CEO, Dot Advice Limited From: accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org] On Behalf Of Roelof Meijer
Sent: 25 October 2015 16:51
To: Mathieu Weill; Thomas Rickert; León Felipe Sánchez Ambía
Cc: accountability-cross-community@icann.org
Subject: [CCWG-ACCT] FW: Fw: [At-Large] (no subject) I herewith formally request you to consider
revoking mr. Ron Baione's (example email below) access to and entry on the CCWG email list(s). As arguments supporting this request I submit that: - The nearly 80 emails mr. Baione sent to this list only this month, lack both subject (as of late) and content in almost all cases. Theypre cost other subscribers to the list precious time and bring us (and the community) nothing;
- Mr. Baione’s Statement of Interest states very little in
general and and is quite unclear about his interests in particular.
@ my fellow CCWG members and participants: please feel free to support or object to this request. Best regards, Roelof A. Meijer CEO SIDN | Meander 501 | 6825 MD | P.O. Box 5022 | 6802 EA | ARNHEM | THE NETHERLANDS
T +31 (0)26 352 55 00 | M +31 (0)6 11 395 775 | F +31 (0)26 352 55 05
roelof.meijer@sidn.nl | www.sidn.nl Is anyone aware of when the next Winston Churchill trivia session will be? Is that a weekly thing? Monthly? Just trying to blend in to the hard work process that is strictly adhered to, it seems.
Ron |
I suggest we ALL try to limit personal back-and-forth email on this global list. We have enough real work to do without distractions. Not quite sure what you are trying to say, but I would be glad to ask the list to comment on the relative value of your contributions to my emails, meeting contributions, Working Party contributions and drafting contributions over the last 10+ months. As you say, it's all relative.
On Saturday, October 24, 2015, Ron Baione <ron.baione@yahoo.com> wrote:
The email sought was not found in the archives. The point I was making is that there was no email alerting the community to a known IT problem, nor will there be. The quality of anyone's contributions is relative to the
person reading them, as this is an open and inclusive process, and lastly, the quality of your contributions have helped lead ICANN to the success it is today.
Best,
Ron |
This is a publicly archived email list. You have the same access to the prior emails as every other participant. I suggest you start reading from the beginning of the list and work your way forward until you have caught up with the group. You should find the email you seek in the process. This will likely have the effect of improving the quality of your contributions as well.
On Friday, October 23, 2015, Ron Baione
<ron.baione@yahoo.com> wrote: The bounceback/spam IT Issue the email lists have been having was a known issue to the office of the ICANN IT director since Yahoo changed its spam filter to DMARC. The information in this email chain (below) was not provided to me when I signed up as a participant to ccwg-accountability. The patch to fix the issue was available in August (read conversation below). If anyone can provide me an email from August 2015 or before, from the IT director or IT Staff, which instructs the members, participants and observers of this or any mailing
list that a patch or fix to the mailing list bounceback/spam issue would be tested and implemented, kindly forward that email to me.
Ron |
Yes, we first started experiencing the problem back when http://yahoo.com changed their DMARC policy to a strict reject. We didn’t have many http://yahoo.com senders on our lists surprisingly so the problem wasn’t a huge deal. We were waiting on a vendor back port patch (CentOS via Redhat) to help with header munging for senders with strict reject DMARC policies. The back port patch was ready back in August but we didn’t have time
to fully test. We have completed testing as of this morning and plan schedule the change for this weekend. The change will be almost transparent with exception to senders from domains with strict reject DMARC policies. In this case, the “from:” will be replaced with the list address and we will insert a “reply-to:” header with the senders address. Our testing indicates this is working flawlessly with the vendor patch. Director of IT Operations, ICANN 12025 Waterfront Dr. Suite 300 Thanks David, any way you can provide when the DMARC email issue was initially brought to
your attention? For example, has the referenced upgrade been in the works for a few months or is this something that occurred just within the last few weeks/days?
Ron |
We are testing the version upgrade now in our test environment but need about a week before the actual production upgrade. Director of IT Operations, ICANN 12025 Waterfront Dr. Suite 300 David,
If possible, provide the date or time-frame that the ICANN system upgrade for DMARC related emails was planned for or ordered by your office.
Ron |
Thanks John.
We can discuss off-list if you would like.
Yes, I was attempting to avoid an email discussion regarding DMARC but we already have a upgrade planned to our mailman system since some DMARC support is a necessity moving forward.
--
David Closson
Director of IT Operations, ICANN
12025 Waterfront Dr. Suite 300
Los Angeles, CA 90094
Office: +1-310-578-8670
Cell: +1-213-270-3866
--
-----Original Message-----
From: "John R. Levine" <johnl@iecc.com>
Date: Thursday, October 22, 2015 at 10:54 AM
To: "david.closson" <david.closson@icann.org>
Cc: Olivier MJ Crepin-Leblond <ocl@gih.com>, "at-large@atlarge-lists.icann.org" <at-large@atlarge-lists.icann.org>
Subject: Re: [At-Large] (no subject)
>> We are working to provide a solution to this problem as quickly as possible.
>> We will update Valentina Pavel (ICANN IT support case holder) who can in turn advise the Atlarge stakeholders.
>
>It's actually called DMARC, and I can report there is some work in
>progress to fix it at the group that caused the DMARC problems in the
>first
place.
>
>R's,
>John
_______________________________________________
At-Large mailing list
At-Large@atlarge-lists.icann.org
https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.icann.org |
|
|
|
|
|