Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Attachment files sometimes get corrupted

Featured Replies

Is there any known issue of email attachments getting corrupted after being sent using the Email plugin?  Especially when using an externally stored container field?  It doesn't happen with all files or specific file types - there is no pattern to it, except when I change the container attribute to be locally stored instead of external, the attachment(s) are received A-OK.

I'm using the v2.17 Email plugin, attaching using the EmailAttachFile ( container field ) function.  The attachment and send functions are returning a positive result.  I receive the email with the correct body, subject, etc.  The attachment(s) are there, but when I try to open them/it, the OS states that the file is corrupted and can't be opened.  

Is there something I overlooked, or is this a known issue that I somehow overlooked?

Hi BrentHedden,

I have not seen this reported before. Does it only happen with externally stored container fields? Are you sending to the same domain? Have you seen it happen across different domains? Does it happen with different mail clients? Different OS?

  • Author

As far as I can tell, it only happens when the container is stored externally.  I had the IT personnel who maintains the SMTP server check the email(s) that went through it, and he mentioned that the attachments were corrupted when the email reached that server.

For the most part, it's one domain that we're dealing with.  The attachment is bad regardless of the client or OS, since it got corrupted before it hit the mail server.  

So far, this has been an isolated incident, as other parts of our system that is using the plugin are working just fine.  I'm not going to raise an alarm yet, as I'm unable to replicate the issue from scratch.  I'll inform you guys again if I notice this issue again.

If you are able to reproduce it, please let us know as this is something that we would definitely want to address. Send an email to [email protected] with instructions and/or an example that reproduces it.  Thank you!

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.