> Basically we alias [email protected] to [email protected]. doveadm@ has a > sieve-Script which files into the public folder. You could also configure > a postfix transport which does the job.
Ah. OK. That may be more complexity than I need for my situation. So please bear with me as I try to understand this. IF: Postfix is already configured to deliver mail destined for the virtual domain "domain.com" to Dovecot --and-- I create the NAMESPACE and NAME setup as you described --and-- I create a Dovecot userdb entry for [email protected] (but no passdb entry) --and-- I configure ACLs so that all domain.com users can read NAME's mailbox but only admin users can delete messages in NAME's mailbox --and-- I configure the virtual INBOX for POP users to include "RealMails" and "NAME" THEN, I'm thinking that: Because there is no passdb entry, user [email protected] cannot log in --and-- Because userdb defines NAME's home directory, incoming mail to [email protected] would be delivered to the NAME mailbox, just like any other user in domain.com, without the need for aliasing or sieve --and-- Because of the ACLs, IMAP admin users would be able to delete/manage NAME's messages and everyone else would be able to read NAME's messages --and-- Because of the virtual INBOX, POP users would be able to read the NAME messages. Does that make sense? Am I missing something? > Its necessary to overlook the whole process chain to properly configure > everything. Yes! Agreed! That's why I'm trying to think through the whole thing before diving down a rabbit hole that leads to a dead end. > And a lot of try out :) For sure. (Just as soon as I understand what I'm trying to do.) ;-) Michael
