"You should use the same C compiler and options to compile OpenSSL, perl, and Net::SSLeay."

I'm pretty sure I'm doing everything right in trying to install the module (but I could be wrong...!), so I'm beginning to wonder if the version of perl in devx_217.sfs was compiled with a different C compiler than the one in there now? Seems unlikely, but I'm lost for ideas. I notice in the thread above that vovchik is using Puppy 2.10 not 2.17. I'd be grateful if anyone could find the time to simply try and install Net:SSLeay in Puppy 2.17.1 with devx_217.sfs loaded and let me know if they have the same problems (or not) that I do.

Posted: Mon 10 Sep 2007, 10:18 Post subject:
As u have learned Perl isn't easy to use.Subject description: So a desirable option is to solve the problem for many people by...

taking some time to code TLS support into 'email'. I read the source code and i'm sure you can look at the smtp pear module for php http://pear.php.net/package/Net_SMTP and figure out from that code how to put TLS support into 'email'. Since i've hacked Net_SMTP and have read through the code for 'email' both are very very similiar. cough cough besides being written in different languages. Issue with PHP is it is super embarrasingly slow. Lets face facts, PHP isn't compiled and optimized like C. So speed wise 'email' is unlikely to disappoint.

So while we are at it:
* pipelining (batch) support (hint hint Net SMTP should think about adding this)
* The NET_SMTP code will use the best authentication method that the smtp server supports. With 'email' we are hard coding which auth method to use in a config file. So 'email' will fail if the smtp server does not support that auth method. A very avoidable situation. Use the best auth method silly and stop expecting end users to know what an auth method is.
* Japanese iso-2022-jp support plz. Both in the subject and body. Input text will be either shift_jis or utf-8. Not at all likely to be euc-jp. Net SMTP will never have this... Most PHP modules are lacking multi-byte language support and always will. It's embarrassing and shameful.
* multi-threading. Why be content with a pea shotter when we can have an out of control machine gun.

Perl yuk....Regular expressions yuk...only single byte encoding support yuk...puppy not supporting grub yuk...no way to say no ty thus bypass upgrading to a higher version of puppy yuk...

Good to hear you are working on implementing TLS support into email Dave.

Yes, Perl is a Pain, (though maybe I just wish I had taken the time to learn it years ago!), but its universality on Linux means it can't be ignored.

Hope you manage to code TLS into that other app, but in the meantime, since TLS is already available via perl for sendEmail, I would still like to know how to solve my problem installing Net::SSLeay. (I am pretty sure the problem is a minor one). That done, and I have the TLS support I need. So if anyone can try to install that perl module, please let me know how you got on. That would be a big help for me!

I have experienced similar frustration in other contexts, so I can commiserate. However, I don't think you should give up entirely. My installation went relatively painlessly, once I had found the above-mentioned modules. I think I installed sockets::io first. I also did not use the "-t" switch; rather, I relied on pavlovian automatism with regard to perl module installation:

Code:

perl ./Makefile.PL
make
make test
make install

Why don't you try installing without the "-t" switch and, if that fails, perhaps I can post the modules in question here.

Had already tried it exactly as you say vovchik and even with the module versions you used. Tried installing in all combinations of order too. I think it is something to do with Puppy 2.17.1; I believe you used Puppy 2.10?
I'm using a clean install of 2.17.1 specially, and its no go.

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

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:

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.

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.

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:

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.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum