adding squirrelmail plugins as a reseller - Possible??

gof

Verified User
Joined
Oct 21, 2003
Messages
17
As a reseller on DA, is it possible to add plugins to the detault install of squirrelmail (i.e., without installing the entire package)? I realise that with updates to SM it may require me to reinstall them, but I'd like to add a few of the UI improvements (like the option to view HTML formatted emails!).

Currently we're using DA 1.24.2
 
No it is not, but you may be able to install your own version of squirrelmail.
 
rldev said:
No it is not, but you may be able to install your own version of squirrelmail.
Thanks, I was trying to avoid doing that for each sub account. I was thinking it wasn't possible, but didn't know for sure.

What's the process to request plugins being included in future releases for DA? I would think the HTML plugin (which is an extra click to view) would be a "safe" addition.
 
The system owner can add plugins, but if you'd like them included in DA, write to their sales address.

Jeff
 
Resurrecting an old topic since I've noticed that the "core" plugins such as filters do not seem to be in the default DA install for squirrelmail. I'm over at Dixie/8.95 so as much info as I can provide them on getting filters enabled would be very helpful.

Why are the core plugins not included in the DA image for squirrelmail? Specifically, I'm looking for the basic ability to use (automatic) filters (some of the other standard plugins would be nice too) like squirrelspell and fetch.

The main reason I want the filtering ability is to handle the recent HUGE increase in backscatter email issues, especially when a catchall is desired. Most of the backscatter can be handled with a few simple filters which I'm doing manually now.
 
I'm over at Dixie/8.95 so as much info as I can provide them on getting filters enabled would be very helpful.
Simply let them know you'd like them to add the specific squirrelmail plugins you'd like, and see if they're willing to accommodate you.

Jeff
 
I've put in the suggestion. My question was about why the plugins are not there by default (DA default). Squirrelmail rolled them into the "core" default install in version 1.2. I think the current DA version is 1.47.
 
I couldn't say why they're not there (I've honestly never looked for them). The way we install SM is to take their tar.gz, extract it, change a symbolic link around.. and then to rename their included config_default.php to config.php. After that we do a few perl regexes to swap out some settings, none of which (I would assume) would affect any filters being present.

Perhaps they're there, just not turned on? If someone knows what's missing, do tell ;)

John
 
Long delay in following up on this, but I finally broke down and did a solo install so I could specifically comment on where to put in the plugin information. It looks like the way (my host, and I'm fairly sure it's a generic DA install) squirrelmail is installed is just as the distribution comes (as you pointed out). About 90% of the way down (just search for "plugins") you just add a list of the plugins you want the user to have access to. There are quite a few included in the "core" distribution already. I might suggest (I used 1.49a since it fixes some bugs I was encountering with 1.47) the following

PHP:
/**
 * To install plugins, just add elements to this array that have
 * the plugin directory name relative to the /plugins/ directory.
 * For instance, for the 'sqclock' plugin, you'd put a line like
 * the following.
 *    $plugins[0] = 'sqclock';
 *    $plugins[1] = 'attachment_common';
 */
// Add list of enabled plugins here
$plugins[0] = 'spamcop';
$plugins[1] = 'filters';
$plugins[2] = 'squirrelspell';
 
Oops. I should mention (in case it isn't obvious) that the addition of the three lines in blue above goes in config.php in the ./config directory of the squirrelmail install. :D
 
I couldn't say why they're not there (I've honestly never looked for them). The way we install SM is to take their tar.gz, extract it, change a symbolic link around.. and then to rename their included config_default.php to config.php. After that we do a few perl regexes to swap out some settings, none of which (I would assume) would affect any filters being present.

Perhaps they're there, just not turned on? If someone knows what's missing, do tell ;)

John

Bumping this to see if John noticed I posted where the config change is needed.
 
Back
Top