[Dovecot] set \Seen flag on mail
I'm looking for a way to set the \Seen flag on certain mail no matter what. Currently I'm using a global sieve script to do this. From what I've read, there is no way to enforce the global script if the user creates their own sieve script.
More details:
I have a postfix transport that along with sender_bcc_maps and recipient_bcc_maps uses deliver to create a read only archive of user's mail. The mail intended to be archived is stored in a per user imap folder called "Archives" that uses the ACL plugin to make the messages there read only. In addition to that, I want the mail marked as \Seen upon delivery so that user's who subscribe to the Arhives folder don't see new mail indications and what not when mail is delivered there.
Is there a better way to set the \Seen flag other than the global sieve script since it can be overridden by the user?
-- J.P. Trosclair
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
On 2009-03-04 10:53, J.P. Trosclair wrote: | Is there a better way to set the \Seen flag other than the global sieve | script since it can be overridden by the user?
One idea: You could use the Sieve include extension to include the global script in the user's default sieve script. You can then check periodically (with a cron script that contains a few 'grep' calls) that all users' sieve scripts still include the include statement and if not, inform them why they better should leave the include statement in their sieve script.
Patrick.
STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779
PGP key: E883A005 https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkmuX1wACgkQ7yMg/OiDoAWDEACfe33hmBXDN2UxPiqH8Kkogd9H v0cAnjHUwDG6CioG5a3EtUEsjUjkhiwf =Gqdt -----END PGP SIGNATURE-----
J.P. Trosclair schreef:
I'm looking for a way to set the \Seen flag on certain mail no matter what. Currently I'm using a global sieve script to do this. From what I've read, there is no way to enforce the global script if the user creates their own sieve script.
More details:
I have a postfix transport that along with sender_bcc_maps and recipient_bcc_maps uses deliver to create a read only archive of user's mail. The mail intended to be archived is stored in a per user imap folder called "Archives" that uses the ACL plugin to make the messages there read only. In addition to that, I want the mail marked as \Seen upon delivery so that user's who subscribe to the Arhives folder don't see new mail indications and what not when mail is delivered there.
Is there a better way to set the \Seen flag other than the global sieve script since it can be overridden by the user?
Since you can separate delivery at the MTA level with *_bcc_maps, you could also make sure that the archive copy of e-mails doesn't touch delivery settings of your regular user, but uses a separate archive user.
-- Regards, Tom
J.P. Trosclair wrote:
I'm looking for a way to set the \Seen flag on certain mail no matter what. Currently I'm using a global sieve script to do this. From what I've read, there is no way to enforce the global script if the user creates their own sieve script.
More details:
I have a postfix transport that along with sender_bcc_maps and recipient_bcc_maps uses deliver to create a read only archive of user's mail. The mail intended to be archived is stored in a per user imap folder called "Archives" that uses the ACL plugin to make the messages there read only. In addition to that, I want the mail marked as \Seen upon delivery so that user's who subscribe to the Arhives folder don't see new mail indications and what not when mail is delivered there.
Is there a better way to set the \Seen flag other than the global sieve script since it can be overridden by the user?
The new Sieve implementation for Dovecot v1.2 has support for the multiscript feature which enables you to execute multiple scripts sequentially, meaning that you can force a specific script to execute before whatever the user has uploaded.
Read the INSTALL file for a concise explanation:
http://hg.rename-it.nl/dovecot-libsieve/file/tip/INSTALL
Read the original internet draft for more detailed information:
http://ietfreport.isoc.org/all-ids/draft-degener-sieve-multiscript-00.txt
Regards,
Stephan.
participants (4)
-
J.P. Trosclair
-
Patrick Nagel
-
Stephan Bosch
-
Tom Hendrikx