Re: Multidrop retrievers: run filter before sorting ?

Bigaunti - Arcor <[email protected]> wrote:
> thank you for responding so quickly.

You're welcome.

However, you're still comitting the error that I linked to - you have a
problem, and have picked a solution to that problem, and you are now asking
for help implementing that solution.  You have not actually described the
*problem itself*.  So I'm (or we're) left groping in the dark trying to figure
out why you're trying to implement X.

The point of the article I linked to (and it links to other explanations of
the same, including one I wrote) is *describe the actual problem* first.  You
can mention your proposed solution, but you need to account for the fact that
the right solution to your problem may not be - and if you're asking for help,
probably will not be - the one you're proposing.

I used to try to guess what the actual problem was when people did this.  I
gave up; it's frustrating and wastes a *lot* of time.

> > > So I composed some shell script to sort things out.  Which adds such
> > > header like "X-Original-To:".  So not removing anything, just adding.
> >
> > So... what does it put in the new X-Original-To: field?  You just said the
> > envelope recipient is not recorded, so what can the script be doing to
> > recreate it?
> 
> That filter does in the end also just guess who most probably is the
> original/envelop recipient - then adds a "X-Original-To:" header containing
> that guessed recipient.

You failed to answer my question, so I'm still not going to provide what I
think is probably the answer.  Please do answer it, so I can help you!
To be very clear:

Please tell us *exactly* what information you are extracting from the message
in your shell script - are you looking at MIME body parts, or plaintext, or
information in the message header?  If the header, *exactly* what header
fields are you extracting it from and what processing (if any) are you doing
to it before you create a new X-Original-To: field and populate it with that
data.

> What I would like Getmail to do: get the email from the provider, run my
> filter, then run the MultidropRetriever using the filter output

As I said above, this is almost certainly the wrong solution to your problem.

> (instead of the original email) to determine the value for the argument
> %(recipient) in the destinations section.

This is a huge red flag.

Charles
-- 
-----------------------------------------------------------------------
Charles Cazabon
GPL'ed software available at:               http://pyropus.ca/software/
-----------------------------------------------------------------------