[ 
https://issues.apache.org/jira/browse/FINERACT-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vishwas Babu A J updated FINERACT-699:
--------------------------------------
    Fix Version/s: 1.3.0

> Allow using Amason SES (and some others) as email sending platform
> ------------------------------------------------------------------
>
>                 Key: FINERACT-699
>                 URL: https://issues.apache.org/jira/browse/FINERACT-699
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Juhan Aasaru
>            Priority: Major
>             Fix For: 1.3.0
>
>         Attachments: image-2019-02-11-15-37-51-076.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> To send out email from platform one can only use SMTP services where SMTP 
> username is an actual email address ([email protected]). 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:
> !image-2019-02-11-15-37-51-076.png!
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to