|
|
|||||||
CDO is Collaboration Data Objects and it is a Component Object Model (COM) component designed to simplify writing programs that create or manipulate Internet messages. So, we should be able to use KiX's COM support to use CDO... we we can! If you want more information about CDO in Win2000 have a look at MSDN's About CDO for Windows 2000 page. I have only used this script on Win2k with KiX Beta2a. Be sure to put @@ in the email addresses too.
code: cj ------------------
[This message has been edited by cj (edited 22 June 2001).] |
||||||||
|
|
|||||||
Hello cj, I've tried your script with the latest KiX2001 under german Windows2000 SP2. The script runs and produdes no error-messages but also it produduces no eMail. Not in Outlook and not in Outlook Express and there is no traffic on my connection to the internet. Where is the eMail gone to? ------------------ |
||||||||
|
|
|||||||
Hi Jens and cj I got the same results, but thought that perhaps our Firewall was the cause. Mine does not send email either. I have English Windows 2000 SP2 and Outlook 2000 NTDOC |
||||||||
|
|
|||||||
cj - if I can butt in for a moment - I don't know whats wrong but what happens if you guys put this in ... $oMsg.Send() ?"ERROR @ERROR: @SERROR"
|
||||||||
|
|
|||||||
Hi Shawn, I get back this error: code:ERROR 1: COM exception error "Send" (CDO.Message.1 - The transport failed to connect to the server. I sent cj an email asking him how the system knows which Server and method to use, but I have not heard back yet. I am using the KixTart 2001 v4.00 beta 2 NTDOC |
||||||||
|
|
|||||||
TBH IDK how it works :D It just does for me... Here is the source code in VBScript that I used: code: Now, that needed some tweaking and I couldn't get the ITEM() bits to work. Here are the first two failed versions: sendmail.k2k code: Sendmail2.k2k code: Normally, you would set the server and login information in the CDO.Configuration object, but when I tried every combination of $Flds.Item("sendusing") I couldn't make it work. Often I would get an error 100 (Cannot create another system semaphore.) too. I tried: $Flds.Item("sendusing")=2 and others that I have not kept. BTW 2 is SMTP and 3 is Exchange (i think). Have a look at that MSDN link and follow it down to the Messenging section. I suspect that one of the above lines worked and I ended up setting the parameters and they were remembered. I only tried this for the novelty and didn't delve too deeply into the workings :} HTH cj [This message has been edited by cj (edited 26 June 2001).] |
||||||||
|
|
|||||||
I've done some work with CDO (v. handy if you run Exchange, but a bit of a bitch) and there are two varieties. (This is all NT4, don't know about W2K cos that's different again) - (1) CDONTS (which I think is the CDOSYS version cj refers to) must be installed and run on an NT server to function. It comes with the Option Pack. W2K uses a new version of CDO which (I believe) is all SMTP based instead of MAPI. If you want to know what you've got installed on your machine, try opening Word, hitting <Alt>+F11 and going to Tool..References and looking for "Microsoft CDO ????????" in the list. Hope it's useful (maybe, maybe not???) MCD |