On Tue, Sep 02, 2003 at 02:33:52AM -0700, rkl wrote:
> My biggest concern is avoiding work for all the virtual domain on sqwebmail
> upgrade.
>
> Any ideas on managing sqwebmail and implementation for large virtual domain
> is appreciated.
My suggestions:
(1) have a separate /images/ directory for each virtual host, but share the
templates. This allows users to replace the images for buttons, and the
background pattern etc, without being able to tamper with the template
structure.
(2) modify the templates so that they cascade: i.e.
<link rel="stylesheet" type="text/css" href="[#SQWEBMAILCSS#]" />
<link rel="stylesheet" type="text/css" href="/images/webmail.css" />
Then users can upload 'webmail.css' with just selective overrides to the
default stylesheet, without having to replace the entire 'sqwebmail.css'
which would need to be kept up-to-date on each new release of sqwebmail.
I also remove the fixed sizes for the navigation buttons, which allows them
to be replaced with other sizes of image. The following script fixes up the
templates:
cd sqwebmail/html/en-us &&
for i in *.html; do \
mv $i $i.prev; \
sed \
-e '/\[#SQWEBMAILCSS#\]/p;s%%/images/webmail.css%' \
-e 's/,width=28 height=20 /,/' \
$i.prev >$i; \
rm $i.prev; \
done
(3) allow your users to write their own login page, which posts the
username/password to sqwebmail. They can prettify this as much as they like.
Regards,
Brian.
