Michelle -- ...and then M. Brownsworth said... % % Suppose a recipient wanted a message that had been marked as spam by % mistake, intercepted, and archived. Is there a way to deliver this % specific message to the recipient, preventing it from being
Almost certainly; anything is possible :-) % intercepted again? It would involve circumventing spamd's scanning Hmmm... On this I'm not so sure, though... % this message so that it can be redelivered to the user's local % mailbox. In some recent posts there has been talk of SA automatically (that is, in the default configuration) pasing over, whitelisting, or otherwise handling x-spama or x-beenthere headers. While I don't believe the latter gets injected by SA in a check pass, I think that the former does. Anything you hand off to sendmail, whether using /usr/bin/mail or anything else, will definitely go through your SA check because it has to be delivered (well, really, transferred by the MTA to hand off to the delivery agent MDA, procmail), so you'll want this sort of whitelisting in place. An alternative, I suppose, could be having SA or procmail or whatever add a header all your own (X-PrimeLogic-SpamTag or such) as it gets delivered to the archive system after interception, and then have your configs whitelist that. [Note that I'm not sure if there is a way to actually tell SA to pass something through other than setting the whitelist value to a sufficiently (ridiculously?) low number like -1000.] Another could be to have your recovery method, whatever that is, hand the mail directly to the user's procmail or mailbox so that you *do* bypass the transport step. HTH & HAND & have fun :-) :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
msg05864/pgp00000.pgp
Description: PGP signature
