[Dovecot] OT: Sieve + Forward as Attachment
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@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 HitlerOn 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
On Tue, Jul 6, 2010 at 12:45, Charles Marcus CMarcus@media-brokers.com wrote:
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...
Seems like what he wants to do is effectively creating a new message which has as an attached document the triggering message.
On 2010-07-06 12:53 PM, Phil Howard wrote:
On Tue, Jul 6, 2010 at 12:45, Charles Marcus CMarcus@media-brokers.com wrote:
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...
Seems like what he wants to do is effectively creating a new message which has as an attached document the triggering message.
Maybe, but that's not how I read it... only the OP can clarify...
--
Best regards,
Charles
On Tue, 06 Jul 2010 12:55:04 -0400 Charles Marcus CMarcus@Media-Brokers.com articulated:
Maybe, but that's not how I read it... only the OP can clarify...
I thought it was clear; however, I guess not.
Now, I all ready know in advance that certain messages that I receive will need to be forwarded to other associates. The "forward as attachment" procedure is what I desire to accomplish. I believe this is covered in RFC-822 (RFC-822 MIME encoded attachment). Virtually every MUA that I have used has that as an option as well as normal 'forward' or 'redirect'.
I hope that clarifies mu question.
-- Jerry ✌ Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
What happens when you cut back the jungle? It recedes.
On Tue, Jul 6, 2010 at 13:11, Jerry dovecot.user@seibercom.net wrote:
On Tue, 06 Jul 2010 12:55:04 -0400 Charles Marcus CMarcus@Media-Brokers.com articulated:
Maybe, but that's not how I read it... only the OP can clarify...
I thought it was clear; however, I guess not.
Now, I all ready know in advance that certain messages that I receive will need to be forwarded to other associates. The "forward as attachment" procedure is what I desire to accomplish. I believe this is covered in RFC-822 (RFC-822 MIME encoded attachment). Virtually every MUA that I have used has that as an option as well as normal 'forward' or 'redirect'.
I hope that clarifies mu question.
I have seen mail clients migrate from true forwarding (but even so, it is a resubmitted message, so technically a new message), to creating a completely new message with the previous message as indented text, and later as an attached document. They may or may not carry over headers.
What you want to do is not a form of forwarding and I doubt Sieve would even have the permissions to do it (well, if it can do forwarding then maybe it can inject new mail, which would make me worry). The best I can suggest based on what I understand of this, is to use Sieve to isolate the messages to be acted on, place them in a special folder for that purpose, and have another process come along to pick them up and do the "foward with original as attachment" thing (many ways to do that, from a cron script on the server to a fetchmail script anywhere).
On 2010-07-06 1:19 PM, Phil Howard wrote:
I have seen mail clients migrate from true forwarding (but even so, it is a resubmitted message, so technically a new message), to creating a completely new message with the previous message as indented text,
This is called being forwarded 'inline'.
and later as an attached document.
This is called forwarding 'as an attachment'.
They may or may not carry over headers.
Inline forwarded message, depending on the client, will normally include either the 'Normal' or 'Short' headers, or the 'Full Headers', whichever is currently selected.
Outlook is a different beast (as usual)...
However, Messages forwarded as *attachments* *always* contain the full headers, which is why this is the preferred way to forward messages for forensic analysis.
What you want to do is not a form of forwarding
Forwarding 'as an attachment', which is what the OP said he wanted, is certainly a form of forwarding...
and I doubt Sieve would even have the permissions to do it (well, if it can do forwarding then maybe it can inject new mail, which would make me worry).
Not as long as it is done properly, This is how 'Vacation' messages using sieve works... although I am a total noob when it comes to sieve...
--
Best regards,
Charles
Jerry wrote:
On Tue, 06 Jul 2010 12:55:04 -0400 Charles Marcus CMarcus@Media-Brokers.com articulated:
Maybe, but that's not how I read it... only the OP can clarify... I thought it was clear; however, I guess not.
Now, I all ready know in advance that certain messages that I receive will need to be forwarded to other associates. The "forward as attachment" procedure is what I desire to accomplish. I believe this is covered in RFC-822 (RFC-822 MIME encoded attachment). Virtually every MUA that I have used has that as an option as well as normal 'forward' or 'redirect'.
I hope that clarifies mu question.
(Summarised version of my original reply.)
Perhaps you could make the Sieve program pipe the message into a (shell) program which encapsulates the message as an attachment to a new message which it then pipes into your local e-mail submission program.
Bill
On Tue, 06 Jul 2010 18:51:52 +0100 William Blunn bill+dovecot@blunn.org articulated:
Perhaps you could make the Sieve program pipe the message into a (shell) program which encapsulates the message as an attachment to a new message which it then pipes into your local e-mail submission program.
It might be easier to just write a new piece of code. Anyway, sieve does use a 'redirect' tag. Not really what I want, however, I might give it a try. I know that there was some talk of sieve employing a 'forward as attachment' scheme a while ago. Perhaps it just died.
-- Jerry ✌ Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
SYSTEM-INDEPENDENT: Works equally poorly on all systems.
Jerry wrote:
On Tue, 06 Jul 2010 18:51:52 +0100 William Blunn bill+dovecot@blunn.org articulated:
Perhaps you could make the Sieve program pipe the message into a (shell) program which encapsulates the message as an attachment to a new message which it then pipes into your local e-mail submission program.
It might be easier to just write a new piece of code. Anyway, sieve does use a 'redirect' tag. Not really what I want, however, I might give it a try. I know that there was some talk of sieve employing a 'forward as attachment' scheme a while ago. Perhaps it just died.
I'd rather write a self-contained one page shell program which interfaced by standard IO pipes and command-line arguments, than several pages of C code which had to integrate with an existing code base on its own application programming API interface which I'd first have to spend N days learning about.
Bill
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@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 parameter
Thanks!
-- Jerry ✌ Dovecot.user@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"
participants (5)
-
Charles Marcus
-
Jerry
-
Phil Howard
-
Stephan Bosch
-
William Blunn