Return-Path: Received: from nm37-vm4.bullet.mail.bf1.yahoo.com ([72.30.238.204] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5469800 for AE-List@media-motion.tv; Sun, 11 May 2014 03:49:31 +0200 Received: from [98.139.212.152] by nm37.bullet.mail.bf1.yahoo.com with NNFMP; 11 May 2014 01:49:29 -0000 Received: from [98.139.212.211] by tm9.bullet.mail.bf1.yahoo.com with NNFMP; 11 May 2014 01:49:29 -0000 Received: from [127.0.0.1] by omp1020.mail.bf1.yahoo.com with NNFMP; 11 May 2014 01:49:29 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 138665.29253.bm@omp1020.mail.bf1.yahoo.com Received: (qmail 26536 invoked by uid 60001); 11 May 2014 01:49:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1399772968; bh=CYQr1xBtQ1Yx8GcPBpJXSQom7+/kUjllr7oBMLr/QM4=; h=References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=tVoRdUEMZrYw7rZ5+/zrMxklb2zLaWKCNl+X70aWw0MgsqAn3T1N0UBBaNWousX5fKD8AowO3yXRoSah23X1xUOWtcS/ssK6BPb48dJ0NertSpXxzb5NqfbV6URcnG3+PW23MhTRFQ5imVVdPGWuhYoBNKMrGlk53SB5ocE4qPU= X-YMail-OSG: hg_XFNoVM1nPgz.YWcjLXCIuBMWFjR2GZGl.dQfoX5M2WvO cVtpzAFk7zYAiXs9RgNWMUYuCafQe.ddv1DrUsCJK5alJ3201JeMGw1iVoPj 3P0iURdL1nOq0Mx540O_f9rb7CP2vLVont6NgM6Q3gPnn3Bh85lxQRi3b01k UzJRjTQYC8tJGrZqpEz27mUylVSqbY2eZxY4sbuW_6uoElMgp_ZibCbX4Ucj qRQJnZrXwcTLaSiVgiSGgIgdcM4KO.yWhDWohud1X9in26Q6x2uMD1q99zVE kVCDNWViQUuxv5VpR_OmCkBf9OTZ05FxnHHK5i_WFQAiDpgMNbyTw3CCfbk0 Whke_pT.RUPQbQYekJPc26gWxTJstHYLQpKLw2OhnABmmYMI9mYWU.7bF1S. zqpQnigT4PjdEJJbZAFmO.HjR4YF.XVhzGB8KYBqLot0QCKbwwbthS_ZT.50 RyJ5wQNn5woR88JPf2CBC8Zod77eQ8o4Y0cAG03frnAUt8HZ8YhinixFM0pM nm8cnzsQAHTvSaPGQrbzVFglMdS4A8rvuUCxm8NnjryqNbXtQo9iss_cdut7 wxj_LvEDuNLIhn7i7oW4Lu_bxDKkwARVQ8LDxyDxCImTToAivXI84BoiFdEt s21yLpvauMyluMryaKOFltDuhGpE5zITIiqyGZOpW4D62pd31so72M4UlRAH Wri29rJsTx5YTRea4KzkpNBh65JXk_tkrWzSNG79HnHdjlG0W9ZvT6wR4l8j UNBRQvyPRACYj2VruQJ4pVpmDgzPvqZuWeGdQx5lNKNnWzWDPKph5fMtDYbB P22Ajc0xO_a2vbyiiV9TZrh10cpxY4ReiJ.AG0KV6enhgtva._Y.IAfPjNSc XYEG70vz5OJjdjmU145nKNWIb1z7z83OKnEjZz.aabkifRxkJZxYSdV55zmI M9N5UjOas0vef5CiUWT.Sz9vGz117Dt64GWQQOV0IopTzjrgNtoaeM5VWIAL 7tUMXnElvN9KUPqexcrUOnfjvL7mlPUORlQsog2wW8DoYomJMcJD4ytuC1Ep Gc1Sf7MuxmHnJkz77maASLKUvXljk07R5sIt.rkaRtCWuK_P1I9H0hKVgEzG 8YfL9iOIGDU1efkZaq.s3gF6dpqP9c.UEKS9AMNEa.jDk_r99zhR_7w92cg5 kYh6lH4TsBTec95bfhK9MoUAm23X0hzTG83Y9mdI3M1CSYlMrKpkBYnWYBL4 qsZFY8MmlxWTRtv_YBacL8Q2Sbcc2G_J7WthDSZUy.YEmVG_0Py9lDIP5vwK _JAxsJ91fhb5GX85djB6Pa6KF5Hl27qywRWPTrV.zGEHeNrI7rzkbvW_TKMr batX90R9POChvETkWsgnQtM_KE1r73iKyN5B_tM7Bg6cs Received: from [67.100.110.145] by web141201.mail.bf1.yahoo.com via HTTP; Sat, 10 May 2014 18:49:28 PDT X-Rocket-MIMEInfo: 002.001,VGhpcyBoYXMgYmVlbiBib3RoIGludGVyZXN0aW5nIGFuZCBlZHVjYXRpb25hbC4gSSB0b28gaGF2ZSBiZWVuIGdldHRpbmcgbW9yZSB0aGFuIHRoZSB1c3VhbCBudW1iZXIgb2YgYm91bmNlIHdhcm5pbmdzIGxhdGVseS4gSXQncyB3b3J0aCBub3RpbmcgdGhhdCBldmVuIHRob3VnaCBJIGFtIGFsc28gb24gdGhlIENvbXByZXNzaW9uIGxpc3QgYW5kIHRoZSBJTVVHIGxpc3QsIEkgb25seSBnZXQgdGhlIHdhcm5pbmdzIGZyb20gdGhlIEFFIGxpc3QuIElmIHRoZXkgYWxsIHJlc2lkZSBpbiB0aGUgc2FtZSBJUCABMAEBAQE- X-Mailer: YahooMailWebService/0.8.188.663 References: Message-ID: <1399772968.31598.YahooMailNeo@web141201.mail.bf1.yahoo.com> Date: Sat, 10 May 2014 18:49:28 -0700 (PDT) From: Ian Barbour Reply-To: Ian Barbour Subject: Re: [AE] AE list bounce WARNING messages - a quick explanation To: After Effects Mail List In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1105474026-1845630650-1399772968=:31598" --1105474026-1845630650-1399772968=:31598 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable This has been both interesting and educational. I too have been getting mor= e than the usual number of bounce warnings lately. It's worth noting that e= ven though I am also on the Compression list and the IMUG list, I only get = the warnings from the AE list. If they all reside in the same IP block, sho= uldn't I get an equal number of warnings from each list?=0A=0A- Ian Barbour= =0A=0A=0A=0A=0A>________________________________=0A> From: Ren=C3=A9 Hedemy= r =0A>To: After Effects Mail List =0A>Sent: Friday, May 9, 2014 4:44 AM=0A>Subject: Re: [AE] AE list bounce= WARNING messages - a quick explanation=0A> =0A>=0A>=0A>Big thank you to Ch= ris and David for explaining this.=0A>=0A>=0A>The Media-motion.tv list serv= er is an email server of it=E2=80=99s own with it=E2=80=99s own IP address= =C2=A062.181.193.71,=C2=A0that I was given by my ISP.=C2=A0=0A>If another c= ustomer at my ISP have another mail server that is sending out spam, our se= rver could be blocked because it=E2=80=99s in the same IP address range, e.= i.=C2=A062.181.xxx.xxx and therefore Gmail block=C2=A0everything that start= s with=C2=A062.181.xxx.xxx=0A>=0A>=0A>The information about DMARC is new to= me, and I=E2=80=99m now googling (is that a verb?) it for information abou= t how to change the DNS=C2=A0zone file=C2=A0which is at GoDaddy=0A>=0A>=0A>= Hopefully this will solve the amount of bounce messages we get from the med= ia-motion server. I got my mail at Gmail so I also get them, sometimes seve= ral times a day.=C2=A0=0A>It=E2=80=99s VERY important that you reply to the= se bounce messages as it is written in them, so the server will continue to= send you messages from the list.=0A>=0A>=0A>I=E2=80=99m really sorry for t= hese bounce messages, but this is how the media-motion list server correctl= y reacts when trying to send you an email and Gmail among others are not ac= cepting the mail.=0A>=0A>=0A>I=E2=80=99ll spend more time during this weeke= nd to this matter.=0A>=0A>=0A>=0A>=0A>Med v=C3=A4nlig h=C3=A4lsning / Kind = Regards=C2=A0=0A>=0A>=C2=A0=0A>=0A>=0A> Ren=C3=A9 Hedemyr=C2=A0=0A>=0A>Pos= t Producer / Key Account Manager=C2=A0=0A>=0A>Chief 20=C2=A0=0A>=0A>TWENTYP= OST AB=C2=A0=0A>=0A>R=C3=A5dmansgatan 20 | SE-114 25 Stockholm | Phone: +46= -8-506 350 76=C2=A0=0A>rene@20post.com=C2=A0|=C2=A0www.20post.com=0A>=0A>= =C2=A0=C2=A0=C2=A0 =0A>CONFIDENTIALITY NOTICE:=C2=A0This e-mail message is = intended only for the above-mentioned recipient(s).=0A>=0A>Its content is c= onfidential. If you have received this e-mail by error, please notify us im= mediately=0A>and delete it without making a copy, nor disclosing its conten= t,=0A>nor taking any action based thereon. Thank you.=0A>Please consider th= e environment before printing this e-mail.=0A>=0A>=0A>=0A>=0A>2014-05-08 19= :39 GMT+02:00 David Baud :=0A>=0A>Thank you Chris for= sharing this information.=0A>>=0A>>I am still having issues with my gmail = account. After doing some research, and to add to Chris information, it loo= ks like the implementation of the=C2=A0new version (starting in April) of= =C2=A0Domain-based Message Authentication, Reporting & Conformance=C2=A0(DM= ARC) might be responsible to some of the problems we are=C2=A0experiencing.= =C2=A0I am wondering if the servers hosting our email lists have to comply= in some way with the new DMARC specifications? =C2=A0(Ren=C3=A9 do you kno= w anything about it?) Could it be that the roll out across the servers has = not been completed yet? It looks like that most of the big players have imp= lemented DMARC (Google, Yahoo, Microsoft, AOL,=E2=80=A6)=0A>>=0A>>=0A>>DMAR= C - What is it?=0A>>source:=C2=A0DMARC.org=0A>>=0A>>=0A>>DMARC, which stand= s for "Domain-based Message Authentication,=C2=A0Reporting & Conformance", = is a technical specification created by a=C2=A0group of organizations that = want to help reduce the potential for=C2=A0email-based abuse by solving a c= ouple of long-standing operational,=C2=A0deployment, and reporting issues r= elated=C2=A0to email authentication=C2=A0protocols.=0A>>=0A>>DMARC standard= izes how email receivers perform email authentication=C2=A0using the well-k= nown SPF and DKIM mechanisms. This means that senders=C2=A0will experience = consistent authentication results for their messages at=C2=A0AOL, Gmail, Ho= tmail, Yahoo! and any other email receiver implementing=C2=A0DMARC. We hope= this=C2=A0will encourage senders to more broadly authenticate=C2=A0their o= utbound email which can make email a more reliable way to=C2=A0communicate.= =0A>>=0A>>Why is DMARC Important?=0A>>With the rise of the social internet = and the ubiquity of e-commerce, =0Aspammers and phishers have a tremendous = financial incentive to =0Acompromise user accounts, enabling theft of passw= ords, bank accounts, =0Acredit cards, and more. Email is easy to spoof and = criminals have found =0Aspoofing to be a proven way to exploit user trust o= f well-known brands. =0ASimply inserting the logo of a well known brand int= o an email gives it =0Ainstant legitimacy with many users.=0A>>Users can't = tell a real message from a fake one, and large mailbox =0Aproviders have to= make very difficult (and frequently incorrect) choices about which message= s to deliver and which ones might harm users. =0ASenders remain largely una= ware of problems with their authentication =0Apractices because there's no = scalable way for them to indicate they want feedback and where it should be= sent. Those attempting new SPF and DKIM deployment proceed very slowly and= cautiously because the lack of =0Afeedback also means they have no good wa= y to monitor progress and debug =0Aproblems.=0A>>DMARC addresses these issu= es, helping email senders and receivers =0Awork together to better secure e= mails, protecting users and brands from =0Apainfully costly abuse. =0A>>How= Does DMARC Work?=0A>>A DMARC policy allows a sender to indicate that their= emails are =0Aprotected by SPF and/or DKIM, and tells a receiver what to d= o if neither of those authentication methods passes - such as junk or rejec= t the =0Amessage. DMARC removes guesswork from the receiver's handling of t= hese =0Afailed messages, limiting or eliminating the user's exposure to =0A= potentially fraudulent & harmful messages. DMARC also provides a way for th= e email receiver to report back to the sender about messages that pass and/= or fail DMARC evaluation.=0A>>David Baud=0A>>K O S M O S =C2=A0 =C2=A0 P R = O D U C T i O N Sdavid@kosmos-productions.com=0A>>www.kosmos-productions.co= m=0A>>=0A>>=0A>>On May 8, 2014, at 6:11 , Chris Zwar = wrote:=0A>>=0A>>=0A>>>So what is probably happening with the AE list is tha= t somewhere, a mail server is experiencing an unusually large amount of SPA= M traffic, and so it has been blocked by other ISPs at a very basic level. = =C2=A0This is not the same as being added to a SPAM blacklist, or having AE= list emails being confused as SPAM.=C2=A0=C2=A0That's not happening. =C2= =A0It just means that some services (such as Gmail) are refusing ALL emails= that come from the same mail server - whether it's a legitimate AE list em= ail or one selling discount meds and so on=E2=80=A6=0A>>>=0A>>=0A>>=0A>>=0A= >>=0A>>=0A>>=0A>>=0A>=0A>=0A> --1105474026-1845630650-1399772968=:31598 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
This has been both interesting and educational. I = too have been getting more than the usual number of bounce warnings lately.= It's worth noting that even though I am also on the Compression list and t= he IMUG list, I only get the warnings from the AE list. If they all reside = in the same IP block, shouldn't I get an equal number of warnings from each= list?

- Ian Barbour


From:<= /b> Ren=C3=A9 Hedemyr <rene@20post.com>
To: After Effects Mail List <AE-List@media-motio= n.tv>
Sent: Friday= , May 9, 2014 4:44 AM
Subject: Re: [AE] AE list bounce WARNING messages - a quick explanation
=

Big thank you to Chris and Dav= id for explaining this.

=0A=0A
The Medi= a-motion.tv list server is an email server of it=E2=80=99s own with it=E2= =80=99s own IP address 62.181.193.71, that I was given by my ISP.=  
=0A=0A
If another cu= stomer at my ISP have another mail server that is sending out spam, our ser= ver could be blocked because it=E2=80=99s in the same IP address range, e.i= . 62.181.xxx.xxx and therefore Gmail block everything that starts= with 62.181.xxx.xxx
=0A=0A

The information about DMARC is new to me, and I=E2=80=99= m now googling (is that a verb?) it for information about how to change the= DNS zone file which is at GoDaddy=
=0A=0A

Hopefully this wil= l solve the amount of bounce messages we get from the media-motion server. = I got my mail at Gmail so I also get them, sometimes several times a day.&n= bsp;
=0A=0A
It=E2=80=99s VE= RY important that you reply to these bounce messages as it is written in th= em, so the server will continue to send you messages from the list.<= /div>=0A=0A

<= /div>
I=E2=80=99m really sorry for thes= e bounce messages, but this is how the media-motion list server correctly r= eacts when trying to send you an email and Gmail among others are not accep= ting the mail.
=0A=0A

I=E2=80=99ll spend more time during this weekend to this matte= r.

=0A=0A
=0A=0A=0A=0A= =0A=0A=0A=0A
Med v=C3=A4nlig h=C3=A4lsning / Kind Regards 

=  
=0A=0A
=0A=0A
Ren=C3=A9 Hedemyr 
=0A=0A
Post P= roducer / Key Account Manager 
=0A= =0AChief 20 
TWENTYPOST AB&nbs= p;
=0A=0A
R=C3=A5dma= nsgatan 20 | SE-114 25 Stockholm | Phone: +46-8-506 350 76 
rene@20post.com&= nbsp;| www.20post.com
=0A=0A
   
=0A=0A
=0A=0ACONFIDENTIALITY= NOTICE: This e-mail message is intended only for the above-men= tioned recipient(s).
=0A=0AIts = content is confidential. If you have received this e-mail by error, please = notify us immediately
and delete it without making a copy= , nor disclosing its content,
nor taking any action based= thereon. Thank you.
=0A=0APlease consider the environment bef= ore printing this e-mail.
=0A=0A
=0A

2014-05-08 19:39 GMT+02:00 David= Baud <david.baud@gmail.com>:
=0A=0A
T= hank you Chris for sharing this information.

I am still having issues with my gmail account. After doing some res= earch, and to add to Chris information, it looks like the implementation of= the new version (starting in April) of Domain-based Message A= uthentication, Reporting & Conformance (DMARC) might be= responsible to some of the problems we are experiencing.  I am w= ondering if the servers hosting our email lists have to comply in some way = with the new DMARC specifications?  (Ren=C3=A9 do you know anything ab= out it?) Could it be that the roll out across the servers has not been comp= leted yet? It looks like that most of the big players have implemented DMAR= C (Google, Yahoo, Microsoft, AOL,=E2=80=A6)
=0A=0A

DMARC - What is it?
source: DMARC.org
=0A=0A
DMARC, which stands f= or "Domain-based Message Authentication, Reporting & Conformance",= is a technical specification created by a group of organizations that= want to help reduce the potential for email-based abuse by solving a = couple of long-standing operational, deployment, and reporting issues = related to email authentication protocols.
=0A= =0A
DMARC standardizes how email receivers perform email = authentication using the well-known SPF and DKIM mechanisms. This mean= s that senders will experience consistent authentication results for t= heir messages at AOL, Gmail, Hotmail, Yahoo! and any other email recei= ver implementing DMARC. We hope this will encourage senders to mo= re broadly authenticate their outbound email which can make email a mo= re reliable way to communicate.
=0A=0A

Why is DMARC Important?

With the ri= se of the social internet and the ubiquity of e-commerce, =0Aspammers and p= hishers have a tremendous financial incentive to =0Acompromise user account= s, enabling theft of passwords, bank accounts, =0Acredit cards, and more. E= mail is easy to spoof and criminals have found =0Aspoofing to be a proven w= ay to exploit user trust of well-known brands. =0ASimply inserting the logo= of a well known brand into an email gives it =0Ainstant legitimacy with ma= ny users.
Users can't tell a real message from a fake one, and large mailbox =0Apr= oviders have to make very difficult (and frequently incorrect) choices=0A a= bout which messages to deliver and which ones might harm users. =0ASenders = remain largely unaware of problems with their authentication =0Apractices b= ecause there's no scalable way for them to indicate they want=0A feedback a= nd where it should be sent. Those attempting new SPF and DKIM=0A deployment= proceed very slowly and cautiously because the lack of =0Afeedback also me= ans they have no good way to monitor progress and debug =0Aproblems.=
DMARC address= es these issues, helping email senders and receivers =0Awork together to be= tter secure emails, protecting users and brands from =0Apainfully costly ab= use.
=0A=0A<= a href=3D"" rel=3D"nofollow" shape=3D"rect" name=3D"145dceb8493d48c7_howdoe= sDMARCwork">=0A

How Does DMARC Work?

A DMARC policy allows a sender to indicate that their em= ails are =0Aprotected by SPF and/or DKIM, and tells a receiver what to do i= f neither=0A of those authentication methods passes - such as junk or rejec= t the =0Amessage. DMARC removes guesswork from the receiver's handling of t= hese =0Afailed messages, limiting or eliminating the user's exposure to =0A= potentially fraudulent & harmful messages. DMARC also provides a way=0A= for the email receiver to report back to the sender about messages that=0A= pass and/or fail DMARC evaluation.
=0A=0A=
=0A=0ADavid Baud
K O S M O S   &= nbsp; P R O D U C T i O N S
david@kosmos-pro= ductions.com=0A=0A

On May 8, 2014, at 6:11 , Chris Zwar <chris@chriszwar.com> wrote:
= =0A=0A

So what is probably happ= ening with the AE list is that somewhere, a mail server is experiencing an = unusually large amount of SPAM traffic, and so it has been blocked by other= ISPs at a very basic level.  This is not the same as being added to a= SPAM blacklist, or having AE list emails being confused as SPAM. &nbs= p;That's not happening.  It just means that some services (such as Gma= il) are refusing ALL emails that come from the same mail server - whether i= t's a legitimate AE list email or one selling discount meds and so on=E2=80= =A6
=0A=0A


=0A=
=0A=0A
=0A=0A
=0A=0A
=0A= =0A
=0A=0A
=0A=0A<= br clear=3D"none">

=0A
=0A



=
--1105474026-1845630650-1399772968=:31598--