Yep, sources confirmed to me that the feed was repaired on March 15th. Cheers, Al
On Sat, Mar 16, 2019 at 6:00 AM Bressier Simon <bressie...@gmail.com> wrote: > Confirmed also on my side, it starts back on 15th for both Laposte & > OpenSRS > > Le sam. 16 mars 2019 à 10:21, Benjamin BILLON <bbil...@splio.com> a > écrit : > >> After thourough checking, we still received a (very) few complaints on >> March 12th to 14th (so non-null), and it's increasing since 15th. It >> might be back to the usual count today. >> >> >> >> -- >> *Benjamin* >> >> >> >> *From:* Benjamin BILLON >> *Sent:* vendredi 15 mars 2019 11:08 >> *To:* 'mailop' <mailop@mailop.org> >> *Subject:* RE: [mailop] Issue receiving fbl reports from laposte.net >> >> >> >> They're checking with ReturnPath. >> >> >> >> -- >> *Benjamin* >> >> >> >> *From:* Benjamin BILLON >> *Sent:* vendredi 15 mars 2019 09:02 >> *To:* 'Al Iverson' <aiver...@wombatmail.com>; mailop <mailop@mailop.org> >> *Subject:* RE: [mailop] Issue receiving fbl reports from laposte.net >> >> >> >> Same here for the FBL, although the Signal-Spam counters still indicates >> non-null values. >> >> >> >> I'll ask them >> >> >> >> -- >> *Benjamin* >> >> >> >> *From:* mailop <mailop-boun...@mailop.org> *On Behalf Of *Al Iverson >> *Sent:* jeudi 14 mars 2019 20:18 >> *To:* mailop <mailop@mailop.org> >> *Subject:* Re: [mailop] Issue receiving fbl reports from laposte.net >> >> >> >> Yep, we're seeing that here as well. Both for LaPoste and for >> OpenSRS/Tucows. >> >> >> >> Cheers, >> >> Al Iverson >> >> Salesforce Marketing Cloud >> >> >> >> >> >> On Thu, Mar 14, 2019 at 2:56 PM Mathew Hodges via mailop < >> mailop@mailop.org> wrote: >> >> Hello, >> >> >> >> I'm a deliverability engineer with Mailchimp. We noticed that on March 11 >> we stopped receiving fbl reports from laposte.net. Our last message came >> in at Mon, 11 Mar 2019 13:04:20 +0000. We aren't noticing any lack of data >> from other domains, including those serviced by Return Path. >> >> I reached out to Return Path customer service and they mentioned >> everything was enabled and active on their end to send fbl reports. I have >> also been able to confirm that our inbox that receives these fbl reports >> isn't full and is receiving messages successfully. Our fbl is still >> registered and active for our full IP range. >> >> For reference, our sending IP ranges are as follows: >> >> 205.201.128.0/20 >> >> 198.2.128.0/18 >> >> 148.105.0.0/16 >> >> Our sending domains are: >> >> mandrillapp.com >> >> rsgsv.net >> >> mcsv.net >> >> mcdlv.net >> >> mctxapp.net >> >> mailchimpapp.net >> >> I wanted to check if anyone else was seeing the same issue? If so, was >> anyone able to find a resolution? >> >> >> >> -- >> >> Mathew Hodges >> >> Deliverability Engineer >> >> mathew.hod...@mailchimp.com >> >> >> >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >> >> >> >> >> -- >> >> al iverson // wombatmail // miami >> http://www.aliverson.com >> http://www.spamresource.com >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >> > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > -- al iverson // wombatmail // miami http://www.aliverson.com http://www.spamresource.com
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
