bitmask-dev issueshttps://0xacab.org/leap/bitmask-dev/-/issues2017-08-24T21:20:48Zhttps://0xacab.org/leap/bitmask-dev/-/issues/8980update UI to the new bitmask.mail.get_token2017-08-24T21:20:48Zmeskioupdate UI to the new bitmask.mail.get_token`get_token` now requires a uid parameter.`get_token` now requires a uid parameter.0.10rc1simonftsimonfthttps://0xacab.org/leap/bitmask-dev/-/issues/8974remove active user from mail_services2017-08-24T21:20:48Zmeskioremove active user from mail_servicesI thought we already did (#8874), but there is still an active user used at least to get the imap/smtp token.I thought we already did (#8874), but there is still an active user used at least to get the imap/smtp token.0.10rc1meskiomeskiohttps://0xacab.org/leap/bitmask-dev/-/issues/8972provide an API about sending mixing2017-08-24T21:20:48Zmeskioprovide an API about sending mixingGiven an email address we need a way from the UI/pixelated to know if will be sent over the mixnet. It should take into account if our provider and the receiving provider support mixing and if we have mixing enabled in bitmask.
For now ...Given an email address we need a way from the UI/pixelated to know if will be sent over the mixnet. It should take into account if our provider and the receiving provider support mixing and if we have mixing enabled in bitmask.
For now we'll have to mock it as we don't have mixing in the server. But we can already implement the configuration in bitmask.0.10rc1meskiomeskiohttps://0xacab.org/leap/bitmask-dev/-/issues/8968Add feedback about status of mixnet in Pixelated UI2017-08-24T21:22:59ZKali KanekoAdd feedback about status of mixnet in Pixelated UI# Definition of done
* [ ] an icon changes status (grey/green) in the compose window if the message is going to be mixed
* [x] an icon changes status (green) in the email view window if the message has been mixed
# Steps
* [x] write r...# Definition of done
* [ ] an icon changes status (grey/green) in the compose window if the message is going to be mixed
* [x] an icon changes status (green) in the email view window if the message has been mixed
# Steps
* [x] write requirements for the client side (bitmask)
* [ ] ~~design server API spec~~
* [x] add mixnet component to core
* [ ] hack on pixelated widgets
* [ ] ~~parse mixnet-service.json~~
* [ ] ~~switch delivery to smtp proxy for mixnet~~
# Specs
* a composing message will be mixed if: a) the recipient provider belongs to the mixable set (advertised by our provider), b) the user has opted-in to mixing (in bitmaskd.conf for now), c) the mixnet is healthy (query status api in the platform).0.10rc1meskiomeskiohttps://0xacab.org/leap/bitmask-dev/-/issues/8957alot doesn't try to automatically decrypt messages sent from Bitmask Client B...2017-08-15T23:13:00Zdrebsalot doesn't try to automatically decrypt messages sent from Bitmask Client BundleSteps to reproduce:
* Use latest Bitmask Client Bundle (bf1984d8707454c1cf13169cc8f937fc3be1dfae)
* Send an email to another account.
* Check the account with latest alot (0.4, from [pypi](https://pypi.python.org/pypi/alot)).
Expected ...Steps to reproduce:
* Use latest Bitmask Client Bundle (bf1984d8707454c1cf13169cc8f937fc3be1dfae)
* Send an email to another account.
* Check the account with latest alot (0.4, from [pypi](https://pypi.python.org/pypi/alot)).
Expected behaviour: alot should be able to detect that it is an encrypted message and try to decrypt it automatically.
Observed behaviour: alot shows an `application/pgp:msg.asc` attachment and doesn't try to decrypt it and show it.
Here is the source of the message, as it arrived: [source.txt](/uploads/8a00481d911d5516a63324fae5a78f8c/source.txt)
Note that it works fine in mutt.
I am not sure if this is a problem from bitmask, pixelated, or alot.0.10rc1meskiomeskio