Deltachat-core written in Rust
To download and install the official compiler for the Rust programming language, and the Cargo package manager, run the command in your user environment:
$ curl https://sh.rustup.rs -sSf | sh
On Windows, you may need to also install Perl to be able to compile deltachat-core.
Compile and run Delta Chat Core command line utility, using cargo
:
$ RUST_LOG=repl=info cargo run -p deltachat-repl -- ~/deltachat-db
where ~/deltachat-db is the database file. Delta Chat will create it if it does not exist.
Optionally, install deltachat-repl
binary with
$ cargo install --path deltachat-repl/
and run as
$ deltachat-repl ~/deltachat-db
Configure your account (if not already configured):
Delta Chat Core is awaiting your commands.
> set addr your@email.org
> set mail_pw yourpassword
> configure
Connect to your mail server (if already configured):
> connect
Create a contact:
> addcontact yourfriends@email.org
Command executed successfully.
List contacts:
> listcontacts
Contact#10: <name unset> <yourfriends@email.org>
Contact#1: Me ββ <your@email.org>
Create a chat with your friend and send a message:
> createchat 10
Single#10 created successfully.
> chat 10
Single#10: yourfriends@email.org [yourfriends@email.org]
> send hi
Message sent.
If yourfriend@email.org
uses DeltaChat, but does not receive message just
sent, it is advisable to check Spam
folder. It is known that at least
gmx.com
treat such test messages as spam, unless told otherwise with web
interface.
List messages when inside a chat:
> chat
For more commands type:
> help
$ git clone https://github.com/deltachat/deltachat-core-rust.git
$ cd deltachat-core-rust
$ cmake -B build . -DCMAKE_INSTALL_PREFIX=/usr
$ cmake --build build
$ sudo cmake --install build
# run tests
$ cargo test --all
# build c-ffi
$ cargo build -p deltachat_ffi --release
-
DCC_MIME_DEBUG
: if set outgoing and incoming message will be printed -
RUST_LOG=repl=info,async_imap=trace,async_smtp=trace
: enable IMAP and SMTP tracing in addition to info messages.
Some tests are expensive and marked with #[ignore]
, to run these
use the --ignored
argument to the test binary (not to cargo itself):
$ cargo test -- --ignored
Install cargo-bolero
with
$ cargo install cargo-bolero
Run fuzzing tests with
$ cd fuzz
$ cargo bolero test fuzz_mailparse --release=false -s NONE
Corpus is created at fuzz/fuzz_targets/corpus
,
you can add initial inputs there.
For fuzz_mailparse
target corpus can be populated with
../test-data/message/*.eml
.
To run with AFL instead of libFuzzer:
$ cargo bolero test fuzz_format_flowed --release=false -e afl -s NONE
vendored
: When using Openssl for TLS, this bundles a vendored version.nightly
: Enable nightly only performance and security related features.
To add the updates from the provider-db to the core, run:
./src/provider/update.py ../provider-db/_providers/ > src/provider/data.rs
Language bindings are available for:
- C [π source | π docs]
- Node.js
- over cffi (legacy): [π source | π¦ npm | π docs]
- over jsonrpc built with napi.rs: [π source | π¦ npm]
- Python [π source | π¦ pypi | π docs]
- Go1 [π source]
- Free Pascal1 [π source]
- Java and Swift (contained in the Android/iOS repos)
The following "frontend" projects make use of the Rust-library or its language bindings: