1

I'm sure I'm overlooking something as this should be routine... But I'm wondering how admins are setting up generic accounts like "support@domain.com" & "info@domain.com"? With OS X Server you can create aliases in a user's mail account and those messages will automatically be forwarded to said user... But I want a separate IMAP (or POP) acct that could be monitored by multiple clients. Do I really need to create a full user in our system & Open Directory for each of these accounts when all we need is email only?

Meltemi
  • 589

3 Answers3

2

We have these setup as aliases for mailing lists, so for example support@domain.com is an alias for support@lists.domain.com. This means that user accounts can be added to/removed from the list as necessary.

theotherreceive
  • 8,445
1

A ticketing system might be the answer if you need to make sure that each question to your generic aliases is answered, and answered by only one person (as you suggest in your comments). Most decent ticketing systems have multiple queues and can attach different email addresses to that different queues; you can then give your employees/users access to and notifications from the relevant queues.

There are a few ServerFault questions about good ticketing systems: ticketing for support types and ticketing for non-developers.

We use OTRS for this purpose.

Community
  • 1
Zanchey
  • 3,051
0

I know the question is old, but a tool has launched not too long ago to do exactly that: https://frontapp.com

You can add any "role based" shared inbox, with its own IMAP account, and have it checked by many users in your team.

Cystack
  • 103