Another problem here with 1.9.3.3 . I've found that the Watch Forum and Watch Topic features don't really work correctly at all - the last time I tried it, I received 78 notification messages because of one reply posted on the forum. Another person received 18 at the same time (though he was watching the topic, not the forum). I've disabled the CreateWatchEmail function temporarily, but I'll need to figure it out. Does anybody have any ideas?

This is issue that should be resolved before beta. Thanks for reporting.

---

Any suggestions for ways to resolve the problem now? I've been poking around in the code, but I haven't been able to find an obvious trouble spot.

Hm, I am not seeing that issue in the latest repository code. In fact, topic and forum subscriptions seem to be working fine for me... do you have any other details that might help? (or, maybe this was fixed by someone since the alpha?)

Hm, I am not seeing that issue in the latest repository code. In fact, topic and forum subscriptions seem to be working fine for me... do you have any other details that might help? (or, maybe this was fixed by someone since the alpha?)

I'm using the version linked from this thread:
http://forum.yetanotherforum.net/yaf_postst5108_YAF-v1933-ALPHA-UPDATED-262008.aspx 

I can't really figure it out. I've made some changes to the code, but nothing that would affect the watch emails. The feature seems to work, it just sends way too many emails. Other messages sent through the same SMTP server are not duplicated, so I don't think that's the problem.

Something interesting is that I disabled the CreateMail.CreateWatchEmail(nMessageID) call in yaf/pages/postmessage.ascx.cs, but that did not disable the sending of the watch emails (and it did not fix the duplicate message problem). I eventually just commented out the contents of that function and recompiled as a temporary measure. I'm trying to track down the source of the problem now.

I "solved" the problem by just ditching the built-in watch email code entirely and writing my own in the posts.ascx.cs and postmessage.ascx.cs files.

Okay, but this is fixed in newer versions of v1.9.3 much more elegantly.