[C Braithwaite]

Originally Posted by tpearl5

Okay, a couple things:

• I setup a usergroup for 'bounced emails' - when setting the plugin to move users with bounced e-mails to this group, it does not save.
  
• The stats page has two rows for 'emails sent' and three for 'bounced emails'
  
• I got about 30 bounced emails registered, but my email for bounced emails had almost 900 bounced messages. I'm not sure if the cpanel pipe to program was working properly or not.

I will look into the issue with the usergroup saving (it does actually save, but when you load the page it decides it doesnt want to show the saved group selection properly - i thought that this was a bug only with vbulletin 3.6x but apparantly not)
i have fixed the reports page for the next release - the missing column was supposed to be "returning users" but it is actually bugged so don't count that number as accurate.
when you say your email has 900 messages - do you mean in your inbox? it's not supposed to save the messages in an inbox it should pipe to the program and not even reach your inbox? is the pipe set up correctly? are any of the emails on the reports showing as bounced?

Originally Posted by dfc005

I had both these problems. It did eventually saved though.

Unfortunately, I'm still getting the problem where it sends multiple emails. Have double and triple checked and I'm using the 1.2.8 version.

I have a feeling it might be the way you are sending the messages. How exactly are you starting the mail send? I have a very large board. So I get the feeling that as multiple users visit the site, they are in fact all getting the same set of emails and initiating the same send. I think a cronjob or something similar would be much more effective.

i am using the vbmail command and i have tested and tested and tested and i ant find any evidence of a duplicated email. it could well be the case that the same query is being executed like you suggest. in vbulletin's options it mentions about big boards and multiple emails being sent, and suggests the use of enabling it's table locking option to avoid such an error. have you enabled this option? i will code in a short delay to stop the same query from being executed twice (assuming this is the reason behind the multiple emails)

thanks for your feedback, comments, and suggestions. :up: