Return-Path: Received: from qmta15.emeryville.ca.mail.comcast.net ([76.96.27.228] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5467910 for ae-list@media-motion.tv; Thu, 08 May 2014 19:39:45 +0200 Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta15.emeryville.ca.mail.comcast.net with comcast id zTyw1n0031wfjNsAFVfRK2; Thu, 08 May 2014 17:39:25 +0000 Received: from [IPv6:2601:1:8200:284:8caf:58f4:b59d:9b75] ([IPv6:2601:1:8200:284:8caf:58f4:b59d:9b75]) by omta23.emeryville.ca.mail.comcast.net with comcast id zVfi1n0062z8kK28jVfjpo; Thu, 08 May 2014 17:39:43 +0000 From: David Baud Content-Type: multipart/alternative; boundary="Apple-Mail=_5CA0FDC1-6487-4BE9-BBFF-D48F3FD57E4B" Message-Id: <87E07B9F-E062-460B-84DB-3BDFE9432E64@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: [AE] AE list bounce WARNING messages - a quick explanation Date: Thu, 8 May 2014 11:39:41 -0600 References: To: After Effects Mail List In-Reply-To: X-Mailer: Apple Mail (2.1874) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1399570765; bh=Hav2SNSn9uZdAZVXpt1Q+YSwMahqdz8ruyvFkDmmhrs=; h=Received:Received:From:Content-Type:Message-Id:Mime-Version: Subject:Date:To; b=mOfUTV6juKCwIwneuIDJKSq35jnZJTElnQ5sY9hWIOcjnVeFw3xEQ2lTjRVLazCEW 3dO2Gig1OF2T6kr2TdgI8Xo/NnQT+rtsPYyvU8oAQ7xfKS+KtP+hD9Ezk4Cw2XmIxH 3tOiuDkE/9nyT/wruGm7M9iMgUCqoDdDlSEQ87zFPOmLgkr2GsMwrjjqsOzkqckWMS qTt46C/tb5DeXEziX8xGDTHSbZ8fz/uK2MvQSqt/U3rsI6BjjgOJW2Ot9/islbI51J 2hrVEd0bCo5ZdmaEg9WU8Bku+E0oZ+T95Kft29PVbdFNCsv0Mno1Y466AMuhdwGFgU Y+19hmccwC69Q== --Apple-Mail=_5CA0FDC1-6487-4BE9-BBFF-D48F3FD57E4B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Thank you Chris for sharing this information. I am still having issues with my gmail account. After doing some = research, and to add to Chris information, it looks like the = implementation of the new version (starting in April) of Domain-based = Message Authentication, Reporting & Conformance (DMARC) might be = responsible to some of the problems we are experiencing. I am wondering = if the servers hosting our email lists have to comply in some way with = the new DMARC specifications? (Ren=E9 do you know 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 implemented DMARC = (Google, Yahoo, Microsoft, AOL,=85) DMARC - What is it? source: DMARC.org DMARC, which stands for "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. DMARC standardizes how email receivers perform email authentication = using the well-known SPF and DKIM mechanisms. This means that senders = will experience consistent authentication results for their messages at = AOL, Gmail, Hotmail, Yahoo! and any other email receiver implementing = DMARC. We hope this will encourage senders to more broadly authenticate = their outbound email which can make email a more reliable way to = communicate. Why is DMARC Important? With the rise of the social internet and the ubiquity of e-commerce, = spammers and phishers have a tremendous financial incentive to = compromise user accounts, enabling theft of passwords, bank accounts, = credit cards, and more. Email is easy to spoof and criminals have found = spoofing to be a proven way to exploit user trust of well-known brands. = Simply inserting the logo of a well known brand into an email gives it = instant legitimacy with many users. Users can't tell a real message from a fake one, and large mailbox = providers have to make very difficult (and frequently incorrect) choices = about which messages to deliver and which ones might harm users. Senders = remain largely unaware of problems with their authentication practices = 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 = feedback also means they have no good way to monitor progress and debug = problems. DMARC addresses these issues, helping email senders and receivers work = together to better secure emails, protecting users and brands from = painfully costly abuse. How Does DMARC Work? A DMARC policy allows a sender to indicate that their emails are = protected by SPF and/or DKIM, and tells a receiver what to do if neither = of those authentication methods passes - such as junk or reject the = message. DMARC removes guesswork from the receiver's handling of these = failed messages, limiting or eliminating the user's exposure to = potentially fraudulent & harmful messages. DMARC also provides a way for = the email receiver to report back to the sender about messages that pass = and/or fail DMARC evaluation. David Baud K O S M O S P R O D U C T i O N S david@kosmos-productions.com www.kosmos-productions.com On May 8, 2014, at 6:11 , Chris Zwar wrote: >=20 > So what is probably happening 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. That's not happening. It 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 email or = one selling discount meds and so on=85 --Apple-Mail=_5CA0FDC1-6487-4BE9-BBFF-D48F3FD57E4B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Thank you Chris for sharing this = information.

I am still having issues with my gmail account. = After doing some research, and to add to Chris information, it looks = like the implementation of the new version (starting in April) = of Domain-based Message Authentication, Reporting & = Conformance (DMARC) might be responsible to some of the = problems we are experiencing.  I am wondering if the servers = hosting our email lists have to comply in some way with the new DMARC = specifications?  (Ren=E9 do you know 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 implemented DMARC (Google, = Yahoo, Microsoft, AOL,=85)


DMARC - What is it?
source: DMARC.org

DMARC, which stands for "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.

DMARC = standardizes how email receivers perform email authentication using = the well-known SPF and DKIM mechanisms. This means that = senders will experience consistent authentication results for their = messages at AOL, Gmail, Hotmail, Yahoo! and any other email = receiver implementing DMARC. We hope this will encourage = senders to more broadly authenticate their outbound email which can = make email a more reliable way to communicate.

Why is DMARC = Important?

With the rise of the social internet and the ubiquity of = e-commerce,=20 spammers and phishers have a tremendous financial incentive to=20 compromise user accounts, enabling theft of passwords, bank accounts,=20 credit cards, and more. Email is easy to spoof and criminals have found=20= spoofing to be a proven way to exploit user trust of well-known brands.=20= Simply inserting the logo of a well known brand into an email gives it=20= instant legitimacy with many users.

Users can't tell a real message from a fake = one, and large mailbox=20 providers have to make very difficult (and frequently incorrect) choices about which messages to deliver and which ones might harm users.=20 Senders remain largely unaware of problems with their authentication=20 practices 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=20 feedback also means they have no good way to monitor progress and debug=20= problems.

DMARC addresses these issues, helping email senders and receivers=20= work together to better secure emails, protecting users and brands from=20= painfully costly abuse.

How Does = DMARC Work?

A DMARC policy allows a sender to indicate that their emails are=20= protected by SPF and/or DKIM, and tells a receiver what to do if neither of those authentication methods passes - such as junk or reject the=20 message. DMARC removes guesswork from the receiver's handling of these=20= failed messages, limiting or eliminating the user's exposure to=20 potentially fraudulent & harmful messages. DMARC also provides a way for the email receiver to report back to the sender about messages that pass and/or fail DMARC evaluation.

David = Baud
K O S M O S     P R O D = U C T i O N = S
<= /span>
david@kosmos-productions.com<= /a>

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

So what is probably happening 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.  That's not = happening.  It 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 email or one selling discount meds and so = on=85




= --Apple-Mail=_5CA0FDC1-6487-4BE9-BBFF-D48F3FD57E4B--