16 NEVER EDIT RT_Config.pm.
18 Instead, copy any sections you want to change to F<RT_SiteConfig.pm> and edit them there.
22 =head1 Base Configuration
28 C<$rtname> is the string that RT will look for in mail messages to
29 figure out what ticket a new piece of mail belongs to.
31 Your domain name is recommended, so as not to pollute the namespace.
32 once you start using a given tag, you should probably never change it.
33 (otherwise, mail for existing tickets won't get put in the right place)
37 Set($rtname , "example.com");
40 =item C<$EmailSubjectTagRegex>
42 This regexp controls what subject tags RT recognizes as its own.
43 If you're not dealing with historical C<$rtname> values, you'll likely
44 never have to enable this feature.
46 Be VERY CAREFUL with it. Note that it overrides C<$rtname> for subject
47 token matching and that you should use only "non-capturing" parenthesis
48 grouping. For example:
50 C<Set($EmailSubjectTagRegex, qr/(?:example.com|example.org)/i );>
54 C<Set($EmailSubjectTagRegex, qr/(example.com|example.org)/i );>
56 This setting would make RT behave exactly as it does without the
61 #Set($EmailSubjectTagRegex, qr/\Q$rtname\E/i );
65 =item C<$Organization>
67 You should set this to your organization's DNS domain. For example,
68 I<fsck.com> or I<asylum.arkham.ma.us>. It's used by the linking interface to
69 guarantee that ticket URIs are unique and easy to construct.
73 Set($Organization , "example.com");
75 =item C<$MinimumPasswordLength>
77 C<$MinimumPasswordLength> defines the minimum length for user
78 passwords. Setting it to 0 disables this check.
82 Set($MinimumPasswordLength , "5");
86 C<$Timezone> is used to convert times entered by users into GMT and back again
87 It should be set to a timezone recognized by your local unix box.
91 Set($Timezone , 'US/Eastern');
95 =head1 Database Configuration
99 =item C<$DatabaseType>
101 Database driver being used; case matters.
103 Valid types are "mysql", "Oracle" and "Pg"
107 Set($DatabaseType , 'Pg');
109 =item C<$DatabaseHost>, C<$DatabaseRTHost>
111 The domain name of your database server.
113 If you're running mysql and it's on localhost,
114 leave it blank for enhanced performance
118 Set($DatabaseHost , 'localhost');
119 Set($DatabaseRTHost , 'localhost');
121 =item C<$DatabasePort>
123 The port that your database server is running on. Ignored unless it's
124 a positive integer. It's usually safe to leave this blank
128 Set($DatabasePort , '');
130 =item C<$DatabaseUser>
132 The name of the database user (inside the database)
136 Set($DatabaseUser , 'freeside');
138 =item C<$DatabasePassword>
140 Password the C<$DatabaseUser> should use to access the database
144 Set($DatabasePassword , '');
146 =item C<$DatabaseName>
148 The name of the RT's database on your database server. For Oracle
149 it's SID, DB objects are created in L<$DatabaseUser>'s schema.
153 Set($DatabaseName , 'freeside');
155 =item C<$DatabaseRequireSSL>
157 If you're using Postgres and have compiled in SSL support,
158 set C<$DatabaseRequireSSL> to 1 to turn on SSL communication
162 Set($DatabaseRequireSSL , undef);
164 =item C<$UseSQLForACLChecks>
166 In RT for ages ACL are checked after search what in some situtations
167 result in empty search pages and wrong count of tickets.
169 Set C<$UseSQLForACLChecks> to 1 to use SQL and get rid of these problems.
171 However, this option is beta. In some cases it result in performance
172 improvements, but some setups can not handle it.
176 Set($UseSQLForACLChecks, undef);
178 =item C<$TicketsItemMapSize>
180 In RT at display page of a ticket and there is the current search,
181 then links for first, next, previous and last ticket are shown in
184 To build full map RT has to fetch full result set out of DB what can
185 eat lots of resourses. Using this option it's possible to limit number
188 Set C<$TicketsItemMapSize> to number of tickets you want RT to look
189 at to build the map. If full result set is bigger than that number
190 then there would be no 'last' link in the menu.
192 Set this to zero to return back to old behaviour.
196 Set($TicketsItemMapSize, 1000);
200 =head1 Incoming Mail Gateway Configuration
206 C<$OwnerEmail> is the address of a human who manages RT. RT will send
207 errors generated by the mail gateway to this address. This address
208 should _not_ be an address that's managed by your RT instance.
212 Set($OwnerEmail , 'root');
214 =item C<$LoopsToRTOwner>
216 If C<$LoopsToRTOwner> is defined, RT will send mail that it believes
217 might be a loop to C<$OwnerEmail>
221 Set($LoopsToRTOwner , 1);
225 If C<$StoreLoops> is defined, RT will record messages that it believes
226 to be part of mail loops.
228 As it does this, it will try to be careful not to send mail to the
229 sender of these messages
233 Set($StoreLoops , undef);
235 =item C<$MaxAttachmentSize>
237 C<$MaxAttachmentSize> sets the maximum size (in bytes) of attachments stored
240 For mysql and oracle, we set this size at 10 megabytes.
241 If you're running a postgres version earlier than 7.1, you will need
242 to drop this to 8192. (8k)
247 Set($MaxAttachmentSize , 10000000);
249 =item C<$TruncateLongAttachments>
251 C<$TruncateLongAttachments>: if this is set to a non-undef value,
252 RT will truncate attachments longer than C<$MaxAttachmentSize>.
256 Set($TruncateLongAttachments , undef);
258 =item C<$DropLongAttachments>
260 C<$DropLongAttachments>: if this is set to a non-undef value,
261 RT will silently drop attachments longer than C<MaxAttachmentSize>.
265 Set($DropLongAttachments , undef);
267 =item C<$ParseNewMessageForTicketCcs>
269 If C<$ParseNewMessageForTicketCcs> is true, RT will attempt to divine
270 Ticket 'Cc' watchers from the To and Cc lines of incoming messages
271 Be forewarned that if you have _any_ addresses which forward mail to
272 RT automatically and you enable this option without modifying
273 C<$RTAddressRegexp> below, you will get yourself into a heap of trouble.
277 Set($ParseNewMessageForTicketCcs , undef);
279 =item C<$RTAddressRegexp>
281 C<$RTAddressRegexp> is used to make sure RT doesn't add itself as a ticket CC if
282 the setting above is enabled. It is important that you set this to a
283 regular expression that matches all addresses used by your RT. This lets RT
284 avoid sending mail to itself. It will also hide RT addresses from the list of
285 "One-time Cc" and Bcc lists on ticket reply.
287 If you have a number of addresses configured in your RT database already, you
288 can generate a naive first pass regexp by using
290 perl etc/upgrade/generate-rtaddressregexp
294 Set($RTAddressRegexp , undef);
296 =item C<$IgnoreCcRegexp>
298 C<$IgnoreCcRegexp> is a regexp to exclude addresses from automatic addition
299 to the Cc list. Use this for addresses that are I<not> received by RT but
300 are sometimes added to Cc lists by mistake. Unlike C<$RTAddressRegexp>,
301 these addresses can still receive email from RT otherwise.
305 Set($IgnoreCcRegexp, undef);
307 =item C<$CanonicalizeEmailAddressMatch>, C<$CanonicalizeEmailAddressReplace>
309 RT provides functionality which allows the system to rewrite
310 incoming email addresses. In its simplest form,
311 you can substitute the value in $<CanonicalizeEmailAddressReplace>
312 for the value in $<CanonicalizeEmailAddressMatch>
313 (These values are passed to the $<CanonicalizeEmailAddress> subroutine in
316 By default, that routine performs a C<s/$Match/$Replace/gi> on any address
321 #Set($CanonicalizeEmailAddressMatch , '@subdomain\.example\.com$');
322 #Set($CanonicalizeEmailAddressReplace , '@example.com');
324 =item C<$CanonicalizeEmailAddressMatch>
326 Set this to true and the create new user page will use the values that you
327 enter in the form but use the function CanonicalizeUserInfo in
332 Set($CanonicalizeOnCreate, 0);
334 =item C<$ValidateUserEmailAddresses>
336 If C<$ValidateUserEmailAddresses> is true, RT will refuse to create users with
337 an invalid email address (as specified in RFC 2822) or with an email address
338 made of multiple email adresses.
342 Set($ValidateUserEmailAddresses, undef);
344 =item C<@MailPlugins>
346 C<@MailPlugins> is a list of auth plugins for L<RT::Interface::Email>
347 to use; see L<rt-mailgate>
351 =item C<$UnsafeEmailCommands>
353 C<$UnsafeEmailCommands>, if set to true, enables 'take' and 'resolve'
354 as possible actions via the mail gateway. As its name implies, this
355 is very unsafe, as it allows email with a forged sender to possibly
356 resolve arbitrary tickets!
360 =item C<$ExtractSubjectTagMatch>, C<$ExtractSubjectTagNoMatch>
362 The default "extract remote tracking tags" scrip settings; these
363 detect when your RT is talking to another RT, and adjusts the
368 Set($ExtractSubjectTagMatch, qr/\[.+? #\d+\]/);
369 Set($ExtractSubjectTagNoMatch, ( ${RT::EmailSubjectTagRegex}
370 ? qr/\[(?:${RT::EmailSubjectTagRegex}) #\d+\]/
371 : qr/\[\Q$RT::rtname\E #\d+\]/));
375 =head1 Outgoing Mail Configuration
379 =item C<$MailCommand>
381 C<$MailCommand> defines which method RT will use to try to send mail.
382 We know that 'sendmailpipe' works fairly well. If 'sendmailpipe'
383 doesn't work well for you, try 'sendmail'. Other options are 'smtp'
386 Note that you should remove the '-t' from C<$SendmailArguments>
387 if you use 'sendmail' rather than 'sendmailpipe'
389 For testing purposes, or to simply disable sending mail out into the world, you
390 can set C<$MailCommand> to 'testfile' which writes all mail to a temporary
391 file. RT will log the location of the temporary file so you can extract mail
396 Set($MailCommand , 'sendmailpipe');
398 =item C<$SetOutgoingMailFrom>
400 C<$SetOutgoingMailFrom> tells RT to set the sender envelope with the correspond
401 mail address of the ticket's queue.
403 Warning: If you use this setting, bounced mails will appear to be incoming
404 mail to the system, thus creating new tickets.
408 Set($SetOutgoingMailFrom, 0);
410 =item C<$OverrideOutgoingMailFrom>
412 C<$OverrideOutgoingMailFrom> is used for overwriting the Correspond
413 address of the queue as it is handed to sendmail -f. This helps force
414 the From_ header away from www-data or other email addresses that show
415 up in the "Sent by" line in Outlook.
417 The option is a hash reference of queue name to email address.
419 If there is no ticket involved, then the value of the C<Default> key will be
424 Set($OverrideOutgoingMailFrom, {
425 # 'Default' => 'admin@rt.example.com',
426 # 'General' => 'general@rt.example.com',
431 =item C<$DefaultMailPrecedence>
433 C<$DefaultMailPrecedence> is used to control the default
434 Precedence level of outgoing mail where none is specified.
435 By default it is C<bulk>, but if you only send mail to
436 your staff, you may wish to change it.
438 Note that you can set the precedence of individual templates
439 by including an explicit Precedence header.
441 If you set this value to C<undef> then we do not set a default
442 Precedence header to outgoing mail. However, if there already is a
443 Precedence header it will be preserved.
447 Set($DefaultMailPrecedence, 'bulk');
451 =item C<$DefaultErrorMailPrecedence>
453 C<$DefaultErrorMailPrecedence> is used to control the default
454 Precedence level of outgoing mail that indicates some kind of
455 error condition. By default it is C<bulk>, but if you only send
456 mail to your staff, you may wish to change it.
458 If you set this value to C<undef> then we do not add a Precedence
459 header to error mail.
463 Set($DefaultErrorMailPrecedence, 'bulk');
467 =item C<$UseOriginatorHeader>
469 C<$UseOriginatorHeader> is used to control the insertion of an
470 RT-Originator Header in every outgoing mail, containing the
471 mail address of the transaction creator.
475 Set($UseOriginatorHeader, 1);
479 =head1 Sendmail Configuration
481 These options only take effect if C<$MailCommand> is 'sendmail' or
486 =item C<$SendmailArguments>
488 C<$SendmailArguments> defines what flags to pass to C<$SendmailPath>
489 If you picked 'sendmailpipe', you MUST add a -t flag to C<$SendmailArguments>
490 These options are good for most sendmail wrappers and workalikes
492 These arguments are good for sendmail brand sendmail 8 and newer
493 C<Set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m");>
497 Set($SendmailArguments , "-oi -t");
500 =item C<$SendmailBounceArguments>
502 C<$SendmailBounceArguments> defines what flags to pass to C<$Sendmail>
503 assuming RT needs to send an error (ie. bounce).
507 Set($SendmailBounceArguments , '-f "<>"');
509 =item C<$SendmailPath>
511 If you selected 'sendmailpipe' above, you MUST specify the path to
512 your sendmail binary in C<$SendmailPath>.
516 Set($SendmailPath , "/usr/sbin/sendmail");
521 =head1 SMTP Configuration
523 These options only take effect if C<$MailCommand> is 'smtp'
529 C<$SMTPServer> should be set to the hostname of the SMTP server to use
533 Set($SMTPServer, undef);
537 C<$SMTPFrom> should be set to the 'From' address to use, if not the
542 Set($SMTPFrom, undef);
546 C<$SMTPDebug> should be set to true to debug SMTP mail sending
554 =head1 Other Mailer Configuration
560 C<@MailParams> defines a list of options passed to $MailCommand if it
561 is not 'sendmailpipe', 'sendmail', or 'smtp'
565 Set(@MailParams, ());
567 =item C<$CorrespondAddress>, C<$CommentAddress>
569 RT is designed such that any mail which already has a ticket-id associated
570 with it will get to the right place automatically.
572 C<$CorrespondAddress> and C<$CommentAddress> are the default addresses
573 that will be listed in From: and Reply-To: headers of correspondence
574 and comment mail tracked by RT, unless overridden by a queue-specific
579 Set($CorrespondAddress , '');
581 Set($CommentAddress , '');
583 =item C<$DashboardAddress>
585 The email address from which RT will send dashboards. If none is set, then
586 C<$OwnerEmail> will be used.
590 Set($DashboardAddress, '');
592 =item C<$UseFriendlyFromLine>
594 By default, RT sets the outgoing mail's "From:" header to
595 "SenderName via RT". Setting C<$UseFriendlyFromLine> to 0 disables it.
599 Set($UseFriendlyFromLine, 1);
601 =item C<$FriendlyFromLineFormat>
603 C<sprintf()> format of the friendly 'From:' header; its arguments
604 are SenderName and SenderEmailAddress.
608 Set($FriendlyFromLineFormat, "\"%s via RT\" <%s>");
610 =item C<$UseFriendlyToLine>
612 RT can optionally set a "Friendly" 'To:' header when sending messages to
613 Ccs or AdminCcs (rather than having a blank 'To:' header.
615 This feature DOES NOT WORK WITH SENDMAIL[tm] BRAND SENDMAIL
616 If you are using sendmail, rather than postfix, qmail, exim or some other MTA,
617 you _must_ disable this option.
621 Set($UseFriendlyToLine, 0);
623 =item C<$FriendlyToLineFormat>
625 C<sprintf()> format of the friendly 'To:' header; its arguments
626 are WatcherType and TicketId.
630 Set($FriendlyToLineFormat, "\"%s of ". RT->Config->Get('rtname') ." Ticket #%s\":;");
632 =item C<$NotifyActor>
634 By default, RT doesn't notify the person who performs an update, as they
635 already know what they've done. If you'd like to change this behaviour,
636 Set C<$NotifyActor> to 1
640 Set($NotifyActor, 0);
642 =item C<$RecordOutgoingEmail>
644 By default, RT records each message it sends out to its own internal database.
645 To change this behavior, set C<$RecordOutgoingEmail> to 0
649 Set($RecordOutgoingEmail, 1);
651 =item C<$VERPPrefix>, C<$VERPPrefix>
653 VERP support (http://cr.yp.to/proto/verp.txt)
655 uncomment the following two directives to generate envelope senders
656 of the form C<${VERPPrefix}${originaladdress}@${VERPDomain}>
657 (i.e. rt-jesse=fsck.com@rt.example.com ).
659 This currently only works with sendmail and sendmailppie.
663 # Set($VERPPrefix, 'rt-');
664 # Set($VERPDomain, $RT::Organization);
667 =item C<$ForwardFromUser>
669 By default, RT forwards a message using queue's address and adds RT's tag into
670 subject of the outgoing message, so recipients' replies go into RT as correspondents.
672 To change this behavior, set C<$ForwardFromUser> to true value and RT will use
673 address of the current user and leave subject without RT's tag.
677 Set($ForwardFromUser, 0);
679 =item C<$ShowBccHeader>
681 By default RT hides from the web UI information about blind copies user sent on
684 To change this set the following option to true value.
688 Set($ShowBccHeader, 0);
690 =item C<$DashboardSubject>
692 Lets you set the subject of dashboards. Arguments are the frequency (Daily,
693 Weekly, Monthly) of the dashboard and the dashboard's name. [_1] for the name
698 Set($DashboardSubject, '%s Dashboard: %s');
702 =head1 GnuPG Configuration
704 A full description of the (somewhat extensive) GnuPG integration can be found
705 by running the command `perldoc L<RT::Crypt::GnuPG>` (or `perldoc
706 lib/RT/Crypt/GnuPG.pm` from your RT install directory).
712 Set C<OutgoingMessagesFormat> to 'inline' to use inline encryption and
713 signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format.
715 If you want to allow people to encrypt attachments inside the DB then
716 set C<AllowEncryptDataInDB> to true
718 Set C<RejectOnMissingPrivateKey> to false if you don't want to reject
719 emails encrypted for key RT doesn't have and can not decrypt.
721 Set C<RejectOnBadData> to false if you don't want to reject letters
722 with incorrect GnuPG data.
728 OutgoingMessagesFormat => 'RFC', # Inline
729 AllowEncryptDataInDB => 0,
731 RejectOnMissingPrivateKey => 1,
732 RejectOnBadData => 1,
735 =item C<%GnuPGOptions>
737 Options of GnuPG program.
739 If you override this in your RT_SiteConfig, you should be sure
740 to include a homedir setting.
742 NOTE that options with '-' character MUST be quoted.
747 homedir => '/opt/rt3/var/data/gpg',
750 # keyserver => 'hkp://subkeys.pgp.net',
752 # enables the automatic retrieving of keys when encrypting
753 # 'auto-key-locate' => 'keyserver',
755 # enables the automatic retrieving of keys when verifying signatures
756 # 'auto-key-retrieve' => undef,
762 =head1 Logging Configuration
764 The default is to log anything except debugging
765 information to syslog. Check the L<Log::Dispatch> POD for
766 information about how to get things by syslog, mail or anything
767 else, get debugging info in the log, etc.
769 It might generally make sense to send error and higher by email to
770 some administrator. If you do this, be careful that this email
771 isn't sent to this RT instance. Mail loops will generate a critical
776 =item C<$LogToSyslog>, C<$LogToScreen>
778 The minimum level error that will be logged to the specific device.
779 From lowest to highest priority, the levels are:
780 debug info notice warning error critical alert emergency
784 Set($LogToSyslog , 'info');
785 Set($LogToScreen , 'info');
787 =item C<$LogToFile>, C<$LogDir>, C<$LogToFileNamed>
789 Logging to a standalone file is also possible, but note that the
790 file should needs to both exist and be writable by all direct users
791 of the RT API. This generally include the web server, whoever
792 rt-crontool runs as. Note that as rt-mailgate and the RT CLI go
793 through the webserver, so their users do not need to have write
794 permissions to this file. If you expect to have multiple users of
795 the direct API, Best Practical recommends using syslog instead of
800 Set($LogToFile , undef);
801 Set($LogDir, '/opt/rt3/var/log');
802 Set($LogToFileNamed , "rt.log"); #log to rt.log
804 =item C<$LogStackTraces>
806 If set to a log level then logging will include stack traces for
807 messages with level equal to or greater than specified.
809 NOTICE: Stack traces include parameters supplied to functions or
810 methods. It is possible for stack trace logging to reveal sensitive
811 information such as passwords or ticket content in your logs.
815 Set($LogStackTraces, '');
817 =item C<@LogToSyslogConf>
819 On Solaris or UnixWare, set to ( socket => 'inet' ). Options here
820 override any other options RT passes to L<Log::Dispatch::Syslog>.
821 Other interesting flags include facility and logopt. (See the
822 L<Log::Dispatch::Syslog> documentation for more information.) (Maybe
823 ident too, if you have multiple RT installations.)
827 Set(@LogToSyslogConf, ());
829 =item C<$StatementLog>,
831 RT has rudimentary SQL statement logging support if you have
832 DBIx-SearchBuilder 1.31_1 or higher; simply set C<$StatementLog> to be
833 the level that you wish SQL statements to be logged at.
837 Set($StatementLog, undef);
841 =head1 Web Interface Configuration
845 =item C<$WebDefaultStylesheet>
847 This determines the default stylesheet the RT web interface will use.
848 RT ships with several themes by default:
850 web2 The totally new, default layout for RT 3.8
851 3.5-default RT 3.5 and 3.6 original layout
852 3.4-compat A 3.4 compatibility stylesheet to make RT look
855 This bundled distibution of RT also includes (enabled by default):
856 freeside2.1 Integration with Freeside
858 This value actually specifies a directory in F<share/html/NoAuth/css/>
859 from which RT will try to load the file main.css (which should
860 @import any other files the stylesheet needs). This allows you to
861 easily and cleanly create your own stylesheets to apply to RT. This
862 option can be overridden by users in their preferences.
866 Set($WebDefaultStylesheet, 'freeside2.1');
868 =item C<$UsernameFormat>
870 This determines how user info is displayed. 'concise' will show one of
871 either NickName, RealName, Name or EmailAddress, depending on what exists
872 and whether the user is privileged or not. 'verbose' will show RealName and
877 Set($UsernameFormat, 'verbose');
881 Domain name of the RT server, eg 'www.example.com'. It should not contain
882 anything else, but server name.
886 Set( $WebDomain, 'localhost' );
890 If we're running as a superuser, run on port 80
891 Otherwise, pick a high port for this user.
893 443 is default port for https protocol.
897 Set($WebPort, 80);# + ($< * 7274) % 32766 + ($< && 1024));
901 If you're putting the web ui somewhere other than at the root of
902 your server, you should set C<$WebPath> to the path you'll be
905 C<$WebPath> requires a leading / but no trailing /, or it can be blank.
907 In most cases, you should leave C<$WebPath> set to '' (an empty value).
913 =item C<$WebBaseURL>, C<$WebURL>
915 Usually you don't want to set these options. The only obviouse reason is
916 RT accessible via https protocol on non standard port, eg
917 'https://rt.example.com:9999'. In all other cases these options are computed
918 using C<$WebDomain>, C<$WebPort> and C<$WebPath>.
920 C<$WebBaseURL> is the scheme, server and port (eg 'http://rt.example.com')
921 for constructing urls to the web UI. C<$WebBaseURL> doesn't need a trailing /.
923 C<$WebURL> is the C<$WebBaseURL>, C<$WebPath> and trailing /, for example:
924 'http://www.example.com/rt/'.
928 my $port = RT->Config->Get('WebPort');
930 ($port == 443? 'https': 'http') .'://'
931 . RT->Config->Get('WebDomain')
932 . ($port != 80 && $port != 443? ":$port" : '')
935 Set($WebURL, RT->Config->Get('WebBaseURL') . RT->Config->Get('WebPath') . "/");
937 =item C<$WebImagesURL>
939 C<$WebImagesURL> points to the base URL where RT can find its images.
940 Define the directory name to be used for images in rt web
945 Set($WebImagesURL, RT->Config->Get('WebPath') . "/NoAuth/images/");
949 C<$LogoURL> points to the URL of the RT logo displayed in the web UI
953 Set($LogoURL, RT->Config->Get('WebImagesURL') . "bplogo.gif");
955 =item C<$LogoLinkURL>
957 C<$LogoLinkURL> is the URL that the RT logo hyperlinks to.
961 Set($LogoLinkURL, "http://bestpractical.com");
963 =item C<$LogoAltText>
965 C<$LogoAltText> is a string of text for the alt-text of the logo. It
966 will be passed through C<loc> for localization.
970 Set($LogoAltText, "Best Practical Solutions, LLC corporate logo");
972 =item C<$LogoImageHeight>
974 C<$LogoImageHeight> is the value of the C<height> attribute of the logo
979 Set($LogoImageHeight, 33);
981 =item C<$LogoImageWidth>
983 C<$LogoImageWidth> is the value of the C<width> attribute of the logo
988 Set($LogoImageWidth, 177);
990 =item C<$WebNoAuthRegex>
992 What portion of RT's URL space should not require authentication.
994 This is mostly for extension and doesn't mean RT will work without
995 login if you change it.
999 Set($WebNoAuthRegex, qr{^ /rt (?:/+NoAuth/ | /+REST/\d+\.\d+/NoAuth/) }x );
1001 =item C<$SelfServiceRegex>
1003 What portion of RT's URLspace should be accessible to Unprivileged users
1004 This does not override the redirect from F</Ticket/Display.html> to
1005 F</SelfService/Display.html> when Unprivileged users attempt to access
1010 Set($SelfServiceRegex, qr!^(?:/+SelfService/)!x );
1012 =item C<$MessageBoxWidth>, C<$MessageBoxHeight>
1014 For message boxes, set the entry box width, height and what type of
1015 wrapping to use. These options can be overridden by users in their
1018 Default width: 72, height: 15
1020 These settings only apply to the non-RichText message box.
1021 See below for Rich Text settings.
1025 Set($MessageBoxWidth, 72);
1026 Set($MessageBoxHeight, 15);
1028 =item C<$MessageBoxWrap>
1030 Default wrapping: "HARD" (choices "SOFT", "HARD")
1032 Wrapping is disabled when using MessageBoxRichText because
1033 of a bad interaction between IE and wrapping with the Rich
1038 Set($MessageBoxWrap, "HARD");
1040 =item C<$MessageBoxRichText>
1042 Should "rich text" editing be enabled? This option lets your users send html email messages from the web interface.
1046 Set($MessageBoxRichText, 1);
1048 =item C<$MessageBoxRichTextHeight>
1050 Height of RichText javascript enabled editing boxes (in pixels)
1054 Set($MessageBoxRichTextHeight, 200);
1056 =item C<$MessageBoxIncludeSignature>
1058 Should your user's signatures (from their Preferences page) be included in Comments and Replies
1062 Set($MessageBoxIncludeSignature, 1);
1064 =item C<$MessageBoxIncludeSignatureOnComment>
1066 Should your user's signatures (from their Preferences page) be included in Comments. Setting this to false overrides C<$MessageBoxIncludeSignature>.
1070 Set($MessageBoxIncludeSignatureOnComment, 1);
1072 =item C<$WikiImplicitLinks>
1074 Support implicit links in WikiText custom fields? A true value
1075 causes InterCapped or ALLCAPS words in WikiText fields to
1076 automatically become links to searches for those words. If used on
1077 RTFM articles, it links to the RTFM article with that name.
1081 Set($WikiImplicitLinks, 0);
1083 =item C<$TrustHTMLAttachments>
1085 if C<TrustHTMLAttachments> is not defined, we will display them
1086 as text. This prevents malicious HTML and javascript from being
1087 sent in a request (although there is probably more to it than that)
1091 Set($TrustHTMLAttachments, undef);
1093 =item C<$AlwaysDownloadAttachments>
1095 Always download attachments, regardless of content type. If set,
1096 this overrides C<TrustHTMLAttachments>.
1100 Set($AlwaysDownloadAttachments, undef);
1102 =item C<$AttachmentUnits>
1104 Controls the units (kilobytes or bytes) that attachment sizes use
1105 for display. The default is to display kilobytes if the attachment
1106 is larger than 1024 bytes, bytes otherwise. If you set
1107 C<$AttachmentUnits> to C<'k'> then attachment sizes will always be
1108 displayed in kilobytes. If set to C<'b'>, then sizes will be bytes.
1112 Set($AttachmentUnits, undef);
1114 =item C<$EditCustomFieldsSingleColumn>
1116 When displaying a list of Ticket Custom Fields for editing, RT defaults
1117 to a 2 column list. If you set this to 1, it will instead display the
1118 Custom Fields in a single column.
1122 Set($EditCustomFieldsSingleColumn, 0);
1124 =item C<$RedistributeAutoGeneratedMessages>
1126 Should RT redistribute correspondence that it identifies as
1127 machine generated? A true value will do so; setting this to '0'
1128 will cause no such messages to be redistributed.
1129 You can also use 'privileged' (the default), which will redistribute
1130 only to privileged users. This helps to protect against malformed
1131 bounces and loops caused by autocreated requestors with bogus addresses.
1135 Set($RedistributeAutoGeneratedMessages, 'privileged');
1137 =item C<$PreferRichText>
1139 If C<$PreferRichText> is set to a true value, RT will show HTML/Rich text
1140 messages in preference to their plaintext alternatives. RT "scrubs" the
1141 html to show only a minimal subset of HTML to avoid possible contamination
1142 by cross-site-scripting attacks.
1146 Set($PreferRichText, undef);
1148 =item C<$WebExternalAuth>
1150 If C<$WebExternalAuth> is defined, RT will defer to the environment's
1151 REMOTE_USER variable.
1155 Set($WebExternalAuth, undef);
1157 =item C<$WebExternalAuthContinuous>
1159 If C<$WebExternalAuthContinuous> is defined, RT will check for the
1160 REMOTE_USER on each access. If you would prefer this to only happen
1161 once (at initial login) set this to a false value. The default setting
1162 will help ensure that if your external auth system deauthenticates a
1163 user, RT notices as soon as possible.
1167 Set($WebExternalAuthContinuous, 1);
1169 =item C<$WebFallbackToInternalAuth>
1171 If C<$WebFallbackToInternalAuth> is defined, the user is allowed a chance
1172 of fallback to the login screen, even if REMOTE_USER failed.
1176 Set($WebFallbackToInternalAuth , undef);
1178 =item C<$WebExternalGecos>
1180 C<$WebExternalGecos> means to match 'gecos' field as the user identity);
1181 useful with mod_auth_pwcheck and IIS Integrated Windows logon.
1185 Set($WebExternalGecos , undef);
1187 =item C<$WebExternalAuto>
1189 C<$WebExternalAuto> will create users under the same name as REMOTE_USER
1190 upon login, if it's missing in the Users table.
1194 Set($WebExternalAuto , undef);
1196 =item C<$AutoCreate>
1198 If C<$WebExternalAuto> is true, C<$AutoCreate> will be passed to User's
1199 Create method. Use it to set defaults, such as creating
1200 Unprivileged users with C<{ Privileged => 0 }>
1201 ( Must be a hashref of arguments )
1205 Set($AutoCreate, undef);
1207 =item C<$WebSessionClass>
1209 C<$WebSessionClass> is the class you wish to use for managing Sessions.
1210 It defaults to use your SQL database, but if you are using MySQL 3.x and
1211 plans to use non-ascii Queue names, uncomment and add this line to
1212 F<RT_SiteConfig.pm> will prevent session corruption.
1216 # Set($WebSessionClass , 'Apache::Session::File');
1218 =item C<$AutoLogoff>
1220 By default, RT's user sessions persist until a user closes his or her
1221 browser. With the C<$AutoLogoff> option you can setup session lifetime in
1222 minutes. A user will be logged out if he or she doesn't send any requests
1223 to RT for the defined time.
1227 Set($AutoLogoff, 0);
1229 =item C<$LogoutRefresh>
1231 The number of seconds to wait after logout before sending the user to the
1232 login page. By default, 1 second, though you may want to increase this if
1233 you display additional information on the logout page.
1237 Set($LogoutRefresh, 1);
1239 =item C<$WebSecureCookies>
1241 By default, RT's session cookie isn't marked as "secure" Some web browsers
1242 will treat secure cookies more carefully than non-secure ones, being careful
1243 not to write them to disk, only send them over an SSL secured connection
1244 and so on. To enable this behaviour, set C<$WebSecureCookies> to a true value.
1245 NOTE: You probably don't want to turn this on _unless_ users are only connecting
1246 via SSL encrypted HTTP connections.
1250 Set($WebSecureCookies, 0);
1252 =item C<$WebFlushDbCacheEveryRequest>
1254 By default, RT clears its database cache after every page view.
1255 This ensures that you've always got the most current information
1256 when working in a multi-process (mod_perl or FastCGI) Environment
1257 Setting C<$WebFlushDbCacheEveryRequest> to '0' will turn this off,
1258 which will speed RT up a bit, at the expense of a tiny bit of data
1263 Set($WebFlushDbCacheEveryRequest, '1');
1266 =item C<$MaxInlineBody>
1268 C<$MaxInlineBody> is the maximum attachment size that we want to see
1269 inline when viewing a transaction. RT will inline any text if value
1270 is undefined or 0. This option can be overridden by users in their
1275 Set($MaxInlineBody, 12000);
1277 =item C<$DefaultSummaryRows>
1279 C<$DefaultSummaryRows> is default number of rows displayed in for search
1280 results on the frontpage.
1284 Set($DefaultSummaryRows, 10);
1286 =item C<$HomePageRefreshInterval>
1288 C<$HomePageRefreshInterval> is default number of seconds to refresh the RT
1289 home page. Choose from [0, 120, 300, 600, 1200, 3600, 7200].
1293 Set($HomePageRefreshInterval, 0);
1295 =item C<$SearchResultsRefreshInterval>
1297 C<$SearchResultsRefreshInterval> is default number of seconds to refresh
1298 search results in RT. Choose from [0, 120, 300, 600, 1200, 3600, 7200].
1302 Set($SearchResultsRefreshInterval, 0);
1304 =item C<$ResolveDefaultUpdateType>
1306 Set the default Update Type when clicking the Resolve link in the Ticket
1309 Comment Comments (Not sent to requestors)
1310 Respond Reply to requestors
1314 Set($ResolveDefaultUpdateType, 'Comment');
1316 =item C<$SuppressAutoOpenOnUpdate>
1318 When users click Comment or Reply on a new ticket in the web UI, the default
1319 status for the ticket gets set to 'open' if the status is currently 'new'.
1320 Setting this option to 1 will suppress that behavior and leave the default
1321 status as 'new'. This option can be overridden by users in their preferences.
1325 Set($SuppressAutoOpenOnUpdate, 0);
1327 =item C<$OldestTransactionsFirst>
1329 By default, RT shows newest transactions at the bottom of the ticket
1330 history page, if you want see them at the top set this to '0'. This
1331 option can be overridden by users in their preferences.
1335 Set($OldestTransactionsFirst, '1');
1337 =item C<$ShowTransactionImages>
1339 By default, RT shows images attached to incoming (and outgoing) ticket updates
1340 inline. Set this variable to 0 if you'd like to disable that behaviour
1344 Set($ShowTransactionImages, 1);
1346 =item C<$PlainTextPre>
1348 Normally plaintext attachments are displayed as HTML with line
1349 breaks preserved. This causes space- and tab-based formatting not
1350 to be displayed correctly. By setting $PlainTextPre they'll be
1351 displayed using <pre> instead so such formatting works, but they'll
1352 use a monospaced font, no matter what the value of C<$PlainTextMono> is.
1356 Set($PlainTextPre, 0);
1359 =item C<$PlainTextMono>
1360 To display plaintext attachments,
1361 Set C<$PlainTextMono> to 1 to use monospaced font and preserve
1362 formatting, but unlike PlainTextPre, the text will wrap to fit into the
1367 Set($PlainTextMono, 0);
1369 =item C<$ShowUnreadMessageNotifications>
1371 By default, RT will prompt users when there are new, unread messages on
1372 tickets they are viewing.
1374 Set C<$ShowUnreadMessageNotifications> to a false value to disable this feature.
1378 Set($ShowUnreadMessageNotifications, 1);
1381 =item C<$HomepageComponents>
1383 C<$HomepageComponents> is an arrayref of allowed components on a user's
1384 customized homepage ("RT at a glance").
1388 Set($HomepageComponents, [qw(QuickCreate Quicksearch MyCalendar MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards)]);
1390 =item C<@MasonParameters>
1392 C<@MasonParameters> is the list of parameters for the constructor of
1393 HTML::Mason's Apache or CGI Handler. This is normally only useful
1394 for debugging, eg. profiling individual components with:
1396 use MasonX::Profiler; # available on CPAN
1397 Set(@MasonParameters, (preamble => 'my $p = MasonX::Profiler->new($m, $r);'));
1401 Set(@MasonParameters, ());
1403 =item C<$DefaultSearchResultFormat>
1405 C<$DefaultSearchResultFormat> is the default format for RT search results
1409 Set ($DefaultSearchResultFormat, qq{
1410 '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__id__</a></B>/TITLE:#',
1411 '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
1419 '<small>__Requestors__</small>',
1420 '<small>__CustomerTags__</small>',
1421 '<small>__CreatedRelative__</small>',
1422 '<small>__ToldRelative__</small>',
1423 '<small>__LastUpdatedRelative__</small>',
1424 '<small>__TimeLeft__</small>'});
1426 =item C<$DefaultSelfServiceSearchResultFormat>
1428 C<$DefaultSelfServiceSearchResultFormat> is the default format of searches displayed in the
1429 SelfService interface.
1433 Set($DefaultSelfServiceSearchResultFormat, qq{
1434 '<B><A HREF="__WebPath__/SelfService/Display.html?id=__id__">__id__</a></B>/TITLE:#',
1435 '<B><A HREF="__WebPath__/SelfService/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
1440 =item C<%AdminSearchResultFormat>
1442 In admin interface format strings similar to tickets search result
1443 formats are used. Use C<%AdminSearchResultFormat> to define format
1444 strings per RT class.
1448 Set(%AdminSearchResultFormat,
1450 q{'<a href="__WebPath__/Admin/Queues/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1451 .q{,'<a href="__WebPath__/Admin/Queues/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1452 .q{,__Description__,__Address__,__Priority__,__DefaultDueIn__,__Disabled__},
1455 q{'<a href="__WebPath__/Admin/Groups/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1456 .q{,'<a href="__WebPath__/Admin/Groups/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1457 .q{,'__Description__'},
1460 q{'<a href="__WebPath__/Admin/Users/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1461 .q{,'<a href="__WebPath__/Admin/Users/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1462 .q{,__RealName__, __EmailAddress__},
1465 q{'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1466 .q{,'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1467 .q{,__AppliedTo__, __FriendlyType__, __FriendlyPattern__},
1470 q{'<a href="__WebPath__/__WebRequestPathDir__/Scrip.html?id=__id__&Queue=__QueueId__">__id__</a>/TITLE:#'}
1471 .q{,'<a href="__WebPath__/__WebRequestPathDir__/Scrip.html?id=__id__&Queue=__QueueId__">__Description__</a>/TITLE:Description'}
1472 .q{,__Stage__, __Condition__, __Action__, __Template__},
1475 q{'<a href="__WebPath__/__WebRequestPathDir__/Template.html?Queue=__QueueId__&Template=__id__">__id__</a>/TITLE:#'}
1476 .q{,'<a href="__WebPath__/__WebRequestPathDir__/Template.html?Queue=__QueueId__&Template=__id__">__Name__</a>/TITLE:Name'}
1477 .q{,'__Description__'},
1480 =item C<$SuppressInlineTextFiles>
1482 If C<$SuppressInlineTextFiles> is set to a true value, then uploaded
1483 text files (text-type attachments with file names) are prevented
1484 from being displayed in-line when viewing a ticket's history.
1488 Set($SuppressInlineTextFiles, undef);
1490 =item C<$DontSearchFileAttachments>
1492 If C<$DontSearchFileAttachments> is set to a true value, then uploaded
1493 files (attachments with file names) are not searched during full-content
1498 Set($DontSearchFileAttachments, undef);
1502 The L<GD> module (which RT uses for graphs) ships with a builtin font
1503 that doesn't have full Unicode support. You can use a given TrueType font
1504 for a specific language by setting %ChartFont to (language =E<gt> the
1505 absolute path of a font) pairs. Your GD library must have support for
1506 TrueType fonts to use this option. If there is no entry for a language
1507 in the hash then font with 'others' key is used.
1509 RT comes with two TrueType fonts covering most available languages.
1515 'zh-cn' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1516 'zh-tw' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1517 'ja' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1518 'others' => "$RT::BasePath/share/fonts/DroidSans.ttf",
1521 =item C<$ChartsTimezonesInDB>
1523 RT stores dates using the UTC timezone in the DB, so charts grouped
1524 by dates and time are not representative. Set C<$ChartsTimezonesInDB>
1525 to a true value to enable timezone conversions using your DB's
1526 capabilities. You may need to do some work on the DB side to use this
1527 feature, read more in F<docs/timezones_in_charts.pod>.
1529 At this time, this feature only applies to MySQL and PostgreSQL.
1533 Set( $ChartsTimezonesInDB, 0 );
1535 =item C<@Active_MakeClicky>
1537 MakeClicky detects various formats of data in headers and email
1538 messages, and extends them with supporting links. By default, RT
1539 provides two formats:
1541 * 'httpurl': detects http:// and https:// URLs and adds '[Open URL]'
1544 * 'httpurl_overwrite': also detects URLs as 'httpurl' format, but
1545 replace URL with link and *adds spaces* into text if it's longer
1546 then 30 chars. This allow browser to wrap long URLs and avoid
1547 horizontal scrolling.
1549 See F<share/html/Elements/MakeClicky> for documentation on how to add your own.
1553 Set(@Active_MakeClicky, qw());
1555 =item C<$DefaultQueue>
1557 Use this to select the default queue name that will be used for creating new
1558 tickets. You may use either the queue's name or its ID. This only affects the
1559 queue selection boxes on the web interface.
1563 #Set($DefaultQueue, 'General');
1565 =item C<$DefaultTimeUnitsToHours>
1567 Use this to set the default units for time entry to hours instead of minutes.
1571 Set($DefaultTimeUnitsToHours, 0);
1575 =head1 L<Net::Server> (rt-server) Configuration
1579 =item C<$StandaloneMinServers>, C<$StandaloneMaxServers>
1581 The absolute minimum and maximum number of servers that will be created to
1582 handle requests. Having multiple servers means that serving a slow page will
1583 affect other users less.
1587 Set($StandaloneMinServers, 1);
1588 Set($StandaloneMaxServers, 1);
1590 =item C<$StandaloneMinSpareServers>, C<$StandaloneMaxSpareServers>
1592 These next two options can be used to scale up and down the number of servers
1593 to adjust to load. These two options will respect the C<$StandaloneMinServers
1594 > and C<$StandaloneMaxServers options>.
1598 Set($StandaloneMinSpareServers, 0);
1599 Set($StandaloneMaxSpareServers, 0);
1601 =item C<$StandaloneMaxRequests>
1603 This sets the absolute maximum number of requests a single server will serve.
1604 Setting this would be useful if, for example, memory usage slowly crawls up
1609 #Set($StandaloneMaxRequests, 50);
1611 =item C<%NetServerOptions>
1613 C<%NetServerOptions> is a hash of additional options to use for
1614 L<Net::Server/DEFAULT ARGUMENTS>. For example, you could set
1615 reverse_lookups to get the hostnames for all users with:
1617 C<Set(%NetServerOptions, (reverse_lookups => 1));>
1621 Set(%NetServerOptions, ());
1626 =head1 UTF-8 Configuration
1630 =item C<@LexiconLanguages>
1632 An array that contains languages supported by RT's internationalization
1633 interface. Defaults to all *.po lexicons; setting it to C<qw(en ja)> will make
1634 RT bilingual instead of multilingual, but will save some memory.
1638 Set(@LexiconLanguages, qw(*));
1640 =item C<@EmailInputEncodings>
1642 An array that contains default encodings used to guess which charset
1643 an attachment uses if not specified. Must be recognized by
1648 Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii));
1650 =item C<$EmailOutputEncoding>
1652 The charset for localized email. Must be recognized by Encode.
1656 Set($EmailOutputEncoding, 'utf-8');
1661 =head1 Date Handling Configuration
1665 =item C<$DateTimeFormat>
1667 You can choose date and time format. See "Output formatters"
1668 section in perldoc F<lib/RT/Date.pm> for more options. This option can
1669 be overridden by users in their preferences.
1672 C<Set($DateTimeFormat, 'LocalizedDateTime');>
1673 C<Set($DateTimeFormat, { Format => 'ISO', Seconds => 0 });>
1674 C<Set($DateTimeFormat, 'RFC2822');>
1675 C<Set($DateTimeFormat, { Format => 'RFC2822', Seconds => 0, DayOfWeek => 0 });>
1679 Set($DateTimeFormat, 'DefaultFormat');
1681 # Next two options are for Time::ParseDate
1683 =item C<$DateDayBeforeMonth>
1685 Set this to 1 if your local date convention looks like "dd/mm/yy" instead of
1686 "mm/dd/yy". Used only for parsing, not for displaying dates.
1690 Set($DateDayBeforeMonth , 1);
1692 =item C<$AmbiguousDayInPast>, C<$AmbiguousDayInFuture>
1694 Should an unspecified day or year in a date refer to a future or a
1695 past value? For example, should a date of "Tuesday" default to mean
1696 the date for next Tuesday or last Tuesday? Should the date "March 1"
1697 default to the date for next March or last March?
1699 Set $<AmbiguousDayInPast> for the last date, or $<$AmbiguousDayInFuture> for the
1702 The default is usually good.
1706 Set($AmbiguousDayInPast, 0);
1707 Set($AmbiguousDayInFuture, 0);
1711 =head1 Approval Configuration
1713 Configuration for the approval system
1717 =item C<$ApprovalRejectionNotes>
1719 Should rejection notes be sent to the requestors? The default is true.
1723 Set($ApprovalRejectionNotes, 1);
1728 =head1 Miscellaneous Configuration
1732 =item C<@ActiveStatus>, C<@InactiveStatus>
1734 You can define new statuses and even reorder existing statuses here.
1735 WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT
1736 will break horribly. The statuses you add must be no longer than
1741 Set(@ActiveStatus, qw(new open stalled));
1742 Set(@InactiveStatus, qw(resolved rejected deleted));
1744 =item C<$LinkTransactionsRun1Scrip>
1746 RT-3.4 backward compatibility setting. Add/Delete Link used to record one
1747 transaction and run one scrip. Set this value to 1 if you want
1748 only one of the link transactions to have scrips run.
1752 Set($LinkTransactionsRun1Scrip, 0);
1754 =item C<$StrictLinkACL>
1756 When this feature is enabled a user needs I<ModifyTicket> rights on both
1757 tickets to link them together, otherwise he can have rights on either of
1762 Set($StrictLinkACL, 1);
1764 =item C<$PreviewScripMessages>
1766 Set C<$PreviewScripMessages> to 1 if the scrips preview on the ticket
1767 reply page should include the content of the messages to be sent.
1771 Set($PreviewScripMessages, 0);
1773 =item C<$UseTransactionBatch>
1775 Set C<$UseTransactionBatch> to 1 to execute transactions in batches,
1776 such that a resolve and comment (for example) would happen
1777 simultaneously, instead of as two transactions, unaware of each
1782 Set($UseTransactionBatch, 1);
1784 =item C<@CustomFieldValuesSources>
1786 Set C<@CustomFieldValuesSources> to a list of class names which extend
1787 L<RT::CustomFieldValues::External>. This can be used to pull lists of
1788 custom field values from external sources at runtime.
1792 Set(@CustomFieldValuesSources, ('RT::CustomFieldValues::Queues'));
1794 =item C<$CanonicalizeRedirectURLs>
1796 Set C<$CanonicalizeRedirectURLs> to 1 to use $C<WebURL> when redirecting rather
1797 than the one we get from C<%ENV>.
1799 If you use RT behind a reverse proxy, you almost certainly want to
1804 Set($CanonicalizeRedirectURLs, 0);
1805 =item C<$EnableReminders>
1807 Hide links/portlets related to Reminders by setting this to 0
1811 Set($EnableReminders,1);
1816 Set C<@Plugins> to a list of external RT plugins that should be enabled (those
1817 plugins have to be previously downloaded and installed).
1820 C<Set(@Plugins, (qw(Extension::QuickDelete RT::FM)));>
1824 Set(@Plugins, (qw(RTx::Calendar
1825 RT::Extension::MobileUI))); #RTx::Checklist ));
1829 =head1 Development Configuration
1835 RT comes with a "Development mode" setting.
1836 This setting, as a convenience for developers, turns on
1837 all sorts of development options that you most likely don't want in
1840 * Turns off Mason's 'static_source' directive. By default, you can't
1841 edit RT's web ui components on the fly and have RT magically pick up
1842 your changes. (It's a big performance hit)
1848 Set($DevelMode, '0');
1853 =head1 Deprecated Options
1857 =item C<$AlwaysUseBase64>
1859 Encode blobs as base64 in DB (?)
1861 =item C<$TicketBaseURI>
1863 Base URI to tickets in this system; used when loading (?)
1865 =item C<$UseCodeTickets>
1867 This option is exists for backwards compatibility. Don't use it.