• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Offsite email hosting to onsite Exchange server?

riahc3

Senior member
We have our email hosted on a offsite mail server/provider and we receive it via POP3 or IMAP. Now, I was wondering if we could onsite install a Exchange server, and receive all email from our provider on that server and everyone on their client PC would get their email from there.
 
What is the business need driving bringing your email in house?
1: (Using POP3) There is a copy of emails here in house as well
2: Exchange support for email clients locally.



Is the host running Exchange? If not, you'd need a connector, something like this:

http://www.jam-software.com/smartpop2exchange/
The hosts charge extra for Exchange so I would think it is better to use a connector.

I have a question: Since I already have a domain bought, could I just make a mail server here and configure it to send/receive email? I rethought about it so maybe I don't have to have email offsite at all....
 
I worked for a quite big business which had a solution very much the one you ask about - an Mdeamon server (actually 3), recieved emails and forwarded them to en Exchange server.
It was a fucking mess, and definitely recommand against it.

I have a question: Since I already have a domain bought, could I just make a mail server here and configure it to send/receive email? I rethought about it so maybe I don't have to have email offsite at all....

Much better solution.
 
I worked for a quite big business which had a solution very much the one you ask about - an Mdeamon server (actually 3), recieved emails and forwarded them to en Exchange server.
It was a fucking mess, and definitely recommand against it.

Seconded. I have supported a couple of clients under a manged services umbrella and they had the exact same setup...it was a dumb setup. For me personally, it's go Exchange or go home.
 
Well, from what Ive seen, Im guessing Ill have to go with the messy solution.

So is a connector like that the only thing I need? Anything other than this one as in freeware (better yet open source)?

Thank you
 
Thank you and I appreciate your recommendation but I still prefer to do this 🙂

Please see the other thread you posted for feedback from people with much, much more experience than you and see what they're saying. Again, no offense, but you're making a big mistake. You're committing your company to large future capital expenditures and yourself to supporting a product you don't have the knowledge and expertise to support.

P.S. Also, Exchange 2003 reached end of life on extended support on April 8, 2014. If you seriously implement that per your other thread, you're nuts.
 
Last edited:
Please see the other thread you posted for feedback from people with much, much more experience than you and see what they're saying. Again, no offense, but you're making a big mistake. You're committing your company to large future capital expenditures and yourself to supporting a product you don't have the knowledge and expertise to support.

P.S. Also, Exchange 2003 reached end of life on extended support on April 8, 2014. If you seriously implement that per your other thread, you're nuts.
Lets not mix threads. I want to do one or the other. I PERFER a standalone Exchange server.

And I believe I said it but just in case: This will not be Exchange 2003. This will be a much newer version.
 
Back
Top