Closed brenc closed 2 months ago
I'm not sure what I did but postmark and local SpamAssassin are both working now. This must've been on my end.
Mailpit will try to connect to the spamassassin server on startup, and in this case Mailpit is starting much faster than spamassassin so you're getting the warning. Despite the error however, it should not have prevented the integration from working once it was all loaded, so I assume you simply hadn't reloaded your browser after enabling spamassassin 🤷♂️
Either way, I'm glad it's working 👍
I'm setting up mailpit today (which is awesome) but I can't get SpamAssassin integration to work. First I set
MP_ENABLE_SPAMASSASSIN: postmark
and I can see the log line[spamassassin] enabled via postmark
but in the UI there is no Spam Analysis tab on my test emails. No logs of an attempt either when sending test emails with verbose logging on.Then I tried setting up the Docker container and using it locally. Here's my full compose file:
mailpit logs show:
It takes a few seconds for SpamAssassin to open the port. I can connect to it via the mailpit container using nc after it starts. It appears mailpit attempts to connect one time on startup (before the port opens up) then gives up. It doesn't attempt to use the local SpamAssassin instance again (or maybe I'm missing something obvious).
I'm sending test emails with bun script + nodemailer if that makes any difference.