Ray -
I am sorry that I have to get back to this matter, but after putting a lot of energy into getting to the source of the BCC "problem," I am more convinced than ever that "something" is being affected by the Sesame design itself.
I have contacted technical support for both my ISP (Road Runner) and my E-mail provider (Incredimail) and all the tests we made show no problem with a BCC.
Yet when I make the same test from my Sesame database, the BCC fails.
First let me give you some background. My personal E-mail account is
SWulwick@tampabay.rr.com
I have another account for my business E-mail which is
Spencer@SilversOlutionS.org
When E-mail is sent to my business account, two things happen:
1) The sender of the E-mail receives an acknowlegement (from my business account) that the E-mail was received and that I would reply to them as soon as possible.
2) The incoming business E-mail is forwarded to my personal road-runner account.
When
USING INCREDIMAIL, it is sent as follows:
From: SWulwick@tampabay.rr.com
To: Swulwick@tampabay.rr.com
CC: (None entered)
BCC: Spencer@SilversOlutionS.org
Sure enough, I get 3 pieces of E-mail (1) The E-mail addressed to me (2) the "acknowledgement" from SilversOlutionS that my E-mail was received and (3) the E-mail BCC'd to SilversOlutionS and forwarded to me.
That's as it should be. As far as I'm concerned this should be "proof positive" that neither my ISP nor my E-mail provider is prohibiting the sending of a BCC, when I'm the recipient of the BCC.
YET, when I execute my E-mail from within my
SESAME DATABASE to do the same thing, the BCC fails. I get only the original E-mail. I do not get an acknowledgement from SilversOlutionS that any message has been received nor do I get the forwarded copy from SilversOlutionS.
That leaves only
TWO VARIABLES (as far as I can tell) and
BOTH of these variables are
WITHIN SESAME. The two variables are (1) the database design itself and (2) the coding that I use to implement @sendmail.
As for the latter (my coding) I have checked it dozens of times and it seems to me that I have it done correctly. In fact when you had me modify my programming to send you the BCC, it woked just fine. That tells me that my coding is correct (although here is the code once again, in case I am overlooking something).
var ii as Int
ii = [color=Maroon]@SendMail("SMTP-SERVER.TAMPABAY.RR.COM", vsubject, "swulwick@tampabay.rr.com",EmailAddress,"","Spencer@SilversOlutionS.org"[/color], "Hi " + First Name + ", " + @newline()
+ @newline() + vlastemail + @newline() +@newline() + "Spencer Wulwick" +@newline() + "Silver sOlutionS of Tampa, Inc." + @newline() + "www.SilversOlutionS.org")
If ii = "0"
then
@Msg(" ****************************** YOUR E-MAIL IS BEING PROCESSED ****************************** ")
LastEMail = ("The following e-mail was sent to " + First Name + " " + Last Name + " on "
+ @month$(@date) + " " + @dom(@date) + ", " + @year(@date) + " at " + @time + @newline() + @newline()
+ "Hi " + First Name + ", " + @newline () + @newline() + vlastEMail + @newline() + @newline() + "Spencer Wulwick" +@newline() + "Silver sOlutionS of Tampa, Inc." +@newline() + "www.SilversOlutionS.org")
Subject = vsubject
If there
IS a problem with my coding, then I need help, because I just can't see it.
If there is
NOT a problem with my coding, then, as far as I can tell, that leaves only one variable, and that variable is within the design of Sesame.
Knowing that neither the ISP nor the E-mail provider has anything to do with the problem, I would really appreciate it if the design could be explored further.
Apparently, I am not the only person who has had this problem. Others have said they circumvented it by sending the E-mail to a text file and by other means.
Steve, in Texas, said:
Quote:Last time I tried it (months ago), I was not able to send to any CC or BCC recipient...Ray mentioned it was likely an issue of my ISP. I have been working around this by using programming to send a seperate email to the other recipients, seperately. It's been working fine, though not as convenient.
It would be a great service to those of us using this feature if it could be resolved once and for all.
Thanks much!