Hello LinuxQuestions,

So far, this has been a great forum, and most of the solutions to my configuration problems have come from here, and I'm glad that I seldom (if ever) observe any trolling or n00b-bashing here

I am posting this thread because I am trouble even phrasing the question I have in a way that Google will understand that I'm not looking for a basic email server configuration tutorial, but rather a solution (if any) to a very specific configuration problem, so I will provide two examples: the first being the ideal outcome I expect to achieve, the second being the way things are actually working.

Ideally, I could have email forwarded from service@somewhere.net to user1@somewhere.net, user2@someplace.org, etc. Then, from Webmail or a Mail User Agent like Outlook or Thunderbird, user3 can actually send and receive mail from service@somewhere.net like a regular email account. Ideally, incomming messages are duplicated and forwarded to several recipients, but service@somewhere.net can still be accessed as a standard user mailbox.

Currently, after the forwarding process from service@somewhere.net to user1@somewhere.net and user2@someplace.org, user3 gets receives nothing from webmail or the MUA. In effect, service@somewhere.net seems to function exclusively as an alias used for forwarding emails to other recipients or as a standard email recipient, but not both.

Is there any graceful settings or well-known configurations for this type of functionality, or am I going to have to hack the server to pieces with work-arounds?

Set up service@somewhere as a regular mailbox and stick a .forward file in it's home sending copies to user1 & user2

Thank you for responding! Unfortunately, the standard/regular email users are ~all~ virtual (with the exception of the domain they're hosted under), so there isn't really a place for me to put a '.forward' that I can think of.

That said, the '.forward' would be the ideal solution for this problem if I were using local mailboxes instead of virtual mailboxes. At this time, I'm strongly reconsidering the validity of such an operation in the first place; it really doesn't make sense from a workflow perspective for several people to receive copies of messages delivered to a mailbox that only one person is authorized to send from. If non-authorized agents need the information, then perhaps the authorized agent should be responsible for delegation and not the email server.

Perhaps this would be some sort of per-mailbox-always-cc setting?