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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: