0

My company is setting up a partner company. Some work may be subcontracted from one company to another. In these cases it would be useful to be able to share email domains, disk storage and so on.

I'm not sure how one would set up email address sharing across two different companies.

I'm also not sure on the best strategy to share common disk storage between two physically seperate companies (one will be in the UK and one in ths US)

3 Answers 3

1

W/o knowng the nature of your business, the length of the engagement, and the specific relationship between the partner Firms it's really difficult to make any specific recommendations for your questions. Personally, I'd err on the side of keeping everything at "arm's length". As a partner in such a venture, I'd want to be sure that my other business concerns weren't getting mixed up in this project, and I'd want to see the same for the other partner(s) involved.

Depending on the need for "realtime" collaboration, I'd consider keeping all the data in some "cloud" solution. I'd either contract with a hosting provider for data file storage, revision control, etc, or put up servers specifically for that purpose (ones that aren't used for my "regular" business). Something simple like a wiki engine might be all you need, or you could look at something that integrates a revision control system (Subversion, etc). I'd want to work out a protocol with the partners about who performs IT administration duties for this hosting solution (performing backups, controlling access, monitoring availability, etc).

re: sharing an SMTP address space: If you're concerned about "leaking" out the email addresses of the partner companeis (instead of the shared "unified" domain name) then you'll probably want to keep the email out of the affected users' "regular" email at each company. It's a pain for the users, but having to use a different email client / webmail / etc, versus something like "Remember to change your From: address when replying to Customer xxx..." is likely going to be problematic. If your MTA is smart enough to support selective mangling of the "From:" address depending on the recipients specified in a message you might get away w/o this.

I'd consider contracting email delivery for the shared domain name out to a third-party MTA. Have that third-party deliver incoming messages to the appropriate SMTP addresses at each partner company (in their own SMTP address spaces) if you want to intermingle the shared domain email with each partner company's regular email, or have them host web-based email for the partner company addresses (to keep it separate from each partner's "regular" email).

Like I said, it's hard to make many specific recommendations. Hopefully there are some ideas there that are helpful to you.

1

You didn't mention what mail solution you are using. If you're using Microsoft Exchange, I'd recommend:

  • Assigning users different domain names, but including both organizations and associated shared resources in the GAL
  • Storing user mailboxes in separate Exchange databases to ease potential migration down the road.

Disk storage is a similar matter, separate the two companies logically (ie. create a namespace for companyX and companyY), but host them on a common platform. Since each company is on a different continent, you may find the there is a natural split anyway that will lead to a bigger split down the road. The VP of somethingorother will get sick of those unresponsive Yank/Brit IT people.

0

Perhaps a collaboration tool such as Microsoft Sharepoint or Mindtouch would be suited for sharing of information and files.

E-mail addresses may be forwarded or subdomained, depending on the requirements of the project.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .