This repository was archived by the owner on Jan 9, 2025. It is now read-only.
AttributeError: 'module' object has no attribute 'private_keys'#1
Open
jomagalo wants to merge 47 commits intorandogoth:masterfrom
Open
AttributeError: 'module' object has no attribute 'private_keys'#1jomagalo wants to merge 47 commits intorandogoth:masterfrom
jomagalo wants to merge 47 commits intorandogoth:masterfrom
Conversation
…for me without this fix)
…line GPG keys work now.
- Cron now notifies user what happened (key successfully added/deleted or error) - More options to customize templates - Separating concepts in settings (S/MIME, templates) - Register-handler now only informs on failed PGP submissions (reduce mails to user and false positive mails)
… keychain was done case sensitive
…ailgate might not find the certificate for a recipient even if it was available.
…nt received a S/MIME encrypted mail. Furthermore, the header data is now preserved in S/MIME
…nstallation and reflecting recent changes
uragit@779e712 ( Changed GPGEncryptor.encrypt() to also give PGP return code. Write rc to logfile in encrypt_payload(). )
uragit@584eee1 ( Added check that config file keymap fingerprint exists in actual GPG keyring. Decline encryption if mismatch. )
Make check for keys in keymap case insensitive
uragit@62f60f0 ( Added option to convert text/plain source email into MIME/PGP attachment style during encryption. Useful if sending to recipient that can't handle the PGP-inline style. )
…GP encryption in keychain was done case sensitive
…at the mailgate might not find the certificate for a recipient even if it was available." This reverts commit 746aad0.
This reverts commit 99a1108.
…otocol). The previous reverted commits made the gateway incompatible with the RFC. However, compatibility has to be activated in the settings. Most mail servers ignore the case sensitivity of the mail addresses, so this should not be a big issue. A quick solution to make the S/MIME functionality compatible with the RFC was not found so this needs to be fixed later.
… compatibility and ignoring the case sensitivity of mail addresses are supported my S/MIME.
…ssignments of lists as call by object references. So the for-loop broke after first iteration.
…defined recipients (useful if you have some recipients which can't handle one style).
…on existing method Bugfix for PGP/MIME: Make it compatible to RFC 3156 (MIME Security with OpenPGP) when using mails with attachments
Changes while refactoring: The gateway now handles mail addresses case sensitivity compitable to RFC 2821 as default.
…sages correct and not mess up them
…fig file (previously it thought it should write to a file called 'syslog' instead of the real syslog)
…e as the gateway does.
…ave a recipient with two keys.
…backs and might cause some security issues. So before using it please read carefully through the installation instructions.
…as some drawbacks (e.g. content type for files getting lost).
… for and also adding possibility to use default keys for domain ranges
…ypted with PGP/MIME was not encrypted if at least one attachment ot the body itself contained the PGP-tags.
…ing a default key for recipient in domain keymap crashed mailgate.
… they are encrypted if possible.
…se the encryption port for sending messages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After installing, patching and configuring everything I send a test email and return it to me with these metadata:
`Reporting-MTA: dns; mail.email.com
X-Postfix-Queue-ID: 13CD884CAC
X-Postfix-Sender: rfc822; test@email.com
Arrival-Date: Fri, 21 Sep 2018 12:01:34 +0200 (CEST)
Final-Recipient: rfc822; other@gmail.com
Original-Recipient: rfc822;other@gmail.com
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; Traceback (most recent call last): File
"/usr/bin/gpg-mailgate.py", line 688, in
sort_recipients(raw_message, from_addr, to_addrs) File
"/usr/bin/gpg-mailgate.py", line 648, in sort_recipients
recipients_left = gpg_decrypt(raw_message, recipients_left) File
"/usr/bin/gpg-mailgate.py", line 81, in gpg_decrypt keys =
GnuPG.private_keys( cfg['gpg']['keyhome'] ) AttributeError: 'module' object
has no attribute 'private_keys'`