Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this page for instructions on how to get full permissions. Sorry for the inconvenience.
This is an archived project. Repository and other project resources are read-only.
[install purple-plugin-delta] support out-of-box Email-chat spec communication
There is a libpurple plugin that supports (autocrypted) chatting over and with any standard email address (also backwards compatible with classic email client users). Repository: https://gitlab.com/lupine/purple-plugin-delta
The plugin was recently updated and is now based on the current deltachat-core code.
Note that the deltachat development has already lead to Open-Xchange (OE) pushing the Email-chat standard to their email provider customers, and this has also been presented at Fosdem. https://www.coi-dev.org/
You can find and check out the current reference client implementations for Android (Play-Store and F-Droid), Desktop, node.js, and iOS (Testflight) through https://delta.chat
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Linked items
0
Link issues together to show that they're related.
Learn more.
inxchanged title from [include purple-plugin-delta] support out-of-box Email-chat spec communication to [install purple-plugin-delta] support out-of-box Email-chat spec communication
changed title from [include purple-plugin-delta] support out-of-box Email-chat spec communication to [install purple-plugin-delta] support out-of-box Email-chat spec communication
@inx
I've built the delta-core and the purple-delta plugin for a quick look. The plugin loads successfully in Pidgin, but can't connect to an IMAP server then. After the plug tries a couple of times to connect, Purple locks up completely. Each connect attempt produces the following output:
INFO: Trying: abc@abc.de haeckse:***:imap.xxx.de:143 haeckse:***:smtp.xxx.de:587 AUTH_NORMAL IMAP_STARTTLS SMTP_STARTTLSGnuTLS error: The operation timed outmy_delta_handler(mailbox, 100, 0, 140643200438528)INFO: IMAP stream lost; we'll reconnect soon.my_delta_handler(mailbox, 401, 0, 140643200413872)ERROR: 0: Could not connect to IMAP-server imap.xxx.de:143 using STARTTLS. (Error #4)my_delta_handler(mailbox, 100, 0, 140643200437696)INFO: IMAP disconnected.
I'm the author of the plugin mentioned above, and would love to help you get it working. I definitely had purism in mind when I started work on it! Although I don't have a device or an environment to test it on.
I've made a few changes just now that fix some re-entrancy issues, which might help with "Purple locks up completely".
I've seen the "Could not connect to IMAP-server imap.xxx.de:143 using STARTTLS. (Error #4 (closed))" message in the past; it's a libetpan MAILIMAP_ERROR_STREAM coming out of its mailimap_socket_connect (called from deltachat-core's IMAP setup_handle_if_needed function).
I think in the past it's been related to the detected IMAP configuration not matching reality. Are you using autoconfig (i.e., just providing email address and password) or configuring everything explicitly?
I'm glad to hear that you would like to help to get the plugin working with Chatty. And it's great, that you considered the Librem phone being a platform for Delta Chat, when you started working on the plugin. I will test the plugin soon again and let you know how it worked.
Hi @lupine , your work to broaden the capabilities of the Librem 5 are much appreciated!
Since the shipment date of the Librem 5 is rapidly approaching, our team will need to remain mostly focused on the features we promised in the campaign. It would be great if Delta Chat was added to our Messages app and we are happy to provide support and code reviews, but we need help from outside community members (like yourself) to port cool new features, like Delta Chat. This means we are happy to answer questions related to all things Librem 5 to help development and testing, but we need outside members to submit the merge request for integrating additional features.
Just a small update on this - the problem seems to be related to running delta on buster generally, not just delta on librem5.
I can reproduce the error against my own mail server (which works when I'm compiling & running from stretch) in a buster chroot on my local machine.
My first guess would be something to do with the new version of libetpan - on stretch, I'm compiling libetpan1.8, but that doesn't compile on buster. Using the buster-packaged libetpan, I reliably get the same output as above.
I'll keep digging, I need this to work on desktop generally ;)
@lupine I've tried to get delta up and running with the latest core/plugin sources and different mail accounts two days ago, but I still wasn't able to make Pidgin connect to the server.
However, I have added the delta-plugin Id to the Chatty code, so the Protocol can be enabled in the settings. But an account for delta needs to be created in Pidgin first, since Chatty has no support for the account setup yet.
@andrea.schaefer right, without the patch above, libetpan configures gnutls to time out far too quickly, which is probably what you saw. I'll keep an eye out on the debian and upstream bugs and try to shepherd them into releases that will be useful to librem5. Thanks for the work getting it into the multi-protocol branch though \o/.
Separately, I've been informed that there may be licensing problems linking libdeltachat (which uses openssl, even in the debian-packaged variant) and libpurple together, due to openssl / GPL license incompatibilities :/. My own plugin code is GPL as well. I'm not a licensing expert, and don't know if it's actually a problem, but if it is, it would prevent us from shipping delta on the librem5 anyway.
Hi all,
good to see purism is interested to ship the librem 5 fully capable to chat with any email address in the world, and autocrypted, out of the box.
As the blocker for shipping the plugin is so trivial to fix, and because the benefit for the librem family is so much more immanent than for debian, maybe that simple one line patch that is required can be applied in pureOS in the meantime:
@inx since pidgin / libpurple lacks the openssl exemption as far as I can see, I don't think it'd solve the issue, would it?
Since the need for the exemption is going away, I'd rather avoid introducing it without a very good reason. To me, the right thing to do would seem to be to get delta to build without pulling in openssl, if possible.
OK, I had a brief chat about this with EionRobb1 of #pidgin on Freenode. They clarified that libpurple lacks the openssl exemption, and confirmed that distributing purple-plugin-delta, linking libpurple <- purple-plugin-delta -> deltachat-core -> openssl, violates GPL in their opinion.
Accordingly, I've removed build instructions and prebuilt binaries from https://gitlab.com/lupine/purple-plugin-delta , and updated with a summary of the issue. Hopefully we can come back to it in a release or two :/