| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
If you try to fetch the incoming service while it's still starting it
throws a KeyError.
- Resolves: #9174
|
|
To get the status of a single message providing it's mailbox and
message-id. For now it only returns encryption/signature status.
- Resolves: #6914
|
|
To have consistency with all API calls related to messages and start all
of them with msg_*
|
|
- Resolves: #9023
|
|
There was a mismatch on the return values of Nicknym class and the
expectations. As most of the code was expecting an OpenPGPKey, but it
was returning the json as it came from the nickserver. Now is just
returning the key data.
|
|
|
|
There was common situations where two provider instances where running
in parallel. And was creating weird errors (like getting wrong api_uri)
because the bootstrap deferreds were global but the Provider objects
not.
I don't like much singletons, but I think now is simpler than before.
- Resolves: #9073
|
|
node-mail chokes if we don't.
|
|
the UI is expecting it there, not inside the result data.
we probably could delete it from the later.
|
|
- Related: #9010
|
|
So each service can have it's own config section passed to the
constructor.
|
|
|
|
- Resolves: #9025
|
|
|
|
- Resolves: #8973
|
|
We need to update the UI to use the new API.
- Resolves: #8974
|
|
For now we say it will be mixed on every request if the mixnet is
enabled. We might want a better mock in the future.
- Resolves: #8972
|
|
|
|
This is a first approach to automatic gateways selection.
More things are missing:
- allow manual selection, by location or country code.
- take the hemisphere into account.
- expose the selected gw to the api/cli
but overall seems this is a good approach to make 0.10 release usable in
terms of vpn.
- Resolves: #8804
|
|
this allows for better modularization in, for instance, the debian
package. we should be able to install just the submodules for the vpn
service, or the mail service.
a better modularization needs the mail_services under core to be moved
to bitmask.mail, and do the switch in the main service module for
bitmask daemon.
|
|
- Resolves: #8986
|
|
Let's also catch the exceptions raised by stopping services so bitmaskd can
stop.
|
|
- Resolves: #8852
|
|
If is set keyamanger will try to discover and download the key.
- Resolves: #8821
|
|
- Resolves: #8921
|
|
- Resolves: #8931
|
|
Deal as well with sending key if key is outdated in the providers nicknym.
- Resolves: #8819, #8832
|
|
- Resolves: #8835
|
|
- Resolves: #8910
|
|
|
|
Allows to upload a key to providers that use a different api uri than
api.provider.net
- Resolves: #8868
|
|
When setting the listeners in the IMAP Folder, we avoid setting more
than one listener for the same imap mailbox (because in some situations
we were registering way too many listeners).
this was making the pixelated inbox registering the notification and
therefore the imap mailbox not being registered.
this MR also refactors the way pixelated is initialized, so that it
avoid creating a second Account instance. In this way, we make sure that
the pixelated mua and the imap server share the same collections for a
given mailbox, and therefore any of the two is able to get a
notification whenever the other adds a message to the mailbox.
- Resolves: #8846, #8798
|
|
|
|
- Resolves: #8886
|
|
|
|
This fixes two bugs with handling the autoconf parameter:
- It looks for "True" instead of "true" in the dispatching code to
account for json.dumps() converting true into a boolean and str()
returning the python-style capitalized version "True".
- It moves the initial definitions of offirst_bootstrap,
ongoing_bootstrap, and stuck_bootstrap into the class instantiation
method so they don't get shared between instances of the
class. Previously, this caused one instance being bootstrapped to
causes other instances to think they were also actively being
bootstrapped.
Resolves #8843
|
|
- Resolves: #8873
|
|
None is recognized as not-default and gives an error if the
searched config value is not present in the config file. This was
provoking an error with manhole not being configured.
|
|
|
|
|
|
|
|
I changed most of the logger statements to use a class attribute, in
this way it's easier to identify which class it's logging them.
in some cases I leave a module-level logger, when we're either using
functions or when the module it's too small.
at the same time I did a general review and cleanup of the logging
statements.
|
|
- Resolves: #8845
|
|
|
|
|
|
- Resolves: #8786
|
