Our Exchange server handles emails for @ourdomain.com (for example).
We have multiple clients that will send emails to our support@ourdomain.com email address and we want to configure server-side rules that will forward emails from each client's domain to a different email address within our exchange server.
For example:
steve@client01.com sends an email to support@ourdomain.com and we forward
We are offering multiple SSL-enabled services in our local network.
To avoid certificate-warnings we bought certificates for server.ourdomain.tld and firewall.ourdomain.tld.
We now created a zone in our local DNS-server in which we pointed the hosts to the corresponding private-ips.
Now, each time another record for ourdomain.tld, like for example www.ourdomain.tld or alike are changed, we need
This morning, our entire company received a spam message sent to users@ourdomain.on.ca, where "ourdomain.on.ca" is our actual domain.
Autodiscover on Microsoft Exchange 2010 can’t be used in my environment, due to the migration and consolidation of an email domain. As this e-mail domain is used in multiple exchange forests as an authorative e-mail domain, if we would enable autodiscover this would result in clients connecting to the newly build exchange 2010 environment prior to the users being migrated.
Basically what i'm after is to have a centralized IIS Server on the Local LAN where port 80/443 would be forwarded to from the router. Then through this server it can forward/redirect the requests to other servers in order to access the exchange OWA and for example the Remote Desktop web apps which are located on other local servers, the Exchange server and RDS Server respectively?
We have a SBS2008 server with 9 users using the embeeded Exchange. The MX record points to this server. This works fine.
We want 2 remote users to also have a mailbox on this server. The consultant say we can't because SBS don't allow to have remote users for Exchange. He may be right but seems very strange to me.
I have a Windows Server 2008R2 Active Directory and Exchange 2010 server (client access, hub transport and mailbox roles) in a primarily Linux server environment. A Linux server running BIND9 is master for all zones, including AD specific ones, with updates allowed from the Windows server (and from a separate Linux DHCP server).
I have a postfix mail server that should relay all outgoing mail to an Exchange 2010 server (the Exchange box is my smarthost). I have administrator access to the Exchange 2010 system, but I'm not very familiar with it.
I have an out of the box SBS2011 install which is fully patched and updated.
During SBS2011 installation did not give me the option of putting a .com and has instead setup my domain name with a local extension, i.e.
Email this page
