Re: [Outllook.com] Mail-service integration in diverse .* management systems

For your reference, records indicate that
Michael Uplawski <michael.uplawski@uplawski.eu> wrote:

It hurts, because the insurance company is actually great.

Well, that’s the thing.  People who know technology have to find a way to
work with people who *actively* do not, but who do other things very well. 
Even if I see an insurance company as needing to have a *core* technology
competence to function in the modern world, maybe they don’t see it that
way (at least not for “solved” technology problems like email).

Do you have an advice? There was one occasion on which I considered
suing the company in question, but hesitated long enough to finally
calm down. This would anyway be a crusade without end…

It really depends on the specifics of their behavior.  Generally, I find
I’ll get more traction if I frame the problem as an
accessibility/accommodations issue.  That is, instead of hitting them with
the exact kind of technical details I know they don’t want to hear, I go
the opposite path and just say I don’t know how to use “that fancy stuff”
and ask what other options there are.

Another reframing is to point out that the problem on their side is bigger
than just me.  I had Microsoft block messages from my email server last
year for literally *no* reason:

<https://impossiblystupid.com/node/1021/?content=microsoft's-smartscreen-embrace-extend-and-extinguish-for-email>

It usually lights a fire under people when they realize their email
provider isn’t actually providing them legitimate business emails, or is
dumping them into a spam folder.

Of course, if they’re outsourcing their internal operations *anyway*,
anything you find a way to “safely” give them is still likely to be escape
their control at some point . . .

--
"Also . . . I can kill you with my brain."
River Tam, Trash, Firefly