bdcorps / candymail Goto Github PK

There should be a Click here to unsubscribe option on every email body. Unsubscribes emails also need to be recorded. This will be for in-memory and after #9 part of the persistence layer.

Unit Tests are failing on other machines. Need to investigate. Reported by @Omkaragrawal.

The config option of db.reset is not working. The db is resetting every time server restarts.

SEMVAR versioning should be used in the next updates. runAutomation() was changed to runWorkflow() in V13. Since it is a breaking change so it should have been published as a major update.

Currently users can unsubscribe but what if they want to re-subscribe?

Add a EMAILS table instead of UNSUBSCRIBED

Add sqlite3 on file (not in-memory) to persist scheduled messages and unsubscribed users

Nodemailer already has support for DKIM. Need to expose it on Candymail.

Failed attempt: https://github.com/bdcorps/candymail/tree/add-typeorm

Hey,
Are you open to contributions?
I forked and cloned the repository, but the tests fail on the newly forked repo, can you line out how can I start contributing? I am sure that I can help you with adding different mail providers and some other stuffs.

Do let me know, can contact me on [email protected] or website

In order to be consistent and easily scalable, might want to consider using date-fns.

Currently Candymail uses an internal SQLLite DB to keep track of all the emails to be sent out. For more production use cases, we should have the option to specify an external DB.

The config object might look like:

{
    mail: {
      host: 'smtp.gmail.com',
      port: 465,
      secure: true,
      auth: {
        user: process.env.MAIL_USER,
        pass: process.env.MAIL_PASSWORD,
      },
      tls: {
        rejectUnauthorized: true,
      },
    },
    hosting: { url: process.env.HOSTING_URL },
    db: { url: "SQLITE_URL", reset: true },
    debug: { trace: true },
  }

Include steps like "if opened send this email" or "if link clicked send this email"