@ActorMike just like someone else suggested view raw source is available still but not under three dots button above message but above message list.
When it comes to trusted senders IMHO it might be related to return-path.
SMTP log on incoming gateway:
...
2023.06.28 11:21:24.202 [69.169.224.126][27770915] cmd: MAIL FROM:<01070189014eba02-e17d6307-9131-4e22-9386-02235475965d-000000@eu-central-1.amazonses.com>
2023.06.28 11:21:24.202 [69.169.224.126][27770915] senderEmail(1): 01070189014eba02-e17d6307-9131-4e22-9386-02235475965d-000000@eu-central-1.amazonses.com
2023.06.28 11:21:24.202 [69.169.224.126][27770915] rsp: 250 OK <01070189014eba02-e17d6307-9131-4e22-9386-02235475965d-000000@eu-central-1.amazonses.com> Sender ok
2023.06.28 11:21:24.202 [69.169.224.126][27770915] Sender accepted. Weight: 0. Block threshold: 90.
2023.06.28 11:21:24.233 [69.169.224.126][27770915] cmd: RCPT TO:<RECIPIENTEMAILWASHERE>
2023.06.28 11:21:24.342 [69.169.224.126][27770915] rsp: 250 OK <RECIPIENTEMAILWASHERE> Recipient ok
2023.06.28 11:21:24.373 [69.169.224.126][27770915] cmd: DATA
2023.06.28 11:21:24.373 [69.169.224.126][27770915] Performing PTR host name lookup for 69.169.224.126
2023.06.28 11:21:24.436 [69.169.224.126][27770915] PTR host name for 69.169.224.126 resolved as b224-126.smtp-out.eu-central-1.amazonses.com
2023.06.28 11:21:24.436 [69.169.224.126][27770915] rsp: 354 Start mail input; end with <CRLF>.<CRLF>
2023.06.28 11:21:24.482 [69.169.224.126][27770915] senderEmail(2): message@moje.zalando.pl parsed using: Zalando <message@moje.zalando.pl>
Delivery log on incoming gateway:
2023.06.28 11:21:52.453 [89968425] CMD: MAIL FROM:<01070189014eba02-e17d6307-9131-4e22-9386-02235475965d-000000@eu-central-1.amazonses.com> RET=HDRS ENVID=febcfc6e-a2af-4563-bbc3-657ac7576008 SIZE=102494
2023.06.28 11:21:52.484 [89968425] RSP: 250 OK <01070189014eba02-e17d6307-9131-4e22-9386-02235475965d-000000@eu-central-1.amazonses.com> Sender ok
Delivery log on primary server:
2023.06.28 11:21:52.362 [40553307] Delivery started for 01070189014eba02-e17d6307-9131-4e22-9386-02235475965d-000000@eu-central-1.amazonses.com at 11:21:52
2023.06.28 11:21:55.830 [40553307] Added to SpamCheckQueue (0 queued; 3/150 processing)
2023.06.28 11:21:55.830 [40553307] [SpamCheckQueue] Begin Processing.
2023.06.28 11:21:55.830 [40553307] Blocked Sender Checks started.
2023.06.28 11:21:55.830 [40553307] Blocked Sender Checks completed.
2023.06.28 11:21:55.830 [40553307] Spam Checks started.
2023.06.28 11:21:55.830 [40553307] Spam Checks skipped: Spam checks done by inbound gateway
2023.06.28 11:21:55.830 [40553307] Spam Checks completed.
2023.06.28 11:21:56.705 [40553307] Removed from SpamCheckQueue (1 queued or processing)
2023.06.28 11:21:59.674 [40553307] Added to LocalDeliveryQueue (0 queued; 2/150 processing)
2023.06.28 11:21:59.674 [40553307] [LocalDeliveryQueue] Begin Processing.
2023.06.28 11:21:59.690 [40553307] Starting local delivery to RECIPIENTEMAILWASHERE
2023.06.28 11:21:59.721 [40553307] Process delivery status notification step from local recipient success. Recipient: [RECIPIENTEMAILWASHERE], Notify: [failure], Delivered: [True], Forwarded: [False], Deleted: False
2023.06.28 11:21:59.721 [40553307] Delivery for 01070189014eba02-e17d6307-9131-4e22-9386-02235475965d-000000@eu-central-1.amazonses.com to RECIPIENTEMAILWASHERE has completed (Delivered to Junk Email) Filter: Spam (Weight: 33), Action (Global Level): MoveToFolder
2023.06.28 11:21:59.721 [40553307] End delivery to RECIPIENTEMAILWASHERE (MessageID: <01070189014eba02-e17d6307-9131-4e22-9386-02235475965d-000000@eu-central-1.amazonses.com>)
So as you can see email from return path is being used for verification (it looks that way) during checking process BUT when I go to junk mail in webmail and I'm opening this message it shows trusted sender (
message@moje.zalando.pl) info.