pfiore

Stripped down but basically: Global $oOL = _OL_Open() $aResult = _OL_ItemFind($oOL, "*Calendar", $olAppointment, "[subject]='" & $sSubject & "'", "", "", "EntryID") $aPatten = _OL_ItemRecurrenceGet($oOL, $aResult[1][0], Default) $oItem=_OL_ItemRecurrenceSet($oOL, $aResult[1][0], Default, $sStartDate, $sStartTime, int($sCount), $sEndTime, $sFREQ, $iDayOf, "", "") _OL_ItemSend($oOL, $oItem) _OL_Close($oOL)

Hello, Trying to reschedule a repeating meeting which seems to work OK using _OL_ItemRecurrenceSet but we found a problem in that if we use _OL_ItemSend to send the notifications then there will be 2 meeting items listed in the Outlook calendar. If we don't send then users on the other end don't receive the meeting update. Any suggestions for updating the meeting schedule and sending out updates without getting a new entry on the Calendar? Thanks.

My apologies, the Options->Encrypt Mail and Options->Sign Mail are contributed by an add-in. We're not currently using the built in X.509 certificates. That said I had some luck following the method in the KB article to at least read and attempt to set the regular security settings under Options->More Options->Security Settings...

I can for testing purposes but the current 3.3.8.1 is frozen for the time being in our environment.

We're current running AutoIt version 3.3.8.1

Any samples you could provide would be greatly appreciated.

I was wondering if there are methods to send a message that can be signed and / or encrypted. Basically I just want to mimic the settings (this is on Outlook 2013): Options->Encrypt Mail Options->Sign Mail when sending a new memo. I saw this article: http://support.microsoft.com/kb/2636465 but was hoping for a more straigtforward approach. Is there a way to check if these properties are set as well? Thanks.

The latest UDF didn't have any effect on the outcome, still can't move the mail message to a new folder. I recreated the test user account to make sure everything was clean and reran the example script. Now get: "Error creating test environment. @error = 300, @extended = 5" The Outlook-UDF-Test that was created was difficult to remove as well: "Cannot move the items. Cannot move folder; access is denied. To check your permissions for the folder, right-click the folder, and then click Properties on the shortcut menu. See the folder owner or your administrator to change your permissions."

Running: Outlook 2013 I can try the latest UDF tomorrow and report back. As for the _OL_ItemMove example script: No, it seems to think the environment already exists. "Testenvironment already exists. Should it be deleted and recreated?" If I click Yes I get: "Error creating the test environment. @error = 2, @extended = 2" If I click No I get: "Error: Subscript used with non-Array variable." on line 18 Granted that example is working on tasks vs. mail as well. Thanks.

That document seems to indicate the issue is moving from one EAS store to another EAS store. In this case we're just moving a mail message from the Inbox to a test folder under the same user. This works OK when done manually.

Hello, Having a problem with _OL_ItemMove issuing: OutlookEx UDF version = 0.9.0 @AutoItVersion = 3.3.8.1 @AutoItX64 = 0 @Compiled = 0 @OSArch = X64 @OSVersion = WIN_7 Scriptline = 2991 NumberHex = 80020009 Number = -2147352567 WinDescription = Description = Sorry, Exchange ActiveSync doesn't support what you're trying to do. Source = Microsoft Outlook HelpFile = HelpContext = 0 LastDllError = 0 I'm just trying to move a test email from the Inbox to a user generated folder. The _OL_FolderAccess returns the proper object as does the call to _OL_ItemFind. Just can't seem to get by the call to _OL_ItemMove. Here is a stripped down version of the test script: Global $oOL = _OL_Open() $sFolderName = "FolderTest" $aDstFolder = _OL_FolderAccess($oOL, "*\" & $sFolderName) $sSubject = "Test" $aItems = _OL_ItemFind($oOL, $aSourceFolder[1], $olMail, "[Subject]='" & $sSubject & "'", "", "", "EntryID") _OL_ItemMove($oOL, $aItems[1][0], Default, $aDstFolder[1]) _OL_Close($oOL) Hoping I'm just missing something obvious. Thanks.

Possible. The initial work around you provided is working well at this time.

Sorry that was your logic in our test script. Line 84 mapped to the $oReply.Save() in the _OL_ItemReplyEX method. I retried using your vanilla script and got the same error on line 53 which is the same $oReply.Save() in the _OL_ItemReplyEX method.

That method didn't work. It gives us the Active Sync error we previously encountered. COM Error Encountered in ResponseTest.au3 OutlookEx UDF version = 0.9.0 @AutoItVersion = 3.3.8.1 @AutoItX64 = 0 @Compiled = 0 @OSArch = X64 @OSVersion = WIN7 Scriptline = 84 NumberHex = 80020009 Number = -2147352567 WinDescription = Description = Sorry, Exchange ActiveSync doesn't support what you're trying to do. Source = Microsoft Outlook HelpFile = HelpContext = 0 LastDllError = 0

That seems to working well. Many thanks for the assistance!

Hi water, We've been trying to use OutlookEX to generate responses to meeting invitations but seem to be running into some issues. Basically we're doing: $items = _OL_ItemFind($oOL, "*Calendar", $olAppointment, ...) <--- This part works OK and we find the meeting invitation OK $responseItem = _OL_ItemModify, $items[1][0], Default, "ResponseStatus=" & $sResponse) <--- sResponse is passed into the script and matched the values for $olMeeting[Accepted|Declined|Tentative], just using _OL_ItemReply wasn't working at all for us in this case going over Exchange ActiveSync. _OL_ItemSend($oOL, $responseItem) We encounter a couple of issues. - Invite is marked with the wrong response at times (Tentative vs. Accepted) - Invite is marked as Accepted as None (vs. an actual time stamp) - Invite is Accepted but response is still not sent to invitee This general mechanism was working for us but stopped some time in the past month, we;ve been trying to isolate any changes to the environment but the only consistent change seems to be MS updates being applied. Any samples you could provide for responding to meeting invitations would be appreciated. Thanks.