Dynamic parameters.

[kuez]

Hi guy, i have a question.. how to overwrite/configure dynamic SMTP? I have a business case that he can send email from 3 different accounts and the SMTP, port, direction, etc he can configure and save in database. Tnks :D

[helgew]

You beat me to it! 👍
I posted in the slack #plugin channel yesterday with a similar business requirement to see if there had been any discussions or efforts on implementing this. It is mentioned as a TODO in the documentation.

I would be motivated to take this on but think it would be best if the authors pitch in with their thoughts on how this should be implemented.

Currently, the mail sender is a bean created in the plugin class and injected in the MailMessageBuilderFactory, which in turn creates a builder for every message sent. Options for implementing a more flexible configuration of dynamically configured servers could include

• adding the ability to configure multiple senders together with a name-based specification of which sender to use in the sendMail closure.
• adding a getter to the service that returns a clone of the current sender, which could be reconfigured and provided as an attribute to the sendMail closure
• adding a configuration map as an attribute to the sendMail that then gets merged with the default configuration

Thoughts? Other options/preferences?

[helgew]

In the absence of any feedback so far, I have been able to implement a workaround by replacing the mailMessageBuilderFactory bean with the following:

import grails.config.Config
import grails.core.GrailsApplication
import grails.plugins.mail.MailMessageBuilder
import org.springframework.mail.MailSender
import org.springframework.mail.javamail.JavaMailSenderImpl

import javax.mail.Session
import java.security.Security

class MailMessageBuilderFactory extends grails.plugins.mail.MailMessageBuilderFactory {

    GrailsApplication grailsApplication

    @Override
    MailMessageBuilder createBuilder(Config config) {
        MailSender mailSender = this.mailSender
        if (config.props) {
            mailSender = getMailSender(config)
        }
        new MailMessageBuilder(mailSender, config, mailMessageContentRenderer)
    }

    MailSender getMailSender(config) {
        JavaMailSenderImpl mailSender = new JavaMailSenderImpl()
        if (config.host) {
            mailSender.host = config.host
        } else if (!config.jndiName) {
            def envHost = System.getenv()['SMTP_HOST']
            if (envHost) {
                mailSender.host = envHost
            } else {
                mailSender.host = "localhost"
            }
        }

        if (config.encoding) {
            mailSender.defaultEncoding = config.encoding
        } else if (!config.jndiName) {
            mailSender.defaultEncoding = "utf-8"
        }

        if (config.port) {
            mailSender.port = config.port
        }

        if (config.username != null) {
            mailSender.username = config.username
        }

        if (config.password != null) {
            mailSender.password = config.password
        }

        if (config.protocol != null) {
            mailSender.protocol = config.protocol
        }

        if (config.props instanceof Config) {
            Session session = Session.getInstance(config.props.toProperties())
            session.setDebug(config.debug ?: false)
            mailSender.session = session
        }

        mailSender
    }
}

Basically, the above relies on the config object to contain a key props when the mailService.sendMail(config) { ... } method is used. Seems a bit hackish, but it works.

That was the easy part... figuring out how to use XOAUTH2 with a service account user for Google Apps, not so much :)