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

[enhancement]: Return Queue IDs during message acceptance #927

Open
1 task done
nomadturk opened this issue Nov 15, 2024 · 0 comments
Open
1 task done

[enhancement]: Return Queue IDs during message acceptance #927

nomadturk opened this issue Nov 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@nomadturk
Copy link

Which feature or improvement would you like to request?

I'd like to see this feature:

The current way Stalwart accepts an emails makes tracing impossible in times of debugging.
For example, when people are reporting missing emails that should have been delivered, knowing the queue id becomes important.
But if they can't.
Good luck...

The way currently Stalwart accepts emails is as follows.
250 2.0.0 Message queued for delivery.

Why doesn't it return the queue ID back to the sender?

Like Postfix:
250 2.0.0 Ok: queued as D863060BD9

or Google:
250 2.0.0 OK 1731389794 ffacd0b85a97d-381ed975a54si7856017f8f.119 - gsmtp

or others
250 2.0.0 OK ef6e1f86a16411ef8a5442010a7c0015

Also, ideally, with this enhancement:

  • The way the current message queue IDs are structured is not right for this as they seem to be sequential.
    So, the queue IDs should go through a change and be randomized instead of 208497278021809665

  • we should have the ability to search for emails with queue ID

Is your feature request related to a problem?

I'm having a problem with...

Code of Conduct

  • I agree to follow this project's Code of Conduct
@nomadturk nomadturk added the enhancement New feature or request label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant