By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,357 Members | 1,021 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,357 IT Pros & Developers. It's quick & easy.

ASP.NET bug in SMTP

P: n/a
I followed this article to do authenticated SMTP, it works fine with port
25. (using .NET framework 1.1)
http://support.microsoft.com/default...b;en-us;555287

However, if I change the port number to 10025 (my email server is running on
this port too). I got error message "Fields update failed. For further
information, examine the Status property of individual field objects."

After some testing, I found that if the port number is under 9999 and it
will work, it won't work if port number is larger and equal to 10000? Is
this a BUG?

Help..

Dec 31 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Are you sending these emails to your mail server or to another server? As I
understand SMTP (which I confess is fairly limited), it is simply a telnet
session on another computer using port 25 as the gateway.

Before you ask if it's a bug, verify that it's not already a feature. In
other words, under standard use of SMTP, can you use port numbers over 9999?
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"00_DotNetWarrior" <00**************@gmail.com> wrote in message
news:43**********************@news.astraweb.com...
I followed this article to do authenticated SMTP, it works fine with port
25. (using .NET framework 1.1)
http://support.microsoft.com/default...b;en-us;555287

However, if I change the port number to 10025 (my email server is running
on this port too). I got error message "Fields update failed. For further
information, examine the Status property of individual field objects."

After some testing, I found that if the port number is under 9999 and it
will work, it won't work if port number is larger and equal to 10000? Is
this a BUG?

Help..


Dec 31 '05 #2

P: n/a
On the ports issue, you should be able to use any you like, it is down to
your app and any routers to eal with it.

For example you could send out to port 9594 if you wanted using smtp, but
the router at the other end receiving that connection would then need to
listen to that port and forward any connections to a local smtp server on
port 25.

Do check if the ports you are using are already in use with netstat -a from
the command prompt. If they are free and your apps know which port it wants
to use for the smtp you should have no probs.

I have to ask, why would you want to use a different port? And how/why is
your email server running on two ports??
"Christopher Reed" <ca****@nospam.nospam> wrote in message
news:Oq*************@tk2msftngp13.phx.gbl...
Are you sending these emails to your mail server or to another server? As
I understand SMTP (which I confess is fairly limited), it is simply a
telnet session on another computer using port 25 as the gateway.

Before you ask if it's a bug, verify that it's not already a feature. In
other words, under standard use of SMTP, can you use port numbers over
9999?
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"00_DotNetWarrior" <00**************@gmail.com> wrote in message
news:43**********************@news.astraweb.com...
I followed this article to do authenticated SMTP, it works fine with port
25. (using .NET framework 1.1)
http://support.microsoft.com/default...b;en-us;555287

However, if I change the port number to 10025 (my email server is running
on this port too). I got error message "Fields update failed. For
further information, examine the Status property of individual field
objects."

After some testing, I found that if the port number is under 9999 and it
will work, it won't work if port number is larger and equal to 10000? Is
this a BUG?

Help..



Dec 31 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.