Looking for a Microsoft person who can help w/ v6 and Office365 email

[Ted Mittelstaedt]

I guess I don't understand why this is an IPv6 issue.

You said:

"...we've discovered that there are sporadic failures even when there 
are valid SPF records...""

If there are sporadic failures internally in Microsoft how can they
guarantee that those sporadic failures will go away if you change to
IPv4?

They can't.

Bill, you sound like one of my customers who 5 months ago bought a
Dell Windows 8 tablet.  He was a "believer"  He setup that tablet
and he was dammed if he was going to get it to work like the laptop
it replaced.  Every time he had a problem, instead of blaming the
tablet he blamed everything else - the network, the peripherals, the
software - on and on and on.

Finally last week he admitted defeat.  The tablet went home for the
kids to take to school (and probably lose/drop/whatever) and he bought a 
laptop.

You called Microsoft and gave their support team a fair chance to fix
the problem.  They didn't.  Cut your losses and move on.  There are
plenty of other cloud providers who are offering email that works.  By 
the time Microsoft finally fixes O365 you will be retired and so will I.

How long did it take for them to fix all the bugs in the Outlook mail
client?

Ted

On 4/1/2015 5:02 PM, Bill Owens wrote:
> 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.
>
> 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.
>
> We've been pursuing this through Microsoft support but are not making
> progress. The latest response is a recommendation to give up and disable
> IPv6 mail. I would really rather not do that, because the next step will
> be for me to push as hard as I can for our company to abandon Office365
> as a defective product. I don't think there's anything fundamentally
> wrong with requiring SPF for IPv6 mail; I believe this is a bug that
> ought to be fixable, if we can just find someone within Microsoft who is
> willing to look hard at it. Is there anyone from Microsoft on this list
> who is willing to look into this, or any suggestions for someone at
> Microsoft who could help encourage the support folks to take it seriously?
>
> Thanks,
> Bill.
>
> PS - After sending this from my work/Office365 I realized that I hadn't
> seen any ipv6-ops email in a couple of weeks, and I've come to the
> conclusion that it's all being bounced by Microsoft because
> lists.cluenet.de <http://lists.cluenet.de> doesn't have an SPF record. I
> wouldn't be surprised to find out that Mailman has already unsubscribed
> my work address for excessive bounces. So I've re-subscribed from my
> personal Google account in order to have something that actually works...