Super-restrictive mail server implementation

zefflyn

Registered. User.
I need some ideas for implementing this uber-restrictive mailserver at my company.

Some background: CEO doesn't want to buy Exchange. We have basically 3 user groups: lusers, their team leads, and the technology group + executive staff.

The goal is: Execs don't want lusers to e-mail each other or anyone outside the company. Lusers can only e-mail people in the company who are not lusers. Lusers are also prohibited from receiving e-mail from anyone outside the company. Summary: lusers can only send mail to and receive from their leads or execs or techs.

The hitch is: non-lusers are on Google Apps. We have 3 GA domains, depending on which corporate identity the employee uses.

I'd like to build a Linux mailserver with Postfix, and have it prevent local delivery between users, and only relay to and from specified users at the two GA domains. But even something like a LAMP forum package, or RT would just about fit the bill, if the forums could be configured to prevent the lusers from reading each others' posts.
I looked at Zimbra, which is built on Postfix, and would work great if it could be configured restrictively.

Any tips? I'm reading Postfix documentation to see if its directives can do this. There's only 60 lusers and 35 non-lusers, so having to manually maintain access lists isn't a huge deal.
 

mercurial

Well-known member
Wow A fucked up, highly restricted email setup that uses a combination of unix daemons and google apps and will be totally unmaintainable in the long term when you have IT turnover.

Your CEO and execs sound like they are the lusers.
 
Last edited:

F4iChic

Kiss My Arse
It *never* ceases to amaze me what fucking stupid ideas CEO/CIO/CTO types come up with

*never*

:rolleyes
 

zefflyn

Registered. User.
Yep. It's amazing how full-of-themselves such podunk little executives can get.

Happily, it looks like they are considering buying Exchange licenses.
 

F4iChic

Kiss My Arse
my ex boss used to come up with some ridiculous ideas. Even after I explained to him the impact of his requests (having to undo/modify/nullify) data interfaces to support his wanting a particular web form to be up-datable, and that in a grand scheme of things we could address this "identity" issue as part of the larger "identity" project, he still insisted the web team waste time doing what he wanted. Great for them, they would take weeks to modify something really simple on the form, crap for me to undo the whole data/information flow...................

I now have no job because I didn't ask how high when he said jump :x

twit
 

/dev/null

taking a wrong turn
Seriously, come up with the most expensive solution you can to fit those criteria then watch them cancel the project due to excessive costs.
 
Top