Closed Marcool04 closed 2 years ago
Yeah, even regular attachments aren't supported yet. So inline attachments, which are one step further, aren't either.
But this is to a non-encrypted, non-protonmail recipient… (outlook, as the headers make clear) Attachments work there with no problem for me 🤨
Ah, then yeah. Need to update the code to do whatever the webapp is doing to make that work, probably setting a few more fields in the attachment JSON object to set the content disposition and the content ID.
Is there a solution yet?
@coffseducation since the front page has the warning :+1:
warning Warning: IMAP support is work-in-progress. Here be dragons. For now, it only supports unencrypted local connections.
and the maintainer/author of hydroxide, @emersion has create an issue announcing that he is going to "Drop IMAP support", I think it's pretty safe to assume no solution to this will be forthcoming unless somebody else decides to start developing and maintaining the IMAP side of hydroxide.
As also mentioned in that issue, since the point of hydroxide was never to bypass Proton Mails pricing, and that the official client is now open source (which the similar project peroxide builds on), the point of actually putting effort into this seems a bit mute to me...
Hi there,
It appears hydroxide somehow truncates images placed in
multipart/alternative
emails, under themultipart/related
, this happens for instance when using HTML to compose an email in Thunderbird, selecting the image insertion dropdown, then "Image", selecting a file and ticking "attach image to the message".My guess is it is happening somewhere in the few lines after this : https://github.com/emersion/hydroxide/blob/b122ca8a1f0fe1203d58b99c716f282de4a4a3df/smtp/smtp.go#L192 when the SMTP data gets converted into internal structures, since in the log, the POST data looks good, but the uploaded "Draft" email already has the image missing, right after. Possibly something to do with this line? https://github.com/emersion/hydroxide/blob/b122ca8a1f0fe1203d58b99c716f282de4a4a3df/smtp/smtp.go#L240
As you can see, in the POST data we have:
but in the JSON sent to the Protonmail API this has become:
where I have checked that the clipped PGP encrypted data above decrypts to the HTML only:
Let me know if I can help further. Thanks, as always, for this mighty useful piece of software 👍 Regards, Mark.