Occasionally, the email triggers experience an error with the mail server and deactivate themselves automatically... Often we might be in the middle of a reboot, etc when this happens. Would it be possible to just suspend them for a few minutes when they encounter an error?

I apologize if I've missed this option somewhere...

Thanks,
Dustin

It would be interesting to get the exact error from your log file. Because the Trigger was inactivated due to an error.

---

Trigger error: Error in Mail Trigger(2), ex: A connection attempt failed because the connected party did not respond after a period of time...

We'll see how we can tackle this the best way - our timeout is already quite long (3 minutes).

---

I figured out the cause of it... Some exchange servers do not enforce POP3 protocols...

Here is an article on resolving it:
http://technet.microsoft...us/library/aa996686.aspx 

Basically, when messages would not end in the correct ending, VisualCron would throw the error and deactivate the trigger.

After repeated testing, I figured out it was dying at the same message each time... So this is probably not something VisualCron should address. The timeout setting is sufficient.

Sorry for the trouble.

It would be nice to limit the number of concurrent connections at a time... I.e. If I have 10 triggers set against one Pop3 connection, they all seem to run at the same time. I know I can set intervals up to help this, but it feels like the connection should have a queue as well.

Just a thought.

Thanks again for a great product!

Thanks for the feedback. We will see what we can do about this. I am moving this post to Feature Requests forum.

---

Hi,

this version has two new settings on the email trigger;

1. number of retries
2. connection timeout

Please test it.

http://www.visualcron.co...m.aspx?g=posts&t=940 

---