[AccessD] CDO Windows Handles

Gustav Brock Gustav at cactus.dk
Mon Dec 3 10:23:38 CST 2007


Hi Max

You wouldn't know. That process runs asynchronously. CDO delivers the mail to the SMTP server - this will normally not fail except for disk I/O failures - and from that point on the delivery is in the hands of the SMTP server. Should delivery fail, it will try a couple of times more, the receiver may be busy and request a delay and retry. This can take days and you wouldn't wish to wait for that.
What you can do is to pick up a failure of delivery note from the SMTP server, or you may somehow study the log file of the SMTP server which is a task on its own.
Or - if you wish a quick positive feedback - set yourself (the application or system) as Bcc receiver on the mails you send, pick these up as they come in and mark those missing. However, you will only see what has been sent how and when, but not wether the mails actually reached the recipient.

/gustav

>>> max.wanadoo at gmail.com 03-12-2007 16:40 >>>

Can anybody advise/help here please.
I am using CDO to send emails and it works just fine BUT I can never tell
when it has finished.
What it does on the "cdo.send" is to pause for a second or two and then
return to the statement following that line BUT I don't think it has
actually sent it at that point. I think it has just "handed it over" to the
system task scheduler (or something like that).
I need to know that the actually event has truly finished.  If it was a
Shell I was using I could grab the handle, but as it is just a build-in
function within the CDO events, this is not possible.
Can anybody throw any light on this?
Thanks
Max






More information about the AccessD mailing list