| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
One of the pixelated adaptors was trying to access a non-existing
attribute in HashableMailbox, which for some reason was blocking the
operation of the imap server (uncatched exception in listeners call
maybe).
adding an attribute skips this error and therefore allows seamless use
of both pixelated and thunderbird user agents at the same time.
Resolves: #8083
|
|
This fixes a bug in which the tls transport complains about receiving
unicode. It was only made evident by running against twisted 16.
|
|
This fixes a bug in which the tls transport complains about receiving
unicode. It was only made evident by running against twisted 16.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Tag version 0.4.1
|
|
Tag version 0.4.1
|
|
|
|
|
|
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
|
