PHP Programming Language - Cultural View
PHP Programming Language - Cultural View PHP Programming Language - Cultural View
SquirrelMail 306 SquirrelMail SquirrelMail in use as the webmail service for University College London Original author(s) [1] Nathan and Luke Ehresman Developer(s) The SquirrelMail Project Team Initial release December 14, 1999 [2] Stable release 1.4.20 / March 6, 2010 Preview release 1.5.1 / February 19, 2006 Development status Active Written in PHP Platform Cross-platform Available in [3] More than 50 languages Type Web-based email License GNU General Public License v2 Website www.squirrelmail.org [4] SquirrelMail is a web-based email application started by Nathan and Luke Ehresman. [1] and written in the PHP scripting language. It can be installed on almost all web servers as long as PHP is present and the web server has access to an IMAP and SMTP server. SquirrelMail outputs valid HTML 4.0 for its presentation, making it compatible with a majority of current web browsers. SquirrelMail uses a plugin architecture to accommodate additional features around the core application, and over 200 plugins are available on the SquirrelMail website [5] Licensed under the GNU General Public License, SquirrelMail is free software. It is currently available in over 50 languages. [3] SquirrelMail is included in many major GNU/Linux distributions [6] [7] [8] [9] [10] [11] [12] [13] [14] and is independently downloaded by tens of thousands of people every month. [15]
SquirrelMail 307 Platforms SquirrelMail is available for any platform supporting PHP. Most commonly used platforms include Linux, FreeBSD, Mac OS X and the server variants of Microsoft Windows. Future development New releases of the stable SquirrelMail product are made as needed to address any bugs or security issues which may be discovered. Development of new features and enhancements is concentrated on the development product, which, in time, will itself become the stable product. The SquirrelMail 1.5 Roadmap [16] outlines some of the features slated for the next developmental release, including: • A templating system • A RPC interface for use by other applications as well as AJAX-enabled SquirrelMail template sets (skins) • A new initialization system • Faster login times due to improved message header caching • Security enhancements, such as HTTPOnly cookies • Improved usability/accessibility Plugins The SquirrelMail client itself is a complete webmail system, but extra features are available in the form of plugins. A plugin allows non-standard features to be added to SquirrelMail, often without the need to modify the source code. There are over 200 third-party plugins available for download from the SquirrelMail website, [5] and SquirrelMail ships with several "standard" or "core" plugins, allowing an administrator to add: • Spell checking (squirrelspell) • Mail filters (filters) • Web-based administration of SquirrelMail (administrator) • A calendar (calendar) • An interface to submit bug reports semi-automatically (bug_report) Examples of functionalities added by various third-party plugins include: • Address book/contact grouping and other address book expansions • Monitoring and security tools to track usage, fight attackers and improve security • Password change • Quota reporting • Rich text (HTML) email composition and display • User-configurable front-ends for autoreponders, spam filtering systems such as SpamAssassin and server-side mail filters • Weather reporting • User account control panel
- Page 261 and 262: PmWiki 255 Wiki structure In PmWiki
- Page 263 and 264: PrestaShop 257 PrestaShop Stable re
- Page 265 and 266: PrestaShop 259 • Real-time curren
- Page 267 and 268: Project Zero 261 Project Zero Devel
- Page 269 and 270: Propel (PHP) 263 Propel (PHP) Prope
- Page 271 and 272: QPHP Framework 265 Data validation
- Page 273 and 274: Quick.Cart 267 Support It is suppor
- Page 275 and 276: Ravennuke 269 Ravennuke Developer(s
- Page 277 and 278: ReOS 271 ReOS Developer(s) Elazos S
- Page 279 and 280: RefDB 273 RefDB Developer(s) RefDB
- Page 281 and 282: efbase 275 References [1] http://ww
- Page 283 and 284: ResourceSpace 277 ResourceSpace Res
- Page 285 and 286: Robogallery 279 Robogallery Develop
- Page 287 and 288: RoundCube 281 RoundCube Developer(s
- Page 289 and 290: SWiZ 283 SWiZ SWiZ (simple visualis
- Page 291 and 292: Seagull PHP Framework 285 Seagull P
- Page 293 and 294: Seagull PHP Framework 287 Reference
- Page 295 and 296: Serendipity (software) 289 It's goi
- Page 297 and 298: SilverStripe 291 Features Notable f
- Page 299 and 300: SilverStripe 293 Recognition Awards
- Page 301 and 302: Simple Cloud API 295 Simple Cloud A
- Page 303 and 304: Simple Machines Forum 297 Simple Ma
- Page 305 and 306: Simple Machines Forum 299 Modificat
- Page 307 and 308: SimpleXML 301 SimpleXML SimpleXML i
- Page 309 and 310: Simply AJAX Forum System (SAFS) 303
- Page 311: SocialEngine 305 • Games • Sear
- Page 315 and 316: SquirrelMail 309 References [1] "Sq
- Page 317 and 318: Squiz 311 MySource Matrix in Use My
- Page 319 and 320: SugarCRM 313 Deployment types Sugar
- Page 321 and 322: Symfony 315 Technical Symfony makes
- Page 323 and 324: Symfony 317 See also • Comparison
- Page 325 and 326: Textpattern 319 Textpattern Develop
- Page 327 and 328: Textpattern 321 • TXPQ Magazine [
- Page 329 and 330: TikiWiki 323 Major components TikiW
- Page 331 and 332: TinyWebGallery 325 TinyWebGallery D
- Page 333 and 334: Torpor (PHP) 327 External links •
- Page 335 and 336: TYPO3 329 TYPO3 TYPO3 4.1 backend m
- Page 337 and 338: TYPO3 331 TemplaVoila TemplaVoila i
- Page 339 and 340: UBB.threads 333 Version 7.x While G
- Page 341 and 342: Ubercart 335 Ubercart Developer(s)
- Page 343 and 344: uddeIM 337 uddeIM Developer(s) Step
- Page 345 and 346: uddeIM 339 References • Official
- Page 347 and 348: vBulletin 341 vBulletin Developer(s
- Page 349 and 350: vBulletin 343 • A database-stored
- Page 351 and 352: vBulletin 345 vBulletin Blog Now in
- Page 353 and 354: vBulletin 347 External links • vB
- Page 355 and 356: Vwar 349 License Virtual War is not
- Page 357 and 358: WakkaWiki 351 References [1] http:/
- Page 359 and 360: Website Baker 353 WebsiteBaker vers
- Page 361 and 362: Website Baker 355 Translations In t
SquirrelMail 306<br />
SquirrelMail<br />
SquirrelMail in use as the webmail service for University College London<br />
Original author(s) [1]<br />
Nathan and Luke Ehresman<br />
Developer(s) The SquirrelMail Project Team<br />
Initial release December 14, 1999 [2]<br />
Stable release 1.4.20 / March 6, 2010<br />
Preview release 1.5.1 / February 19, 2006<br />
Development status Active<br />
Written in <strong>PHP</strong><br />
Platform Cross-platform<br />
Available in [3]<br />
More than 50 languages<br />
Type Web-based email<br />
License GNU General Public License v2<br />
Website www.squirrelmail.org [4]<br />
SquirrelMail is a web-based email application started by Nathan and Luke Ehresman. [1] and written in the <strong>PHP</strong><br />
scripting language. It can be installed on almost all web servers as long as <strong>PHP</strong> is present and the web server has<br />
access to an IMAP and SMTP server.<br />
SquirrelMail outputs valid HTML 4.0 for its presentation, making it compatible with a majority of current web<br />
browsers. SquirrelMail uses a plugin architecture to accommodate additional features around the core application,<br />
and over 200 plugins are available on the SquirrelMail website [5]<br />
Licensed under the GNU General Public License, SquirrelMail is free software. It is currently available in over 50<br />
languages. [3] SquirrelMail is included in many major GNU/Linux distributions [6] [7] [8] [9] [10] [11] [12] [13] [14] and is<br />
independently downloaded by tens of thousands of people every month. [15]
Change language