[Bug]: PDF signed file has been damaged
Issue Description
PDF signed file after received to the email recipient cannot open with error by pdf reader that file has been damaged after update to the latest version [v2.12.0]
Expected Behavior
Receive normally like before.
Current Behavior
This happen after I update the image to the latest version.
Steps to reproduce
Fresh install with docker, I try to make a test from menu "Sign yourself" after the document successfully signed, opensign immediately send email to my self and then I also clicked on the menu button "Mail" after button "Download" then fill with another email address and send. the result of generated pdf signed file on both email is cannot open cause has been damaged.
Screenshots of the issue(optional)
Operating System [e.g. MacOS Sonoma 14.1, Windows 11]
Windows 11
What browsers are you seeing the problem on?
Microsoft Edge
What version of OpenSignâ„¢ are you seeing this issue on? [e.g. 1.0.6]
v2.12.0
What environment are you seeing the problem on?
No response
Please check the boxes that apply to this issue report.
- [x] I have searched the existing issues & discussions to make sure that this is not a duplicate.
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
- [x] I have searched the existing issues & discussions to make sure that this is not a duplicate.
@lsahidin Can you download the file again from "Main menu -> Documents -> Completed" and let us know if its still corrupted? If not, it has to do something with the email attachment. What SMTP server are you using?
@lsahidin Can you download the file again from "Main menu -> Documents -> Completed" and let us know if its still corrupted? If not, it has to do something with the email attachment. What SMTP server are you using?
no, its not. file downloaded from menu Completed can open and read without problem. I am using SMTP server from hosting, something like cpanel webmail.
@andrew-opensignlabs this will be fix in the next release or I need to custom config on email attachment match with SMTP server configuration ?
We are yet to figure out a solution to this. This is being reported more often with google SMTP.
We are having this same issue. Using Microsoft 365 with Outlook.