ShellSend RSS: ShellSend Bad Examples https://www.binaryfortress.com/ShellSend/Discussions/RSS/?TopicID=e766cb4e-bc8b-4952-a114-ff66876f6339 ShellSend RSS: ShellSend Bad Examples Mon, 04 May 2026 01:12:26 GMT en hourly 1 https://www.binaryfortress.com/ShellSend/Discussions/RSS/?TopicID=e766cb4e-bc8b-4952-a114-ff66876f6339 RE: ShellSend Bad Examples https://www.binaryfortress.com/ShellSend/Discussions/View/shellsend-bad-examples/?ID=e766cb4e-bc8b-4952-a114-ff66876f6339#2 Tue, 06 Apr 2010 16:10:32 GMT Binary Fortress Software https://www.binaryfortress.com/ShellSend/Discussions/View/shellsend-bad-examples/?ID=e766cb4e-bc8b-4952-a114-ff66876f6339#2 ShellSend Thanks for bringing that to my attention, I can't believe I missed that. :) I have released a new build (version 1.2) that takes care of this:
http://www.binaryfortress.com/shellsend/

The new build comes with fixed command line examples, a license file and a instructions in a .txt file. Thanks! ]]> ShellSend Bad Examples https://www.binaryfortress.com/ShellSend/Discussions/View/shellsend-bad-examples/?ID=e766cb4e-bc8b-4952-a114-ff66876f6339 Fri, 02 Apr 2010 10:19:54 GMT Binary Fortress Software https://www.binaryfortress.com/ShellSend/Discussions/View/shellsend-bad-examples/?ID=e766cb4e-bc8b-4952-a114-ff66876f6339 ShellSend As far as I can see, your examples for shellsend are bad/broken

e.g.

[size=10pt][font=courier]shellsend.exe "user@host.com" "user@host.com" "smtp.gmail.com" "465" "1" "username@domain.com" "mypassword" "C:\File.txt"
This will send the contents of the file "C:\File.txt" to "user@host.com" through SMTP port 465 while using SSL and logging in as "username@domain.com" using the password "mypassword".
[/font][/size]

that didn't work, but the following syntax did:

shellsend.exe "user@host.com" "user@host.com" "smtp.gmail.com" "465" "1" "gmailusername" "gmailpassword" "subjectline" "C:\File.txt"

- username@domain is not relevant to a gmail example like this, just put "username" please
- subjectline was missing, so the syntax as per your example fails.

Maybe you could put a few more examples in also (but please check they work also !).

Regards,

Roy ]]>