+The A-Team Posted April 27, 2012 Share Posted April 27, 2012 There's a definite problem with notifications. In some cases, not following any noticeable pattern, notification (and owner) emails simply don't get generated. I suspect it hasn't been mentioned in detail before because since the email doesn't get sent, there's no way for the intended recipient to know there was supposed to be an email in the first place. Here are some examples I've encountered: January 25, 2011 - 3 new caches were published, but no "Publish" notification emails were sent out. I never received any emails, and after talking to other local cachers, they didn't receive them either. The publish logs in question are GL4ZVMAX, GL4ZVMAB, and GC2MX7N. I was able to get FTF on all 3, but only because I had a recurring PQ that captured them the morning they were published. February 7, 2012 - Another cache was published without any emails being sent (GL7CTN2H is the publish log). I again confirmed with others that they didn't receive an email. April 5, 2012 - A cacher logged a find on one of my caches (GL7TR49P is the find log). No email. The only reason I realized they had logged was because it's an Earthcache and they had emailed me their answers. I was wondering why it was taking them so long to log their find, so I checked the website and discovered they had indeed logged already. As I mentioned in the post title, it is absolutely not a spam filter problem. I checked each time just to make sure, but in the case of the new caches listed above, NO ONE received emails, regardless of email provider. They simply were not sent. If anyone wants more examples, I fully believe I could find many if I match up the emails I have on file to the logs on the site. I seem to remember a few of these occurences a few years ago, and I could probably find them again if needed. Most of the time, not receiving an email is simply an inconvenience, or even less. However, if the email that didn't get sent was a NM, NA, or Reviewer Note, it could result in badly-needed maintenance being missed, or the archival of a cache. Unfortunately, this problem seems to be very intermittent, which are the hardest type of problem to troubleshoot. Still, it is a problem that needs to be investigated. Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.