Cloudron Forum

@d19dotca both the statements are orthogonal. Cloudron can provide feature to tackle spam and make it more accessible for all users. At the same time, Cloudron can also not expose implementation details like SpamAssassin configs. In fact, there are newer solutions out there like say rspamd which even help with integrating email with LLM. But because Cloudron exposed SA we are now "stuck" and possibly have to break support at some point. We have always taken this approach to our product, so it's not anything new. We don't expose docker configs, haraka configs, dovecot configs, nginx configs etc. It's not how we do things. The SpamAssasin config was done only because an immediate problem had to be fixed and was done in haste.

whitelist will be supported in coming release. There is no plan to expose spamassasin configs and specific variables though. In some future, we want to move away from SA (unlikely but this should remain an implementation detail).

@imc67 So were we using the same rules from @d19dotca ? For now I removed from all istances, but in future I want to keep only rules who works in local, not requiring any outbound connection.

@james Yes, this is a great find. Thanks a lot for your cooperation. In email service’s logs no any log... Whenever you want, I can reproduce issue and I can send you raw log. Keep me posted.

Fixed in support. Not clear what the issue is, but it could be possibly because spamcop dnsbl was not responding. I removed it from the mail acl - https://docs.cloudron.io/email/#dnsbl.

You should see a summary in the email header just after the X-Spam-Status one, which explains how it came to this (ham) score. This should looks something like this, with different scores of course: X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no * trust * [87.253.236.95 listed in list.dnswl.org] * 0.0 HTML_MESSAGE BODY: HTML included in message

@james Yes it’s technically a feature request. I only threw it in here since it seemed like Girish was already making adjustments to the filtering in the mail event log viewer. If you’re okay forking it to a feature request, that’s totally fine.

@girish Oh that is interesting, I didn’t realize we could customize the DNS server. This is helpful. Thanks so much!

there are also some posts from @d19dotca a while back about fine tuning spam rules

Hello @iamthefij Did this ever get resolved? Did you get access to the mail-addon repo? Is assistance still required?

Yes they are added via the custom spam filtering. I have to check with the client as to whether they are going to inbox or junk folder, they might be expecting them to be blocked outright. Also some spam has the key words as sender name, rather than in the subject... Not sure how to classify that.

Thanks - that sounds interesting. Didn't know that - but this is a reason to rethink my approach.

@Kubernetes lol, thanks, thats both useful, and a laugh at myself, at my new level of stupidity unlocked.

3 1/2 years ago? Sorry, no I don’t even remember what I had for dinner yesterday….

Not 100% sure but are there any files under /home/yellowtent/boxdata/mail/spamd/<mailboxname> ? Those are the per mailbox spamassassin bayes databases. Maybe it's picking up something from there?

@necrevistonnezr I was looking in the forum Thank you!

@girish Yes I definitely do use mailing lists, sorry I thought I noted that before. Many (though I don’t think all) of the email directories that are unexpectedly found in this directory are from mailing list addresses. In other words they are on the recipient list of a mailing list. So it’s as if the mailing list feature is creating these too, but it doesn’t make sense of course to have one on the forwarding addresses. The mailing list email I could see and understand I guess since it’s still trying to identify spam to not forward, but I don’t get why it’s adding the destination addresses in as if they’re mailboxes that it can learn from. I can’t reproduce on-demand that I’ve seen so far but just giving it time for a day or two and they’ll start to appear. I guess sending an email to the mailing list would trigger it, I can try that too next time I’m at my computer again.