CLI SMTP mailer
maybe the modules?
Of course, I'm only assuming I'm using the exact same modules you did, since the same version numbers. I get the IO socket one direct from CPAN but had to get the Net::SSLeay one (which is the problem module) elsewhere (having failed with the higher versioned CPAN one)... So maybe your module would work on Puppy 2.17.1, though for some reason I doubt it. I might try and get a hold of Puppy 2.10 and try on that, but its a lot of downloading to get all the bits with dialup.
Thanks for you help and offer though.
William
PS Its way past my bedtime again. In fact its tomorrow - daylight outside. I have to go
Thanks for you help and offer though.
William
PS Its way past my bedtime again. In fact its tomorrow - daylight outside. I have to go
Net_SSLeay.pm-1.30 for sendEmail
mcewanw:
Try this one out. Perhaps it will work.....
regards,
vovchik
Try this one out. Perhaps it will work.....
regards,
vovchik
- Attachments
-
- Net_SSLeay.pm-1.30.tar.gz
- (76.79 KiB) Downloaded 641 times
Thanks
Thanks vovchik, I'll give that a try "tomorrow" (when I get up again in too few hours)
Re: Net_SSLeay.pm-1.30 for sendEmail
No, sorry, on an absolutely clean install of Puppy Linux 2.17.1 with devx_217.sfs loaded, the Net_SSLeay.pm-1.30 file you sent me gave exactly the same errors as the other ones I tried installing. After untarring the file I tried:vovchik wrote:mcewanw:
Try this one out. Perhaps it will work.....
regards,
vovchik
perl ./Makefile.PL
make
make test
make install
But no go... Thanks for your help anyway.
I'll check the md5sums on my puppy 2.17.1 distribution and devx_217.sfs but I expect they are fine.
Oh well, I'll try again later when Puppy 2.20 comes out officially (I'll try 2.10 at some stage too probably, just to confirm that I'm not doing anything wrong. Can you just confirm the version of Puppy linux you have successfully installed it on.
Cheers
William (mcewanw)
same md5sum
Actually I've just run md5sums on the file you sent and the one with the same version number that I already had. That confirmed that they are identical!
Puppy versions
mcewan:
I have Puppy 2.10 (HD and frugal), Puppy 2.15CE, 2.16 and 2.17 under QEMU and an old version Puppy 1.07 on two old machines. I have only tried sendEmail on my 2.10 and am perfectly happy with it now that all modules are in place. I just may have been lucky during installation. The idea proposed above of modifying email to include TLS is great and will avoid perl dependency hell.
Regards,
vovchik
I have Puppy 2.10 (HD and frugal), Puppy 2.15CE, 2.16 and 2.17 under QEMU and an old version Puppy 1.07 on two old machines. I have only tried sendEmail on my 2.10 and am perfectly happy with it now that all modules are in place. I just may have been lucky during installation. The idea proposed above of modifying email to include TLS is great and will avoid perl dependency hell.
Regards,
vovchik
Re: Puppy versions
Yes, that would be the best.vovchik wrote: The idea proposed above of modifying email to include TLS is great and will avoid perl dependency hell.
I notice that the author of that email program would like to add TLS support to it, but doesn't know enough about it, so is looking for help.
Dave (Faulkmore) you should get in touch with him with your ideas!
edbrowse for CLI smtp email
Hello vovchik
I don't know if you are still interested in CLI email capable programs, but I've been working with edbrowse for a while now, for other reasons, and it looks like it is capable of TLS too (though I've still to try that). I created a dotpet for it. Details here:
http://www.murga-linux.com/puppy/viewtopic.php?t=26184
I don't know if you are still interested in CLI email capable programs, but I've been working with edbrowse for a while now, for other reasons, and it looks like it is capable of TLS too (though I've still to try that). I created a dotpet for it. Details here:
http://www.murga-linux.com/puppy/viewtopic.php?t=26184
Hi mcewanw,
I am still interested and have been waiting for "email" (cleancode.org) to post a new SSL-capable version - long promised. I have just downloaded edbrowse and will have a look. Thanks. What I like about cleancode's email is that the binary is less than 50k stripped, making it very suitable for lean puppies. Perhaps we should contact the author (run email -v to get the email address), and make a polite enquiry.
Regards,
vovchik
I am still interested and have been waiting for "email" (cleancode.org) to post a new SSL-capable version - long promised. I have just downloaded edbrowse and will have a look. Thanks. What I like about cleancode's email is that the binary is less than 50k stripped, making it very suitable for lean puppies. Perhaps we should contact the author (run email -v to get the email address), and make a polite enquiry.
Regards,
vovchik
cleancode.org
Yes, I've continued to regularly look at that site too, and keep thinking the SSL-capable version is about to be done, but not yet... And, yes, the size of that is a big attraction indeed.vovchik wrote:have been waiting for "email" (cleancode.org) to post a new SSL-capable version - long promised.
Good news - email with SSL coming soon
The author of email just replied to my message enquiring about the status of an SSS-enabled email. He had the following to say:
Regards,
vovchik
I think we will have a new version soon!Funny I should get this e-mail from you right now as I'm writing some code for eMail as I type this.
Surprisingly, I have had quite a few number of e-mails in the past month about this same thing. It seems that even though email took a small hiatus, it is growing in popularity which is neat.
It's in the process of getting a completely makeover right now and the next release will have a more secure code base, better mime type support and TLS/SSL support, of course. The size of the original binary may grow a small bit, but not by much. Also, a new dependency will obviously be introduced which will be OpenSSL (or GnuTLS since it has OpenSSL wrappers).
I'm actually in the process of relocating to a new state in the next week, so I probably won't have anything done with it in the next week. However, I'm hoping to have a new version released by mid-March at the latest. Who knows, I may get extra ambitious in the next few days and crank it out sooner.
What I will do is keep this e-mail and hit you back when the release is final and give you a "heads-up" on it in case you guys are in a hurry for a new release or anything.
Regards,
vovchik
looking forwards to the next release
Well done. It was clearly a good move contacting the program's author. Looking forwards to the SSL-capable version of the program being ready.
Here is a .pet compiled in 3.0 retro
- Attachments
-
- email-3.0.0.pet
- Console based email with ssl support
- (114.85 KiB) Downloaded 812 times
trapster
Maine, USA
Asus eeepc 1005HA PU1X-BK
Frugal install: Slacko
Currently using full install: DebianDog
Maine, USA
Asus eeepc 1005HA PU1X-BK
Frugal install: Slacko
Currently using full install: DebianDog
Dear Trapster,
I was just making a dotpet of the same when I noticed that you had beaten me to it. Thanks. I noticed one small "bug" in the prog (in the version I compiled on Puppy 3.01) that has an easy workaround (and have notified the author already). If you leave the /usr/local/etc/email/email.conf variable
commented out (as is the default), you will get a segfault with an email provider that does not use tls. The solution is to uncomment this var as follows:
so that the var gets initialized (or 'true', if that is what you prefer). Furthermore, user conf files indicated on the command line by "--conf-file filename" should not have a full filespec (i.e. preceding dirs), since this file is read from the root of the user's home directory, as far as I can tell.
Hope this info is useful. The program works very nicely after that, and is in keeping with Puppy's philosophy of "small is beautiful". The binary is only 56k stripped! Thanks also to Dean Jones (the author, at cleancode.org) for including tls support and for posting the announcement about the email upgrade on our forum.
With kind regards,
vovchik
I was just making a dotpet of the same when I noticed that you had beaten me to it. Thanks. I noticed one small "bug" in the prog (in the version I compiled on Puppy 3.01) that has an easy workaround (and have notified the author already). If you leave the /usr/local/etc/email/email.conf variable
Code: Select all
# USE_TLS = 'false'
Code: Select all
USE_TLS = 'false'
Hope this info is useful. The program works very nicely after that, and is in keeping with Puppy's philosophy of "small is beautiful". The binary is only 56k stripped! Thanks also to Dean Jones (the author, at cleancode.org) for including tls support and for posting the announcement about the email upgrade on our forum.
With kind regards,
vovchik
vovchick,
I didn't mean to "butt in" but I downloaded the latest version this morning and while playing with it decided to make a .pet
I noticed the same seg fault and ended up doing the same as you with the TLS option. I didn't change it in the .pet because I thought it might be just my provider.
I didn't mean to "butt in" but I downloaded the latest version this morning and while playing with it decided to make a .pet
I noticed the same seg fault and ended up doing the same as you with the TLS option. I didn't change it in the .pet because I thought it might be just my provider.
trapster
Maine, USA
Asus eeepc 1005HA PU1X-BK
Frugal install: Slacko
Currently using full install: DebianDog
Maine, USA
Asus eeepc 1005HA PU1X-BK
Frugal install: Slacko
Currently using full install: DebianDog
stripped binary version
I presume the dotpet provided by trapster hasn't had the binary stripped since it is still quite large. (Well, its not big anyway I suppose). I think it would be better to produce a dotpet with the stripped binary since small size is really what we are after here, no?
Perhaps vovchik or trapster could reupload an optimised dotpet?
Really great that this TLS version is ready at last, I've been waiting for this for a long time too.
Perhaps vovchik or trapster could reupload an optimised dotpet?
Really great that this TLS version is ready at last, I've been waiting for this for a long time too.
segfault fixed
I see that an update has now been released at cleancode.org to fix the segfault.
Updated binary v. 3.0.1
Dear wiak,
Here is the updated binary. It is stripped and 56 k small. Just use Trapster's pet and copy over this binary into /usr/local/bin. It no longer segfaults with an uninitialized USE_TLS var.
With kind regards,
vovchik
Here is the updated binary. It is stripped and 56 k small. Just use Trapster's pet and copy over this binary into /usr/local/bin. It no longer segfaults with an uninitialized USE_TLS var.
With kind regards,
vovchik
- Attachments
-
- email-bin-3.0.1.tar.gz
- (20.18 KiB) Downloaded 754 times