OutlookEX UDF - Help & Support (III)

[water]

Glad you did find a solution and thanks for sharing

Edited November 13, 2015 by water

[davzell13]

Hi  

is it possible to pop this window with the udf ? 

I have a pop3 account without password.

I would like pop this windows to specify the password with the script.

Is not possible with registry modification.

thx

[water]

I've never worked with a pop3 account.
The OutlookEX UDF only allows to specify a password as parameter for _OL_Open. More details can be cfound on MSDN.

[nitekram]

@water...is there anyway to find out if the "New Mail Alerts" is blank or actually has an email in it *(the rule is created in Outlook, for when emails come in from certain people)? I am trying to create a function that will allow me to take more control over which window is active, as when an email comes in, it takes control (active) and it is APIA to have to start typing again - after you click into your recent active window.

 

EDIT, by default it is hidden until email arrives, maybe that is the key - going to test now.

 

Edit, nope not able to with this, yet I am not sure this is the right command?

If WinGetState('New Mail Alerts') = 15 Then ContinueLoop ; 1 = Window exists 2 = Window is visibe 4 = Window is enabed 8 = Window is ative

 

Edited November 24, 2015 by nitekram

[water]

I wouldn't automate the GUI. I would either check the number of unread mails in the Inbox (will grab all mails even those which arrive while your computer is shut down) or wait for the new mail event to be triggered (only grabs those mails that arrive while the script is running).
Which one would you prefer?

[nitekram]

I was wanting something like this to work: or for the very least something that will turn off the Alert Window becoming the Active Window.

Global $hNewMail = ''

While 1 
    $hNewMail = WinActive("[active]", "")
    
    ;    1 = Window exists 2 = Window is visibe 4 = Window is enabed 8 = Window is ative    
    If WinGetState('New Mail Alerts') = 15 Then ContinueLoop ; BitAND(WinGetState('New Mail Alerts'), 2) Then ContinueLoop
        Opt('WinTitleMatchMode', 3)
        If WinExists('New Mail Alerts') Then WinActivate($hNewMail)
        Opt('WinTitleMatchMode', 1)
    EndIf
WEnd

But if either of your methods will do the same thing, that would be the one the I would like to use LOL

[water]

Can't you switch off the "New Mail" alert and run your own?

[nitekram]

That would work, but I tried to use your rule creator before and was lost...as long as I was still able to get the ones that my rules are set for now - that would be great.

[water]

Which version of Outlook do you run?
I think you can define a rule to run an Exe every time a new mail arrives.
If you like I'll check as soon as I'm at a Windows PC again.

[nitekram]

Office version 2013...and thanks for any help you share my way.

[nitekram]

@water...I missed what you were saying...I am going to look at this issue again - thanks for the hint, as I believe creating EXE will work

[water]

I can't test the rule to create an Exe in Outlook at the moment because Trend Micro seems to block my efforts.
Now I need to convince our TM guys

[nitekram]

This works

#include <GUIConstantsEx.au3>


EmailAlert()

Func EmailAlert()
    Local $hNewMail = ''

    $hNewMail = WinActive("[active]", "")
    Sleep(200)

    Local $hGUI = GUICreate('new email alert')
    Local $idOK = GUICtrlCreateButton("OK", 310, 370, 85, 25)
    GUISetState(@SW_SHOW, $hGUI)

    WinActivate($hNewMail)

    ; Loop until the user exits.
    While 1
        Switch GUIGetMsg()
            Case $GUI_EVENT_CLOSE, $idOK

                ExitLoop

        EndSwitch
    WEnd
EndFunc   ;==>EmailAlert

 

...though I would still like to determine who the email was from - I guess I could create a different EXE for each of the rules, and therefore allow met to put more information into the GUI to state where it was coming from.

 

Thanks again for your help.

[water]

Or you could try my _OL_Example_NewMail_Event.au3 in the Example scripts thread for Outlook (please see my signature).

[nitekram]

This seems to work, but I have a question about how it works? There does not seem to be any call to the function with adlib or a simple call...I would like to add this to my already running script, and I am just not sure how it will work. Testing now you example now! By the way it does work on 2013

#include "OutlookEX\OutlookEX 1.0.0.0\OutlookEX.au3"
; *****************************************************************************
; Example Script
; Handle Outlook NewmailEX event when a new mail arrives.
; This script loops until Shift-Alt-E is pressed to exit.
; *****************************************************************************
HotKeySet("+!e", "_Exit") ;Shift-Alt-E to Exit the script
MsgBox(64, "OutlookEX UDF Example Script", "Hotkey to exit the script: 'Shift-Alt-E'!")

Global $oOApp = ObjCreate("Outlook.Application")
Global $test = ObjEvent($oOApp, "oOApp_")

While 1
    Sleep(10)
WEnd

; Outlook 2007 - NewMailEx event - http://msdn.microsoft.com/en-us/library/bb147646%28v=office.12%29.aspx
Func oOApp_NewMailEx($sOL_EntryId)

    Local $oOL_Item = $oOApp.Session.GetItemFromID($sOL_EntryId, Default)
    MsgBox(64, "OutlookEX UDF Example Script", "New mail has arrived!" & @CRLF & @CRLF & _
            "From:    " & $oOL_Item.SenderName & @CRLF & _
            "Subject: " & $oOL_Item.Subject)

EndFunc   ;==>oOApp_NewMailEx

Func _Exit()
    Exit
EndFunc   ;==>_Exit

 

[water]

Outlook triggers an event when a new mail arrives. The AutoIt script registers a function to grab this event (ObjEvent line) and process the new mail.

[nitekram]

That Sir, is very cool...now I just have to create a INI GUI to create the rules, and I am set. I thank you very much for your great example and help.

[water]

Glad to be of service

[nitekram]

Sorry, I have a question. When I try to get the length of the string for the subject line, it does not appear to work correctly. Here is what I have but it never seems to get the whole subject line - any ideas?

expandcollapse popup

; Outlook 2007 - NewMailEx event - http://msdn.microsoft.com/en-us/library/bb147646%28v=office.12%29.aspx
Func oOApp_NewMailEx($sOL_EntryId)
    If @UserName = 'UserName' Then
        Local $oOL_Item = $oOApp.Session.GetItemFromID($sOL_EntryId, Default)
        #cs
            MsgBox(64, "OutlookEX UDF Example Script", "New mail has arrived!" & @CRLF & @CRLF & _
            "From:    " & $oOL_Item.SenderName & @CRLF & _
            "Subject: " & $oOL_Item.Subject)
        #ce

        Local $hNewMail = ''

        $hNewMail = WinActive("[active]", "")
        Sleep(200)
        Local $iWidth = StringLen("Subject: ") + StringLen($oOL_Item.Subject)
        Local $hGUI = GUICreate('New Email Alert', $iWidth + 300, 200)
        Local $idOK = GUICtrlCreateButton("OK", 110, 150, 85, 25)
        Local $idLable01 = GUICtrlCreateLabel("From:    " & $oOL_Item.SenderName, 10, 10)
        Local $idLable01 = GUICtrlCreateLabel("Subject: " & $oOL_Item.Subject, 10, 50)

        GUISetState(@SW_SHOW, $hGUI)

        WinActivate($hNewMail)

        ; Loop until the user exits.
        While 1
            Switch GUIGetMsg()
                Case $GUI_EVENT_CLOSE, $idOK
                    GUISetState(@SW_HIDE, $hGUI)
                    ExitLoop

            EndSwitch
        WEnd


    EndIf
EndFunc   ;==>oOApp_NewMailEx

 

[water]

I suggest to not have long running code in a function to handle events.
As AutoIt is single threaded you could miss a mail while processing the previous one.

Can you please elaborate on what you mean by "it does not appear to work correctly"?