Andris Reinman - EmailEngine Blog (Page 2)

Andris Reinman

Interpreting job queue types

Interpreting job queue types

EmailEngine uses queues to process background tasks, and there is a lot of these. The exact queue library used is BullMQ. EmailEngine includes a UI for BullMQ called Arena to give a better overview and allow managing these queues. You can access the tool from the Tools->Arena menu.

Using an authentication server

Using an authentication server

The easiest way to use OAuth2 with EmailEngine would be to use the hosted authentication form feature. EmailEngine would take care of getting user permissions and renewing access tokens. However, having EmailEngine manage everything is not always desirable. For example, you already use OAuth2 integration in other parts of your

Using EmailEngine to manage OAuth2 tokens

If you want to use the OAuth2 accounts registered in EmailEngine for other activities, for example, you want to run API requests against MS or Google APIs directly, you do so by asking EmailEngine for the tokens. 1. When setting up the Azure app or Google Cloud app, select all

Sending replies and forwarding emails

While EmailEngine (a headless email client that allows accessing IMAP and SMTP accounts over REST API) can send regular emails where you provide all the details for the message yourself (recipients, subject line, and so on), two special modes help to achieve email-client-like behavior. These are "reply" and

Tailing webhooks

If you run an application that produces a lot of webhooks like EmailEngine, you might want to observe what kind of data is even sent before you try to start consuming it. This post shows an easy way to do this with PHP. The concept is simple. Your webhooks producer

Install EmailEngine on Render.com

Render is one of the newest popular web infrastructure services. It makes managing applications very easy – deploying EmailEngine on Render can be done from the web UI without accessing the SSH. For the fastest way to set up EmailEngine on Render.com use the "Deploy to Render" button

Gmail OAuth Service Accounts

Starting from version 2.10.0, EmailEngine can use Gmail service accounts. In this post, I'll show you how to set up such service accounts with EmailEngine.

Nodemailer has zero dependencies

This post is not about EmailEngine but another software project I maintain – Nodemailer. It's a nifty module for Node.js (as you might assume from the name) that allows to send out emails. And in this post, I'll explain how and why I ended up having

Using the EmailEngine API to send email

In this blog post, I'm walking through the required steps to register an account with EmailEngine and sending an email from that account. Step 1. Register a new account Register a new account with IMAP and SMTP settings (reference) curl -XPOST "http://127.0.0.1:3000/

Using EmailEngine with PHP and Composer

EmailEngine [https://emailengine.app/] is an application that allows access to any email account to send and receive emails. It has a small helper library for Composer that you can find here [https://packagist.org/packages/postalsys/emailengine-php]. So, in this post, I'll show how to register an

Version 2

Tl;dr EmailEngine version 2 is now available. EmailEngine is an email syncing application that allows to access your user's email accounts via an easy to use REST API instead of IMAP. Some big news this time. For the past months, I’ve been secretly working on a

Transactional email service

EmailEngine is a self-hosted open-source application that provides a REST interface on top of any email account you can access, to read and send emails. Combining these features would give you a similar email sending experience you'd get from a transactional email service.

Data and security compliance

In this post I'm going to address different security related topics, how EmailEngine handles these and what are the concerns. I'll also list all the data that is stored by EmailEngine.

Mailbox locking in ImapFlow

ImapFlow library allows to open folders in an IMAP account via two different methods, that are mailboxOpen(path) and getMailboxLock(path). What is the actual difference and why would you need something like that?

Tracking email replies

Reply tracking is useful when building integrations with users’ email accounts. Let’s say our service sends out emails as if these were sent by the user, eg. automated sales emails, and now the recipient replies to such message.

Tracking deleted messages on an IMAP account

While it is pretty easy to get the current snapshot state of a mailbox, and it is not hard to track new emails coming in, one particular change is usually quite challenging to follow. That is message deletions.