Steffen Kaiser <skdovecot@smail.inf.fh-brs.de> writes:

On Fri, 12 Feb 2010, Kamil Jońca wrote:

...

Is any posibility to pass parameters/environment variables to deliver with sieve plugin?

No. But you could check the "extdata" extension posted by Stephan Bosch lately.

But, if I understand, this plugin can store only global parameters, not 'per message'?

KJ

-- http://blogdebart.pl/2009/12/22/mamy-chorych-dzieci/ Uwolnić słonia !!!

Timo Sirainen <tss@iki.fi> wrote:

On Fri, 2010-02-12 at 14:42 +0100, Kamil Jońca wrote:

...

Is any posibility to pass parameters/environment variables to deliver with sieve plugin?

I have some procmail rules to decide where mail should go, which can't be migrated to sieve (uses external programs). So far I write it to maildirs, but I wonder to migrate to mdbox, and procmail can't handle it. Any ideas?

If you've gone that far, how about just calling deliver from procmail like:

deliver -m your_mailbox_name

(With Sieve that actually only specifies the default mailbox, which is used only if Sieve doesn't decide to save it elsewhere.)

Slightly extended approach may make procmail script generate some extra headers (based on external programs) before executing deliver so sieve can consider "extra data".

-- [pl>en: Andrew] Andrzej Adam Filip : anfi@onet.eu It has long been an axiom of mine that the little things are infinitely the most important. -- Sir Arthur Conan Doyle, "A Case of Identity"

On Sat, 2010-02-20 at 11:55 +0100, Kamil Jońca wrote:

...

deliver -m your_mailbox_name

(With Sieve that actually only specifies the default mailbox, which is used only if Sieve doesn't decide to save it elsewhere.)

Yes, I know about this switch. Maybe I should tourned off sieve (So switch works unconditionally) and rewrite all my destinations like deliver -m <mbox>

Well, another possibility:

deliver -a user+your_mailbox_name@domain.org

Then in the Sieve script check :detail.