[Top] [All Lists]

[sieve] On "reject" and :fcc

2017-01-17 16:17:44
I wasn't on the list until just now, but it's one of my users who requested 
:fcc or similar.

A vendor that uses Cyrus IMAP has some customers that would like to have
copies of outgoing Sieve-generated messages (e.g. reject, vacation)
stored in their Sent mailbox.  We could obviously do this with a user
configurable option, but I was thinking of extending Sieve to support a
:fcc <mailbox> option on reject, vacation and any new actions where it
might apply.  The option could also leverage
draft-bosch-sieve-special-use to do something like :fcc "\\Sent"

I see no problem for notify or vacation, but there's a serious semantics issue
with reject - when you reject a message you are saying, "I didn't receive" 
message". If you implement an action where you do in fact receive the message,
albeit as a part of a DSN, you're essentially lying about what you did.

Accurate information about who actually received what is especially important
in environments with compliance archiving requirements. I don't look forward 
explaining how a reject ended up being a keep.


So don't lie if you don't want to lie.  I see things the other way around, if 
you want to
reject something then you want to reject it, but you might also want to keep a 
of every email that's been sent out of the system on your behalf.

If your environment has compliance archiving requirements, then don't let users 
that.  If you're not allowed to keep copies of reject emails, then don't keep a 
copy of

It's quite possible to set up an environment where every email going out of the 
gets archived completely independent of the sieve engine, in which case you'd 
still be keeping
copies of outbound rejects.  Not even allowing this in sieve doesn't change the 
fact that people
might want to lie and not everybody has compliance archiving requirements.


  Bron Gondwana

sieve mailing list

<Prev in Thread] Current Thread [Next in Thread>