Description
General informations
- system/distribution (with version): Ubuntu 22.04 LTS
- offlineimap version (
offlineimap -V): offlineimap v8.0.0, imaplib2 v3.06, Python v3.8.10, OpenSSL 1.1.1f 31 Mar 2020 - Python version: Python v3.8.10 (from offlineimap -V output)
- server name or domain: Proton Mail
- CLI options: nil
Configuration file offlineimaprc
[general]
accounts = proton
pythonfile = /path/to/a/password/function.py
[Account proton]
localrepository = proton-local
remoterepository = proton-remote
autorefresh = 0.2
quick = 10
postsynchook = notmuch new
[Repository proton-local]
type = Maildir
localfolders = /path/to/maildir
sync_deletes = yes
[Repository proton-remote]
type = IMAP
remoteport = 1143
remotehost = 127.0.0.1
remoteuser = [email protected]
remotepasseval = get_pass()
keepalive = 60
holdconnectionopen = yes
expunge = yes
folderfilter = lambda foldername: foldername not in ['Labels.', 'Labels']
ssl = no
pythonfile (if any)
import sys
pwd = 'proton bridge password'
if len(sys.argv) == 1:
def get_pass():
return pwd
elif sys.argv[1] == 'mutt':
print('set imap_pass=' + pwd)
else:
print('error')
Logs, error
...
Folder Trash [acc: proton]:
Copy message UID -1 (1/1) proton-local:Trash -> proton-remote:Trash
ERROR: Saving msg ([email protected]) folder 'Trash', repo 'proton-remote'failed (error). Server responded: APPEND command error: BAD [b'invalid rfc5322 message: Sender should not be present if equal to From']. Data: b'KJLL287 APPEND Trash () "27-Aug-2023 12:33:47 +0100" {79306}\r\n'
...
Steps to reproduce the error
Run offlineimap (with no CLI options) after using mutt to move an email from INBOX to any other folder. In this case, to Trash.
From and Sender are indeed equal, more or less. In this case:
From: "PALM REPORT by Poolsuite" [email protected]
Sender: PALM REPORT by Poolsuite [email protected]
If I manually delete the sender line from the email, then offlineimap returns to work normally.
I am assuming this is some issue with protonmail thinking that offlineimap is trying to give it a badly formatted email so perhaps the fault is with badly formatted emails. Just wondering if there's something I can do to stop this from happening without manually locating and deleting the sender line in these cases.