You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which feature or improvement would you like to request?
In JMAP specification an email can exists in multiple mailbox simultaneously (see mailBoxIds). This is useful to mimic Gmail's tag or label by using folders.
Ideally, I can sort an email in multiple folder via sieve script by using multiple fileinto clauses, but then I have copies of the mail, so deleting the mail from one folder leaves it in the other folder.
I wonder if it would be possible to add an extension to fileinto called :link so instead of copying the mail, it changes its mailboxid property to include both mailbox's id (one for each folder). That way, deleting the mail in whatever folder will actually delete it since it only exists once.
Is your feature request related to a problem?
Not able to have a unique mail appears at multiple place in the inbox hierarchy.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Which feature or improvement would you like to request?
In JMAP specification an email can exists in multiple mailbox simultaneously (see mailBoxIds). This is useful to mimic Gmail's tag or label by using folders.
Ideally, I can sort an email in multiple folder via sieve script by using multiple
fileinto
clauses, but then I have copies of the mail, so deleting the mail from one folder leaves it in the other folder.I wonder if it would be possible to add an extension to fileinto called
:link
so instead of copying the mail, it changes its mailboxid property to include both mailbox's id (one for each folder). That way, deleting the mail in whatever folder will actually delete it since it only exists once.Is your feature request related to a problem?
Not able to have a unique mail appears at multiple place in the inbox hierarchy.
Code of Conduct
The text was updated successfully, but these errors were encountered: