Outlook UDF

[water]

Based on this threads (UDF Standards and UDF Public Build Templates) I suggest to:

• Verify/change the function names
• Verify/Change the variable names
• Verify/Change the parameters
• Verify/Change the function documentation
• Run Au3Check
• Run tidy to re-format the code
• Create example files for each function
• Generate the help files
• Generate the necessary files for SciTE integration (calltips etc.)

If you like I can start to work on this list Edited November 1, 2010 by water

[Wooltown]

It is OK for me if you like to do it and have the time.

[water]

OK. I will start to work on it in a few days and post the results as soon as I have finished one of the mentioned tasks.

Edited November 1, 2010 by water

[water]

Would you like me to send questions via private mail or should we discuss them in this thread?

Example: _OutlookSendMail specifies parameter $sTo as optional. Can you send an email with just $sCC or $sBCC specified?

[Wooltown]

We can discuss them here so if other have opinions on the work they can contribute.

$sTo is optional, if you would like to send BCC mail to a group of people and they should not be able to see other mailaddresses.

[water]

There are multiple instances in your UDF where _OutlookError is "defined".

I would suggest to enhance the UDFs error handling in the way other UDFs work. Some debugging could be included as well.

The error handler could be established with _OutlookOpen.

What do you think?

[Wooltown]

There was some reason I put that in all functions, but I don't remember what my problem was.

[water]

There was some reason I put that in all functions, but I don't remember what my problem was.

As global variables should be avoided with UDFs this might be the problem.

But as other UDFs use a low number of global variables as well it should be ok if properly named.

[water]

Here is my first try:

• Did use Tidy to clean up the code
• Ran Au3Check and corrected some minor problems
• Changed the function header so all necessary help files etc. can be created automatically
• Added the COM error handler to _OutlookOpen if one does not already exist
• Enhanced _OutlookError to retrieve as much information as possible for debugging
• Added function _OutlookClose to reset the COM error handler when no longer needed
• Introduced global variable $iOutlookDebug to write the debugging information to screen or file

What do you think?(Attachment deleted as the code has been posted on the ) Edited March 9, 2011 by water

[water]

Another question.

When enhancing the UDF should existing scripts run without modification?

When I modified the original Active Directory UDF some script breaking changes were necessary.

[Wooltown]

It doesn't matter to me. I wrote it at my previous occupation and they don't use it anymore. For the rest of the people using it, perhaps we can do a documet describing the changes. Both the new and the old can be available for download.

/Sven

[water]

That sounds good.

In the next step I will create example scripts for every function.

[water]

Found (and removed) a bug in _OutlookSendMail. $olFormatHTML never worked because the body has to be written to $oMessage.HTMLBody not $oMessage.Body.

[Wooltown]

I got it to work, but it was Outlook 2000 I think !

[water]

Another question.

Do you know of an easy way to get the email address of the current user?

The example scripts should run without modification so I want to send the email to the user who runs the script.

Edited November 2, 2010 by water

[Wooltown]

No unfortunately not, hopefully you know who you are

echo@sunet.se - will give you an email in return, good to validate email is working

/Sven

[Rigest]

You are incorrect, but you've helped me on the right way. It should be: $oMessage.Sentonbehalfofname = $sFrom. Tnx anyway

Maybe you can include the above as well? Also I added

$oMessage.DeferredDeliveryTime =$sDelay

To send e-mails with delay. I don't know if anyone but me uses these functions but maybe you can add them.

[water]

Maybe you can include the above as well? ...

What do you think is the best way to collect the enhancement requests for this UDF?

I would like to compile a list of all requests and process them one by one.

[Wooltown]

They can mail me on the forum or make a reply on the forum and I can put the list together and we can have a discussion how to continue.

[KingNED]

Maybe you can create a function that will move the mail to another folder?