You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like the possibility to "proof" that a remote MX has accepted the email, by logging body message ID, hostname as well as exact response.
Note alternatives you considered and why they are not useful.
Enabling debug mode allows some correlation between a hostname and the mail delivery, however it is missing body message ID and MX response, and the hostname is only a guess based on timestamp correlation.
Your idea for a solution
How your solution would work in general?
To the "queue: delivered" log I would suggest to add:
Hello,
I'm using maddy since a few days, I read about it on the healthchecks.io blog re it's email setup, I like it.
Thank you for this!
Use case
What problem you are trying to solve?
I'd like the possibility to "proof" that a remote MX has accepted the email, by logging body message ID, hostname as well as exact response.
Note alternatives you considered and why they are not useful.
Enabling debug mode allows some correlation between a hostname and the mail delivery, however it is missing body message ID and MX response, and the hostname is only a guess based on timestamp correlation.
Your idea for a solution
How your solution would work in general?
To the "queue: delivered" log I would suggest to add:
example-org.mail.protection.outlook.com
)[email protected]
)250 OK id=w8eghw80ehg-BW
)Something like:
Sorry, I'm not a go developer.
Best regards,
Lukas
The text was updated successfully, but these errors were encountered: