Hi,
I'm trying out the Solution in this book chapter by chapter in my home computer and I'm stuck in Chapter 4 where we send emails using <mailDefinition> I was able to send email successfully from the contact.aspx page using the following web.config
<system.net>
        <mailSettings>
            <smtp deliveryMethod ="Network" from ="[email protected]">
                <network defaultCredentials="false" host="smtp.gmail.com" userName="[email protected]" password="xxx" port="587"/>
            </smtp>
        </mailSettings>
    </system.net>

and the following code

  SmtpClient client = new SmtpClient();
            client.EnableSsl = true;
            client.Send(msg);

Please note I had to add
             client.EnableSsl = true;


But the Register.aspx and PasswordRecovery.aspx page gives the following error :(

"The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.0 Must issue a STARTTLS command first. i12sm10525493wxd.4 "

Kindly help me resolve this error.

You will have to interrupt the sending of the mail in the SendingMail event, and use a custom Smtp client in the event handler.

In the page, you'd have something like this:

<asp:PasswordRecovery ID="PasswordRecovery1" runat="server" OnSendingMail="PasswordRecovery1_SendingMail">
   <MailDefinition BodyFileName="passwordrecovery.txt" Subject="Your Password Reminder" />
</asp:PasswordRecovery>

Then, in code, something like this:

 protected void PasswordRecovery1_SendingMail(object sender, MailMessageEventArgs e)
 {
    MailMessage message = e.Message;

    try
    {
       SmtpClient smtp = new SmtpClient();
       smtp.EnableSsl = true;
       smtp.Send(message);
    }
    catch (Exception ex)
    {
       throw new Exception("There was a problem sending the email.", ex);
    }

    e.Cancel = true;
 }

Thanks a lot Lee,
It worked like a charm.

If you don't mind could you please tell me why we had to add e.cancel = true;
When I didn't have that before the program sent 2 emails instead of one.

This event handler is invoked when the PasswordRecovery control is attempting to send an email. What you are doing here is grabbing the message from that initial attempt and sending it with your own SSL-enabled SmtpClient. Then, you need to call e.Cancel to stop the original send; otherwise, it will still try to go through. This will result in two emails being sent -- one through your SSL-enabled client, and one through the original non-SSL client.

Somewhat makes sense Lee,
So when we didn't interrupt the natural email process, It gave "client was not authenticated", When we interrupted and created a new SmtpClient() and client.EnableSsl = true; the original email process also works (Unless we cancel it explicitly like we did)??

I'm always weak in Email process, may be I don't understand the basics.

Anyway,
Thank you so much for your time and effort!
Seetha.

Yes, that's exactly right.