Dim objMail As New MailMessage()
        objMail.From = "myemailaddress"
        objMail.To = "myemailaddress"
        'objMail.Cc = "[email protected]"
        'objMail.Bcc = "[email protected]"
        objMail.BodyFormat = MailFormat.Text
        objMail.Priority = MailPriority.High

        objMail.Subject = "My first ASP.NET email"

         objMail.Body = "This is my first email sent via ASP.NET."

         SmtpMail.SmtpServer = "servername"
         SmtpMail.Send(objMail)
------------------------------------------

It fails because it was rejected due to "Client was not authenticated". In ASP 3.0 with CDO I used this code:

objConfig.Fields(cdoSendUsingMethod) = cdoSendUsingPort
objConfig.Fields(cdoSMTPServer) = "servername"
objConfig.Fields(cdoSMTPServerPort) = 25
objConfig.Fields(cdoSMTPAuthenticate) = 2
objConfig.Fields(cdoSendUserName) = "ausername"
objConfig.Fields(CdoSendPassword) = "apassword"

Does ASP.NET have this option?

I would say from looking at the members list of System.Web.Mail.MailMessage that you can't. And by the sounds of it your mail server is pretty well buttoned up.

I think if you omit setting SmtpServer the object will try to use the localhost SMTP server in IIS. That might work for you.

Peter

If I omit it this is the error that I get:

"The "SendUsing" configuration value is invalid"

I'll enable windows authentication and see what that does.

Now you have me confused. What "SendUsing" configuration value? I don't recall seeing a SendUsing property in System.Web.Mail.MailMessage.

Peter

I was following along with this article:

http://www.sitepoint.com/article/1030

If I recall correctly, SendUsing is what used under the hood as the mail server. It defaults to localhost, but you can override it with the SmtpServer property of the SmtpMail class.

Apparently, you don't have an SMTP Server installed on the machine that tries to send the e-mail, so the Send call fails.

I know of no way to authenticate using the SmtpMail class. You can, however as Peter pointed out, install a local SMTP server. This mail server can then forward your e-mail to your ISP's mail server.

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

It's installed and running because it's being used right now for classic asp 3.0.

But Peter is right, it is locked down so it won't get 'black listed'. The server person has locked it down.

I changed the SmtpMail.SmtpServer = "servername" to "localhost" and got a can't relay message.

So, I looked at an email from a someone who works across the campus and saw that he was using an email server that allows outside access and used that server name and it worked. My server is [u]intranet</u> only because of ip restrictions. I wonder if that has anything to do as to why it didn't work?

Thanks for your help Peter and Imar.

As long as the following conditions are met, you should be able to send mail thru a mail server using the .Net mail classes:

A. You can access the server via an IP connection (inside a network or outside)
B. The mail server does not require authentication to drop mail onto it. (This is most likely the cause of problems.)
C. The mail server is running (You never know! ;))

Whether or not mail dropped onto a valid SMTP server will get OUT is a different issue. In the case of the IIS SMTP server, I believe it makes the connection to the appropriate mail server itself. It shouldn't even need to know about another mail server to get the mail out (i.e. it doesn't need to talk to your company's public mail server.)

One thing to note regarding sending mail. Let's say my company's mail server is mail.mycompany.com. If I use the .Net mail classes to send mail, the mailmessage class talks directly to that server and I'm trying to send mail to "[email protected]", I have to ensure that there is actually an account for "someaddress" on that mail server. You'll get an immediate failure when you try to create the message on the SMTP when that SMTP is on the same mail system as the POP server that will eventually handle any recipient's address. Hope that makes sense. However, when you use "localhost" (IIS SMTP on the web server) you shouldn't have a problem. If the email address is bad, the message will just bounce and probably end up in the bit bucket unless you used a real "from" address.

The authentication issue may be a discussion to have with the mail server administrator. In most LAN configuration's I've seen, the SMTP service is set up so that anyone who's on the local network can drop mail. From the outside (public IP addresses) only users who have authenticated into POP can drop mail. I think the server recognizes the user's IP address and allows mail relay from that address for some predetermined amount of time. Additionally, the SMTP service (if capable) can be set up to require authentication to send mail. Typically, allowing accessive security from the outside is acceptable, but usually that much security from inside the LAN is not necessary. IMO, if the mail server administrator is that worried/paranoid about someone unauthorized accessing the mail server from the LAN s/he should be more worried about how they got into the LAN in the first place!

There's my dissertation on accessing mail servers. :)

Peter

All you have to do is go to your smtp properties...select the access tab...under relay select all computers except or list the ip address of your machine.