I think it is a good idea. The users of a mailserver with gpg-lacre should have a right to the source code of the exact version of gpg-lacre responsible for encrypting their emails. The AGPL does…
Hi @pfm,
are there any news on this?
Should this issue be opened again or should we open a new one?
Also, there is another weird thing going on, some emails look like this after being…
root@klarheit:~/gpg-lacre# make test
mkdir test/tmp
mkdir test/logs
rm -fv test/gpg-mailgate.conf
rm -f test/logs/*.log
git restore test/keyhome
python3 test/e2e_test.py
.
------------…I just updated to the current master branch to which the fix was merged.
Well, all emails do arrive, but it still messes up special characters in emails from Thunderbird for me.
Did you also get my two additional emails about encoding errors regarding messages sent from K9-Mail?
I'm asking because if you're using gpg-lacre already on your server they might have not…
First of all, thanks for the fix and the information. Emails sent from Thunderbird arrive again now!
Sadly however, there is still something going wrong during the encryption of emails sent…
With this version emails sent from Thunderbird won't arrive at all for me:
Python 3.9:
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; Traceback (most recent call last): File
…After the update I still get the error:
UnicodeEncodeError:
'ascii' codec can't encode character '\xf6' in position 612: ordinal not in
range(128)
For emails sent from K-9 Mail everything works fine:
Return-Path: <office@klarheit.at>
Delivered-To: office@klarheit.at
Received: from mail.klarheit.at
by klarheit with LMTP
id…I just updated. However, gpg-lacre still seems to have a hard time encrypting 8-Bit UTF-8 messages cntaining emojies and umlauts.
Return-Path: <mail@emanuel-loos.eu>
Delivered-To:…Thanks, I saw the update after commenting on this issue and and have already installed it.
It seems this only happens with emails not to be encrypted by the server. After setting up server side encryption for the account, the confirmation emails from keyserver@keys.openpgp.org arrive,…
I am getting this error as well, but with an email that should not even be touched by gpg-lacre as there is no public key for the receiving address in the server's keyring. It is a confirmation…
Turns out I forgot to copy gpg-lacre-logging.conf.sample to /etc/gpg-lacre-logging.conf. Sorry for the noise.