Sieve does server sided filtering, so before the email ever hit the special user's inbox, it is moved to the special use shared folder. I've named the special user "shared" with password "shared" and user group 3. The email sent to the "shared" user needs to automatically be moved to the shared folder, so its available to everyone subscribed to the shared folder. I have [#Public] included in the subject line of the email, which sieve uses to filter and move the emails into the shared folder.

When I sent an email to the special user the sieve filter caught it and moved it into the shared folder of user shared, no problem, and the email was then available to everyone. Then I had another user reply to the email, and again it when to the "shared" user and showed up to everyone. Then I had a second user reply to the email, but it didn't show up to everyone; because, the from address, (e.g. reply address), had changed, so the reply went to another user other than "shared". The other user did not have a sieve script to move the email into the shared folder.

Now I am comtemplating whether to set up a sieve filter on ever user, so regardless of who received the reply, it would be available to all, or Perhaps it would be better to change the [Reply to] address of the Thunderbird cleint to [EMAIL PROTECTED], but then all replies would go the the shared folder and be available to all user, even when it was private email not intended to be shared.

I think I would need to set up a sieve filter with every user of the group to insure it worked like mailman, but it definite look like its possible to do this.

Regards,

LelandJ



Aleksander Kamenik wrote:
Leland F. Jackson, CPA wrote:
Thanks for the reply.  I'm not familiar with using a .forward file.

I'm going to try to set up a sieve filter to move mail coming into an inbox of a special user to the shared folders. I'll set up a special user with the shared folder that would receive all emails and replies on a thread. I'll have a flag in the subject header like [Dbmail Shared Folder 1], for example, that sieve can catch to move the email into the Shared Folder 1 of the speical user.

Why's the [Dbmail Shared Folder 1] part necessary if you're going to have a custom user for this anyway?



_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to