You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm unable to attach .zip files that are well under the threshold for PHP max file upload. It seems to be something specific to the .zip file extension as I have no problems attaching large pictures (.png, .jpg) and archives that are anything but .zip (.rar, .7z).
To Reproduce
Steps to reproduce the behavior:
Create a text file (test.txt)
Add some text to it (e.g. abc123)
Add test.txt to a zip file using utility of choice
Create a new email
Attempt to attach zip file to email
Notice that the attachment filename is red which indicates an error.
Attempt to send the email gets the ""Warning! Not all atthacments have been uploaded" error.
Expected behavior
Snappy mail should send the email or give a very specific reason as to why the attachment failed to upload.
Screenshots
Please complete the following information:
Browser: Firefox 135b02
unknown - IMAP is hosted service at ionos
PHP version: 8.1-fpm
SnappyMail Version: 2.38.2
Mode: standalone
Debug/logging information
No errors appear in nginx PHP logs or in snappy mail application logs.
Browser console window does show a "Error: Attempt to postMessage on disconnected port" error but that doesn't really seem important.
Additional context
Really at the end of my rope trying to figure this out as as usually errors show up in either the console or the server logs. This seems suspiciously like the client side snappymail app is trying to peek inside or otherwise interpret files with a .zip extension instead of treating them like an opaque binary blob.
The text was updated successfully, but these errors were encountered:
On a hunch, I enabled debug logging and this turned out to be the result of the php-zip package not being installed. The error is "Class ZipArchive not found".
This is still a problem because:
Why does snappymail care about .zip at all vs any other opaque binary blob I might attach to an email?
My default logging level is set to Warning (4) which should still show errors
And it looks like the class not found error is getting wrapped and returned as an INFO level message. That explains why it wasn't showing up in my logs.
Describe the bug
I'm unable to attach .zip files that are well under the threshold for PHP max file upload. It seems to be something specific to the .zip file extension as I have no problems attaching large pictures (.png, .jpg) and archives that are anything but .zip (.rar, .7z).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Snappy mail should send the email or give a very specific reason as to why the attachment failed to upload.
Screenshots
Please complete the following information:
Debug/logging information
No errors appear in nginx PHP logs or in snappy mail application logs.
Browser console window does show a "Error: Attempt to postMessage on disconnected port" error but that doesn't really seem important.
Additional context
Really at the end of my rope trying to figure this out as as usually errors show up in either the console or the server logs. This seems suspiciously like the client side snappymail app is trying to peek inside or otherwise interpret files with a .zip extension instead of treating them like an opaque binary blob.
The text was updated successfully, but these errors were encountered: