Email Image/Attachment (Incoming) - 403 Forbidden

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • esforim
    Active Community Member
    • Jan 2020
    • 2204

    Email Image/Attachment (Incoming) - 403 Forbidden

    Anyone know how I can fix this to work? It been awhile and still no luck.

    Attachment is being as inline and EspoCRM don't accept these file format even though I allowed for it, perhaps in the wrong field...? But there is no other field we can Edit in the GUI.

    Here is the field setting.
    Click image for larger version

Name:	image.png
Views:	126
Size:	46.6 KB
ID:	110012


    Here is the error
    Click image for larger version

Name:	image.png
Views:	65
Size:	7.9 KB
ID:	110013

    Here is the email look like.
    Click image for larger version

Name:	image.png
Views:	64
Size:	2.7 KB
ID:	110014
  • victor
    Active Community Member
    • Aug 2022
    • 727

    #2
    Try Reset to Default and send the test email again. Also try specifying permissions again: https://docs.espocrm.com/administrat...n/#permissions.
    If the situation recurs, send the EspoCRM error log.

    Comment


    • esforim
      esforim commented
      Editing a comment
      Reset what to default? Does it fall under Attachments field for example inline image? Thank you.
  • yuri
    Member
    • Mar 2014
    • 8440

    #3
    There's no MIME type "image/jpg". It should be "image/jpeg".

    Maybe an issue is the code that generated that email.
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

    Comment

    • victor
      Active Community Member
      • Aug 2022
      • 727

      #4
      Reset what to default? Does it fall under Attachments field for example inline image?
      I mean field settings​​​​​​​:

      Click image for larger version

Name:	image.png
Views:	67
Size:	22.9 KB
ID:	110087

      Comment

      • esforim
        Active Community Member
        • Jan 2020
        • 2204

        #5
        There is no issue with the image itself. I can open it fine in Webmail.

        If it a codec issue or incorrect file extension, is there any way to force it to be allow when importing (POP) email?

        If I download the file, upload it somewhere else, for example in Documents, there is no issue in EspoCRM, seem to be email importing related?

        The same file from the email:
        Click image for larger version

Name:	image.png
Views:	87
Size:	13.9 KB
ID:	110090

        Comment

        • yuri
          Member
          • Mar 2014
          • 8440

          #6
          When email was composed, the client (or some script if an email is generated somewhere) added an image attachment and set an incorrect mime-type.
          If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

          Comment


          • esforim
            esforim commented
            Editing a comment
            Thank you. That is certainly odd that email does that. But I also find it odd that we can open the same file without making any edit by just re-uploading it, but I'm not a coder so my thinking is on an user level.

            I guess I just wait for the future. Thank you.

          • yuri
            yuri commented
            Editing a comment
            File can be opened. But it cannot be displayed inline as the system blocks it (because of the wrong mime type of the attachment). It's a programmer's mistake in the code that composed the email. We unlikely ever will display inline images regardless of mime types.

            You can add allowed mime types in metadata: https://github.com/espocrm/espocrm/b.../image.json#L2

            But use "__APPEND__" when extending arrays.
            Last edited by yuri; 09-10-2024, 10:48 AM.

          • esforim
            esforim commented
            Editing a comment
            Thank you! Sorry to be nuisance, any way to make it upgrade safe with a custom file?
        Working...