I'm the one that has been trying to get answers as to why the
infamous .Spam box gets created when I send the sample spam text to a
user with spam detection enabled. Thanks to those who tried to help out.
In the end, I had to just keep reading on my own, and reverse
engineering Qmailtoaster in order to gain a better understanding of how
it all fits together. I've learned that Simscan rejects spam before it
ever reaches the Qmail queue for processing. My user's .Spam box never
gets created because the mailfilter script doesn't get called unless
Simscan passes it through. So the point of the infamous "spambox"
is...what, exactly?
I.e., Qmailtoaster is working exactly as it was intended after all.
But, while I can see the advantage of having multiple spam filters, if
users--or System Administrators new to Simscan--want proof that it's not
rejecting valid email, the Spam box functionality should work at the
door, shouldn't it? Otherwise, the multiple tutorials on "how to create
spam folders so users can double-check that nothing useful is being
thrown away" seems like a false sense of security.
Am I wrong about any of this?
-John B.
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
