dovecot - May 2020 - What causes mails to get striked-over only, and not deleted?

I have tried with this sieve config:

  imapsieve_mailbox1_name = Sent
  imapsieve_mailbox1_causes = COPY APPEND
  imapsieve_mailbox1_after = file:/etc/dovecot/sieve/sent.sieve

and this sieve file (sent.sieve):

discard;


This should clearly cause the mail to be deleted right?
But whats happen, is that the mail is not deleted, its just marked for
deletion (gets a strike-through in Microsoft Outlook).

(have tried with _before too, but it wont help).

What can I do to ensure the mail actually gets deleted (completely, not
moved to trash) and not just flagged for deletion?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: discard.png
Type: image/png
Size: 2579 bytes
Desc: not available
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20200523/c28e1abe/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5249 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20200523/c28e1abe/attachment.p7s>

On 5/22/20 4:01 PM, Sebastian Nielsen wrote:
> and this sieve file (sent.sieve):
> 
> discard;
> 
> This should clearly cause the mail to be deleted right?
> But whats happen, is that the mail is not deleted, its just marked for
> deletion (gets a strike-through in Microsoft Outlook).
That means the message has had its "\Deleted" flag set, which is what
the discard command does:

https://tools.ietf.org/html/rfc6785#section-3.5

But the mailbox has not been "expunged". You probably want to set
"imapsieve_expunge_discarded=yes"; see:

 https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/imapsieve.txt#L125


-- 
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/

Thanks.
That solved the problem.
Finally got rid of all duplicate items in sent folder. (Because of some mail
clients not supporting disabling "Save a copy in sent folder when
sending").

But why isn't this documented in the documentation?

https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve


-----Ursprungligt meddelande-----
Fr?n: dovecot-bounces at dovecot.org <dovecot-bounces at dovecot.org> F?r
Robert L Mathews
Skickat: den 23 maj 2020 01:43
Till: dovecot at dovecot.org
?mne: Re: What causes mails to get striked-over only, and not deleted?

On 5/22/20 4:01 PM, Sebastian Nielsen wrote:
> and this sieve file (sent.sieve):
> 
> discard;
> 
> This should clearly cause the mail to be deleted right?
> But whats happen, is that the mail is not deleted, its just marked for
> deletion (gets a strike-through in Microsoft Outlook).
That means the message has had its "\Deleted" flag set, which is what
the discard command does:

https://tools.ietf.org/html/rfc6785#section-3.5

But the mailbox has not been "expunged". You probably want to set
"imapsieve_expunge_discarded=yes"; see:

 https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/imapsieve.txt#L125


-- 
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5249 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20200523/f6009e33/attachment-0001.p7s>

On Sat, May 23, 2020 at 01:01:13AM +0200, Sebastian Nielsen
wrote:
> I have tried with this sieve config:
> 
>   imapsieve_mailbox1_name = Sent
>   imapsieve_mailbox1_causes = COPY APPEND
>   imapsieve_mailbox1_after = file:/etc/dovecot/sieve/sent.sieve
> 
> and this sieve file (sent.sieve):
> 
> discard;
> 
> 
> This should clearly cause the mail to be deleted right?
> But whats happen, is that the mail is not deleted, its just marked for
> deletion (gets a strike-through in Microsoft Outlook).
If it is a deliberate design decision, it's probably so that if you made 
a mistake you can undelete them again.

-- hendrik
> 
> (have tried with _before too, but it wont help).
> 
> What can I do to ensure the mail actually gets deleted (completely, not
> moved to trash) and not just flagged for deletion?
>