~sircmpwn/sr.ht-discuss

2 2

Question about Tutanota

Details
Message ID
<NNSgwhO--3-9@tutanota.com>
DKIM signature
missing
Download raw message
Hi everyone,
I am wondering if anyone has anyone succeded in using git send email and a Tutanota email?  I have asked the Tutanota team if they can provide SMTP credentials so I can use git-send-email but they said they cant give them to me. I have to have to unfortunately use gmail to contribute to sr.ht <http://sr.ht/> projects. 
Thanks to anyone who replies,
Jakob
(I am new to mailing lists so please tell me if something I did does not respect ettiquette)
Adolfo Santiago <epoch@nixnetmail.com>
Details
Message ID
<20230204193348.kykaogjya5o3bi7l@MacBook-Pro-de-Adolfo.local>
In-Reply-To
<NNSgwhO--3-9@tutanota.com> (view parent)
DKIM signature
missing
Download raw message
As far as I know, Tutanota doesn't provide that information to anyone. I
think it's part of its protocol.
Details
Message ID
<87k00xeyvg.fsf@isnotmyreal.name>
In-Reply-To
<NNSgwhO--3-9@tutanota.com> (view parent)
DKIM signature
missing
Download raw message
Jakob Neufeld <jakobneufeld@tutanota.com> writes:

> Tutanota

Stuff like this is why I stopped using Tutanota as well.  Their
non-standard way of doing things precludes the use of many power user
email tools.

That plus the fact that I realized, for private chatting, I would be
better off using (self hosted) XMPP + OMEMO.  In my case anyway, the
vast majority of my email just does not contain anything really
confidential.  Mostly email from businesses I have relationships with
(your package shipped, etc.) and mailing list correspondence which is
public anyway.  YMMV of course, but perhaps think hard about risk
surfaces, what you are trying to protect and why, and you may come to
conclusion as I did (or you may not).

Fundamentally, email comes from a simpler time when the network was just
a handful of academic sites, a very high trust environment.  It was
never really designed to deal with the sort of challenges that came
later, which is why any sort of email encryption scheme is either
awkward to use, bolted on, causes some problems with functionality, etc.
There will be some trade-off or another, depending on the solution you
choose.

Just some food for thought.

-- 
Cheers,
TRS-80
Reply to thread Export thread (mbox)