in reply to Re: Sending Mail on a Windows Machine
in thread Sending Mail on a Windows Machine

Well -- the problem there is that I'm not an admin on this windows machine. My client simply gave me his user/pass for his domain hosted by NetworkSolutions and said "go to town". So I'm at the mercy of NetworkSolutions, if they ever do respond to my ticket. I don't even have ssh access, so I can't even try to snoop around. :-\

- Justin
  • Comment on Re^2: Sending Mail on a Windows Machine

Replies are listed 'Best First'.
Re^3: Sending Mail on a Windows Machine
by digger (Friar) on Feb 23, 2005 at 12:25 UTC

    You don't need to be an admin to install your own perl modules, as long as there is no C portion that needs to be built. Start by creating a new directory in your home directory, say it is called mylib.

    Now, download and untar/zip the distribution files from CPAN. In the lib directory of the directory created when you unpack the distribution, you will find another directory named Mail. Copy this directory to the mylib directory you created earlier. At the top of your perl script, insert the line use lib "path/to/mylib". You can use this same method to install any perl module you need, as long as it doesn't include any C code.

    One last note. You already have a Mail directory in your personal library. If you install another module in the Mail family, you just need to copy the .pm file and any provided subdirectories into the existing Mail directory.

    More experienced monks - please feel free to add/clarify anything I may have missed.

    HTH
    digger

Re^3: Sending Mail on a Windows Machine
by hsinclai (Deacon) on Feb 23, 2005 at 13:52 UTC
    Ah, got it. It should work by copying the installation structure of Mail::SendEasy to a subdirectory somewhere from another working Windows installation and then specifying that subdirectory in a "use lib" statement in your script on the hosted server .. as described by digger..

    In such a tight hosted environment I would recommend asking the provider which SMTP outbound server to use, and how to authenticate to it (rather than picking some random servers based on the hosting company's name and mx), further, ensure your web server can in fact initiate connections outward bound, and the provider doesn't filter for reasons of spam prevention .. some folks have the opinion a virtual hosting web server shouldn't send anything to the Internet with a SYN flag :)