At 04:40 PM 3/3/2005 -0500, Andy Schmidt wrote: >I generally agree that the new function is desirable. Now we just need to >figure out how to implement it "robustly". > >E.g., when Declude modifies the "envelope" to the new "route-to" address, it >may have to "remember" that new recipient so that it can reference it in >case it later encounters a DELETE action. > >Or, to reverse that logic, let the ROUTETO remember the "new" recipient - >but don't actually update the envelope until Spam processing for that user >is complete.
The problem is the COPYALL account as it will always be HELD rather than have SPAM deleted as it always fails enough HOLD actions prior to DELETE weight. And as the COPYALL isn't a "real" part of the "envelope" it most likely causes more problems since it is added somewhere in IMAIL as a seperate addressee. [This E-mail scanned for viruses by F-Prot] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
