Emails with unwanted cc

[Steve Workings]

Tonight this happened again, and it's happened twice before, I don't know why. This is for an SAAS application, so there are many companies using it, and no one company should see anything from another, of course.

I have a runtime instance that processes a work queue -- it simply runs on a timer every 60 seconds, works wonderfully.

Much of what that runtime does is process and send emails -- I use the email_send2() function. And it sends thousands of emails a month, just fine.

Except, tonight again, one user of one company showed us emails he received as a cc: recipient of another company's emails.

So, the Xbasic instruction for the email is in the work queue, of course, and it proved that this email was never constructed with a cc

And I have another function that stores a copy of the email just processed by the runtime instance, again proving that there was never a cc: recipient in the Xbasic.

So I can prove all over the place that there's no cc: in the emails going out, yet an apparently random user from Company A is getting Company B's emails as the cc: recipient.

And this is just what this user has showed us -- I have no idea if there might be others going out that aren't even reported to us. This isn't good at all.

So, any ideas where to look, what to do, how to figure out what's going on?

[kkfin]

Re: Emails with unwanted cc

Because your are using desktop runtime parts maybe something is not thread safe and obviously is not. Maybe solution to this special problem is to always clear cc before sending email.

[frankbicknell]

Re: Emails with unwanted cc

I use the email_send2() function and am not having any issues. I send the emails one at a time though.

[Steve Workings]

Re: Emails with unwanted cc

Thanks. Mine go one at a time as well.

Ken - Good suggestion - I'm going to amend my code with a specific Message.cc = ""

[Garry Flanigan]

Re: Emails with unwanted cc

Steve, my guess is you are sending emails in at least two parts of your script and Message.cc is being set to a value in an early part and later you do send another email with no cc so it uses the value set earlier. So Message.cc = "" as well as some or all all other Message values is a safe way forward in every block of email send code.

[Steve Workings]

Re: Emails with unwanted cc

Well, I've set the cc = "" in all my emails now.

It's possible what you and Ken think is the issue, though why it only happens once in a while would seem to be a good question.

The simplified version of the work queue processor execution function is:

sql = "select * from WorkQueue where IsCompleted = 0"
cn.execute(sql)
rs = cn.ResultSet
flag = rs.nextRow()
while flag
	do_text = rs.data("WorkData")
	for each line in do_text
		evaluate_template(line.value)
	next
	flag = rs.nextRow()
end while

This isn't always of sending emails, but emails make up a major portion of the days' work. Each email begins with the standard dim message as p but that just may not be enough.

I think I'm going to look into Evaluate_template_private() as well.

[Pat Bremkamp]

Re: Emails with unwanted cc

Do you delete message prior to dimming it?

[Steve Workings]

Re: Emails with unwanted cc

I had not, Pat, until this discussion pointed pretty strongly to the probable source of the problem. It's among the amendments I've made to quash this.

[Garry Flanigan]

Re: Emails with unwanted cc

I don't think Evaluate_template_private() will be very useful in any multi-lined code as each line is evaluated in its own variable name-space.
The key here is really as Pat suggested, for the work queue processor, delete all pointer variables then dim. I say all because over time new scripts get added and who knows what they may contain. We are creatures of habit and tend to use the same variable names over and over in similar situations.