0

I have a site which uses a lot of email to confirm actions to clients. As the site has grown the number of emails generated from the pages has grown likewise.

Recently we've started to see the site hanging (or at least anyone who was at the point of sending an email) for a minute or two. I'd put it down to network issues but the guys in the office kept raising it so I've investigated. It turns out that whilst email is going fine 95% of the time, now and again an email send seems to hang for a while and this then hangs anyone else who follows sending a mail. It's as if CDO just freezes and blocks anyone in the queue.

I've proven this by writing a database record immediately before the call to CDO.Send and updating an end time field on it one immediately after... the before record is there 99% of the time but now and again the after record has a NULL date/time so the update never gets called.

CDO seems to have no logs.

The code is correct as it works before and after the glitch. Any ideas?

EDIT: Just realized that the error occurs when the email module is used from two different PC's at the same time. We are talking about a module that sends shipping confirmation from our clients. Using a bar-code scanner we scan the order number and the shipping number into the application, and the javascript function redirects to the ASP page with the details to be included in the email in QueryString.

Happy to post the code if one finds it relevant.

Calon
  • 4,174
  • 1
  • 19
  • 30

1 Answers1

0

Could it be that one of the email addresses is not a real email address, or that one email address is unauthorised for your mail service?

I ask this because I always get errors like this when setting up a site in IIS for the first run. Most often the localhost (mail server) is not allowed to relay for that user or domain. But by routing through a mail server that is already configured and enabled or at least allowed to relay from your web server usually fixes the problem.

WilliamK
  • 821
  • 1
  • 13
  • 32
  • Thanks for the answer. Mail is already being routed through SmarterMail SMTP service and is being signed. Sending to invalid email addresses should and does result in replies from the user domain mailer daemon or from ours. Sending to email address "#$!@#!@#!@" results in a reply from SmarterMail mailer daemon saying that the address is invalid. – Samuel Kurtmann Apr 30 '13 at 15:18