S
STom
Guest
I sent the email below to the VPC newsgroup but was told that this really had
nothing to do with VPC specifically, but had more to do with how to setup a
lone server that could send email to itself (like for doing labs etc where
the student only has one machine and not networking capability).
Here is that email:
********************************************
I have a vpc image created with VPC 2007. It is:
Windows 2003 Standard SP2 with all the latest patches (named DEMOAPPSERVER)
SMTP
POP3
IIS
Office 2007 Professional
Visual Studio 2005
SQL 2005
MOSS
I just login as Administrator so there are no other users on the machine.
What I want to be able to do is send an email to
Administrator@demoappserver.com. So here is what I did:
SMTP
1. Installed SMTP
2. Enabled Logging.
3. Set Relay Restrictions to ‘Only the list below’ to grant ‘127.0.0.1’.
4. In my domains list I see ‘demoappserver Local(default).
POP3
1. Installed POP3
2. Had to create a new domain so I called this ‘demoappserver’. In this
domain I created a mailbox for the Administrator. Unfortunately, now I see a
second ‘demoappserver’ in my SMTP domains list.
I then go into Outlook and create an email account pointing to POP3. My
‘Incoming mail server’ is set to localhost (also tried demoappserver) and the
‘Outgoing mail server’ is localhost (also tried demoappserver). When I test
the account settings, it shows logging into the POP server and sending the
email a success. If I go to the C:\Inetpub\mailroot\Queue directory, I can
see where message is dropped in but eventually it goes to the Badmail
directory.
So at this point, I’ve been pulling my hair out. Anyone with any idea on
what I am missing here?
***************************************************
So, my questions would be here, does this server need to be a domain
controller in order to be able to do something like this? And if I make it a
domain controller, what do I have to do then to get this to work?
--
Thanks.
STom
nothing to do with VPC specifically, but had more to do with how to setup a
lone server that could send email to itself (like for doing labs etc where
the student only has one machine and not networking capability).
Here is that email:
********************************************
I have a vpc image created with VPC 2007. It is:
Windows 2003 Standard SP2 with all the latest patches (named DEMOAPPSERVER)
SMTP
POP3
IIS
Office 2007 Professional
Visual Studio 2005
SQL 2005
MOSS
I just login as Administrator so there are no other users on the machine.
What I want to be able to do is send an email to
Administrator@demoappserver.com. So here is what I did:
SMTP
1. Installed SMTP
2. Enabled Logging.
3. Set Relay Restrictions to ‘Only the list below’ to grant ‘127.0.0.1’.
4. In my domains list I see ‘demoappserver Local(default).
POP3
1. Installed POP3
2. Had to create a new domain so I called this ‘demoappserver’. In this
domain I created a mailbox for the Administrator. Unfortunately, now I see a
second ‘demoappserver’ in my SMTP domains list.
I then go into Outlook and create an email account pointing to POP3. My
‘Incoming mail server’ is set to localhost (also tried demoappserver) and the
‘Outgoing mail server’ is localhost (also tried demoappserver). When I test
the account settings, it shows logging into the POP server and sending the
email a success. If I go to the C:\Inetpub\mailroot\Queue directory, I can
see where message is dropped in but eventually it goes to the Badmail
directory.
So at this point, I’ve been pulling my hair out. Anyone with any idea on
what I am missing here?
***************************************************
So, my questions would be here, does this server need to be a domain
controller in order to be able to do something like this? And if I make it a
domain controller, what do I have to do then to get this to work?
--
Thanks.
STom