keyshost.blogg.se - Surgemail settings 587

This is where changes get saved if you edit within the global scope on the surgeweb customisation page of the admin interface.

surgemail/surgeweb/custom/config_global.dat : Surgeweb customisation that will be applied globally.

This is the primary reference for available settings and valid values for these settings.

surgemail/surgeweb/tpl/config_system.dat : The system default behaviour.

A subset of the settings available in these files can be edited using the surgeweb customisation page of the surgemail admin interface. Subsequent levels of specialisation will override the settings at a more general level. These are self documenting plain text files that control the behaviour of just about everything is surgeweb. The majority of surgeweb configuration options are configured using the config_*.dat files. You generally should not modify this directly unless you are doing some very specialised administration.

surgemail/surgeweb/work : This is the surgeweb work folder where all per user files are stored.

This includes global, per domain and per user group customisation. This is where all your customisation would generally be made.

surgemail/surgeweb/custom : The surgeweb customisation folder.

This folder should not be directly modified and will get completely overwritten on upgrades.

surgemail/surgeweb/tpl : This defines the whole of the surgeweb clientside interface in terms of javascript, html, css and default settings.

There are three primary surgeweb folder trees: In addition there are a small number of surgeweb related surgemail.ini settings. Virtually all surgeweb customisation can be configured globally, per domain, per user group, and most behaviour can be configured per account either manually by the admin or by the user.Ĭustomisation gets applied using settings in config_*.dat files, using extension css and extension javascript files. Surgeweb is configured using a system of customisation that allows settings, styling and behaviour changes to be applied “over top of” the existing core interface.