Peter Peltonen wrote:
I'm not in a spot to check the delivery schema. but is the message being passed through spamassassin and scored, just not passed through the mailfilter script? I seem to remember that you could delete the alias in the database and revert to the old style .qmail files - I know this USED to work a long time back, but I have not tried it on any of the newer versions (at least a year or more). Might be able to use a .qmail file for the alias and if it's being scanned pass it through mailfilter that way. Or you could be brave and try putting the mailfilter script in before the delivery in the DB. I'm not sure that will work - once again never tried it. I'll try and look some more at it this week, but I'm not promising anything. Seems like this would be a very nice feature (actually a fix) for the current versions.On 3/5/07, Jake Vickers <[EMAIL PROTECTED]> 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).The valias table looks likes this: | alias | domain | valias_line | peter.peltonen | example.com | /home/vpopmail/domains/example.com/peter/Maildir/ | So I guess it is using qmail-inject to deliver the message. Is there anything I can do about it?
smime.p7s
Description: S/MIME Cryptographic Signature
