Outlook automation in a Shared mailbox - (Moved)

[Gowrisankar]

Dear members of the forum,

I'm working on a project where incoming emails are to be analyzed based on the subject line and moved to various folders in a shared mailbox.

I'm using "OutlookEx.au3" of @water. The macro can can move emails  to any folder that I newly create. But the macro couldn't move emails to specific folders that are already existing.

I checked the permission levels of those folders and found that nothing is wrong with that. The function I use is _OL_ItemMove.

Please guide me how to proceed further. Thanks in advance.

-Gowrisankar.

 

[water]

The value of @error and @extended after _OL_ItemMove should shed some light onto the subject.

[Gowrisankar]

2 minutes ago, water said:

The value of @error and @extended after _OL_ItemMove should shed some light onto the subject.

@error is 1 and @extended is 4

[water]

@error 4 stands for: Specified folder could not be found.

Can you please post the _OL_ItemMove statement you run?

[Gowrisankar]

16 minutes ago, water said:

@error 4 stands for: Specified folder could not be found.

Can you please post the _OL_ItemMove statement you run?

_OL_ItemMove($oOutlook, $sEntryId1, Default, $sDestinationFolder)

(Example : $sDestinationFolder = "abc.xyz@abc.com\Inbox\Central")

The folder is present in mailbox and I've even checked the spellings, extra punctuation, spaces etc., and everything is correct. 

Edited November 22, 2018 by Gowrisankar

[Melba23]

Moved to the appropriate forum, as the Developer General Discussion forum very clearly states:

Quote

General development and scripting discussions. If it's super geeky and you don't know where to put it - it's probably here.

---

Do not create AutoIt-related topics here, use the AutoIt General Help and Support or AutoIt Technical Discussion forums.

Moderation Team

[water]

Can you please test to access the Folder using _OL_FolderAccess?
@error and @extended will then give better error Information.

[Gowrisankar]

3 hours ago, Melba23 said:

Moved to the appropriate forum, as the Developer General Discussion forum very clearly states:

Moderation Team

My sincere apologies @Melba23.

[Gowrisankar]

On 11/22/2018 at 5:06 PM, water said:

Can you please test to access the Folder using _OL_FolderAccess?
@error and @extended will then give better error Information.

@water, I tried _OL_FolderAccess and got the following. @error = 4 ; @extended = 3

As in the example, "abc.xyz@abc.com\Inbox\Central" the @extended denotes that error is in accessing the folder "Central".

Edited November 27, 2018 by Gowrisankar

[water]

Can you please post the full line where you call _OL_FolderAccess (means: Do you set parameters $iFolderType or $iItemType?).

[Gowrisankar]

3 minutes ago, water said:

Can you please post the full line where you call _OL_FolderAccess (means: Do you set parameters $iFolderType or $iItemType?).

@water, I dont' call _OL_FolderAccess.

I use item move statement as below.

_OL_ItemMove($oOutlook, $sEntryId1, Default, $sDestinationFolder)

I presume _OL_FolderAccess is called from _OL_ItemMove.

[Gowrisankar]

This is the code I use for Folder access... please ignore the previous response. I mistook it.

Global $aFolder = _OL_FolderAccess($oOutlook, "abc.xyz@abc.com\Inbox\Central")

Global $aFolderDisplay[6][2] = [[$aFolder[0]],["","Folder object"],["","Default item type for the folder"],["", "StoreID where the folder resides"],["", "EntryID of the folder"],["", "Folder path"]]

$aFolderDisplay[1][0] = $aFolder[1]

$aFolderDisplay[2][0] = $aFolder[2]

$aFolderDisplay[3][0] = $aFolder[3]

$aFolderDisplay[4][0] = $aFolder[4]

$aFolderDisplay[5][0] = $aFolder[5]

_ArrayDisplay($aFolderDisplay, "Folder successfully accessed.")

Edited November 27, 2018 by Gowrisankar

[water]

OK, let's strip it down as far as possible:

Global $aFolder = _OL_FolderAccess($oOutlook, "abc.xyz@abc.com\Inbox")
ConsoleWrite("Inbox: @error = " & @error & ", @extended = " & @extended & @CRLF)
Global $aFolder = _OL_FolderAccess($oOutlook, "abc.xyz@abc.com\Inbox\Central")
ConsoleWrite("Inbox\Central: @error = " & @error & ", @extended = " & @extended & @CRLF)

Please post the output of the SciTE console pane.

[Gowrisankar]

21 minutes ago, water said:

OK, let's strip it down as far as possible:

Global $aFolder = _OL_FolderAccess($oOutlook, "abc.xyz@abc.com\Inbox")
ConsoleWrite("Inbox: @error = " & @error & ", @extended = " & @extended & @CRLF)
Global $aFolder = _OL_FolderAccess($oOutlook, "abc.xyz@abc.com\Inbox\Central")
ConsoleWrite("Inbox\Central: @error = " & @error & ", @extended = " & @extended & @CRLF)

Please post the output of the SciTE console pane.

I'll get back to you after 3-4 hours @water. Thanks for your support.

[Gowrisankar]

@water, I'm able to access "abc.xyz@abc.com\Inbox". Array with folder details are populated.

 When I tried to access ""abc.xyz@abc.com\Inbox\Central", the following error was popped up.

"Inbox: @error = 4, @extended = 3"

[water]

Do you run your script or mine?
My script does not show a "pop up".

If you run my script then the message you posted tells us that accessing the Inbox does not work. Because when there is a problem with "Central" the message would tell "Inbox\Central" not just "Inbox".

Please run my 4-line-script and post the exact output (all lines) you get from SciTE.

[Gowrisankar]

@water, the problem is within a client machine and they don't have AutoIt installed. So I shared 2 exe files one for "Inbox" and one for "Inbox\Central" with array display for positive results and message box with @error and @extended for negative results.

That is how I got the result as @error = 4, @extended = 3

[water]

Does the client machine have a different language setup?
I have a german setup and hence my directory structure would be named "abc.xyz@abc.com\Posteingang\Central"

[Gowrisankar]

No such different language. They use English only. I have seen it many times.

[water]

Can you try to access the Inbox\Central folder on your machine?
If it works we know it is related to a single/few computers. If it doesn't work at all we know it is a global problem.