On Sun, Oct 26, 2008 at 1:19 PM, Todd Alan Smith
> On Sun, Oct 26, 2008 at 9:51 AM, Steffi Rausch <steffi@...> wrote:
>> Thanks for all your help. I finally got it working. To answer your questions
>> below, the ./lib line was commented out when I downloaded it. Please check
>> on that (modular version, not compat), and it has a note to uncomment it for
> Modules version, not the compat. That's a good detail to list at the outset.
>> some reason. I agree I think that is odd, but that's what it was when I
>> downloaded it. See for yourself. It says:
>> # You may need to uncomment the line below and adjust the path.
>> # use lib './lib';
> Like I said, I know what it states in the program file. My question
> was why did you decide to comment it out. Since you haven't supplied a
> reason, it sounds like you just commented it out in the off chance
> that doing so would get the program to work for you. And that's fine.
> I was merely inquiring as to your line of thinking. My opinion is that
> the README could be more specific as to why one would need/want to
> comment out that line.
I don't know why I continue to refer to your "commenting out" that
line, when I actually mean to say "uncomment". I apologize for the
>> And for the sendmail.pm file, I looked at line 99, and the path that we use
>> for sendmail is different than what you use.
>> You use /usr/lib/sendmail -oi -t
>> We use /usr/bin/sendmail -t
>> So perhaps this is worth noting in your documentation to change, since once
>> I altered it, it worked.
> It _is_ noted in the documentation. Read the full entry for $mailprog
> in the README, including the last paragraph:
> Your system administrator or hosting provider should be able to tell
> you either the path to sendmail on the web server or the name of a
> host that will act as an SMTP relay for the web server.
> Granted the README doesn't give _your_ specific path a mention, but it
> does get the point across that the path may vary from server to
> server, so you'll need to consult with your system administrator or
> hosting provider if you aren't sure. I don't think the README should
> list too many possible paths, as it would clutter the text.
>> Maybe what I did makes more sense now to you. I was just trying to do what I
>> thought I needed to do to get it to work, but now I've moved back to using a
>> php script because I know more people who can help me with that environment.
>> But was worth a try. I was very interested in trying cgi and like the ease
>> of it. Thanks again for atleast responding to my emails and helping me
>> through it.
> Not a problem. That's why this list exists.
>> My host could not help me so much with your script problems, but is helping
>> me more with the php script I am using.
> I think what you meant to say was, "My host could not help me so much
> with my problems in successfully configuring your script."
> Nevertheless, it sounds like you made the right decision. Since your
> hosting provider wasn't inclined enough (or adept enough) to help you
> configure NMS FormMail, you were probably better off switching to what
> they will support... PHP.
> Personally, I think it's lame of them not to provide better support
> for Perl scripts. If I found myself in your situation, then I would
> consider changing hosting providers.