• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Webmail

T

tgray96

[H]ard|Gawd
Joined
Dec 13, 2010
Messages
1,055
ok so i own a domain... with the company that is hosting, we have unlimited accounts and i was wondering how i could setup a mail server to use and i also want to use horde webmail... Any Input?
 
I know nothing about horde webmail but to setup your own server you will need to point your MX record to your external IP and open port 25 on your firewall and forward that to your internal IP of the server.
 
For Windows I'd use Hmailserver. If you are wanting webmail off of that, I'd install Apache and PHP (or IIS with PHP) and SQL server or MYSQL and install RoundCube Webmail. Or you could go the Exchange route and then you'd have OWA with it.
 
Secure, stable, easy to use, frusturation free? Novell Groupwise! (Disclaimer: groupwise is none of these things).

Exchange for windows, Communigate for linux.

Also if you are doing mail out of your house and you are on a residential ISP make sure that they allow for port 25 traffic. Most ISPs block this for residential accounts.
 
C7J0yc3 said:
Secure, stable, easy to use, frusturation free? Novell Groupwise! (Disclaimer: groupwise is none of these things).

Exchange for windows, Communigate for linux.

Also if you are doing mail out of your house and you are on a residential ISP make sure that they allow for port 25 traffic. Most ISPs block this for residential accounts.
Click to expand...

Haha the groupwise joke made me laugh lol what about webmail for exchange?
 
yes... but i want to do in-house email hosting preferbaly exchange so it an be distributed to phones and what not
 
Exchange has OWA builtin. No need to setup any other webmail client.
 
oh ok that easy enough... i am downloading exchange (yes valid) and am formatting my asterisk box over to server 2k3
 
I also hope your 2003 box isn't an Active Directory Domain Controller. After 2003, MS stopped supporting installing Exchange on a DC.
 
C7J0yc3 said:
I also hope your 2003 box isn't an Active Directory Domain Controller. After 2003, MS stopped supporting installing Exchange on a DC.
Click to expand...

No, Its not my DC it was my secondary for a while, but the server was needed for something else and windows was wiped, now i am reinstalling 2k3
 
C7J0yc3 said:
I also hope your 2003 box isn't an Active Directory Domain Controller. After 2003, MS stopped supporting installing Exchange on a DC.
Click to expand...

? Exchange 2010 installed fine on my Server 2008 R2 server fine and it's running as a DC.
 
/usr/home said:
? Exchange 2010 installed fine on my Server 2008 R2 server fine and it's running as a DC.
Click to expand...

Did you install the AD role before or after installing Exchange. Also did you ignore the message during the exchange setup telling you that it isn't supported?

It is like the fact that there is a 32 bit version of exchange 2007 and 2010. They are for lab use only, and have no support from MS.
 
Exhange SHOULD be installed with an AD backend. It just works better that way. Yeah, I had AD on there already. Exchange never gave me any errors beforehand or afterhand. MS does semi-support it as well.
 
Microsoft not supporting Exchange on a DC? Shit..better throw away all those Small Business Servers out there...cuz they must not be supported by Microsoft...

..wait..no, I believe Microsoft does support SBS...
 
Its just not recommended for larger enterprise deployments. Non SBS servers running AD and Exchange can be done as long as its SBS sized.

I recommend A LOT of ram for the SBS servers. With Exchange and SQL running on the same box, youll need it.
 
Larger deploys....true.
I don't recall seeing the OP state the amount of intended users, hopefully since it looks like he's planning on hosting on a home broadband connection...not a lot of users (lets think of that upload..which is what counts for remote users)

Full SQL isn't always with SBS, that comes with SBS Premium.
 
install that mofo! you shouldnt have issues. more ram though never hurts, exchange loves it.

Are you familar with Exchange? I made a quick setup guide for Exchange that will get you up and running, nothing indepth though.
 
YeOldeStonecat said:
Microsoft not supporting Exchange on a DC? Shit..better throw away all those Small Business Servers out there...cuz they must not be supported by Microsoft...

..wait..no, I believe Microsoft does support SBS...
Click to expand...

SBS is a different setup then Exchange.

Also I stand corrected

Installing Exchange 2010 on Directory Servers

For security and performance reasons, we recommend that you install Exchange 2010 only on member servers and not on Active Directory directory servers. However, you can't run DCPromo on a computer running Exchange 2010. After Exchange 2010 is installed, changing its role from a member server to a directory server, or vice versa, isn't supported.
Click to expand...

http://technet.microsoft.com/en-us/library/aa996719.aspx
 
tgray96 said:
I'm Fing confused lol
Click to expand...

Ok, so reading the MS library article I posted it turns out that MS says it is OK to have Exchange on a DC though it is not recommended because of security reasons and also because AD decreases your disk IO performance, thus making exchange slower.

Personally I believe that exchange should stand on its own, however in some cases that can't be done for lack of available resources. If you decide to run a domain controller with your exchange 2007 environment you will need to setup your server as a DC first, then install exchange.

Also make sure you have enough CALs to cover user and resource mailboxes.
 
/usr/home said:
Also link to guide? I'm interested as well.
Click to expand...

I suppose I'll put it in a post rather than a PM. This guide is a little old and I dont use it word for word anymore. It is extremely basic and doesnt take any kind of security/hardening into mind. But it will get your server up and sending/recieving externally pretty quick.

This guide does not include how to setup your internet domain to point to your mail server. While similar in most aspects every domain provider (godaddy, 1and1, etc...) can be different

That being said... I dont need to hear any "WTF thats a stupid way of doing that!" Use this at your own risk, and if anyone has anything CONSTRUCTIVE to add to it, I'll be more than happy to edit it. :)

Install Exchange
Organization Config ---->Hub Transport-----> Send Connector------->Create Send Connector for outgoing mail (google create send connector - use the petri.com article, it will show you how to set it up so not just any asshole can send mail through your server, this will get you blacklisted instantly.


Organization Config ---->Hub Transport----->Accepted Domains------>Specify accepted external domain(s)

Server Config------>Hub Transport------>Recieve Connctor----->Default Recieve Connector------>Network----->Recieve mail from these servers that have these IP addresses-----> specify range of 0.0.0.0-255.255.255.255


Server Config------>Hub Transport------>Recieve Connctor----->Default Recieve Connector------>Authentication Tab------>Uncheck all except TLS and Basic Auth.


Server Config-----> Exchange Server------> Properties-------->External DNS Lookups------->Speficy External DNS server in server properites (I use 208.67.222.222)


Ports you may need to forward: 25 587 993 995 110 143


Turn on POP3 and/or IMAP services in services.msc


Recepient Config ------>Mailbox------>User Properties------>E-Mail addresses Tab------>Add external email address to Active Directory User
Recepient Config ------>Mailbox------>User Properties------>Mailbox Features Tab------>Turn on POP3/IMAP4 Protocols for users (should be on by default)


For email to your phone open Exchange Console and enter command: Set-PopSettings -LoginType PlainTextLogin


Outlook Setup - Using Exchange is pretty straightforward. To setup pop/imap use this:


My settings:


Your Name: J-Rod Adams!
Email Address: user@domain.com


Account Type: POP3
Incoming Mail Server: pop.domain.com
Outgoing Mail Server: smtp.domain.com


Username: user
Password: <active directory password>


More settings button:


Outgoing Server Tab


Tick my outgoing server requires authentication


enter FQDN and password of user in Active Directory: example: user@domain.local


Advanced Tab:


Incoming POP3 Server Port 110


Outgoing Server Port: 587

Hope this helps.
 
Last edited:
jadams said:
I suppose I'll put it in a post rather than a PM. This guide is a little old and I dont use it word for word anymore.

Snip
Click to expand...

Why are you using pop for exchange instead of just using exchange to push like it should? If you are doing an exchange 2003 single server setup, ok this is logical so you can get your mail outside your network, however if you have a multi server exchange 2003, or single server 2007/2010 server why not just run outlook anywhere. You only have to open port 25 and port 443 on your firewall to get that working, and it doesn't require any additional setup or configuration other then checking the box that says "Enable Outlook anywhere."

The only time I use POP with exchange anymore is for a tool called mail flow monitor to ensure that my customer's are still getting email (it is nice because it forces the mail through the external spam filtering, any routing, then into the server, so if one link in the chain is down, you can find it and fix it).

This is a pretty decent guide for setting up Exchange 2010, and most of what is said here carries over to exchange 2007 as well.

http://www.enterprisenetworkingplan...601/Installing-Exchange-2010-Step-by-Step.htm
 
C7J0yc3 said:
Why are you using pop for exchange instead of just using exchange to push like it should?
Click to expand...

Did you miss this part?

jadams said:
Outlook Setup - Using Exchange is pretty straightforward. To setup pop/imap use this:
Click to expand...

Meaning to use Outlook to connect to the Exchange server the way it was intended is straight forward, BUT if you want to use pop/imap for some other reason use the other settings. Theres any number of reasons why someone would want to use pop/imap, and the guide covers it. Perhaps I should have said "mail client setup" rather than "Outlook Setup"

The guide you linked to is very similar to the one I made through trial and error for my own records. Good link.
 
Last edited:
Can you get Exchange With a technet subscription? I was hoping to find the 32 bit but yet to have, I dont have 64 Bit capable server hardware
 
You must log in or register to reply here.
Back
Top