Email Problem

[bondo]

I have an unusual error occurring when sending email from an ASP.NET
page. Basically, the first attempt at sending an email fails, whilst
subsequent attempts succeed without any issues. The code looks like
this:

MailMessage msg = new MailMessage();
msg.From = "te********@myaddress.com";
msg.To = "bo***@myaddress.com";
msg.Body = "Testing Mail";
msg.BodyFormat = MailFormat.Text;
msg.Subject = "Testing Mail";
SmtpMail.SmtpServer = ConfigurationSettings.AppSettings["MailServer"];
SmtpMail.Send(msg);

The error messages i get by iterating through the inner exceptions of
the thrown exception are:

1st ex - Could not access 'CDO.Message' object
2nd ex - Exception has been thrown by the target of an invocation
3rd ex - The transport failed to connect to the server

I also tried using the Indy.Sockets.IndySMTP from
http://www.atozed.com/indy/ to see if this fixed the problem, but
nope, same issues.

The web server is a win2003 server. The SmtpServer variable is stored
in web.config, and is the IP address of our unix SendMail server. Its
kind of weird that the first attempt fails, then subsequent attempts
(spanning multiple sessions) succeed. Has anyone seen this before?
what did you do to fix it?

[Nick Malik]

just a hunch...
you could try turning on SMTP services on the Windows 2003 box and
configuring it to forward all messages to the Unix box, then have your app
use the local server. The Windows SMTP server will be a lot more forgiving
if you are having connection issues, and will get the message delivered on a
retry, without affecting your web app.

Something I read somewhere...

Hope it helps,
--- Nick

"bondo" <mb***@astrum.com.au> wrote in message
news:8c**************************@posting.google.c om...

I have an unusual error occurring when sending email from an ASP.NET
page. Basically, the first attempt at sending an email fails, whilst
subsequent attempts succeed without any issues. The code looks like
this:

MailMessage msg = new MailMessage();
msg.From = "te********@myaddress.com";
msg.To = "bo***@myaddress.com";
msg.Body = "Testing Mail";
msg.BodyFormat = MailFormat.Text;
msg.Subject = "Testing Mail";
SmtpMail.SmtpServer = ConfigurationSettings.AppSettings["MailServer"];
SmtpMail.Send(msg);

The error messages i get by iterating through the inner exceptions of
the thrown exception are:

1st ex - Could not access 'CDO.Message' object
2nd ex - Exception has been thrown by the target of an invocation
3rd ex - The transport failed to connect to the server

I also tried using the Indy.Sockets.IndySMTP from
http://www.atozed.com/indy/ to see if this fixed the problem, but
nope, same issues.

The web server is a win2003 server. The SmtpServer variable is stored
in web.config, and is the IP address of our unix SendMail server. Its
kind of weird that the first attempt fails, then subsequent attempts
(spanning multiple sessions) succeed. Has anyone seen this before?
what did you do to fix it?

[Mark Bond]

Hi Nick,

I'll try this on Monday and fingers crossed it will sort it out...

Thanks for the reply!

Mark

Nick Malik wrote:

just a hunch...
you could try turning on SMTP services on the Windows 2003 box and
configuring it to forward all messages to the Unix box, then have your app
use the local server. The Windows SMTP server will be a lot more forgiving
if you are having connection issues, and will get the message delivered on a
retry, without affecting your web app.

Something I read somewhere...

Hope it helps,
--- Nick

[Mark Bond]

Yep - that worked a treat, I set the SMTP server on the webserver to
relay to the sendmail server and problem has gone - works every time :)
Mark Bond wrote:

Hi Nick,

I'll try this on Monday and fingers crossed it will sort it out...

Thanks for the reply!

Mark

Nick Malik wrote:

just a hunch...
you could try turning on SMTP services on the Windows 2003 box and
configuring it to forward all messages to the Unix box, then have your
app
use the local server. The Windows SMTP server will be a lot more
forgiving
if you are having connection issues, and will get the message
delivered on a
retry, without affecting your web app.

Something I read somewhere...

Hope it helps,
--- Nick