Peter Peltonen wrote:
Yeah, there's a break in there. The message comes in, hits the forward (which does no scanning) and then gets locally delivered (inject) to the account. I think when it used to be .qmail files you could tee in the mailfilter script, but I have not tried to do so since it changed to using the database method. Maybe look at the structure of the forward table and see how it's actually sending the message (is it using qmail-inject or a .qmail style forward).On 3/2/07, Jake Vickers <[EMAIL PROTECTED]> wrote:I haven't been keeping an eye on the thread, so can you detail what the issue was again?My issue was: I have built my toaster with --define 'spambox 1. Spam sent to an account that has "Spam Detection?" enabled in qmailadmin is handled correctly and moved to the Spam subfolder. But it does not seem to work with forwards: Say I have email account "peter" that has spam detection enabled, and then a forward named "peter.peltonen" which mail is delivered to "peter" account. All spam sent to "peter.peltonen" is delivered to INBOX and not moved to the spam subfolder. I tested this with the GTUBE test spam message you get withspamassassin -D < /usr/share/doc/spamassassin-toaster-3.1.7/sample-spam.txtIs there a way to fix this so that also forwarded email that is recognised as spam will end up to the spambox?
smime.p7s
Description: S/MIME Cryptographic Signature
