smpt virtual server

[mb123]

Hello ppl

I was wondering if someone here could help me out with iis 5.1

I have a standalone computer with cable access to the internet that runs the windows XP prof OS.

Ive recently installed the optional iis windows component on my machine.

And noticed that under this program i also have access to a Smtp virtual server.

My initial question is this:
Is it possible for emails to be recieved by this mail server?

If so
Do i have to set up an folder/account name first or is the Drop folder in the mail root directory ok for this?

And finally
How would i address emails id like to send to this account?

Any help would be great

Thanks in advance

mb123

[TripleRLtd]

Welcome to WD mb123. How you posted once and ended up with two threads I'll never know, but...;)
Anyway, you do know that you're asking about something new that has something of a learning curve and many pages of tutorial written about it? Right? So, how about you check here:
http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/smtp_admin_configuring_virtual_server.mspx
...and then come back and help us out? http://forums.windrivers.com/images/smilies/thumbs.gif
Seriously, I, personally have not worked with Virtual SMTP. But, since you brought it up, I do have it bookmarked and will start studying.
Damn, this line of work never stops being interesting.
But, that is a good thing, most of the time.
And, it wears you out. http://forums.windrivers.com/images/smilies/wink.gif

[confus-ed]

Is it possible for emails to be recieved by this mail server?

Yes, but you need a publicly resolvable address as well so that other people have somewhere to send to e.g. mb123.com so any mail would be 'something'@mb123.com (you can either register your own domain name, or use something like Dynamic DNS (http://www.dyndns.org/) to get the same result) - Note before even starting make sure your ISP will forward port 25 traffic, not all of them will ;) - also note this is a potential 'big security risk' as as soon as you've any kind of server whatsoever then your 'attack levels' will go up & IIS isn't exactly a winner at the 'secure application award ceremories' ! ;)

If you don't 'need' a mailserver, then I'd say don't, but like trip said (in lots of words ! :D :p) as a learning exercise it may very well be worthwhile :)

[mb123]

Hello confus-ed

Yes, I have discovered that to send and receive email ,i initially have to register my domain name.

However your reply has raised a few more questions, that i hope you might address :)

For example:
I understand that by running my computer as a server i may pose a security risk to myself, but what does this have to do with my isp exactly.

If i register a domain name so that i might set myself up with a publicly resolvable email address etc- then presumably the emails that are intended for that email address would travel along the bandwidth alocated me by my isp , just like any other web traffic.
And when the email arrived, my computer would read it in through port 25 , after scanning the header info and identifying the packet as an email. Right?

Or are you saying that my isp might be able to identify all traffic intended for port 25 on my machine and decide not to send it through on account of the security risk this may pose to their system.. somehow??
And if so.. what is that security risk exactly??

Anyways thats all i got for now.

I am doing this as a learning exercise , so any input would like you say, be worthwhile, sure.

Thanks again

mb123

[confus-ed]

I understand that by running my computer as a server i may pose a security risk to myself, but what does this have to do with my isp exactly.

Nothing, either I didn't type it too well, or you didn't get it as intended ;)

If i register a domain name so that i might set myself up with a publicly resolvable email address etc- then presumably the emails that are intended for that email address would travel along the bandwidth alocated me by my isp , just like any other web traffic.
And when the email arrived, my computer would read it in through port 25 , after scanning the header info and identifying the packet as an email. Right?

Well it reads it from port 25 & then looks at whats in the packets but yeah that's about it.

Or are you saying that my isp might be able to identify all traffic intended for port 25 on my machine and decide not to send it through on account of the security risk this may pose to their system.. somehow??

I'm saying many ISP's won't forward port 25 traffic ..

And if so.. what is that security risk exactly??

Because of things called open relays (http://www.webopedia.com/TERM/o/open_relay.html) which spammers can take a hold of ... which has no real security risk except that it can appear that an awful lot of spam originates from you ;)