<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
There is an RFC:<br>
<br>
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc1122">http://tools.ietf.org/html/rfc1122</a><br>
<br>
Section 1.2.2 Robustness Principle<br>
<br>
Ted<br>
<br>
On 4/22/2015 8:40 AM, Frank Bulk wrote:
<blockquote cite="mid:008601d07d12$b6e52be0$24af83a0$@iname.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Glad
to hear that Microsoft did this on their O365 platform.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Is
there an RFC or other standard that we can point other email
providers to about implementing email admission in this
manner?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Frank<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<a class="moz-txt-link-abbreviated" href="mailto:ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de">ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de</a>
[<a class="moz-txt-link-freetext" href="mailto:ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de">mailto:ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de</a>]
<b>On Behalf Of </b>Bill Owens<br>
<b>Sent:</b> Wednesday, April 22, 2015 8:08 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de</a><br>
<b>Subject:</b> Re: Looking for a Microsoft person who can
help w/ v6 and Office365 email<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Apr 1, 2015 at 8:02 PM, Bill
Owens <<a moz-do-not-send="true"
href="mailto:owens.bill@gmail.com">owens.bill@gmail.com</a>>
wrote:<br>
><br>
> We've been running our Office365 mail account for a few
weeks now with IPv6 enabled. We went into this knowing that
Microsoft was going to enforce SPF checks on inbound mail,
and we've run into a number of issues with people sending
mail over v6 transport and having bad SPF records (or none).
So far we've been able to resolve all but one of those
issues, or are in the process of doing so; that's not a big
deal. The one that won't fix their record is going to
require us to resubscribe to a few mail lists, not the end
of the world.<br>
><br>
> However, we've discovered that there are sporadic
failures even when there are valid SPF records, and in some
cases even when the email enters the Microsoft 'world' using
v4 and transitions to v6 between two Microsoft servers - at
which point the SPF check is applied even though the message
was "accepted" several hops prior, and the check sometimes
fails. That's something we can't fix on our own.<br>
><br>
<br>
I don't know whether this is in response to the problems
we've reported, but Microsoft has changed their attitude
towards SPF and<br>
IPv6 just a little. Rather than returning a 5xx error code,
which causes the mail to bounce immediately, they're going
to return 4xx<br>
and allow the sender to attempt redelivery. This ought to
prevent the majority of bounces that we've been seeing,
although it<br>
doesn't fix the underlying issue(s) that cause the false SPF
failures:<br>
<br>
<a moz-do-not-send="true"
href="http://blogs.msdn.com/b/tzink/archive/2015/04/18/office-365-will-slightly-modify-its-treatment-of-anonymous-inbound-email-over-ipv6.aspx">http://blogs.msdn.com/b/tzink/archive/2015/04/18/office-365-will-slightly-modify-its-treatment-of-anonymous-inbound-email-over-ipv6.aspx</a><br>
<br>
Bill.<o:p></o:p></p>
</div>
</div>
</blockquote>
</body>
</html>