Plugins You can find out about all the publicly available Grails plugins.

queuemail plugin

  • Tags: /
  • Latest: 1.0
  • Last Updated: 10 January 2017
  • Grails version: 2.4 > *
0 vote
Dependency:
compile "org.grails.plugins:queuemail:1.0"

 Documentation  Source  Issues

Summary

Queuemail plugin is a centralised email queueing system configurable for many providers all centrally controlled and limited to either daily limit or failures exceeding failureTolerance limit (in a row). By default all email's passing through are priority driven and configured by overall customService name. Two methods of priority queueing are provided BASIC and ENHANCED (default). Enhanced launches an additional thread for each running task and will attempt to kill any running process considered as stuck (if time taken exceeds killLongRunningTasks configuration period).

Description

Queuemail plugin is a centralised email queueing system configurable for many providers all centrally controlled and limited to either daily limit or failures exceeding failureTolerance limit (in a row). By default all email's passing through are priority driven and configured by overall customService name. Two methods of priority queueing are provided BASIC and ENHANCED (default). Enhanced launches an additional thread for each running task and will attempt to kill any running process considered as stuck (if time taken exceeds killLongRunningTasks configuration period).

Email's that arrive in queue are processed through priority rules, please refer to example configuration, each new service you create can be configured to have a specific priority. Higher ones run in preference of lower ones.

Configure how many active concurrent email threads can run at any one time and how many can wait in the queue to be served. Each email is then bound to the emailService that you create and within it you define the configNames and limit. The configName will then need to be created in your applications Config.groovy/application.groovy and essentially contains the SMTP configuration required to connect through and send email's.

The queueing system will use the first provided configuration for every email requested. If this first configName goes offline or was configured incorrectly it will hit a threshold and plugin will mark configuration as inactive

If an email send attempt fails the sole email is re-attempted until it reaches failuresTolerated level. Once this happens current configName is marked as inactive and the next configName is attempted to deliver this email. All new email's will now be going through second configName. The configName that was made inactive will automatically re-join active pool after either setPeriod of time or amount of queueId's passing through. Please refer to notes/configuration and specific segment on message exceptions below.

Please check with your SMTP provider to ensure you are not violating any TOC's whilst attempting to keep within their set limits/boundaries and consequently/possibly having to switch accounts/providers.

For examples and full documentation visit the documentation link provided