Need help with sending email using a godaddy account.

Question

Hi,

I'm trying to send an email using my godaddy hosting.

I've also given away the username and password (as you can see in the code) for the testing email account so if anyone has the time, can they try and send an email using these settings? I'm totally at a brick wall.

I've got Thunderbird setup and it connects and sends emails fine using the settings below, but when I run this peice of code, it just times out. If Thunderbird can send email to this server then It must be my code. Its really frustrating.

SmtpClient ss = new SmtpClient();

                try {
                    ss.Host = "smtpout.secureserver.net";
                    ss.Port = 465;
                    ss.Timeout = 10000;
                    ss.DeliveryMethod = SmtpDeliveryMethod.Network;
                    ss.UseDefaultCredentials = false;
                    ss.Credentials = new NetworkCredential("[email protected]", "abc123", "comicidolonline.com");
                    ss.EnableSsl = true;

                    MailMessage mailMsg = new MailMessage("[email protected]", "[email protected]", "subject here", "my body");
                    mailMsg.DeliveryNotificationOptions = DeliveryNotificationOptions.OnFailure;
                    ss.Send(mailMsg);

                    Console.WriteLine("Sent email");
                    Console.ReadKey();

Answer 1

When you say it worked with Thunderbird, I'm assuming you tried from Thunderbird on the webserver? (You RDP'd in?)

Also, if this is a web app (assuming it is, since you are referring to godaddy), why do you have Console statements in a web app?!? There isn't any console involved.

Also, you say the code isn't working. How do you know? What is the exception?

Cheers! Dave

Answer 2

Hi, Since you are asking how to send email, and it can't be sent with System.Net.Mail (because of the SSL issue), one option is to use aspNetEmail (something I wrote -- so this is partially a shameless plug). I'm not aware of any open source email component that can do this, with the SSL connection required.

Here is some code (just tested, and it works).

EmailMessage m = new EmailMessage();
m.LogPath = "c:\\email.log";
m.Logging = true;

m.Server = "smtpout.secureserver.net";                    
m.Port = 465;                    
m.TimeOut = 10000;                    
m.Username = "[email protected]";
m.Password = "abc123";            

m.From ="[email protected]";
m.To = "[email protected]";
m.Subject = "subject here";
m.Body = "my body";                    

AdvancedIntellect.Ssl.SslSocket ssl = new AdvancedIntellect.Ssl.SslSocket();
//load the SSL socket, but tell it to connect *before* the 220 Welcome response
m.LoadSslSocket( ssl, true );

m.Send();                    
Console.WriteLine("Sent email");

If you want to try aspNetEmail, feel free to download the latest build update from link text

You will also need a free eval license, which you can get from: link text

If you have any other questions, feel free to ping me offline.

Cheers!

Dave

(more info added during later edit) I couldn't find the orignal doc on MSDN that I was thinking of (it's been a few years). But here is a MSDN blog post from Dan Bagley. http://blogs.msdn.com/webdav_101/archive/2008/06/02/system-net-mail-with-ssl-to-authenticate-against-port-465.aspx

System.Net.Mail with SSL to authenticate against port 465 Sending mail using System.Net.Mail with SSL will fail:

System.Net.NetworkCredential aCred = new System.Net.NetworkCredential("myacct", "mypassword");

SmtpClient smtp = new SmtpClient("smtp.mail.myserver.com", 465);
smtp.EnableSsl = true;
smtp.UseDefaultCredentials = false;
smtp.Credentials = aCred;

System.Net.Mail only supports “Explicit SSL”.

Explicit SSL

System.Net.Mail only supports “Explicit SSL”. Explicit SSL starts as unencrypted on port 25, then issues a STARTDLS and switches to an Encrypted connection. See RFC 2228.

Explicit SLL would go something like: Connect on 25 -> StartTLS (starts to encrypt) -> authenticate -> send data

If the SMTP server expects SSL/TLS connection right from the start then this will not work.

Implicit SSL

There is no way to use Implicit SSL (SMTPS) with System.Net.Mail. Implicit SSL would have the entire connection is wrapped in an SSL layer. A specific port would be used (port 465 is common). There is no formal RFC covering Implicit SSL.

Implicit SLL would go something like: Start SSL (start encryption) -> Connect -> Authenticate -> send data

This is not considered a bug, it’s a feature request. There are two types of SSL authentication for SMTP, and we only support one (by design) – Explicit SSL.

Answer 3

I found this post about GoDaddy's SMTP settings

THe code below worked for me. I had to change the port to the default SMTP port, and remove the domain specification from the NetworkCredentials.

 SmtpClient ss = new SmtpClient();

        try
        {
            ss.Host = "smtpout.secureserver.net";
            ss.Port = 25;
            ss.Timeout = 10000;
            ss.DeliveryMethod = SmtpDeliveryMethod.Network;
            ss.UseDefaultCredentials = false;
            ss.Credentials = new NetworkCredential("[email protected]", "abc123");

            MailMessage mailMsg = new MailMessage("[email protected]", "[email protected]", "subject here", "my body");
            mailMsg.DeliveryNotificationOptions = DeliveryNotificationOptions.OnFailure;
            ss.Send(mailMsg);

            Console.WriteLine("Sent email");
            Console.ReadKey();
        }
        catch (Exception ex)
        {
            Console.WriteLine(ex.Message);
            Console.ReadKey();
        }

Answer 4

Remove the EnableSsl = true and see if that fixes it. The way SmtpClient works is that if credentials are provided and the server advertises the AUTH keyword in the EHLO response headers, and when we try to do something it asks for auth, we attempt to auth with the provided credentials. However, with EnableSsl, if the server does NOT advertise STARTTLS as a response to the EHLO then we throw immediately since we will not be able to use it. Therefore, unless you are 100% CERTAIN that the smtp server you are using supports SSL (TLS actually) you should not set EnableSsl and leave it at its default value of false. If you post up the exception you're getting I can tell you why it's being thrown.