On 20 May 2019, at 01:42, Brent Clark <brentgclarkl...@gmail.com> wrote: > My colleague has proposed that at smtp time, if a mail is deemed as spam, the > server issues a reject code, but then to too accept the mail and forward the > mail the user for incase its a false positive.
The odds of a mail scoring over 10.0 on SpamAssassin being legit are so low as to be meaningless, so that's a silly reason to implement a completely non-standard email chain that is likely to only anger your users with even more spam to sort through. > His logic is that, that the spammer does not build up a database. The days of that are long past. Spammers simply buy lists of billions of emails. They do not care about delivery at all. > Currently what we do is, if the score is between 5 and 15, just accept and > move the spam to the users SPAM box. Above 15 we out right block. I'd say 15 is far too high and including that much spam probably trains your users to never even bother looking at the spam folder, but that's fine. > I am on the fence on this one, hence the reason to pick the communities brain. I would never do this. My rule is very simple, anything we accept gets delivered to the user. Anything we reject gets rejected during the SMTP transaction. If it is LEGITIMATE mail, the sender will see the rejection. -- And east is east and west is west and if you take cranberries and stew them like applesauce they taste much more like prunes than rhubarb does.
