[At-Large] (no subject)

[Dev Anand Teelucksingh]

Perhaps the issue can be raised at a future At-Large Technology
Taskforce call. I've added this issue to the
https://community.icann.org/display/atlarge/At-Large+Technology+Issues
page

Dev Anand

On Thu, Oct 22, 2015 at 2:26 PM, David Closson <david.closson at icann.org> wrote:
> 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 at iecc.com>
> Date: Thursday, October 22, 2015 at 10:54 AM
> To: "david.closson" <david.closson at icann.org>
> Cc: Olivier MJ Crepin-Leblond <ocl at gih.com>, "at-large at atlarge-lists.icann.org" <at-large at 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 at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
> At-Large Official Site: http://atlarge.icann.org