Spam report program re-launch #59
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#59
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?
We should create easy to opt-in for users program as well as easy to process way of feeding spamassasin with spam and ham
Where will that be set?
Something we should decide. My two suggestions atm are:
The reason to make it opt-in is to give users choice whether they want to participate and give us their junk mail which by default we should not be touching without user's consent.
Personally I think going for the second option will make things a but more consistent and straight forward for the users but also for us after the initial work. We will need to write a script that will check for users that did decided to opt-in to the program and automatically pull their junk folders, feed it to amavis and remove them. However when the script is ready, the enitre process will be automatic and user can at any time decide to opt-out of the program without need for our intervention. Of course this solution needs some extra work eg. adding new attribute to ldap, make the script search for all users with the new attribute enabled etc. but majority of the script would be no different no matter which option we would choose. Form on the website I would use as a very secondary option in case we did not manage to make the script or for other reasons currently unknown for me.
If no objections, I will create a task for this and try to schedule the work on the script in my todo list. I think more priority should be put on roundcube at this moment, but perhaps this could be dealt with right after.
On last meeting with @meaz we've decided to go for autolearn. We just need to create flase positive email addresses so people could submit those in order to adjust filters.
The actual procedure is to be discussed during upcoming meeting.