To the best of our knowledge, there is no problem with PingPlotter 2.60 and sending emails.
It may be that the association between the alert you created and the target you want monitored was changed / removed somehow.
Make sure there is a bracket around the hop number of the hop you'd like to have monitored. Most likely, you want to monitor the final destination. If your route is 8 hops long, make sure the final hop shows with brackets, like this: [8]. If you're just seeing the hop number, then you need to associate the alert to the target (btw, this is *by far* the most often encountered problem with alerts).
Not firing alert (but configured on hop 10 - the [10] shows that the alert is associated with hop 10. Hops 9 and 11 do not have alerts associated):
That same alert, but now the alert conditions have been met:
Another way to check is to go in to the alert setup screen and hit the "Show Targets" button. If the target address isn't listed there, then you're not going to get alerted when that site stops responding. That's not the best place to add new targets, but is a way to check it out.
For more details on configuring (and troubleshooting!) alerts, see some of these resources:
Please let us know if this gets things working for you.
- Pete