From: Tomas K. <to...@us...> - 2004-12-30 12:59:50
|
> Tomas Kuliavas escreveu: > >>>>I am looking for informations about template structures or template >>>>samples to understand this squirrelmail feature . Where could I get it? >>>>There are some site or manual for to explain this subject? I saw this >>>>possibilities in "nutsmail.com". >>>> >>>> >>>Thanks for the link. They have "hacked" the source. There is no >>>templating in the current iteration of SM (except in Marc's devel >>> branch). >>> That is, it's in development and projected for a future release (no >>> time >>>soon). If you want to see what those people have done, you'll have to >>> pay >>>them and look at how they changed the code. >>> >>> >> >>lovemyhost skin does same thing without paying installation fees. People >>that have downloaded it, can take a look at the code. Only graphics are >>copyrighted >> >>It is not template. Only modification that changes layout and adds >>graphics and css. Maybe login and logout pages were modified too. >> >>Once you have done it for one theme, you only need to replace graphics >> and >>css in order to use other theme. >> >>If they use templates, they might be able to show screenshots that differ >>in layout and not only in graphics. >> >> >> > Thanks Tomas and Paul, > "Templates?!?" > Perhaps we will buy one skin to understand their "new" code structure. http://www.topolis.lt/squirrelmail/skined/ > IMAP & Sieve > We are testing and using squirrelmail with avelsieve (it's not just in > prodution system). It's working fine. The rules are in the sieve server. > The avelsieve plugin write serializables variables in "phpscript" file > (with sieve code too). This plugin don't work with parse, just > serielizing and unserializing the rules in this file. We have near > 40.000 email counts in our servers, with redundance and cluster > configuration. The references to IMAP servers are different to SIEVE > servers, the names area different, but the avelsieve and the sieve > beleave that they are same, using the SM function sqimap_get_user_server > ($imapServerAddress, $username). > > For to reduce inconvenients attacks or sieve customizations not > autorizated without our interface, we are using this way, separating > access references. Perhaps the solution about it was with avelsieve > programmers but we beleave that other people will need to reference > distinct servers or names in relation to IMAP server. Creating array of > servers names or a boolean variable, the solution will be easier. from avelsieve sample config. /* **** NEW OPTION (as of 0.9.6) ***** Enable ImapProxy mode. * If you use imapproxy, because imapproxy cannot understand and proxy the * SIEVE protocol, you must connect to the SIEVE daemon (usually on the IMAP * server) itself. So you need to set $imapproxymode to true, and define a * mapping, from the imapproxy host (usually localhost) to your real IMAP * server (usually the same that is defined on Imapproxy's configuration). * * This will not work if you use a perdition-style proxy, where different users * go to different IMAP servers; it applies mostly to people running imapproxy * for speed and want a quick hack. */ $imapproxymode = false; $imapproxyserv = array( 'localhost' => 'imap.example.org' ); I might be wrong, but it looks like setting different address of sieve server. Only replace imapproxy with 'imap server that does not talk sieve' -- Tomas |