Task and Message Queues with Multiple Providers
Tiny queue data structure
A reliable job queue with deduplication, request/response support, and pluggable storage
queue up function calls
 
A node.js driver for mysql. It is written in JavaScript, does not require compiling, and is 100% MIT licensed.
A live preview of your emails right in your browser.
Email address and domain validation
Transform React components into HTML email templates
Extremely fast double-ended queue implementation
A simple Markdown to jsx parser for email templates written in typescript.
Email address and domain validation
An email address parser based on rfc5322
Email parser for Node.js and browser environments
Parse an author, contributor, maintainer or other 'person' string into an object with name, email and url properties following npm conventions.
Provides a fast, pretty robust e-mail validator. Only checks form, not function.
Get a GitHub username from an email address
mjml-body
Twilio SendGrid NodeJS internal helpers
Forge SQL sdk
Node library for parsing plain text email content. Based on https://github.com/willdurand/EmailReplyParser
The Mailosaur Node library lets you integrate email and SMS testing into your continuous integration process.
A Node.js module for verifying email addresses
A queue that is dequeued by forked processes
With this gem you will be able to enqueue your emails on your Resque workers to avoid making your user wait for the email to be send when he causes an email sending action in your application. Using resque_action_mailer_backend makes email sending a breeze as you will be able to use Resque to retry failed emails, easily deliver all those marketing emails to your clients and without changing anything at your email sending code. Just tell your application to use :resque for sending emails and you're done, no need to add yet another tool just for delivering your emails if you're already using Resque for your asynchronous processing.
This is a weak deduper to make things like bulk email run safer. It is not a lock safe for financial/security needs because it uses a weak redis locking pattern that can have race conditions. However, imagine a bulk email job that loops over 100 users, and enqueues a background email for each user. If the job fails at iteration 50, a retry would enqueue all the users again and many will receive dupes. This would continue multiple times as the parent job continued to rerun. By marking that a subjob has been enqueued, we can let that isolated job handle its own failures, and the batch enqueue job can run multiple times without re-enqueueing the same subjobs.
A Resque plugin to alarm when queue is too long. Using email or rails log, or others log system. Use other tools to analyze result. Queue is checked every time job enqueued.