|
Hi,
I have a system-wide rule which delivers all recognized spam addressed to all domains and recipients to one centralized spam folder (of an account created exclusively for this purpose) for temporary storage and teaching SpamAssassin’s bayes filter.
I’m considering changing my strategy to having a per-user spam folder instead. I’m thinking this could, at the very least, empower the users to actually receive these messages and manage possible false positives.
Does anyone have any experience or insights about the strengths and weaknesses of alternate handling strategies?
What would be the best way to implement this? Do I just need to make a ’Store In’ domain-wide rule for each domain instead of the single system-wide rule I have now?
--
Palvelin.fi Hostmaster
postmaster@palvelin.fi
|
|