Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: additional infos in "queue: delivered" logging #676

Open
1 of 2 tasks
lukastribus opened this issue Feb 8, 2024 · 1 comment
Open
1 of 2 tasks
Labels
new feature New feature.

Comments

@lukastribus
Copy link

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:

  • hostname (example: example-org.mail.protection.outlook.com)
  • body message id (example: s0dhgv0shgherhghwsgg@thunderbird.local)
  • MX answer (example: 250 OK id=w8eghw80ehg-BW)

Something like:

queue: delivered {"attempt":1,"msg_id":"a70cc095","body_msg_id":"s0dhgv0shgherhghwsgg@thunderbird.local","hostname":"example-org.mail.protection.outlook.com","answer":"250 OK id=w8eghw80ehg-BW","rcpt":"john@example.org"}
  • I'm willing to help with the implementation
  • I'm willing to test with the implementation

Sorry, I'm not a go developer.

Best regards,

Lukas

@lukastribus lukastribus added the new feature New feature. label Feb 8, 2024
@foxcpp
Copy link
Owner

foxcpp commented Feb 9, 2024

MX answer (example: 250 OK id=w8eghw80ehg-BW)

Related upstream issues and PR:
emersion/go-smtp#189
emersion/go-smtp#190

Once this is merged we will be able to add this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature New feature.
Projects
None yet
Development

No branches or pull requests

2 participants