I work for a company who are looking to bring emails in house due to a rise in cost. Maybe you noticed that SMTP and DNS are companions and you can't get it work if one thing is missing in real world scenarios (you know, mx and a records ect), Iam curious how manged to make hMailServer work in your own corporate Network without your own DNS-Server?ĭid you say to your Users "please insert the ip address or local Email will not work? And didn't have no where near a complicated setup as you describe. I knew diddley squat about mail servers when i started but had an I.T mind and understanding and did very well serving the company. Remind me not to ask you to sell my services or products.įor people with knowledge it isn't as difficult as you make out out to be. I think the easiest way would be for you, to buy a Office365 Exchange Online plan or a Google Gmail for Business Cloud Plan to get what you want or running hMailServer on a Dedicated Windows Root Server at some Hosting Company with proper backup capabilities. There is also no Revision safe Emailsystem required by some Country laws. You will face a total and complete outage of all things Email in your Company and your Boss will be pissed and mad as If something bad is happening to your hMailServer But there is no Backup or failsafe mechanism right know. It also isn't a Groupware Server, has no Calenders or Global Address book.It has only shared Imap Inboxes which can raise all sort of crappy UID Errors which can make Outlook or hMailServer crash regulary.Īll the above is describing the effort requiring 1x hMailServer, running your coorporate and public Email If you want Mailing lists, just forgeh hMailServer. PS: hMailServer doesn't supports Email Lists like for example on Linux with the Postfix or Exim Emailserver in addition with GNU Mailman or Majordomus. You can buy a expansive CISCO PIX Hardware Firewall and Router or a Checkpoint Software Firewall but i recommend two Linux or OpenBSD UNIX boxes to make your DNS Setups more secure and reliable and costs doesn't get out of control. I cannot recommend to do all the involved work allone on basis on Windows because the Windows Firewall sucks for such tasks. However, this is the bare minimum, but you need a few things more, like a Firewall (or more than one) to protect your new Network. Of cause you need a SSL-Certificate which needs to be renewed from tine to time so your Email Users dont get Security and fraud Warnings by your Thunderbird/Outlook or Webmail Email Client programs. This on the other side requires setting up atleast 2x DNS-Servers like BIND9 which needs to be setup as Master Slave Replication (this is a a mandatory requirement before yourĭomain Provider is allowed to transfer DNS Zone Authority to your own DNS-Servers. To make it possible you need to setup hMailServers Relay Feature or your Local Area Network Subnet and all its IPs needs to be a official, public Internet visible Subnet (this means contacting your coorperate Broadband Provider and ordering a Public Internet Static ip address subnet) In this case your DNS-Server needs to be also visible and accessible to the public Internet. This will only allow sending and receiving Emails in your Local Area Network of your Company but NOT communicating and exchanging Emails with the public Internet. First and for all, you need to Setup and ConfigureĪ Local Area Network and a local DNS-Server and hMailServer and all Email sending and receiving Users needs to be in the same Subnet, if you use IPv4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |