Menu

#652 Empty body when decrypting to folder

fixed
nobody
None
nightly
Major
45.4.0
2.0.30
Mac_OS_X
2.1
nobody
2019-11-03
2016-11-12
hmijail
No

I have a set of PGP-encrypted mails that are decrypted and displayed correctly by Enigmail, but that are left with an empty body when using the "Decrypt to folder" or the Enigmail filter actions to create a decrypted copy of the mail.

This happens both with the release version of Enigmail and with the nightly build.

I can provide an example email and a debug log, but I would prefer not to publish them here. Could I send them somewhere non-public?

Discussion

  • Patrick Brunschwig

    Can you please attach a sample message? I don't need to be able to decrypt it, but just to see the message structure

     
  • hmijail

    hmijail - 2016-11-13

    I'm attaching a sample with some bits edited (host names, subject), and the PGP block snipped.

     
  • hmijail

    hmijail - 2016-11-13

    And this is the result of "Decrypt to folder". Again, I have edited the host names and subject string, but here I haven't snipped anything.

     
  • hmijail

    hmijail - 2016-11-26

    Was that enough, or should I post something else?

     
  • Patrick Brunschwig

    I can successfully decrypt such messages. Can you please create a debug log file (repeat the decryption attempt; then follow these steps:

    • Open the Enigmail Preferences panel (OpenPGP->Preferences)
    • Activate the checkbox Display Expert Options and close the dialog
    • Open the menu Enigmail > Debugging Options > View Log.
    • Click the Save Log to File ... button to save the log.
     
  • hmijail

    hmijail - 2016-11-26

    Done.

     
  • Patrick Brunschwig

    Excuse me, but you attached a log with 17 mails that were possibly decrypted (or not). I cannot debug this. Please limit your test to only 1 attempt that shows the failing behavior.

     
  • hmijail

    hmijail - 2016-11-26

    Trying again.

    Sorry about the previous one, I was careful to only get a single try and clean it up - so I don't know what happened. This time the log is shorter for sure...

     
  • Patrick Brunschwig

    According to the log, the decryption was successful. The log looks exactly as I expected, and identical to my own log. Can you try to decrypt to a local folder instead of an IMAP folder (just as a test)?

     
  • hmijail

    hmijail - 2016-11-28

    Those decryptions were already done to a local folder.

     
  • hmijail

    hmijail - 2016-11-28

    I just tried again and diffed the log, and the only differences are in the timestamps (and the parts I masked out)

     
  • Olav Seyfarth

    Olav Seyfarth - 2016-11-28

    I don't know if this hits you also, but since approx. half a year I regulary have corrupted index files. This is VERY bad in conjunction with decryption. If logs show that your decryption was successful but your message isn't, pleas try to re-create the local index by "Repairing" the folder you saved your message to: Rightclick on the folder, choose Properties, hit Repair folder button. HTH.

     
  • hmijail

    hmijail - 2016-11-28

    Thank you for the tip. I just tried, but nothing changes.

    In the properties window of the folder there is a path to the file ("Location"). I checked that file with 'less' in a Terminal window. The message really is cut off, as shown in my attachment "decrypted.txt" from November 13.

     
  • Patrick Brunschwig

    • status: open --> fixed
    • Fixed in version: --- --> 2.1
     
  • Patrick Brunschwig

    I have re-written the decrypt-to-folder function (and the filter action) from scratch using a different approach to obtain the full message. I hope that this is fixed now.

     

Log in to post a comment.

MongoDB Logo MongoDB