Dear members of the list,
by chance I found out, that DC does not disconnect from the IMAP server.
My configuration
DeltaChat client (Linux & Android) latest version (1.12.0).
IMAP-Server Dovecot latest version (2.3.11.3).
I have a few processes who should not be there - all linked to Deltachat
activity:
m.stenz+ 8486 7550 0 18:57 ? 00:00:00 dovecot/imap
m.stenz+ 8488 7550 0 18:57 ? 00:00:00 dovecot/imap
m.stenz+ 8490 7550 0 18:57 ? 00:00:00 dovecot/imap
m.stenz+ 9288 7550 0 18:59 ? 00:00:00 dovecot/imap
m.stenz+ 9289 7550 0 18:59 ? 00:00:00 dovecot/imap
m.stenz+ 9290 7550 0 18:59 ? 00:00:00 dovecot/imap
m.stenz+ 11162 7550 0 19:02 ? 00:00:00 dovecot/imap
m.stenz+ 12221 7550 0 19:05 ? 00:00:00 dovecot/imap
m.stenz+ 12229 7550 0 19:05 ? 00:00:00 dovecot/imap
m.stenz+ 12238 7550 0 19:05 ? 00:00:00 dovecot/imap
m.stenz+ 14286 7550 0 19:10 ? 00:00:00 dovecot/imap
If I understand correctly, once a message is sent via the DC client and
processed by the IMAP server there should not be a process running any
longer.
I do not think this is a dovecot problem.
If there are too many processes from one client IP dovecot will stop
process further messages (max. default is 10).
Martin.
--
Find PGP public key here <https://www.xy-space.de/m.stenzel@mail.xy-space.de.asc>
__________ Information from ESET Mail Security, version of virus signature database 22135 (20201011) __________
The message was checked by ESET Mail Security.
http://www.eset.com
the june 2020 opentechfund report ... It's a high-level overview
and i certainly left out some things ...
holger
----- Forwarded message from holger krekel <holger(a)merlinux.eu> -----
Date: Wed, 8 Jul 2020 12:36:48 +0200
From: holger krekel <holger(a)merlinux.eu>
To: otf-active(a)opentechfund.org
Subject: [otf-active] Delta Chat June 2020: new releases, search, app stores, burner-messages ...
hi all,
Delta Chat's has done a full round of releases on Android, iOS and Desktop,
see https://delta.chat/en/2020-06-24-releases for details and screenshots.
Note that the F-droid releases is still not there due to
build problems on their side which we are trying to help resolve.
Delta Chat Desktop is now also available on Microsoft and Apple stores --
this took many rounds of interaction/buereaucracy and fixes. phew!
Speaking of desktop, there finally is SEARCH (Android had it for a while),
a primary feature many users asked for.
WebRTC audio/video support is progressing nicely on Desktop currently.
Ephemeral messaging ("self-destruct" or "dissappearing" messages)
is now integrated in Desktop and Android development versions.
We aim for a public release in July after some more testing ...
We've done remote and now also a small physical UX testing round
in Eastern Europe and continue to collect and address feedback from
various circles, including our lively online one https://support.delta.chat
There is a new much improved version of our server-side "burner account" tool,
see https://github.com/deltachat/mailadm for details.
take care and best wishes for everyone,
holger
hi all,
below the yearly april reporting we just sent to the otf mailing lists,
contains a lot of developments ... actual store releases will still take
a while as last bugs and issues are fixed ...
cheers,
holger
----- Forwarded message from holger krekel <holger(a)merlinux.eu> -----
Date: Fri, 1 May 2020 11:00:58 +0200
From: holger krekel <holger(a)merlinux.eu>
To: otf-active(a)opentechfund.org, otf-talk(a)opentechfund.org
Subject: [otf-active] Delta Chat April 2020: Russian data requests, and lots of features upcoming
This was one of the weirdest Aprils, wasn't it? Felt more like a year worth in
events and happenings ... anyway, here are the highlights of Delta Chat developments:
- Today we officially declined Russia's request from April 27 for turning
over user data of Delta Chat users, see:
https://twitter.com/delta_chat/status/1256137319150751744
- Often demanded from users, Delta/Android is now the first mobile version of
Delta Chat that offers multi-account support. It's still only
in nightly builds, making its way through testing to the stores.
Delta/Desktop has multi-account support for a longer while already
while Delta/iOS is still lacking it.
- Upcoming Delta Android/iOS/Desktop releases will have
part 1 of ephemeral messages: autodeletion of messages on the device and/or on server.
Auto-deletion is interesting especially for phones used in missions or other delicate
situations because it gives certainty that messages in *all* chats will be removed
after a user-configurable time span. Not much history to be gleaned when a device
is taken away this way.
Part 2 of ephemeral messaging will be more classical per-chat burner-messages
as you know them. The self-destruct timer only starts after you saw a message etc.
- Delta/iOS now also has support for Burner Accounts, the second big
ephemerality feature: you can setup a new temporary account by scanning
a QR code in the setup screen. Also, Delta/iOS now has search support and
generally, Delta/iOS is progressing steadily and users are increasingly
giving happy feedback (stats: 34 PRs, 3 authors, 137 commits).
- All upcoming releases will now default to EDD25519 keys. They
are shorter and faster than RSA2048 keys which Delta Chat still supports.
Support was in prior releases already but we had to fix bugs and wait a little
to make sure that new EDD25519-by-default installs work well with older
app installs -- not all people update immediately and the stores sometimes
take weeks to offer a release to all users (staged roll out, other wait-queue
issues especially with F-droid).
Note that you can't manually change/regen your key. Once we see that
the rollout went smoothly we'll see to offer a away to upgrade
existing RSA2048 to EDD25519. "Just doing it" would break verified groups
so we'd like to ponder the best way forward a bit.
- An organizational feature, and also part of addressing the UX
needfinding report we published in March, Pinned-chats are now becoming
available for Desktop as well (Android/iOS got it earlier already).
This way you can (temporarily) keep chats at the top of your chat list,
overriding the recent-messages-first ordering.
- Delta/Android now grew in-chat search, another feature prioritized from
UX needfinding. Prior, Android only had global search.
- The Delta Chat core Rust library, as usual, got many bug fixes and little
improvements that benefit all platforms (stats: 46 PRs, 10 authors, 254 commits).
As did Delta/Desktop which also grew support for QR code scanning.
- We further explored how to best go for the one big remaining feature:
WebRTC session integration into Delta Chat. It will require a signalling
server instance to be configured with Delta Chat. We are currently testing
some minimal server software for that which serves to establish P2P
audio/video streaming between chat users.
We decided to not frame it as "Audio/Video calls" because especially on iOS
we can't gurantee quick-enough-message-receival while in background
(a common problem for all apps that don't integrate with Apple clouds)
So we rather want to use UX terminology like "A/V sessions" that you enter.
sidenote: we are developing plans for optional google/apple cloud integration
but we'll detail the thoughts about this another time, big topic of its own.
- UX-tests with people in eastern Europe and elsewhere are soon
commencing. We originally had planned this as real-life mission
tests but with Covid19 lockdowns we are now adapting this to be about
burner accounts, auto-deletion and some virtual scenario game play.
- For Easterhegg2020 and IFF we had aimed for (accepted) sysadmin-sessions
which we are now likely turning into documentation and maybe a video-tutorial
activities.
- There is now, thanks to help via OTF's localization team,
an Indonesian translation, shipped in all upcoming releases.
We also established first contacts to the community there ...
- Speaking of community, it's growing and already a little overwhelming
as we are learning with our users to channel feedback to appropriate
places. One note-worthy development (funded by NLNET, not OTF) is a
Delta Chat OAUTH bot that allows to e.g. log into the
https://support.delta.chat Discourse forum using Delta Chat QR-code scans.
More info about how this works here:
https://support.delta.chat/t/the-discourse-login-bot-login-to-this-forum-wi…
The OAUTH Delta Chat bot also just got a quick independent security review FWIW.
We still consider it a prototype because we have not done any specific UX design
which would probably lead us to "Login Chat" which lists all the logins/logouts
to the various web sites that use this automated method of verifying e-mail addresses
(removing the need for manual clicking on "confirmation links" in e-mails).
Besides web sites could use the out-of-band verified key for end-to-end encrypted
notifications to logged-in users ...
so much for this year called april ;)
holger
Greetings to the list,
first but not least: A great many thanks for this great masterpiece of
software - Chapeau!
I am very grateful that this software runs on my Jolla 1 phone
(manufactured 2014, running Sailfish OS (https://sailfishos.org/ (https://sailfishos.org/)) with
android support.
It would be great if you keep it this way, keeping the needed Android
API version the way it is...
This way it is not necessary to have a native Sailfish OS client.
Everything works as expected, fully satisfied!
Keep up the good work!
Martin, Germany
__________ Information from ESET Mail Security, version of virus signature database 21118 (20200406) __________
The message was checked by ESET Mail Security.
http://www.eset.com
android as well as desktop clients are crashing immediately after
startup, also send you the android
crash protocol (look for a crash report from hmajo8585(a)gmail.com).
Afterwards, android client keeps sending crash asserts minutely.
both are crashing immediately after startup, also send you the android
crash protocol (look for a crash report from hmajo8585(a)gmail.com).
Afterwards, android client keeps sending crash asserts minutely.
Here is a little post with my #covid-19 modified thoughts March 17:
https://holgerkrekel.net/2020/03/17/message-to-my-it-hacking-friends-mar17/
There is a lot to digest.
FWIW, in regards to DC i am also consdiering various things, as are others.
Here are a few quick thoughts/efforts that could help general resilience and
desaster usage of DC:
- implement porting your e-mail address to a new e-mail provider.
People often need/want to change their e-mail providers
because they are on crappy ones.
- ensure the IMAP/SMTP network stacks work robustly. People depend on it.
- implement POP3 because some countries have large providers that only
offer POP3
- consider putting DNS fallback IP addresses for common providers
into next DC releases -- blocked or dying DNS would be less
of a problem then.
- write web bots that can manage large groups (but people can also
try using Matrix for that or Telegram channels etc). We don't
need to rule the world.
We can ask for funding here and there and engage / contract more people.
Will discuss with folks but it's not super-urgent for me at the moment.
I'll also probably be online the next days but if you read my above
post you'll know that it's not "constant" onlineness.
Hi DeltaChat Folks.
Today I've setup DeltaChat successfully on Android Phones and Linux Desktop.
I can verify that DC works well with /e/ Mail (e.email), Vivaldi Mail (vivaldi.net) and MacBay Mail v3 (macbay. net)
If you want you can use this with the provider list.
All the best
Marko
Below a little report that was sent to OTF today, telling what was going on in January.
FYI we also just closed multi-day gatherings between several Delta Chat contributors in Freiburg ... but this will rather be reported through blog posts and a Feb report.
Many many thanks to all the good folks in the "DC Testing group" who
spent many hours testing our often buggy pre-releases :)
If you are interested to join this testing of pre-releases please
send me a mail, also with the platform you could test releases on.
----- Forwarded message from holger krekel <holger(a)merlinux.eu> -----
Date: Fri, 14 Feb 2020 11:36:21 +0100
From: holger krekel <holger(a)merlinux.eu>
To: otf-active(a)opentechfund.org, otf-talk(a)opentechfund.org
Subject: [OTF-Talk] Delta Chat highlights January 2020
hello all,
hope you all had a good start into 2020! :)
First some Delta Chat release news across all platforms,
then higher level/objective-related happenings,
and finally some strategic questions we are facing.
For the first time, Delta Chat iOS is now available on the app store, and
is reported to work quite well. https://delta.chat/en/2020-01-09-iOS-appstore-releasehttps://apps.apple.com/app/delta-chat/id1459523234
Delta Chat Android 1.1.2 released to Android store with many bug fixes,
in-app help and other improvements:
https://play.google.com/store/apps/details?id=chat.delta
Delta Chat Desktop 0.999.0/.1 prepared (and finally released on Feb 2)
implementing In-App Help, fullscreen view for media files, bcc-self setting,
better windows support and various internal improvements.
https://delta.chat/en/download
All releases use the updated and evolving Delta Chat rust core,
released as beta24, which improves all platform releases:
- reduce traffic: Combine multiple Read-recipets (MDNs) into one message
(previously one receipt-message per displayed chat message would be sent)
- reduce traffic: reduce gossiping of encryption keys
- fix reply-to-encrypted algorithm, which typically leads to more encryption
- fix and improve imap-deletion of messages and secure-join messages
- fix receiving attachments eg with cyrillic filenames
- around 15 PRs with rust-level cleanups in various areas
From an objective/higher-level perspective:
- UX interviews with journalists/activists/organizers are now complete
and report writing is 75% finished. There are several interesting outcomes
which will also shape further Delta Chat developments in 2020 -- around
providing better support for organizing chats, supporting ephemeral messaging
and device modes, and starring/favoriting/saving messages.
- Outreach: we have ongoing conversations with activists from several
hotspots in eastern europe, asia and the middle east. In particular,
Delta Chat is increasingly a real-life option as a complementary messenger
during internet shutdowns in several regions. We also entered promising
discussions with several universities who want to roll out Delta Chat on
campus. We have several new funding opportunities which we continued pursuing,
both with human rights organizations and commercial provider entities.
We now have a 15-people testing group with activists from global south,
Delta Chat enthusiasts and developers who manually test and provide
feedback on pre-releases.
- Burner Account support is nearing completion -- we have the server
side tooling and Android dev release support for arranging setting
up one-week accounts that hide metadata. There is a new "Scan QR code"
action in the setup screen that allows to setup an account by scanning
a paper or online QR code. The account has a random e-mail address
and a user can only choose a display "nickname". More in the upcoming
blog post (expected February/March).
- Onboarding: much improved online FAQ, now available offline/in-app
with all releases; improvements to the blog/news web page;
a better initial setup experience with guidance on whether Delta Chat
is expected to work out of the box, or needs some preparations -- this
info is integrated offline, allowing to avoid leaking information to
the central mozilla "autoconfig" web site. Provider info is curated
and crowd-sourced here: https://providers.delta.chat/
- WebRTC audio/video calls: we now agreed on a clear path how to introduce
a/v streaming. Delta Chat apps will do the signalling ("setup call session",
"Accept/Decline call session") via the e-mail pipeline, and establish
the actual call (P2P) session via the system browser. This requires a configurable
server on the side of opening the session. The other side could just use
a non-delta chat webmail session then, and still join the call.
If possible, we will aim to include "native widgets" at least on mobiles.
More details when we do a blog post and first releases.
- We aim for fresh releases on all platforms before EasterHegg 2020, and are
involved in preparing a game played out at this 1000-hacker twentieth--anniversay
gathering in Hamburg. We are to give hands-on sysadmin sessions on burner
accounts and e-mail server setups, chat bots and other things. We will also
meet there with several people to prepare a bigger event with UX-real-life
testing in Eastern Europe.
A few open strategic questions currently under discussion:
- Which funding efforts are most promising to keep going financially
from mid 2020 on?
- How can we better support folks in internet-shutdown situations?
Namely, how can we introduce POP3 support requested from activists
because it would help them during internet shutdown?
- How to get the Desktop version to Windows and Mac appstores?
eg Apple currently makes it hard to put Elektron-based apps there.
And generally buereaucracy is growing in all app stores -- more and
more policies, processes and sometimes even videos we are required
to produce. This all takes an increasing chunk away from development time.
- How can we further improve Continous-Integration? Doing releases is
somewhat automated but still requires substantial manual work from 2-3
individuals, making it harder to do "quick releases" and get early feedback.
- Which asymetric-organizational features are feasible given
the "get everything ready till mid 2020" timeline?
- How much can we focus on improving and lifting location-streaming to
shift from "experimental" to "production-ready"?
- How much can we focus on improving and lifting "verified groups" to
shift from "experimental" to "production-ready"?
- How to deal with the growing amount of user feedback on the support
channels, contact e-mails and github repositories?
cheers,
holger
