Closed bcspragu closed 3 months ago
This is a configuration issue. Check your spam folder and if the message is not there set the logging level to trace
.
I can confirm my junk
mailbox is empty, I'll get some new logs at TRACE
There should be a log entry indicating that the message has been ingested. This entry includes the account id as well as the mailbox id where the message was stored.
Okay, here's the full TRACE logs from sending an email (with a few unrelated log messages):
I'm not sure what everything means, but the smoking gun might be:
2024-07-26T16:03:16.357671Z DEBUG jmap::email::ingest: Duplicate message skipped. context="email_ingest" event="skip" account_id=3 from=Some(List([Addr { name: None, address: Some("<THE EMAIL>")}])) message_id="17e5cec9198d11c2.479a492aa16b2b3a.5ddefc818e6a5acc@de4b5fe416b6"
Any ideas? Could it be that, because the message is already in the Sent
mailbox, it's being dropped and never hitting the Inbox
?
That warning means that there is already a message in your inbox with the same Message-Id
header.
Looking at the logic, the deduplication only seems to check for the Message-Id
behavior, not what mailbox it is in: https://github.com/stalwartlabs/mail-server/blob/ea77a982608d396f3990d53be000a11266542fdc/crates/jmap/src/email/ingest.rs#L152-L175
So I think what I said above holds true:
I don't know how other mail providers handle this, but self-email seems to be a common way people send notes to themselves, and it does work on other mail providers (e.g. Gmail). Not sure if the correct approach is to special-case self-email, or to move a duplicated email to the inbox if some conditions hold, or what, but I think this should affect any Stalwart deployment.
I have just changed the filter to include the target mailbox on the duplicate check.
What happened?
Sending an email from
me@example.com
tome@example.com
doesn't result in any messages in the Inbox. The message, like any sent message, is visible in theSent
folder.Email on the same local domain (e.g. from
a@example.com
tob@example.com
) work fine.How can we reproduce the problem?
I can reproduce the problem by doing the following steps:
I tried it in a few different clients (a web client and
aerc
), both using JMAP (i.e.EmailSubmission/set
) to send the requestVersion
v0.6.x or lower
What database are you using?
PostgreSQL
What blob storage are you using?
S3-compatible
Where is your directory located?
Internal
What operating system are you using?
Docker
Relevant log output
Logs are scrubbed to replace something like
me@example.com
with<email>@<domain>