The Inbound Delivery Attempts and Outbound Delivery Attempts pages in the web interface (/admin/Management/x:Trace/InboundDelivery & /admin/Management/x:Trace/OutboundDelivery) both show the same e-mails. Only the date can vary by a few seconds between them.
Inbound Delivery Attempts should show only inbound e-mails. Outbound Delivery Attempts should show only outbound e-mails.
Actual Behavior
Inbound Delivery Attempts and Outbound Delivery Attempts both show inbound and outbound e-mails.
Stalwart Version
v0.16.7
Installation Method
Binary (Linux)
Database Backend
RocksDB
Blob Storage
Filesystem
Search Engine
Internal
Directory Backend
Internal
I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.
on
I have searched this support forum (open and closed topics) and confirm this is not a duplicate.
on
I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.
A locally-delivered message does pass through both the inbound ingest and an outbound “local” queue delivery, both logged under the same queue id, so for local-to-local mail showing up in both views can be expected rather than a duplicate.
To tell whether this is that overlap or a view that isn’t filtering: for a message that’s purely inbound-to-a-local-mailbox and one that’s relayed straight back out (no local mailbox), do the two views still show identical sets, or do they correctly diverge? And which Stalwart and web UI versions are you on? That’ll tell me whether the filters need fixing.
There are all external-to-local (or the other way around). No local-to-local.
Although the DMARC reports Stalwart sends itself automatically only show up as outbound.
Web UI is the current one. If the GitHub repo shows the newest one correctly, it should be version 1.0.4 (not sure where to find the version in the Web UI). Also still the same under Stalwart 0.16.9.
My previous reply was incomplete. It is normal and expected that a same message appears both on Inbound and Outbound delivery:
Inbound records when the message was accepted from either a remote host (via port 25) or by an authenticated client (via the submissions port). There should be just one record per received message there.
Outbound records each delivery attempt either to remote hosts or to the local store. There could be one or multiple records for each received message there as each record represents a delivery attempt.
You mentioned also that the records on each section are identical. Outbound records must start with Delivery attempt started while Inbound records with SMTP connection started. If that is not the case then there is something else going on.
