added a theme
[squirrelmail.git] / config / config_default.php
CommitLineData
baf93783 1<?
2// Organization's logo picture (blank if none)
3 $org_logo = "../images/sm_logo.jpg";
4
5// Organization's name
6 $org_name = "SquirrelMail";
7
8// Webmail Title
9// This is the title that goes at the top of the browser window
10 $org_title = "SquirrelMail $version";
11
12// The server that your imap server is on
13 $imapServerAddress = "localhost";
14 $imapPort = 143;
15
16// The domain where your email address is.
17// Example: in "luke@usa.om.org", usa.om.org is the domain.
18// this is for all the messages sent out. Reply address
19// is generated by $username@$domain
20 $domain = "mydomain.com";
21
22// Your SMTP server and port number (usually the same as the IMAP server)
23 $smtpServerAddress = "localhost";
24 $smtpPort = 25;
25
26// Uncomment this if you want to deliver locally using sendmail instead
27// of connecting to a SMTP-server
28// $useSendmail = true;
29// $sendmail_path = "/usr/sbin/sendmail";
30
31// This is displayed right after they log in
32 $motd = "You are using SquirrelMail's web-based email client. If you run into any bugs or have suggestions, please report them to our <A HREF=\"mailto:squirrelmail-list@sourceforge.net\">mailing list</A>";
33
34// Themes
35// You can define your own theme and put it in this directory. You must
36// call it as the example below. You can name the theme whatever you
37// want. For an example of a theme, see the ones included in the config
38// directory.
39//
40// You can download themes from http://squirrelmail.sourceforge.net/index.php3?page=10
41//
42// To add a new theme to the options that users can choose from, just add
43// a new number to the array at the bottom, and follow the pattern.
44
45 // The first one HAS to be here, and is your system's default theme.
46 // It can be any theme you want
47 $theme[0]["PATH"] = "../config/default_theme.php";
48 $theme[0]["NAME"] = "Default";
49
50 $theme[1]["PATH"] = "../config/sandstorm_theme.php";
51 $theme[1]["NAME"] = "Sand Storm";
52
53 $theme[2]["PATH"] = "../config/deepocean_theme.php";
54 $theme[2]["NAME"] = "Deep Ocean";
55
56 $theme[3]["PATH"] = "../config/slashdot_theme.php";
57 $theme[3]["NAME"] = "Slashdot";
58
59 $theme[4]["PATH"] = "../config/purple_theme.php";
60 $theme[4]["NAME"] = "Purple";
61
62 $theme[5]["PATH"] = "../config/forest_theme.php";
63 $theme[5]["NAME"] = "Forest";
64
65 $theme[6]["PATH"] = "../config/ice_theme.php";
66 $theme[6]["NAME"] = "Ice";
67
b6def0e7 68 $theme[7]["PATH"] = "../config/seaspray_theme.php";
69 $theme[7]["NAME"] = "Sea Spray";
70
baf93783 71// Whether or not to use a special color for special folders. If not, special
72// folders will be the same color as the other folders
73 $use_special_folder_color = true;
74
ca1f4a68 75// The following are related to deleting messages.
76// $move_to_trash
77// - if this is set to "true", when "delete" is pressed, it
78// will attempt to move the selected messages to the folder
79// named $trash_folder. If it's set to "false", we won't even
80// attempt to move the messages, just delete them.
81// $trash_folder
82// - This is the path to the default trash folder. For Cyrus
83// IMAP, it would be "INBOX.Trash", but for UW it would be
84// "Trash". We need the full path name here.
85// $auto_expunge
86// - If this is true, when a message is moved or copied, the
87// source mailbox will get expunged, removing all messages
88// marked "Deleted".
baf93783 89
90 $default_move_to_trash = true;
91 $trash_folder = "INBOX.Trash";
92 $auto_expunge = true;
93
ca1f4a68 94// Special Folders are folders that can't be manipulated like normal
95// user created folders can. A couple of examples would be
96// "INBOX.Trash", "INBOX.Drafts". We have them set to Netscape's
97// default mailboxes, but this obviously can be changed. To add one,
98// just add a new number to the array.
baf93783 99
100 $special_folders[0] = "INBOX"; // The first one has to be the inbox (whatever the name is)
101 $special_folders[1] = $trash_folder;
102 $special_folders[2] = "INBOX.Sent";
103 $special_folders[3] = "INBOX.Drafts";
104 $special_folders[4] = "INBOX.Templates";
105
106// Whether or not to list the special folders first (true/false)
107 $list_special_folders_first = true;
108
109// Are all your folders subfolders of INBOX (i.e. cyrus IMAP server)
110// If you are not sure, set it to false.
111 $default_sub_of_inbox = true;
112
ca1f4a68 113// Some IMAP daemons (UW) handle folders weird. They only allow a
114// folder to contain either messages or other folders, not both at
115// the same time. This option controls whether or not to display an
116// option during folder creation. The option toggles which type of
117// folder it should be.
baf93783 118//
ca1f4a68 119// If this option confuses you, make it "true". You can't hurt
120// anything if it's true, but some servers will respond weird if it's
121// false. (Cyrus works fine whether it's true OR false).
122
baf93783 123 $show_contain_subfolders_option = false;
124
ca1f4a68 125// Whether or not to use META tags and automatically forward after an
126// action has been completed.
baf93783 127 $auto_forward = true;
128
129// Path to the data/ directory
ca1f4a68 130// It is a possible security hole to have a writable directory
131// under the web server's root directory (ex: /home/httpd/html).
132// For this reason, it is possible to put the data directory
133// anywhere you would like. The path name can be absolute or
134// relative (to the config directory). It doesn't matter. Here are
135// two examples:
baf93783 136//
137// Absolute:
138// $data_dir = "/usr/local/squirrelmail/data/";
139//
140// Relative (to the config directory):
141// $data_dir = "../data/";
142
143 $data_dir = "../data/";
ca1f4a68 144
145// Path to directory used for storing attachments while a mail is
146// being sent. There are a few security considerations regarding this
147// directory:
148// - It should have the permission 733 (rwx-wx-wx) to make it
149// impossible for a random person with access to the webserver to
150// list files in this directory. Confidential data might be laying
151// around there
152// - Since the webserver is not able to list the files in the content
153// is also impossible for the webserver to delete files lying around
154// there for too long.
155// - It should probably be another directory than data_dir.
156
157 $attachment_dir = $data_dir
baf93783 158?>