ShellSend Discussions RSS

RE: ShellSend 2.1 Now Available!

Binary Fortress Software — Fri, 09 Dec 2022 19:20:48 GMT

Strange, I'm pretty stumped on why that's not working!

In any case, might be easier to just use the Send-MailMessage command in PowerShell. I actually use that here these days instead of ShellSend anyway

RE: ShellSend 2.1 Now Available!

Binary Fortress Software — Fri, 09 Dec 2022 14:15:05 GMT

Still seems to be same outcome for me. Please see attached. Anyway this is no big deal ....

RE: ShellSend 2.1 Now Available!

Binary Fortress Software — Fri, 09 Dec 2022 14:07:32 GMT

It seems to work here okay with that command. Can you double check the version number in the Properties > Details tab for the .exe? It should be 3.2.0.0 with a modified date of 12/1/2022.

Thanks!

RE: ShellSend 2.1 Now Available!

Binary Fortress Software — Mon, 05 Dec 2022 23:48:44 GMT

Thank you Owen, but I still see same results even with the newer version. Here is a sample test case:

c:\onedrive\cron\shellsend.exe "simonlee@me.com" "simonlee@me.com" "smtp.mail.me.com" 587 1 "simonlee@me.com" "xxxxxxxxx" "Check" "" "Testing 1 2 3"

(I x'ed out the password of course)

The result is as shown attached

RE: ShellSend 2.1 Now Available!

Binary Fortress Software — Mon, 05 Dec 2022 18:30:43 GMT

We've released a new version that should have this fixed up. Please let me know if you run into any troubles.

Thanks!

ShellSend 3.2 Now Available!

Binary Fortress Software — Mon, 05 Dec 2022 17:01:36 GMT

We're very excited to announce that ShellSend 3.2 is now available for download!

ShellSend 3.2 Changes

Fix: Resolved an issue parsing command line arguments for the body text and body text from file

Updating ShellSend

We encourage everyone to update to this new version today to take advantage of these improvements. If you would like to see a complete list of all the changes, please visit the ShellSend change log. Thank you to everyone who helped to test the beta versions, that feedback is what makes ShellSend so amazing. Thanks everyone!

RE: ShellSend 2.1 Now Available!

Binary Fortress Software — Mon, 28 Nov 2022 00:01:13 GMT

Hello I am a new user of ShellSend. I found that if you fill in both the filename and body, then it works. If you don't want to send a file and use "" as a placeholder for filename, and then try to add a body, then it doesn't work. IE., the message will have an empty body no matter what you supply.

ShellSend 2.1 Now Available!

Binary Fortress Software — Wed, 13 Sep 2017 16:10:22 GMT

We're very excited to announce that ShellSend 2.1 is now available for download!

ShellSend 2.1 Changes

Notice: Now requires the .NET Framework 4.6
Notice: ShellSend no longer supports Windows XP or Vista
Change: New icon
Change: General improvements and changes

Updating ShellSend

ShellSend Screenshots

ShellSend 2.0 Now Available!

Binary Fortress Software — Mon, 07 Jul 2014 10:00:00 GMT

We're very excited to announce that ShellSend 2.0 is now available for download!

ShellSend 2.0 Changes

Change: Adds a new optional parameter at the end to specify the email body text, instead of using a text file for the body text

Updating ShellSend

RE: Using ShellSend with Scheduled Tasks in XP

Binary Fortress Software — Tue, 01 Apr 2014 15:25:44 GMT

Ah yes, sorry about that, I had modified it when I was testing, forgot to change it back. Glad to hear it's all good now!

RE: Using ShellSend with Scheduled Tasks in XP

Binary Fortress Software — Mon, 31 Mar 2014 20:21:51 GMT

Hey Keith! I just figured it out. I had not noticed but there was a small error in the path for the text file.

Code
Copy
Select All

\"C:\shellsend\shellsend.txt\"

Should have been

Code
Copy
Select All

\"C:\program files\shellsend\shellsend.txt\"

That fixed the problem. Thanks again for your help!

RE: Using ShellSend with Scheduled Tasks in XP

Binary Fortress Software — Mon, 31 Mar 2014 20:16:07 GMT

Thanks Keith! I appreciate your help! That got the batch file working properly. The only problem I'm running into now is that the task fails to run. I get a status code of 0xffffffff. Does that mean anything to you?

RE: Using ShellSend with Scheduled Tasks in XP

Binary Fortress Software — Mon, 31 Mar 2014 19:46:30 GMT

There were a couple of issues that I found with your command. The "Notify Admin: Schedule Ran" was tripping it up because of the colon, and you had forward slashes in the shellsend.txt path. Also, the quotation marks inside the SchTasks arguments need to be escaped. After fixing those up, it should work. Here's the command I used:

Code
Copy
Select All

SchTasks /Create /RU "SYSTEM" /SC DAILY /TN "Notify Admin Schedule Ran" /TR "\"C:\Program Files\ShellSend\shellsend.exe\" \"(email)@(domain).com\" \"(email)@(domain).com\" \"mail.(domain).com\" 26 0 \"(email)@(domain).com\" \"(password)\" \"ScheduleRan\" \"C:\Program Files\shellsend\shellsend.txt\"" /ST 03:30:00

Hope that helps!

Using ShellSend with Scheduled Tasks in XP

Binary Fortress Software — Mon, 31 Mar 2014 19:06:09 GMT

I am trying to use scheduled tasks to send a notification after certain tasks have run on a few winXP workstations we have. (I use a batch file to set the schedules on all the machines.) When the batch file tries to set the task related to shellsend, I get the following error:

Code
Copy
Select All

ERROR: Invalid Argument/Option - 'ran '.
Type "SchTasks /CREATE /?" for usage.

Here is the corresponding line in the batch file:

Code
Copy
Select All

SchTasks /Create /RU "SYSTEM" /SC DAILY /TN "Notify Admin: Schedule Ran" /TR "C:\Program Files\ShellSend\shellsend.exe "(email)@(domain).com" "(email)@(domain).com" "mail.(domain).com" 26 0 "(email)@(domain).com" "(password)" "ScheduleRan" "C:/program files/shellsend/shellsend.txt" /ST 03:30:00

Note that some information has been removed for privacy. All modifications have been outlined with (). The command will run from the command line and email fine.

RE: Unicode support

Binary Fortress Software — Mon, 28 Mar 2011 13:36:46 GMT

Excellent, I'm glad to hear you got it worked out. FileSeek does have full Unicode support, but the file has to be saved in a Unicode-friendly format (UTF-8, UTF-16... etc).

RE: Unicode support

Binary Fortress Software — Mon, 28 Mar 2011 13:17:00 GMT

Hi,

I have found the solution. I save the text file in unicode format (instead of ANSI)

Unicode support

Binary Fortress Software — Fri, 25 Mar 2011 14:43:24 GMT

Hi,

I'am trying ShellSend and I have discovered that the software doesn't support characters in others languages that english.
See the screen shot linked with this message.

Please, can you add support for all languages !

Sorry for my english, I'am french.

RE: ssl account will not work

Binary Fortress Software — Wed, 13 Oct 2010 14:11:42 GMT

Thanks for following-up, I'm glad to hear it is working one way or another.

RE: ssl account will not work

Binary Fortress Software — Thu, 07 Oct 2010 11:53:38 GMT

Jon,

From past experiences with AT&T / Yahoo I would guess the problem is on their end.
Port 25 and 587 will work, without SSL, so I can use the program.

Thanks for taking the time to respond so quickly.
I would have to rate your response time as one of the very best!

Thanks,
JJ

RE: ssl account will not work

Binary Fortress Software — Wed, 06 Oct 2010 13:01:18 GMT

All ISPs are different, some allow port 25, some don't. If you are using any firewall software, make sure you are allowing ShellSend. Other than that, I'm not sure what to tell you. I really have no idea why your mail client would work, and this simple application won't. Use port 25 or 587 if you are able.

RE: ssl account will not work

Binary Fortress Software — Wed, 06 Oct 2010 02:42:26 GMT

Jon,

1.2.1 did not work using 465 1 or 465 0.
It did work using 25 0.

Is it normal for an ISP to also use port 25 if they are using port 465 SSL? I had always assumed that if 465 was used then 25 would not be available.

Thanks,
JJ

RE: ssl account will not work

Binary Fortress Software — Tue, 05 Oct 2010 20:07:54 GMT

Can you give this new build (1.2.1) a try:
http://www.binaryfortress.com/shellsend/

Thanks!

RE: ssl account will not work

Binary Fortress Software — Sat, 02 Oct 2010 10:44:46 GMT

Jon,

Thanks for the quick reply.

"587" "1" gave error: Server does not support secure connections.

"587" "0" This worked.
"25" "0" This worked also. ??

Port 465 SSL is what the ISP said to use for an email client so I didn't think 25 would work.
"465" "1" or "465" "0" did not work but my email client works with 465. ??

Thanks
JJ

RE: ssl account will not work

Binary Fortress Software — Sat, 02 Oct 2010 03:59:43 GMT

Try using port 587 instead of port 465, sometimes this is needed to get around ISP filters.

ssl account will not work

Binary Fortress Software — Sat, 02 Oct 2010 00:48:47 GMT

I am trying to send using an AT&T account with SSL and I get a timed out message.
This is what I have entered on the command line;

shellsend.exe "me9@att.net" "me8@att.net" "smtp.att.yahoo.com" "465" "1" "me8@att.net" "mypassword" "j" "C:\JJ.txt"

Any idea why it doesn't work?

Thanks,
JJ

ShellSend Discussions RSS

RE: ShellSend 2.1 Now Available!

RE: ShellSend 2.1 Now Available!

RE: ShellSend 2.1 Now Available!

RE: ShellSend 2.1 Now Available!

RE: ShellSend 2.1 Now Available!

ShellSend 3.2 Now Available!

RE: ShellSend 2.1 Now Available!

ShellSend 2.1 Now Available!

ShellSend 2.0 Now Available!

RE: Using ShellSend with Scheduled Tasks in XP

RE: Using ShellSend with Scheduled Tasks in XP

CodeCopySelect All

CodeCopySelect All

RE: Using ShellSend with Scheduled Tasks in XP

RE: Using ShellSend with Scheduled Tasks in XP

CodeCopySelect All

Using ShellSend with Scheduled Tasks in XP

CodeCopySelect All

CodeCopySelect All

RE: Unicode support

RE: Unicode support

Unicode support

RE: ssl account will not work

RE: ssl account will not work

RE: ssl account will not work

RE: ssl account will not work

RE: ssl account will not work

RE: ssl account will not work

RE: ssl account will not work

ssl account will not work

Code
Copy
Select All

Code
Copy
Select All

Code
Copy
Select All

Code
Copy
Select All

Code
Copy
Select All