Ghost/ghost/email-events/index.js

module.exports = {
    SpamComplaintEvent: require('./lib/SpamComplaintEvent'),
    EmailBouncedEvent: require('./lib/EmailBouncedEvent'),
    EmailDeliveredEvent: require('./lib/EmailDeliveredEvent'),
    EmailOpenedEvent: require('./lib/EmailOpenedEvent'),
    EmailUnsubscribedEvent: require('./lib/EmailUnsubscribedEvent'),
    EmailTemporaryBouncedEvent: require('./lib/EmailTemporaryBouncedEvent')
};
Added @tryghost/email-events package refs https://github.com/TryGhost/Team/issues/2253 refs https://github.com/TryGhost/Team/issues/2254 This package is analogous to the @tryghost/member-events package. The events here will be consumed by the EmailSuppressionList implementation and used to add emails to said list. They'll be dispatched by the code which handles events received from Mailgun. 2022-11-24 09:54:20 +03:00			`module.exports = {`
			`SpamComplaintEvent: require('./lib/SpamComplaintEvent'),`
Added new email event processor (#15879) fixes https://github.com/TryGhost/Team/issues/2310 This moves the processing of the events from the event-processor to a new email-event-processor in the email-service package. - The `EmailEventProcessor` only translates events from providerId/emailId to their known emailId, memberId and recipientId, and dispatches the corresponding events. - Since `EmailEventProcessor` runs in a separate worker thread, we can't listen for the dispatched events on the main thread. To accomplish this communication, the events dispatched from the `EmailEventProcessor` class are 'posted' via the postMessage method and redispatched on the main thread. - A new `EmailEventStorage` class reacts to the email events and stores it in the database. This code mostly corresponds to the (now deleted) subclass of the old `EmailEventProcessor` - Updating a members last_seen_at timestamp has moved to the lastSeenAtUpdater. - Email events no longer store `ObjectID` because these are not encodable across threads via postMessage - Includes new E2E tests that test the storage of all supported Mailgun events. Note that in these tests we run the processing on the main thread instead of on a separate thread (couldn't do this because stubbing is not possible across threads) There are some missing pieces that will get added in later PRs (this PR focuses on porting the existing functionality): - Handling temporary failures/bounces - Capturing the error messages of bounce events 2022-11-29 13:15:19 +03:00			`EmailBouncedEvent: require('./lib/EmailBouncedEvent'),`
			`EmailDeliveredEvent: require('./lib/EmailDeliveredEvent'),`
			`EmailOpenedEvent: require('./lib/EmailOpenedEvent'),`
Added storage for email failures (#15901) fixes https://github.com/TryGhost/Team/issues/2332 Saves events in the database and collects error information. Do note that we can emit the same events multiple times, and as a result out of order. That means we should correctly handle that a delivered event might be fired after a permanent failure. So a delivered event is ignored if the email is already marked as failed. Also delivered_at is reset to null when we receive a permanent failure. 2022-12-01 12:00:53 +03:00			`EmailUnsubscribedEvent: require('./lib/EmailUnsubscribedEvent'),`
			`EmailTemporaryBouncedEvent: require('./lib/EmailTemporaryBouncedEvent')`
Added @tryghost/email-events package refs https://github.com/TryGhost/Team/issues/2253 refs https://github.com/TryGhost/Team/issues/2254 This package is analogous to the @tryghost/member-events package. The events here will be consumed by the EmailSuppressionList implementation and used to add emails to said list. They'll be dispatched by the code which handles events received from Mailgun. 2022-11-24 09:54:20 +03:00			`};`