I know that this is technically not a Dovecot problem; however, I was wondering if anyone knew if 'sieve' had been updated with the ability to 'forward as attachment' a received document. I believe it has the ability to forward a document; however, I need the ability to forward it as an attachment if possible. Also I believe, somewhat due to my asking for them, that sieve exits with appropriate error codes. Is there a listing of these codes, other than in the actual program code itself, of what those exit codes are? -- Jerry ? Dovecot.user at seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Imagine me going around with a pot belly. It would mean political ruin. Adolf Hitler
On 2010-07-06 7:25 AM, Jerry wrote:> I know that this is technically not a Dovecot problem; however, I was > wondering if anyone knew if 'sieve' had been updated with the ability > to 'forward as attachment' a received document. I believe it has the > ability to forward a document; however, I need the ability to forward > it as an attachment if possible.I think you really mean can it do an Inline forward... *Documents* are not forwarded, *messages* are forwarded. If a message has an attachment, and is forwarded Inline, the attachments appear as directly attached to the forwarded message, otherwise the entire message is shown as an attachment, and you only see the attached document(s) in the attachment pane when you open the attached message. Dang, that was hard to word correctly, and it can still be improved a lot... -- Best regards, Charles
Jerry wrote:> I know that this is technically not a Dovecot problem; however, I was > wondering if anyone knew if 'sieve' had been updated with the ability > to 'forward as attachment' a received document. I believe it has the > ability to forward a document; however, I need the ability to forward > it as an attachment if possible. >There is an enclose extension: http://ietfreport.isoc.org/idref/rfc5703/#page-10 Unfortunately, it explicitly does not affect the redirect action. So you can only `enclose' messages that are stored locally. Still don't know why; no one on the Sieve list bothered to answer my question on this a few months back.> Also I believe, somewhat due to my asking for them, that sieve exits > with appropriate error codes. Is there a listing of these codes, other > than in the actual program code itself, of what those exit codes are? >I should include this in the man pages. Current exit codes are: 0 (EXIT_SUCCESS) All succeeded 1 (EXIT_FAILURE) Generic failure 64 (EX_USAGE) Invalid command line parameter Regards, Stephan
On Thu, 08 Jul 2010 00:21:42 +0200 Stephan Bosch <stephan at rename-it.nl> articulated:> I should include this in the man pages. Current exit codes are: > > 0 (EXIT_SUCCESS) All succeeded > 1 (EXIT_FAILURE) Generic failure > 64 (EX_USAGE) Invalid command line parameterThanks! -- Jerry ? Dovecot.user at seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ There is not opinion so absurd that some philosopher will not express it. Marcus Tullius Cicero, "Ad familiares"