Mail Deliverability - Implement NDR processing

digibandit

Getting a few errors in my google workspace gmail inbox that we use for itFlow.

Unsure if this is a me-only issue or not.

wrongecho

Essentially all the mail queue does is submit messages to the SMTP server. We have no way of knowing if an address is invalid so just keep trying.

Is this a specific address / domain, etc? The NDR will usually spell the exact issue out.

digibandit

wrongecho I have ~9 varying examples but all fall under the Delivery incomplete/Address not found/Message not delivered categories.

Right now, I instruct a staff member to manually check our Gmail inbox once every few hours to ensure itFlow hasn't missed anything.

When Gmail sends an email and it doesn't work out we get a reply stating the failure, It would be awesome if this created an error or simply notified us in a meaningful and actionable way, like a ticket update.

wrongecho

In your other thread, you wrote

ITFlow sends emails. Gmail bounces them. The failures sit in our inbox waiting for manual checks. ITFlow knows it failed, we check manually anyway.

This isn't technically true.

We are aware if the message fails to transmit in the first place, but have no control beyond that.

The mailer notification the email wasn't delivered isn't instantaneous and would depend on the nature of the delivery error. Currently we have no way to parse these (inspiration).

I think there are two main tasks here:

Domain MX validation before sending
Incoming parser support for NDR / Bounce processing, notification/actions for everything else

wrongecho

Added the MX validation before sending to the new cron mail queue (itflow-org/itflow891f710 ).

I think parsing NDRs will be a lot more work..