[EMAIL]: excessive false positive spam detection #409
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#409
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In the past 2-3~ weeks I've noticed that mails from various mailing lists are excessively getting flagged as spam. I've forwarded them to
ham.report@disroot.org
but it doesn't seem to have any effect.Is there anyway to reduce the false positives. Being able to disable automatic spam detection at a profile/account level would be something I'd be interested in as well (I'd rather just delete spam mails myself, as I get very few).
(Appologies if this isn't the right place to report such issues)
Hi,
Thanks for the report. I will be looking into it.
Just to illustrate the ridiculousness of the situation, my own mail that I sent to a mailing list got marked as spam:
Would really appreciate if something can be done about this soon (preferably, I'd just like to disable the spam filter entirely for my account). Thanks!
I understand. It's on my todo list for upcomming week.
I did some research and looks like the issue is affecting mainly mailinglists due to DMARC where mailing list server modifies headers causing the dmarc to fail. If domain has set policy to "reject" which is pretty much most of the public providers (thanks spammers), email should be rejected. We instead of rejecting, give it a higher spam score which results in those email landing in the Junk folder.
I tried to figure out whether this is fixed on mailing list software side and looks like Mailman did some fixes few years back so if list owners updated it should work. I am not sure though if it only applied to DMARC policy "quarantine" though.
So more investigation needs to be done here to verify if the issue is and will persist because of how mailing lists work or if there is something on our end we could do.
One way foward would be of course to somehow make allowlist for most of mailinglists we see passing through the server, but thats of course not ideal as it means we woul have to fish for those smaller ones.
https://lists.debian.org/debian-user/2021/07/msg00449.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752084
https://lists.gnu.org/archive/html/mailman/2017-08/msg00006.html
https://lists.gnu.org/archive/html/help-gnu-emacs/2019-03/msg00007.html
https://lists.gnu.org/archive/html/savannah-hackers-public/2019-06/msg00018.html
I agree that this is more of a temporary hack/workaround than an actual solution. But as of now, I'm having cases where almost every single mail from a mailing list is ending up on the junk folder.
I also noticed that there has been no response regarding being able to disable spam filter on an account basis. Is there any technical (or design/philosophical) reason as to why that cannot be done?
Thanks.
@NRK could you pm me the list of mailinglists (eg. to support@disroot.org or my personal).
As for your other question. ATM spam filtering is set globally for all,there is no possibility to switch it off based on user's preferences.
Done.
Unfortunate - but thanks for answering the question.