On Thu, Nov 20, 2008 at 1:23 PM, Sean <[EMAIL PROTECTED]> wrote:

> I'm still struggling with the overall concepts behind the SpoolManager.
>
> 1) What happens when a message finishes a processor, but never gets
> Ghosted?


I think it just "falls off" and is deleted.  I've seen log messages that say
something to this effect.


>
>
> 2) If a message encounters a ToProcessor, does it get copied and put
> on the new processor, or is its life in the parent processor ended?


It just goes to that processor, it that processor handles it, then it
"ends", if it goes through the entire processor, then it go back to the
parent where the parent left off.  I think.


>
>
> 3) Why don't Resend and Redirect make you choose which processor to
> put the new message onto.  The way I see it, an infinite loop can only
> be avoided by mangling the message-body (I've tried using the fact
> that AbstractRedirection sets the remote addr to 127.0.0.1, and
> changing the 'recipients'); I must be misunderstanding some general
> concept.
>
> 4) How do I combine matchers?  (eg, AND, OR, NOT, XOR, ...)


I don't think you can...?  Wish I knew if you could!


>
>
> 5) Are the 'recipients' separate from the contents of the To: header?


Yes, there's the envelope and the message (imagine a business letter, the
envelope is From Google, To Microsoft, but the actual letter is addressed
>From Eric and To Steve).  There can be multiple envelope recipients, but
only 1 sender.  The envelope sender is where a message is bounced to.
  • Semantics Sean
    • Re: Semantics Richard Levasseur

Reply via email to