Sometimes you might want to send emails that should end up in the same email thread, for example, follow-up emails. Surprisingly, there is (almost) no server-side threading support. Instead, everything related to threads is handled on the client side. In this case, we would have to compose our emails in
The easiest way to use OAuth2 with EmailEngine is to use the hosted authentication form feature. EmailEngine would take care of getting user permissions and renewing access tokens. Having EmailEngine managing everything is not always desirable. For example, you already use OAuth2 integration in other parts of your app and
All larger email providers are slowly but steadily moving away from regular password-based authentication for email protocols like IMAP and SMTP. There are multiple options to do so. For example, iCloud requires you to generate application passwords for IMAP. Gmail is pushing OAuth2, even though it also allows application passwords.
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 "forward" 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 [https://api.emailengine.app/#operation/postV1Account]) curl -XPOST "http://127.0.
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 email account