A clone of https://pep-security.lu/gitlab/thunderbird/pEpForThunderbird , with changes meant to be compatible with recent engines.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Jörg Knobloch fcfc77f307 Version 1.1.109. 1 year ago
addon Version 1.1.109. 1 year ago
tests Remove unused code and adjust tests. 1 year ago
.eslintrc.json Restore "airbnb-base". Oops. See rev. 1f567b1a286a and rev. 224ec02c1e9e. 2 years ago
.gitconfig Add .gitconfig with LESSCHARSET=utf-8 1 year ago
.gitignore Add patches-master/ to .gitignore 1 year ago
.mocharc.json Move forward Decrypt/Encrypt 4 years ago
DEVELOPMENT.md Picked up some text from the old documentation branch. Still mostly out of date. 1 year ago
Dockerfile Show privacy ratings on emails on decrypt and on composing 3 years ago
Makefile Renamed `chrome` directory to `addon` and related changes. No idea why it was called `chrome` in the first place. 2 years ago
README.md Picked up some text from the old documentation branch. Still mostly out of date. 1 year ago
makeXPI.bat Switch from hg to git and stop copying into no longer existent profile. 1 year ago
manual-and-test.md P4TB-73 use identity `protectionDisabled` for disabled accounts 3 years ago
package-lock.json Change p4t and p4tb to pEp4Tb for chrome:, change preferences to pEp, general cleanup. 2 years ago
package.json Lint all the tests, even the dead ones. 1 year ago



p≡p for Thunderbird

This is a Thunderbird extension providing p≡privacy to your mail. It relies on the p≡p JSON adapter to access the key management, synchronisation and automation logic provided by the p≡p engine.

How To Build

Using bash

Just run make to build from the current source, producing a file in build/p4t.xpi that can be installed from Thunderbird's add-ons manager page clicking on "Install from file". For information about building and running the engine adapter see its repo.

cd addon ; zip -r ../build/pEp4Tb@pEp.security.xpi . ; cd ..

Check syntax statically

You can parse the code with Babel in order to catch syntax errors. After installing with npm install just run:

npm run syntaxCheck

Run ESLint

You can run ESLint to check the style guides defined in .eslintrc.json with the npm script:

npm run lint

ESLint can auto fix some problems with the option --fix but most of them must be fixed manually:

npm run lint --fix
npm run lint -- --fix (on Windows)


To run tests first is needed to install all dependencies

npm install


npm run test
npm run linttest

More info

Check the DEVELOPMENT.md file here for a collection of development notes. See also our dev wiki.