[
https://issues.apache.org/jira/browse/FINERACT-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300899#comment-17300899
]
Michael Vorburger commented on FINERACT-1270:
---------------------------------------------
As far as can I call (but I haven't reviewed it in details), [~BLasan] has made
at least a start for this in
https://github.com/apache/fineract/pull/1597/files, which seems to replace the
use of {{org.apache.commons.mail}} in {{GmailBackedPlatformEmailService}} by
{{org.springframework.mail.javamail}} (and introduces
{{spring-boot-starter-mail}} for that). Strangely, I don't see that PR removing
the {{org.apache.commons.mail}} dependency yet though - maybe we can do that
here, some time.
> Unify Fineract 3 (!) different email sender utilities
> -----------------------------------------------------
>
> Key: FINERACT-1270
> URL: https://issues.apache.org/jira/browse/FINERACT-1270
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Priority: Major
>
> While looking into addressing FINERACT-1092, I've just noticed that the
> Fineract code base has not 1 and not 2 but 3 (!) classes which send email:
> *
> org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService
> *
> org.apache.fineract.infrastructure.campaigns.email.service.EmailMessageJobEmailServiceImpl
> *
> org.apache.fineract.infrastructure.reportmailingjob.service.ReportMailingJobEmailServiceImpl
> The best thing is that 2 of those use {{org.springframework.mail.javamail}}
> whereas the 3rd (and probably oldest?) uses {{org.apache.commons.mail}}
> instead.
> They, apparently, also use 3 completely different mail server configurations
> in the database! This doesn't make any sense - I cannot imagine anyone
> wanting to use 3 different mail server for 3 purposes.
> Let's merge all this? Best step by step, in a series of several small PRs,
> instead of 1 big one. The DB change may also require DB migration scripts to
> remove the old config (depending on how we want to "migrate").
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
