Thanks for checking that out, Preston! That information, as well as a few other reports of this behavior, helped us determine that this is a bug related to the Amazon service we use to store attachments. We've reached out to the Amazon team about this and I'll update this thread when we have more information.