Re: [SM-PLUGINS] Problem with Terminal run of conf.pl

[Paul L. <pa...@sq...>]

PLEASE, people, don't top-post.  Please post in-context, thanks.

On 10/16/07, Alex Solomotis <al...@so...> wrote:
> This is not a new configuration. I have been using squirrelmail for
> over 2 years (without additional plugins installed). Installation is

SM 1.4.3a is more than two years old.  Why are you still using a
version with well-known security holes?

> done via an Ensim script during install of  a domain name. Ensim
> creates 3 directories inside each domain (user) install.
> squirrelmail, squirrelmail-attachments, squirrelmail-data. When I
> attempt to add $plugins[?] = 'whatevername' ; manually into the
> config.php file I get this error when clicking on the link that shows
> up in the options or even calendar.
>
> Error opening ../../data/default_pref
> Default preference file not found or not readable!
> Please contact your system administrator and report this error.
> Go to the login page

This is a different problem.  Plenty of help for it can be found if
you take the time to read the SM website or Google for it.

> >>> when attempting to run conf.pl from command line I get this error:
> >>> /var/www/squirrelmail/config/conf.pl: line 11: =: command not found
> >>> /var/www/squirrelmail/config/conf.pl: line 19: my: command not found
> >>> /var/www/squirrelmail/config/conf.pl: line 20: syntax error near
> >>> unexpected token `{'
> >>> /var/www/squirrelmail/config/conf.pl: line 20: `if ( eval q{require
> >>> "File/Basename.pm"} ) {'
> >
> > You have broken syntax inside of your configuration file.
> >
> > If this is a new installation you should simply restore conf.pl

No, the syntax looks fine.  The OP does not seem to be using a perl
interpreter to execute the file.

> >> I would see where perl is intalled on your machine.
> >> "which perl"
> >> /sd
>
> Perl is /var/www/perl

Really?  You typed "which perl" into the terminal?  This is
suspicious.  It's usually something like /usr/bin/perl.  If it isn't,
you need to contact your provider and tell them you are having
problems with perl on their system.

It might be easier for you to put SM on your home (OS X?) machine, run
conf.pl in a terminal there, and then upload the resulting config.php
file to your web server.