Windows 2008 R2 Setting up MailEnable Email Service and Client

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

I have been trying to set the account information for what I thought were the settings required to access the user I set up on my Windows 2008 R2 server, but the settings failed.

Either I have not set up the email and/or the user correctly on the server, or I don't know what values to use for setting up Outlook 2007 to access that account.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

The Server is running Windows 2008 R2 with Hyper-V VPS.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

Everything I see on the Email Service makes me think it is though. I have users in a domain with mailboxes and they are receiving messages as the email counters per user do go up when sent automatic messages within the server itself.

ASKER

I think I just need someone to "twick" the software or point me at where I can find the settings that my outlook email account requires.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

It's looking like I have a blocked port. I am using AVG Internet Suite 2011 for my virus scan and general malware handler and it's way tricky to get it to open a port (I have tried disabling it to no avail as well).

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

ASKER

Again, I think that it is somehow related to blocking of ports by AVG and I don't see how to configure it to allow those ports. An AVG expert at the moment would be nice.

Step as follows:
*Open AVG on your PC. Click "Tools."
*Select "Firewall Settings" and click "Profiles."
*Double-click "Standalone Computer," then double-click "Applications."
*Double-click on the application that requires the opened port. Select "Advanced Configuration" from the "Action" menu. Click "Services," and click "Edit Services." Enter the port numbers you want to open and click "Save as Rule."

You can even disable the firewall just for testing

ASKER

For application requiring the open port, I am assuming you mean Outlook.exe and telnet.exe?

yes and you will also need port open for services SMTP which is port 25 and POP3 services which is 110

ASKER

Ok. In the AVG profiles tree within Firewall Settings there are three profiles:
Directly connected To the Internet (bold/active profile)
Computers within the domain
Small home or office network

If I select the applications within the active profile and select outlook, I see that I can add a rule about access for remote and/or local ports.

Do I select both ports and make the same rules (port 25 and port 110) for local and remote?

Also, I do not have an action menu. I have 5 buttons on the right of a potential list of rules for outlook.

"computers within the domain" is a proper settings for local area network, Port 25 and 110 on server communicates with local and remote clients.
I am not very fimilar with AVG suite 2011 but if you have option for adding rules than you are looking at the right place.

ASKER

I think that my configuration issue also has to do with making ptr records for each domain that I want to have a post office for.

I'd really like some how to for setting up domain records; the how and the why.

At the moment the company hosting my domains is giving me much heartburn to set up the ptr records. I have a vps running Hyper-V, but cannot set this domain record. So far, I am on day "FOUR" after requesting that they make this and explain why the admin panel they offer does not include the capability to create ptr records.

ASKER

Ok. Here it is. The problem was that my domain needed a ptr record in order to get email to work. Unfortunately, that's the one DNS record that this hosting site does not allow clients to create.

After they created the record, all is working.