| Age | Commit message (Collapse) | Author |
|---|
|
for consistency with the previous Account change.
|
|
Previously Account used user id from the store, but this attribute is
optional and None by default. This caused the collection_mapping to be
unable to distinct between multiple users message collections.
This chance adds a non optional user_id attribute to Account and use it
to index the collection_mapping.
- Resolves: https://github.com/pixelated/pixelated-user-agent/issues/674
- Releases: 0.4.0
|
|
The print statement only printed a number. Seeing the print you cannot
know what was printed. Seems that this line was left during a debug
process.
|
|
This greatly simplifies the handling of the password in the thunderbird
extension.
Related: #6041
|
|
|
|
We catch any error on SMTP delivery and format it as a bounce message
delivered to the user Inbox.
this doesn't comply with the bounce format, but it's a nice first start.
leaving proper structuring of the delivery failure report for future
iterations.
- Resolves: #7263
|
|
|
|
this one was missing after the events refactor.
the bug is that client was discarding the first parameter, assuming it
was the userid.
|
|
the mail service uses an Account object created from scratch, so it
wasn't sharing the collections mapping with the other Account object
that is created in the IMAP Service.
I make it a class attribute to allow mailbox notifications.
However, with the transition to a single service tree, this class
attribute can again become a class instance.
This is somehow related to a PR proposed recently by cz8s in pixelated
team:
https://github.com/leapcode/leap_mail/pull/228
However, I'm reluctant to re-use IMAPMailbox instances, since they
represent concurrent views over the same collection. I believe that
sharing the same underlying collection might be enough.
|
|
this was gone with the imap/cred refactor, but the client relies on it
to hide the 'congratulations!' welcome display on the mail widget.
|
|
- Resolves: #7977
|
|
- Resolves: #7898
|
|
|
|
for some reason, available_backends does not work inside a frozen
PyInstaller binary.
- Resolves: #7952
|
|
|
|
- Resolves #7861
|
|
* Resolves: #7889
|
|
|
|
|
|
- leap_mail still uses pycryptopp and therefore still needs the
dependency
- Keymanager calls to async HTTPClient had not been mocked, causing
a test to fail
- fixed a pep8 warning
|
|
- Create a new Generator that doesn't trim the headers
- Extract detached signature from message
- Convert message to the body an attachments level
- Add coment to the generator workaround and shows which python version
has the patch
|
|
- Extract message serialization to a method
- Add new condition to verify signature on plain text mail
- Return InvalidSignature if cannot verify
|
|
|
|
|
|
|
|
imap tests must be adapted, using a dummy credential checker.
|
|
|
|
It won't break anymore if the body is None, but will
return an empty body in that case
|
|
- Resolves: #7656
- Releases: 0.4.1
|
|
we were adding listeners for each mailbox instance, which was making
appends particularly slow, since the method that gets current count and
recent count is expensive and was being called way too many times.
|
|
Related: #7495
|
|
In case of InvalidAuthTokeError from soledad sync we need signal the GUI, so
it will request her to log in again.
- Resolves: #7430
|
|
- Related: #7471
|
|
|
|
|
|
As a class variable multiple account instances share
mailboxes which is bad if its different users or tests
|
|
|
|
|
|
The key extract should check first for attached keys and if this fails
then should try the OpenPGP header.
- Resolves: #7480
|
|
|
|
|
|
|
|
We can't import attached keys with different email address than the
sender. Now we don't fail in this case, just log it.
- Resolves: #7454
|
|
in this way, we're using twisted reactor instead of having another
thread with zmq's own copy of tornado ioloop.
Resolves: #7274
|
|
|
|
So now it:
- Accepts credentials in a file pointed by environment variable.
- Allows to specify the mailbox to select as a command line flag.
- Allows to select a given message by subject.
For example:
BITMASK_CREDENTIALS=/tmp/bm.secrets ./getmail --mailbox INBOX --subject
'test mail
The two flags are case-insensitive.
This is intended to be used as a helper in end-to-end tests.
Getting a message by subject it's suboptimal, but I think it's good
enough for our testing purposes right now.
Related: #7427
|
|
|
|
This way we can tell if a message was originally encrypted, so that we
can show that information to the end user.
|
|
|
|
|
