[CCWG-ACCT] Fw: [At-Large] (no subject)

[Greg Shatan]

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 at 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
>
> ------------------------------
> * From: * David Closson <david.closson at icann.org>;
> * To: * Ron Baione <ron.baione at yahoo.com>;
> * Cc: * Dev Anand Teelucksingh <devtee at gmail.com>;
> * Subject: * Re: [At-Large] (no subject)
> * Sent: * Fri, Oct 23, 2015 7:01:08 PM
>
> Yes, we first started experiencing the problem back when yahoo.com
> changed their DMARC policy to a strict reject.
> We didn’t have many 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.
>
>
> --
> David Closson
> Director of IT Operations, ICANN
> 12025 Waterfront Dr. Suite 300
> Los Angeles, CA 90094
> Office: +1-310-578-8670
> 
> --
>
>
> From: Ron Baione <ron.baione at yahoo.com>
> Date: Thursday, October 22, 2015 at 7:15 PM
> To: "david.closson" <david.closson at icann.org>
> Subject: Re: [At-Large] (no subject)
>
> 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
>
> ------------------------------
> *From: *David Closson <david.closson at icann.org>;
> *To: *Ron Baione <ron.baione at yahoo.com>;
> *Subject: *Re: [At-Large] (no subject)
> *Sent: *Fri, Oct 23, 2015 12:38:48 AM
>
> Greetings Ron,
>
> We are testing the version upgrade now in our test environment but need
> about a week before the actual production upgrade.
>
> -
> David Closson
> Director of IT Operations, ICANN
> 12025 Waterfront Dr. Suite 300
> Los Angeles, CA 90094
> Office: +1-310-578-8670
> 
> --
>
>
> From: Ron Baione <ron.baione at yahoo.com>
> Date: Thursday, October 22, 2015 at 12:51 PM
> To: "david.closson" <david.closson at icann.org>
> Subject: Re: [At-Large] (no subject)
>
> 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
>
> ------------------------------
> *From: *David Closson <david.closson at icann.org>;
> *To: *John R. Levine <johnl at iecc.com>;
> *Cc: *at-large at atlarge-lists.icann.org <at-large at atlarge-lists.icann.org>;
>
> *Subject: *Re: [At-Large] (no subject)
> *Sent: *Thu, Oct 22, 2015 6:26:30 PM
>
> 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
> 
> --
>
>
>
>
>
>
>
>
> -----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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20151024/df110156/attachment.html>