Uploaded image for project: 'Apache Fineract'
  1. Apache Fineract
  2. FINERACT-699

Allow using Amason SES (and some others) as email sending platform

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.3.0
    • Component/s: None
    • Labels:
      None

      Description

      To send out email from platform one can only use SMTP services where SMTP username is an actual email address (email@example.com). Amazon Simple Email Service (and many others) have usernames that don't contain '@' sign at all, Amazon SES has usernames that look like this: 

      AKIAJZ2SHHT7XXXXXXXX

      To solve this issue I propose a fix where one can configure additional parameter "fromEmail" and this is used as fromEmail instead of username. And since we're here I propose also one other additional field "fromName" to be configured as the display name of the sender (can configure organization name to be used there).

      I think it is best to package this new functionality into GmailBackedPlatformEmailService as it everything remains backward compatible with existing installations and they can benefit from being able to set fromName. 

      I have already created and tested code modifications (I will create a pull request shortly).

      In the flyway scripts - when new configuration fields "fromEmail" and "fromName" are created - SQL query looks up the value of "username" and uses that for initial value for both. So no configuration will break but after the changes have been applied the administrator can change these values.

      The good part is that community app doesn't need any new code - it picks up new fields automatically:

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              juhan.aasaru Juhan Aasaru
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 40m
                40m