The Inbound list (x:Trace/InboundDelivery) is every SMTP session that reached MAIL FROM, so mail a user submits over 587/465 shows up there. The Outbound list (x:Trace/OutboundDelivery) is every delivery.attempt-start, and local delivery goes through the queue too, so mail received for local mailboxes shows up there.
Plan: work out a trace's kind from its stored events when the list is queried (an authenticated SMTP session is a submission; a delivery attempt that only delivered locally is local), so existing history is covered without a migration. The two lists leave those out by default, with a filter to bring them back.
Also: no trace event records the spam score or the rules a message hit, so the trace detail page can't show why a message was scored the way it was. Add one Info-level event in the inbound session with the score and the tags.
Reported on the forum: https://community.coffeylabs.org/t/inbound-outbound-delivery-not-properly-scoped/282
The Inbound list (`x:Trace/InboundDelivery`) is every SMTP session that reached MAIL FROM, so mail a user submits over 587/465 shows up there. The Outbound list (`x:Trace/OutboundDelivery`) is every `delivery.attempt-start`, and local delivery goes through the queue too, so mail received for local mailboxes shows up there.
Plan: work out a trace's kind from its stored events when the list is queried (an authenticated SMTP session is a submission; a delivery attempt that only delivered locally is local), so existing history is covered without a migration. The two lists leave those out by default, with a filter to bring them back.
Also: no trace event records the spam score or the rules a message hit, so the trace detail page can't show why a message was scored the way it was. Add one Info-level event in the inbound session with the score and the tags.
Fixed in #398, with inbuxa/inbuxa-admin#208 for the console filter. Thanks to Faisal for reporting it on the forum. Inbound now defaults to mail from other servers and Outbound to deliveries to other servers, each with a Show filter for the other kind or both; older history is sorted too. Received messages also get a spam.result event listing the verdict, score and rules hit, highest first. It will be in the next release.
Fixed in #398, with inbuxa/inbuxa-admin#208 for the console filter. Thanks to Faisal for reporting it on the forum. Inbound now defaults to mail from other servers and Outbound to deliveries to other servers, each with a Show filter for the other kind or both; older history is sorted too. Received messages also get a spam.result event listing the verdict, score and rules hit, highest first. It will be in the next release.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Reported on the forum: https://community.coffeylabs.org/t/inbound-outbound-delivery-not-properly-scoped/282
The Inbound list (
x:Trace/InboundDelivery) is every SMTP session that reached MAIL FROM, so mail a user submits over 587/465 shows up there. The Outbound list (x:Trace/OutboundDelivery) is everydelivery.attempt-start, and local delivery goes through the queue too, so mail received for local mailboxes shows up there.Plan: work out a trace's kind from its stored events when the list is queried (an authenticated SMTP session is a submission; a delivery attempt that only delivered locally is local), so existing history is covered without a migration. The two lists leave those out by default, with a filter to bring them back.
Also: no trace event records the spam score or the rules a message hit, so the trace detail page can't show why a message was scored the way it was. Add one Info-level event in the inbound session with the score and the tags.
Fixed in #398, with inbuxa/inbuxa-admin#208 for the console filter. Thanks to Faisal for reporting it on the forum. Inbound now defaults to mail from other servers and Outbound to deliveries to other servers, each with a Show filter for the other kind or both; older history is sorted too. Received messages also get a spam.result event listing the verdict, score and rules hit, highest first. It will be in the next release.