FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    Amazon SES issues as SMTP with FusionAuth

    Scheduled Pinned Locked Moved
    Q&A
    0
    4
    809
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      faizan
      last edited by

      I am using amazon SES as a smtp and it gives this error
      [
      Unable to send email via JavaMail
      Prime Messaging Exception
      ]

      Any Idea! I have checked everything and there is no problem with SES and EC2 connectivity

      1 Reply Last reply Reply Quote 0
      • D
        degger
        last edited by degger

        I'm having exactly the same with Mailgun. It looks like a bug, we have tried everything. I have now reported it here: https://fusionauth.io/community/forum/topic/1075/amazon-ses-issues-as-smtp-with-fusionauth

        We have this on a FusionAuth cloud deployment as deployed by FusionAuth themselves.

        1 Reply Last reply Reply Quote 0
        • danD
          dan
          last edited by

          If you look at the network tab of your browser dev tools, you can examine the response when you send a test email. Can either of you share the response you are seeing? It will help debug this issue.

          See my screenshot of my devtools window:

          Screen Shot 2021-06-10 at 7.20.11 AM.png

          Also, looks like @degger filed an issue, thanks for that! https://github.com/FusionAuth/fusionauth-issues/issues/1263

          --
          FusionAuth - Auth for devs, built by devs.
          https://fusionauth.io

          1 Reply Last reply Reply Quote 0
          • D
            degger
            last edited by

            As answered on https://github.com/FusionAuth/fusionauth-issues/issues/1263, this was indeed an issue with port 25.

            For anybody encountering the same problem:

            1. Try switching to another port (587, 465, or 2525)
            2. Try switching TLS to SSL and the other way around with all the different port configurations.

            Took me a while to find this, probably because I mistyped 587 as 578.

            1 Reply Last reply Reply Quote 2
            • First post
              Last post