>> > I have a Debian Lenny 64 bit machine. I originally installed >> > Squirrelmail using apt-get install squirrelmail which gave >> me version >> > 1.4.15. By default, this version is installed to >> > /usr/share/squirrelmail on Debian Lenny. >> > >> > I wanted to upgrade to Squirrelmail version 1.4.19. So I created a >> > new folder /usr/share/squirrelmail-1.4.19, unpacked the >> files from the >> > Squirrelmail website, and ran the conf.pl script to configure. In >> > essence, this is a brand new installation and not an attempt to >> > upgrade on top of the original 1.4.15 files. I have >> mimicked the way >> > Debian installs and just changed the symlink in the /var/www folder >> > from /usr/share/squirrelmail to >> /usr/share/squirrelmail-1.4.19. After >> > some initial testing, the system was running fine sending >> and receiving emails. >> > >> > I then wanted to install the first new plugin for the newer >> version. >> > There are no other plugins installed as this is a fresh >> Squirrelmail installation. >> > I followed the instructions in the plugin install file. When I >> > reached the point where I was to activate the plugin from >> the conf.pl >> > file, I noticed that no plugins were shown in the >> configuration menu. >> > I didn't expect any plugins to be installed and activated yet, but >> > there also were none shown as being available. >> >> Hard to know what the problem is. If you don't see Perl >> errors on screen, then it seems like it is probably finding >> an empty "plugins" >> directory. From where exactly are you executing conf.pl? >> From that location, do you see a plugins directory along side >> the config directory? Are its permissions OK? Does it have >> plugins in it? Show directory listing snapshots if you think >> that would help clarify. >> > > Here is the directory listing of the default installation directory when > using "apt-get install squirrelmail" from the Debian Lenny repositories. As > I mentioned, this results in version 1.4.15. > > server:/usr/share/squirrelmail# ls -l > total 44 > drwxr-xr-x 5 root root 4096 Jun 23 22:10 class > lrwxrwxrwx 1 root root 17 Jun 23 22:10 config -> /etc/squirrelmail > drwxr-xr-x 4 root root 4096 Jun 23 22:10 functions > drwxr-xr-x 30 root root 4096 Jun 23 22:10 help > drwxr-xr-x 2 root root 4096 Jun 23 22:10 images > drwxr-xr-x 3 root root 4096 Jun 23 22:10 include > -rw-r--r-- 1 root root 672 May 19 09:43 index.php > drwxr-xr-x 48 root root 4096 Jun 23 22:10 locale > drwxr-xr-x 20 root root 4096 Jun 23 22:10 plugins > drwxr-xr-x 2 root root 4096 Jun 23 22:10 po > drwxr-xr-x 2 root root 4096 Jun 23 22:10 src > drwxr-xr-x 3 root root 4096 Jun 23 22:10 themes > > I then created the following directory and upacked the 1.4.19 version > download into this directory. Please note that the ownership and > permissions are identical to the default installation. > > server:/usr/share/squirrelmail-1.4.19# ls -l > total 60 > -rw-r--r-- 1 root root 56 Mar 26 16:51 README > drwxr-xr-x 5 root root 4096 May 21 12:20 class > -rwxr-xr-x 1 root root 102 Aug 2 2005 configure > drwxr-xr-x 3 root root 4096 May 21 12:20 contrib > drwxr-xr-x 3 root root 4096 May 21 12:21 doc > drwxr-xr-x 4 root root 4096 May 21 12:21 functions > drwxr-xr-x 3 root root 4096 May 21 12:20 help > drwxr-xr-x 2 root root 4096 May 21 12:21 images > drwxr-xr-x 3 root root 4096 May 21 12:20 include > -rw-r--r-- 1 root root 676 Apr 15 17:00 index.php > drwxr-xr-x 2 root root 4096 May 21 12:20 locale > drwxr-xr-x 19 root root 4096 May 21 12:20 plugins > drwxr-xr-x 2 root root 4096 May 21 12:21 po > drwxr-xr-x 2 root root 4096 May 21 12:20 src > drwxr-xr-x 3 root root 4096 May 21 12:20 themes Note the lack of a "config" directory. That won't fly. > Currently, my system is reverted back to the default 1.4.15 installation. > However, when testing the 1.4.19 version, I had created a symlink pointing > to /etc/squirrelmail. I had renamed the default /etc/squirrelmail directory > /etc/squirrelmail-orig. > > Here is the directory structure of that default directory. > > server:/etc/squirrelmail# ls -l > total 72 > -rw-r--r-- 1 root root 1230 May 19 09:43 apache.conf > lrwxrwxrwx 1 root root 32 Jun 23 22:10 conf.pl -> > /usr/sbin/squirrelmail-configure > -rw-r--r-- 1 root root 8291 Jun 25 21:25 config.php > -rw-r--r-- 1 root root 30942 May 19 09:43 config_default.php > -rw-r--r-- 1 root root 460 May 19 09:43 config_local.php > -rw-r--r-- 1 root root 41 May 19 09:43 default_pref > -rw-r--r-- 1 root root 6581 May 19 09:42 filters_setup.php > -rw-r--r-- 1 root root 479 May 19 09:43 index.php > -rw-r--r-- 1 root root 1652 May 19 09:42 sqspell_config.php > > Here is the directory structure of the folder I created for the 1.4.19 > version. > > server:/etc/squirrelmail-1.4.19# ls -l > total 228 > -rwxr-xr-x 1 root root 153355 Apr 13 11:52 conf.pl > -rw-r--r-- 1 root root 31180 Apr 13 11:52 config.php > -rw-r--r-- 1 root root 31180 Aug 7 22:41 config_default.php > -rw-r--r-- 1 root root 464 Apr 15 17:00 config_local.php > -rw-r--r-- 1 root root 483 Apr 15 17:00 index.php Unless you plan to mimic all the changes Debian made to the SquirrelMail configuration system, you need to put back the "config" directory where it was when you unpacked. You don't state if you make /etc/squirrelmail-1.4.19 by copying /etc/squirrelmail or by moving the "config" directory from what you unpacked. If the former, you need to make sure Debian's custom changes work with what you unpacked, and if the latter, you need to make Debian's changes to the stock SM code. We don't support vendor-specific changes, so you're really on your own here. > It is the conf.pl file within this directory in which I was encountering the > issue with no plugins listed. There were no Perl warnings or errors > reported on screen, just an empty listing of available plugins. That's probably because you took a tool that was written to be run from where it was unpacked and you moved it far away from the plugins directory. "Fix" it or move it back. > All other > areas of the configuration utility worked as expected. I could change SMTP > and IMAP settings, Organizational preferences, etc. and those changes were > reflected on the live site. > >> > Just to double check, I undid my changes and restored the directory >> > structure to that of the original Debian install that resulted from >> > using apt-get. When accessing the ./conf.pl program >> plugins menu, all >> > the available plugins are listed. >> > >> > I have doubled checked permissions and ownership on both >> the plugins >> > directory and the files contained within. The permissions and >> > ownership are identical in the new folder as the default >> Debian installed plugins folder. >> > >> > I also ran the configtest.php utility and no errors were found with >> > the new installation. >> > >> > I looked through the known bugs, FAQs and search the email >> list with Nabble. >> > I didn't see anything that described this particular problem. >> > >> > I can provide more information on the system if needed. I >> am running >> > Apache2, Courier, PHP5, & Postfix; all the latest versions >> available >> > from the stable Debian Lenny apt-get cache. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
