Quote:Mark -
MIA CULPA!!!
I found something I was overlooking when modifiying my mass update programming. In case anyone's interested, I'll be glad to explain it (after I get some sleep).
I'll also share the 7 tests (with minor variations between them) that I made.
But the bottom line is that I was wrong about one point ... and that might just prove helpful. When I add a CC before the BCC, it is properly executed.
I receive 3 copies (To, CC, BCC) (along with the notification that comes from SOS to acknowledge receipt of the mail).
So ... that being the case, I would very much appreciate it, if I would be able to try the programming WITHOUT sending the "blank" value for the CC (I believe you referred to it as an RCPT).
No. They are not the same thing. One is derived from the other.
Quote:I cannot help but feel that there MUST be a solution for this and I'll do everything I can to help uncover it. "People" created computers, so "people" ought to be able to make them perform any way we want.
There is a solution. The problem is that there are many solutions, and what works on your SMTP server, may not work on mine. When SMTP was first developed, a client could connect to any SMTP server in the world, and use it to send email. Later, they discovered that that was being abused by spammers, and some SMTP servers (like yours in FLA) decided that they would only except email from servers in the same stated domain - and did so without a change in SMTP. Later still, other servers decided that that was too inconvenient and started requiring a password and login (the EHLO format). Later still, others needed that login and password to be pre-encrypted. Even later, others decided to use a different encryption scheme. On and on...
The changes I just described, encompass only one portion of the SMTP format - the first line sent by a client to the server. SMTP has several hundred other "portions". Many of which have undergone similar transitions over the years.
Dedicated email programs can afford tens of thousands of lines of code needed to accomodate the variations, developments, and new capabilities of SMTP servers. Sesame has to, and should, develop to the most common denominators. When the @sendmail code was originally written, the "HELO" format was most common. Now, the "EHLO" format is most common. Because that is a major change, Sesame 2.0 implements a "dropback" - using EHLO as the default, but dropping back to HELO if EHLO does not succeed.
Because dedicated email programs usually support either command line or DDE, Sesame users can (in an some cases should), use @Shell or @ASynchShell (or in 2.0 - @CreateProcess) to take advantage of the familiarity and capabilities of their own email programs. If your email program cannot be used from command line, here are the first results from a simple Google search for "command line email client":
http://www.febooti.com/products/command-line-email/http://www.beyondlogic.org/solutions/cmdlinemail/cmdlinemail.htmhttp://email-tools.softlandmark.com/command_line_mail_tools/Softabar_Command_Lin...http://caspian.dotconf.net/menu/Software/SendEmail/http://www.exclamationsoft.com/exclamationsoft/default.asphttp://www.blat.net/194/http://www.softpedia.com/get/Internet/E-mail/E-mail-Clients/AutoMail.shtmlhttp://www.alphaworks.ibm.com/tech/NotesCliEmail?open&S_TACT=105AGX13&S_CMP=LSDL...http://www.soft32.com/download_9676.htmlThere are many hundreds of these, ranging in price from free to $50. Linux comes with the original "mail" program as part of the OS.
Quote:And, by the way, you said that you tried it ... but you didn't say what the outcome was. Did it, by any chance, succeed?
As I stated, it worked for me on the two mail servers I have access to at home (Verizon and Adelphia). Both of which require the EHLO format, as opposed to the HELO format your mail server uses (I checked yours as well using telnet). So when you stated that putting a CC in the @sendmail did not work for you, I believed that your server was having a different problem.