Thank you for the assistance, Charlie! SmartList sent me 2 separate emails.... #1 was an error message. Text follows: Unknown command This. This archive server knows the following commands: get filename ... ls directory ... egrep case_insensitive_regular_expression filename ... maxfiles nnn version quit Aliases for 'get': send, sendme, getme, gimme, retrieve, mail Aliases for 'ls': dir, directory, list, show Aliases for 'egrep': search, grep, fgrep, find Aliases for 'quit': exit Lines starting with a '#' are ignored. Multiple commands per mail are allowed. Setting maxfiles to zero will remove the limit (to protect you against yourself no more than maxfiles files will be returned per request). Egrep supports most common flags. If you append a non-standard signature, you should use the quit command to prevent the archive server from interpreting the signature. Examples: ls latest get latest/12 egrep some.word latest/* #2 message arrived four minutes later. It executed the command and attached the most current newsletter from the archive. So, this has half worked! Any suggestions as to eliminate the first message indicating there was an error? Thank you again! Scott
At 12:29 PM -0400 7/9/01, Scott M. Lancey is rumored to have typed:
<DIV>Thank you for the assistance, Charlie!</DIV> <DIV> </DIV> <DIV>SmartList sent me 2 separate emails....</DIV> <DIV> </DIV> <DIV>#1 was an error message. Text follows:</DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2><FONT size=3>Unknown command This.
Um...including the rest of the stock error message from SmartList isn't very helpful, since we all know what it looks like. Obviously, SmartList did not like the word, "This" that was included in your message somewhere.
<DIV>#2 message arrived four minutes later. It executed the command and attached the most current newsletter from the archive.</DIV> <DIV> </DIV> <DIV>So, this has half worked!</DIV> <DIV> </DIV> <DIV>Any suggestions as to eliminate the first message indicating there was an error?</DIV>
You aren't showing is what you're sending (and I'd bet you're not even _aware_ of what you're sending); my guess is that you're sending a non-blank message (probably filled with HTML data) that SmartList is somehow tripping over. (I will admit I don't know where the word, "This" might have come from...I would certainly have understood had SmartList complained about, "<DIV>.") Might I suggest you switch to plain text in Outlook Express before repeting the experiment again? Charlie
participants (2)
-
Charlie Summers -
Scott M. Lancey