I have an agent that is supposed to prefix the Subject of every email that comes in with "SUBMITTAL: ". I have set this up to run with the “After new mail has arrived” trigger. It IS working, but NOT immediately ‘after new mail arrives’. Now, color me dumb, but doesn’t a ‘trigger’ called “After new mail has arrived” indicate that it should work immediately after an email is delivered to the Inbox? Why the heck is there a delay?
The delay is significant because I have a .NET Windows Service that reads the emails in the Inbox. The Windows service runs every 15 minutes. What is happening is that the service is reading the emails BEFORE my “After new mail has arrived” triggered agent…how can that be?!
Julie K, I know you are swamped, but could or anyone else offer a liitle help in explaining when the “After new mail has arrived” trigger actually triggers, because it doesn’t appear to be living up to its name.
Subject: “After new mail has arrived” trigger not triggering as expected
“After new mail arrives” is actually an agent schedule, not an event trigger. It’s frequent, but not instantaneous. (And it does happen after new mail arrives, so there are no promises broken.) If you can’t afford any delay, use “Before new mail arrives”.
Subject: RE: “After new mail has arrived” trigger not triggering as expected
Okay, okay no promises broken? Then this ‘trigger’ is NOT a ‘trigger’ at all, but a “frequently” (not secheduled) run agent. Personally, that name should be filed under the “bad play on words” category. “…hey dude, we said ‘after’…as in sometime after…as in some indetermined time in the future…” They should have a disclaimer on it like Java’s garbage collection has “…there is no way to determine when GC will run so don’t rely on it for your code…”
Sorry to sound so pessimistic, but after dealing with real events in .NET, I think of triggers as “click-BANG!”…not “click-wait-wait-wait-maybe…no, just kidding-wait-okay now-BANG”
I’ll give the “Before new mail arrives” a go, but if I read Julie’s notes correctly, what I want to do won’t be possible.
Subject: RE: “After new mail has arrived” trigger not triggering as expected
I appreciate your frustration, but the reality is not as bad as you describe, but still less than you want.
Check the AMgr_NewMailEventDelay INI variable. It defines the time, in minutes, that the Agent Manager delays before scheduling a new mail-triggered event. The default value is 1 minute.
Also check the AMgr_NewMailAgentMinInterval variable which specifies the minimum time, in minutes, between execution of the same new mail-triggered agent. The default is 0. But this may have been increased by someone to prevent a continual string of mail agents from possibly slowing the server.
Subject: RE: “After new mail has arrived” trigger not triggering as expected
I do appreciate the feedback and direction to the truth. The bottom line is that the available triggers fall short of what I need.
Please understand, we have over 100 servers in two domains all over the world that are managed by IBM. It is not practical to go through the hoops with IBM to have them change an INI setting on one mail server. I think getting a bill through Congress would be easier.
No, I will handle all I need through the Windows Service using the Domino Interop (thank you Gary Devendorf!!!) since Notes doesn’t have what I need.
