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<$NonCustomerEmailRegexp>
346 Normally, when a ticket is linked to a customer, any requestors on that
347 ticket that didn't previously have customer memberships are linked to
348 the customer also. C<$NonCustomerEmailRegexp> is a regexp for email
349 addresses that should I<not> automatically be linked to a customer in
354 Set($NonCustomerEmailRegexp, undef);
356 =item C<@MailPlugins>
358 C<@MailPlugins> is a list of auth plugins for L<RT::Interface::Email>
359 to use; see L<rt-mailgate>
363 =item C<$UnsafeEmailCommands>
365 C<$UnsafeEmailCommands>, if set to true, enables 'take' and 'resolve'
366 as possible actions via the mail gateway. As its name implies, this
367 is very unsafe, as it allows email with a forged sender to possibly
368 resolve arbitrary tickets!
372 =item C<$ExtractSubjectTagMatch>, C<$ExtractSubjectTagNoMatch>
374 The default "extract remote tracking tags" scrip settings; these
375 detect when your RT is talking to another RT, and adjusts the
380 Set($ExtractSubjectTagMatch, qr/\[.+? #\d+\]/);
381 Set($ExtractSubjectTagNoMatch, ( ${RT::EmailSubjectTagRegex}
382 ? qr/\[(?:${RT::EmailSubjectTagRegex}) #\d+\]/
383 : qr/\[\Q$RT::rtname\E #\d+\]/));
387 =head1 Outgoing Mail Configuration
391 =item C<$MailCommand>
393 C<$MailCommand> defines which method RT will use to try to send mail.
394 We know that 'sendmailpipe' works fairly well. If 'sendmailpipe'
395 doesn't work well for you, try 'sendmail'. Other options are 'smtp'
398 Note that you should remove the '-t' from C<$SendmailArguments>
399 if you use 'sendmail' rather than 'sendmailpipe'
401 For testing purposes, or to simply disable sending mail out into the world, you
402 can set C<$MailCommand> to 'testfile' which writes all mail to a temporary
403 file. RT will log the location of the temporary file so you can extract mail
408 Set($MailCommand , 'sendmailpipe');
410 =item C<$SetOutgoingMailFrom>
412 C<$SetOutgoingMailFrom> tells RT to set the sender envelope with the correspond
413 mail address of the ticket's queue.
415 Warning: If you use this setting, bounced mails will appear to be incoming
416 mail to the system, thus creating new tickets.
420 Set($SetOutgoingMailFrom, 0);
422 =item C<$OverrideOutgoingMailFrom>
424 C<$OverrideOutgoingMailFrom> is used for overwriting the Correspond
425 address of the queue as it is handed to sendmail -f. This helps force
426 the From_ header away from www-data or other email addresses that show
427 up in the "Sent by" line in Outlook.
429 The option is a hash reference of queue name to email address.
431 If there is no ticket involved, then the value of the C<Default> key will be
436 Set($OverrideOutgoingMailFrom, {
437 # 'Default' => 'admin@rt.example.com',
438 # 'General' => 'general@rt.example.com',
443 =item C<$DefaultMailPrecedence>
445 C<$DefaultMailPrecedence> is used to control the default
446 Precedence level of outgoing mail where none is specified.
447 By default it is C<bulk>, but if you only send mail to
448 your staff, you may wish to change it.
450 Note that you can set the precedence of individual templates
451 by including an explicit Precedence header.
453 If you set this value to C<undef> then we do not set a default
454 Precedence header to outgoing mail. However, if there already is a
455 Precedence header it will be preserved.
459 Set($DefaultMailPrecedence, 'bulk');
463 =item C<$DefaultErrorMailPrecedence>
465 C<$DefaultErrorMailPrecedence> is used to control the default
466 Precedence level of outgoing mail that indicates some kind of
467 error condition. By default it is C<bulk>, but if you only send
468 mail to your staff, you may wish to change it.
470 If you set this value to C<undef> then we do not add a Precedence
471 header to error mail.
475 Set($DefaultErrorMailPrecedence, 'bulk');
479 =item C<$UseOriginatorHeader>
481 C<$UseOriginatorHeader> is used to control the insertion of an
482 RT-Originator Header in every outgoing mail, containing the
483 mail address of the transaction creator.
487 Set($UseOriginatorHeader, 1);
491 =head1 Sendmail Configuration
493 These options only take effect if C<$MailCommand> is 'sendmail' or
498 =item C<$SendmailArguments>
500 C<$SendmailArguments> defines what flags to pass to C<$SendmailPath>
501 If you picked 'sendmailpipe', you MUST add a -t flag to C<$SendmailArguments>
502 These options are good for most sendmail wrappers and workalikes
504 These arguments are good for sendmail brand sendmail 8 and newer
505 C<Set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m");>
509 Set($SendmailArguments , "-oi -t");
512 =item C<$SendmailBounceArguments>
514 C<$SendmailBounceArguments> defines what flags to pass to C<$Sendmail>
515 assuming RT needs to send an error (ie. bounce).
519 Set($SendmailBounceArguments , '-f "<>"');
521 =item C<$SendmailPath>
523 If you selected 'sendmailpipe' above, you MUST specify the path to
524 your sendmail binary in C<$SendmailPath>.
528 Set($SendmailPath , "/usr/sbin/sendmail");
533 =head1 SMTP Configuration
535 These options only take effect if C<$MailCommand> is 'smtp'
541 C<$SMTPServer> should be set to the hostname of the SMTP server to use
545 Set($SMTPServer, undef);
549 C<$SMTPFrom> should be set to the 'From' address to use, if not the
554 Set($SMTPFrom, undef);
558 C<$SMTPDebug> should be set to true to debug SMTP mail sending
566 =head1 Other Mailer Configuration
572 C<@MailParams> defines a list of options passed to $MailCommand if it
573 is not 'sendmailpipe', 'sendmail', or 'smtp'
577 Set(@MailParams, ());
579 =item C<$CorrespondAddress>, C<$CommentAddress>
581 RT is designed such that any mail which already has a ticket-id associated
582 with it will get to the right place automatically.
584 C<$CorrespondAddress> and C<$CommentAddress> are the default addresses
585 that will be listed in From: and Reply-To: headers of correspondence
586 and comment mail tracked by RT, unless overridden by a queue-specific
591 Set($CorrespondAddress , '');
593 Set($CommentAddress , '');
595 =item C<$DashboardAddress>
597 The email address from which RT will send dashboards. If none is set, then
598 C<$OwnerEmail> will be used.
602 Set($DashboardAddress, '');
604 =item C<$UseFriendlyFromLine>
606 By default, RT sets the outgoing mail's "From:" header to
607 "SenderName via RT". Setting C<$UseFriendlyFromLine> to 0 disables it.
611 Set($UseFriendlyFromLine, 1);
613 =item C<$FriendlyFromLineFormat>
615 C<sprintf()> format of the friendly 'From:' header; its arguments
616 are SenderName and SenderEmailAddress.
620 Set($FriendlyFromLineFormat, "\"%s via RT\" <%s>");
622 =item C<$UseFriendlyToLine>
624 RT can optionally set a "Friendly" 'To:' header when sending messages to
625 Ccs or AdminCcs (rather than having a blank 'To:' header.
627 This feature DOES NOT WORK WITH SENDMAIL[tm] BRAND SENDMAIL
628 If you are using sendmail, rather than postfix, qmail, exim or some other MTA,
629 you _must_ disable this option.
633 Set($UseFriendlyToLine, 0);
635 =item C<$FriendlyToLineFormat>
637 C<sprintf()> format of the friendly 'To:' header; its arguments
638 are WatcherType and TicketId.
642 Set($FriendlyToLineFormat, "\"%s of ". RT->Config->Get('rtname') ." Ticket #%s\":;");
644 =item C<$NotifyActor>
646 By default, RT doesn't notify the person who performs an update, as they
647 already know what they've done. If you'd like to change this behaviour,
648 Set C<$NotifyActor> to 1
652 Set($NotifyActor, 0);
654 =item C<$RecordOutgoingEmail>
656 By default, RT records each message it sends out to its own internal database.
657 To change this behavior, set C<$RecordOutgoingEmail> to 0
661 Set($RecordOutgoingEmail, 1);
663 =item C<$VERPPrefix>, C<$VERPPrefix>
665 VERP support (http://cr.yp.to/proto/verp.txt)
667 uncomment the following two directives to generate envelope senders
668 of the form C<${VERPPrefix}${originaladdress}@${VERPDomain}>
669 (i.e. rt-jesse=fsck.com@rt.example.com ).
671 This currently only works with sendmail and sendmailppie.
675 # Set($VERPPrefix, 'rt-');
676 # Set($VERPDomain, $RT::Organization);
679 =item C<$ForwardFromUser>
681 By default, RT forwards a message using queue's address and adds RT's tag into
682 subject of the outgoing message, so recipients' replies go into RT as correspondents.
684 To change this behavior, set C<$ForwardFromUser> to true value and RT will use
685 address of the current user and leave subject without RT's tag.
689 Set($ForwardFromUser, 0);
691 =item C<$ShowBccHeader>
693 By default RT hides from the web UI information about blind copies user sent on
696 To change this set the following option to true value.
700 Set($ShowBccHeader, 0);
702 =item C<$DashboardSubject>
704 Lets you set the subject of dashboards. Arguments are the frequency (Daily,
705 Weekly, Monthly) of the dashboard and the dashboard's name. [_1] for the name
710 Set($DashboardSubject, '%s Dashboard: %s');
714 =head1 GnuPG Configuration
716 A full description of the (somewhat extensive) GnuPG integration can be found
717 by running the command `perldoc L<RT::Crypt::GnuPG>` (or `perldoc
718 lib/RT/Crypt/GnuPG.pm` from your RT install directory).
724 Set C<OutgoingMessagesFormat> to 'inline' to use inline encryption and
725 signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format.
727 If you want to allow people to encrypt attachments inside the DB then
728 set C<AllowEncryptDataInDB> to true
730 Set C<RejectOnMissingPrivateKey> to false if you don't want to reject
731 emails encrypted for key RT doesn't have and can not decrypt.
733 Set C<RejectOnBadData> to false if you don't want to reject letters
734 with incorrect GnuPG data.
740 OutgoingMessagesFormat => 'RFC', # Inline
741 AllowEncryptDataInDB => 0,
743 RejectOnMissingPrivateKey => 1,
744 RejectOnBadData => 1,
747 =item C<%GnuPGOptions>
749 Options of GnuPG program.
751 If you override this in your RT_SiteConfig, you should be sure
752 to include a homedir setting.
754 NOTE that options with '-' character MUST be quoted.
759 homedir => '/opt/rt3/var/data/gpg',
762 # keyserver => 'hkp://subkeys.pgp.net',
764 # enables the automatic retrieving of keys when encrypting
765 # 'auto-key-locate' => 'keyserver',
767 # enables the automatic retrieving of keys when verifying signatures
768 # 'auto-key-retrieve' => undef,
774 =head1 Logging Configuration
776 The default is to log anything except debugging
777 information to syslog. Check the L<Log::Dispatch> POD for
778 information about how to get things by syslog, mail or anything
779 else, get debugging info in the log, etc.
781 It might generally make sense to send error and higher by email to
782 some administrator. If you do this, be careful that this email
783 isn't sent to this RT instance. Mail loops will generate a critical
788 =item C<$LogToSyslog>, C<$LogToScreen>
790 The minimum level error that will be logged to the specific device.
791 From lowest to highest priority, the levels are:
792 debug info notice warning error critical alert emergency
796 Set($LogToSyslog , 'info');
797 Set($LogToScreen , 'info');
799 =item C<$LogToFile>, C<$LogDir>, C<$LogToFileNamed>
801 Logging to a standalone file is also possible, but note that the
802 file should needs to both exist and be writable by all direct users
803 of the RT API. This generally include the web server, whoever
804 rt-crontool runs as. Note that as rt-mailgate and the RT CLI go
805 through the webserver, so their users do not need to have write
806 permissions to this file. If you expect to have multiple users of
807 the direct API, Best Practical recommends using syslog instead of
812 Set($LogToFile , undef);
813 Set($LogDir, '/opt/rt3/var/log');
814 Set($LogToFileNamed , "rt.log"); #log to rt.log
816 =item C<$LogStackTraces>
818 If set to a log level then logging will include stack traces for
819 messages with level equal to or greater than specified.
821 NOTICE: Stack traces include parameters supplied to functions or
822 methods. It is possible for stack trace logging to reveal sensitive
823 information such as passwords or ticket content in your logs.
827 Set($LogStackTraces, '');
829 =item C<@LogToSyslogConf>
831 On Solaris or UnixWare, set to ( socket => 'inet' ). Options here
832 override any other options RT passes to L<Log::Dispatch::Syslog>.
833 Other interesting flags include facility and logopt. (See the
834 L<Log::Dispatch::Syslog> documentation for more information.) (Maybe
835 ident too, if you have multiple RT installations.)
839 Set(@LogToSyslogConf, ());
841 =item C<$StatementLog>,
843 RT has rudimentary SQL statement logging support if you have
844 DBIx-SearchBuilder 1.31_1 or higher; simply set C<$StatementLog> to be
845 the level that you wish SQL statements to be logged at.
849 Set($StatementLog, undef);
853 =head1 Web Interface Configuration
857 =item C<$WebDefaultStylesheet>
859 This determines the default stylesheet the RT web interface will use.
860 RT ships with several themes by default:
862 web2 The totally new, default layout for RT 3.8
863 3.5-default RT 3.5 and 3.6 original layout
864 3.4-compat A 3.4 compatibility stylesheet to make RT look
867 This bundled distibution of RT also includes (enabled by default):
868 freeside2.1 Integration with Freeside
870 This value actually specifies a directory in F<share/html/NoAuth/css/>
871 from which RT will try to load the file main.css (which should
872 @import any other files the stylesheet needs). This allows you to
873 easily and cleanly create your own stylesheets to apply to RT. This
874 option can be overridden by users in their preferences.
878 Set($WebDefaultStylesheet, 'freeside2.1');
880 =item C<$UsernameFormat>
882 This determines how user info is displayed. 'concise' will show one of
883 either NickName, RealName, Name or EmailAddress, depending on what exists
884 and whether the user is privileged or not. 'verbose' will show RealName and
889 Set($UsernameFormat, 'verbose');
893 Domain name of the RT server, eg 'www.example.com'. It should not contain
894 anything else, but server name.
898 Set( $WebDomain, 'localhost' );
902 If we're running as a superuser, run on port 80
903 Otherwise, pick a high port for this user.
905 443 is default port for https protocol.
909 Set($WebPort, 80);# + ($< * 7274) % 32766 + ($< && 1024));
913 If you're putting the web ui somewhere other than at the root of
914 your server, you should set C<$WebPath> to the path you'll be
917 C<$WebPath> requires a leading / but no trailing /, or it can be blank.
919 In most cases, you should leave C<$WebPath> set to '' (an empty value).
925 =item C<$WebBaseURL>, C<$WebURL>
927 Usually you don't want to set these options. The only obviouse reason is
928 RT accessible via https protocol on non standard port, eg
929 'https://rt.example.com:9999'. In all other cases these options are computed
930 using C<$WebDomain>, C<$WebPort> and C<$WebPath>.
932 C<$WebBaseURL> is the scheme, server and port (eg 'http://rt.example.com')
933 for constructing urls to the web UI. C<$WebBaseURL> doesn't need a trailing /.
935 C<$WebURL> is the C<$WebBaseURL>, C<$WebPath> and trailing /, for example:
936 'http://www.example.com/rt/'.
940 my $port = RT->Config->Get('WebPort');
942 ($port == 443? 'https': 'http') .'://'
943 . RT->Config->Get('WebDomain')
944 . ($port != 80 && $port != 443? ":$port" : '')
947 Set($WebURL, RT->Config->Get('WebBaseURL') . RT->Config->Get('WebPath') . "/");
949 =item C<$WebImagesURL>
951 C<$WebImagesURL> points to the base URL where RT can find its images.
952 Define the directory name to be used for images in rt web
957 Set($WebImagesURL, RT->Config->Get('WebPath') . "/NoAuth/images/");
961 C<$LogoURL> points to the URL of the RT logo displayed in the web UI
965 Set($LogoURL, RT->Config->Get('WebImagesURL') . "bplogo.gif");
967 =item C<$LogoLinkURL>
969 C<$LogoLinkURL> is the URL that the RT logo hyperlinks to.
973 Set($LogoLinkURL, "http://bestpractical.com");
975 =item C<$LogoAltText>
977 C<$LogoAltText> is a string of text for the alt-text of the logo. It
978 will be passed through C<loc> for localization.
982 Set($LogoAltText, "Best Practical Solutions, LLC corporate logo");
984 =item C<$LogoImageHeight>
986 C<$LogoImageHeight> is the value of the C<height> attribute of the logo
991 Set($LogoImageHeight, 33);
993 =item C<$LogoImageWidth>
995 C<$LogoImageWidth> is the value of the C<width> attribute of the logo
1000 Set($LogoImageWidth, 177);
1002 =item C<$WebNoAuthRegex>
1004 What portion of RT's URL space should not require authentication.
1006 This is mostly for extension and doesn't mean RT will work without
1007 login if you change it.
1011 Set($WebNoAuthRegex, qr{^ /rt (?:/+NoAuth/ | /+REST/\d+\.\d+/NoAuth/) }x );
1013 =item C<$SelfServiceRegex>
1015 What portion of RT's URLspace should be accessible to Unprivileged users
1016 This does not override the redirect from F</Ticket/Display.html> to
1017 F</SelfService/Display.html> when Unprivileged users attempt to access
1022 Set($SelfServiceRegex, qr!^(?:/+SelfService/)!x );
1024 =item C<$MessageBoxWidth>, C<$MessageBoxHeight>
1026 For message boxes, set the entry box width, height and what type of
1027 wrapping to use. These options can be overridden by users in their
1030 Default width: 72, height: 15
1032 These settings only apply to the non-RichText message box.
1033 See below for Rich Text settings.
1037 Set($MessageBoxWidth, 72);
1038 Set($MessageBoxHeight, 15);
1040 =item C<$MessageBoxWrap>
1042 Default wrapping: "HARD" (choices "SOFT", "HARD")
1044 Wrapping is disabled when using MessageBoxRichText because
1045 of a bad interaction between IE and wrapping with the Rich
1050 Set($MessageBoxWrap, "HARD");
1052 =item C<$MessageBoxRichText>
1054 Should "rich text" editing be enabled? This option lets your users send html email messages from the web interface.
1058 Set($MessageBoxRichText, 1);
1060 =item C<$MessageBoxRichTextHeight>
1062 Height of RichText javascript enabled editing boxes (in pixels)
1066 Set($MessageBoxRichTextHeight, 200);
1068 =item C<$MessageBoxIncludeSignature>
1070 Should your user's signatures (from their Preferences page) be included in Comments and Replies
1074 Set($MessageBoxIncludeSignature, 1);
1076 =item C<$MessageBoxIncludeSignatureOnComment>
1078 Should your user's signatures (from their Preferences page) be included in Comments. Setting this to false overrides C<$MessageBoxIncludeSignature>.
1082 Set($MessageBoxIncludeSignatureOnComment, 1);
1084 =item C<$WikiImplicitLinks>
1086 Support implicit links in WikiText custom fields? A true value
1087 causes InterCapped or ALLCAPS words in WikiText fields to
1088 automatically become links to searches for those words. If used on
1089 RTFM articles, it links to the RTFM article with that name.
1093 Set($WikiImplicitLinks, 0);
1095 =item C<$TrustHTMLAttachments>
1097 if C<TrustHTMLAttachments> is not defined, we will display them
1098 as text. This prevents malicious HTML and javascript from being
1099 sent in a request (although there is probably more to it than that)
1103 Set($TrustHTMLAttachments, undef);
1105 =item C<$AlwaysDownloadAttachments>
1107 Always download attachments, regardless of content type. If set,
1108 this overrides C<TrustHTMLAttachments>.
1112 Set($AlwaysDownloadAttachments, undef);
1114 =item C<$AttachmentUnits>
1116 Controls the units (kilobytes or bytes) that attachment sizes use
1117 for display. The default is to display kilobytes if the attachment
1118 is larger than 1024 bytes, bytes otherwise. If you set
1119 C<$AttachmentUnits> to C<'k'> then attachment sizes will always be
1120 displayed in kilobytes. If set to C<'b'>, then sizes will be bytes.
1124 Set($AttachmentUnits, undef);
1126 =item C<$EditCustomFieldsSingleColumn>
1128 When displaying a list of Ticket Custom Fields for editing, RT defaults
1129 to a 2 column list. If you set this to 1, it will instead display the
1130 Custom Fields in a single column.
1134 Set($EditCustomFieldsSingleColumn, 0);
1136 =item C<$RedistributeAutoGeneratedMessages>
1138 Should RT redistribute correspondence that it identifies as
1139 machine generated? A true value will do so; setting this to '0'
1140 will cause no such messages to be redistributed.
1141 You can also use 'privileged' (the default), which will redistribute
1142 only to privileged users. This helps to protect against malformed
1143 bounces and loops caused by autocreated requestors with bogus addresses.
1147 Set($RedistributeAutoGeneratedMessages, 'privileged');
1149 =item C<$PreferRichText>
1151 If C<$PreferRichText> is set to a true value, RT will show HTML/Rich text
1152 messages in preference to their plaintext alternatives. RT "scrubs" the
1153 html to show only a minimal subset of HTML to avoid possible contamination
1154 by cross-site-scripting attacks.
1158 Set($PreferRichText, undef);
1160 =item C<$WebExternalAuth>
1162 If C<$WebExternalAuth> is defined, RT will defer to the environment's
1163 REMOTE_USER variable.
1167 Set($WebExternalAuth, undef);
1169 =item C<$WebExternalAuthContinuous>
1171 If C<$WebExternalAuthContinuous> is defined, RT will check for the
1172 REMOTE_USER on each access. If you would prefer this to only happen
1173 once (at initial login) set this to a false value. The default setting
1174 will help ensure that if your external auth system deauthenticates a
1175 user, RT notices as soon as possible.
1179 Set($WebExternalAuthContinuous, 1);
1181 =item C<$WebFallbackToInternalAuth>
1183 If C<$WebFallbackToInternalAuth> is defined, the user is allowed a chance
1184 of fallback to the login screen, even if REMOTE_USER failed.
1188 Set($WebFallbackToInternalAuth , undef);
1190 =item C<$WebExternalGecos>
1192 C<$WebExternalGecos> means to match 'gecos' field as the user identity);
1193 useful with mod_auth_pwcheck and IIS Integrated Windows logon.
1197 Set($WebExternalGecos , undef);
1199 =item C<$WebExternalAuto>
1201 C<$WebExternalAuto> will create users under the same name as REMOTE_USER
1202 upon login, if it's missing in the Users table.
1206 Set($WebExternalAuto , undef);
1208 =item C<$AutoCreate>
1210 If C<$WebExternalAuto> is true, C<$AutoCreate> will be passed to User's
1211 Create method. Use it to set defaults, such as creating
1212 Unprivileged users with C<{ Privileged => 0 }>
1213 ( Must be a hashref of arguments )
1217 Set($AutoCreate, undef);
1219 =item C<$WebSessionClass>
1221 C<$WebSessionClass> is the class you wish to use for managing Sessions.
1222 It defaults to use your SQL database, but if you are using MySQL 3.x and
1223 plans to use non-ascii Queue names, uncomment and add this line to
1224 F<RT_SiteConfig.pm> will prevent session corruption.
1228 # Set($WebSessionClass , 'Apache::Session::File');
1230 =item C<$AutoLogoff>
1232 By default, RT's user sessions persist until a user closes his or her
1233 browser. With the C<$AutoLogoff> option you can setup session lifetime in
1234 minutes. A user will be logged out if he or she doesn't send any requests
1235 to RT for the defined time.
1239 Set($AutoLogoff, 0);
1241 =item C<$LogoutRefresh>
1243 The number of seconds to wait after logout before sending the user to the
1244 login page. By default, 1 second, though you may want to increase this if
1245 you display additional information on the logout page.
1249 Set($LogoutRefresh, 1);
1251 =item C<$WebSecureCookies>
1253 By default, RT's session cookie isn't marked as "secure" Some web browsers
1254 will treat secure cookies more carefully than non-secure ones, being careful
1255 not to write them to disk, only send them over an SSL secured connection
1256 and so on. To enable this behaviour, set C<$WebSecureCookies> to a true value.
1257 NOTE: You probably don't want to turn this on _unless_ users are only connecting
1258 via SSL encrypted HTTP connections.
1262 Set($WebSecureCookies, 0);
1264 =item C<$WebHttpOnlyCookies>
1266 Default RT's session cookie to not being directly accessible to
1267 javascript. The content is still sent during regular and AJAX requests,
1268 and other cookies are unaffected, but the session-id is less
1269 programmatically accessible to javascript. Turning this off should only
1270 be necessary in situations with odd client-side authentication
1275 Set($WebHttpOnlyCookies, 1);
1277 =item C<$RestrictReferrer>
1279 If set to a false value, the HTTP C<Referer> (sic) header will not be
1280 checked to ensure that requests come from RT's own domain. As RT allows
1281 for GET requests to alter state, disabling this opens RT up to
1282 cross-site request forgery (CSRF) attacks.
1286 Set($RestrictReferrer, 1);
1288 =item C<$RestrictLoginReferrer>
1290 If set to a false value, RT will allow the user to log in from any link
1291 or request, merely by passing in C<user> and C<pass> parameters; setting
1292 it to a true value forces all logins to come from the login box, so the
1293 user is aware that they are being logged in. The default is off, for
1294 backwards compatability.
1298 Set($RestrictLoginReferrer, 0);
1300 =item C<$WebFlushDbCacheEveryRequest>
1302 By default, RT clears its database cache after every page view.
1303 This ensures that you've always got the most current information
1304 when working in a multi-process (mod_perl or FastCGI) Environment
1305 Setting C<$WebFlushDbCacheEveryRequest> to '0' will turn this off,
1306 which will speed RT up a bit, at the expense of a tiny bit of data
1311 Set($WebFlushDbCacheEveryRequest, '1');
1314 =item C<$MaxInlineBody>
1316 C<$MaxInlineBody> is the maximum attachment size that we want to see
1317 inline when viewing a transaction. RT will inline any text if value
1318 is undefined or 0. This option can be overridden by users in their
1323 Set($MaxInlineBody, 12000);
1325 =item C<$DefaultSummaryRows>
1327 C<$DefaultSummaryRows> is default number of rows displayed in for search
1328 results on the frontpage.
1332 Set($DefaultSummaryRows, 10);
1334 =item C<$HomePageRefreshInterval>
1336 C<$HomePageRefreshInterval> is default number of seconds to refresh the RT
1337 home page. Choose from [0, 120, 300, 600, 1200, 3600, 7200].
1341 Set($HomePageRefreshInterval, 0);
1343 =item C<$SearchResultsRefreshInterval>
1345 C<$SearchResultsRefreshInterval> is default number of seconds to refresh
1346 search results in RT. Choose from [0, 120, 300, 600, 1200, 3600, 7200].
1350 Set($SearchResultsRefreshInterval, 0);
1352 =item C<$ResolveDefaultUpdateType>
1354 Set the default Update Type when clicking the Resolve link in the Ticket
1357 Comment Comments (Not sent to requestors)
1358 Respond Reply to requestors
1362 Set($ResolveDefaultUpdateType, 'Comment');
1364 =item C<$SuppressAutoOpenOnUpdate>
1366 When users click Comment or Reply on a new ticket in the web UI, the default
1367 status for the ticket gets set to 'open' if the status is currently 'new'.
1368 Setting this option to 1 will suppress that behavior and leave the default
1369 status as 'new'. This option can be overridden by users in their preferences.
1373 Set($SuppressAutoOpenOnUpdate, 0);
1375 =item C<$OldestTransactionsFirst>
1377 By default, RT shows newest transactions at the bottom of the ticket
1378 history page, if you want see them at the top set this to '0'. This
1379 option can be overridden by users in their preferences.
1383 Set($OldestTransactionsFirst, '1');
1385 =item C<$ShowTransactionImages>
1387 By default, RT shows images attached to incoming (and outgoing) ticket updates
1388 inline. Set this variable to 0 if you'd like to disable that behaviour
1392 Set($ShowTransactionImages, 1);
1394 =item C<$PlainTextPre>
1396 Normally plaintext attachments are displayed as HTML with line
1397 breaks preserved. This causes space- and tab-based formatting not
1398 to be displayed correctly. By setting $PlainTextPre they'll be
1399 displayed using <pre> instead so such formatting works, but they'll
1400 use a monospaced font, no matter what the value of C<$PlainTextMono> is.
1404 Set($PlainTextPre, 0);
1407 =item C<$PlainTextMono>
1408 To display plaintext attachments,
1409 Set C<$PlainTextMono> to 1 to use monospaced font and preserve
1410 formatting, but unlike PlainTextPre, the text will wrap to fit into the
1415 Set($PlainTextMono, 0);
1417 =item C<$ShowUnreadMessageNotifications>
1419 By default, RT will prompt users when there are new, unread messages on
1420 tickets they are viewing.
1422 Set C<$ShowUnreadMessageNotifications> to a false value to disable this feature.
1426 Set($ShowUnreadMessageNotifications, 1);
1429 =item C<$HomepageComponents>
1431 C<$HomepageComponents> is an arrayref of allowed components on a user's
1432 customized homepage ("RT at a glance").
1436 Set($HomepageComponents, [qw(QuickCreate Quicksearch MyCalendar MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards)]);
1438 =item C<@MasonParameters>
1440 C<@MasonParameters> is the list of parameters for the constructor of
1441 HTML::Mason's Apache or CGI Handler. This is normally only useful
1442 for debugging, eg. profiling individual components with:
1444 use MasonX::Profiler; # available on CPAN
1445 Set(@MasonParameters, (preamble => 'my $p = MasonX::Profiler->new($m, $r);'));
1449 Set(@MasonParameters, ());
1451 =item C<$DefaultSearchResultFormat>
1453 C<$DefaultSearchResultFormat> is the default format for RT search results
1457 Set ($DefaultSearchResultFormat, qq{
1458 '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__id__</a></B>/TITLE:#',
1459 '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
1467 '<small>__Requestors__</small>',
1468 '<small>__CustomerTags__</small>',
1469 '<small>__CreatedRelative__</small>',
1470 '<small>__ToldRelative__</small>',
1471 '<small>__LastUpdatedRelative__</small>',
1472 '<small>__TimeLeft__</small>'});
1474 =item C<$DefaultSelfServiceSearchResultFormat>
1476 C<$DefaultSelfServiceSearchResultFormat> is the default format of searches displayed in the
1477 SelfService interface.
1481 Set($DefaultSelfServiceSearchResultFormat, qq{
1482 '<B><A HREF="__WebPath__/SelfService/Display.html?id=__id__">__id__</a></B>/TITLE:#',
1483 '<B><A HREF="__WebPath__/SelfService/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
1488 =item C<%AdminSearchResultFormat>
1490 In admin interface format strings similar to tickets search result
1491 formats are used. Use C<%AdminSearchResultFormat> to define format
1492 strings per RT class.
1496 Set(%AdminSearchResultFormat,
1498 q{'<a href="__WebPath__/Admin/Queues/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1499 .q{,'<a href="__WebPath__/Admin/Queues/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1500 .q{,__Description__,__Address__,__Priority__,__DefaultDueIn__,__Disabled__},
1503 q{'<a href="__WebPath__/Admin/Groups/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1504 .q{,'<a href="__WebPath__/Admin/Groups/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1505 .q{,'__Description__'},
1508 q{'<a href="__WebPath__/Admin/Users/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1509 .q{,'<a href="__WebPath__/Admin/Users/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1510 .q{,__RealName__, __EmailAddress__},
1513 q{'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__id__</a>/TITLE:#'}
1514 .q{,'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__Name__</a>/TITLE:Name'}
1515 .q{,__AppliedTo__, __FriendlyType__, __FriendlyPattern__},
1518 q{'<a href="__WebPath__/__WebRequestPathDir__/Scrip.html?id=__id__&Queue=__QueueId__">__id__</a>/TITLE:#'}
1519 .q{,'<a href="__WebPath__/__WebRequestPathDir__/Scrip.html?id=__id__&Queue=__QueueId__">__Description__</a>/TITLE:Description'}
1520 .q{,__Stage__, __Condition__, __Action__, __Template__},
1523 q{'<a href="__WebPath__/__WebRequestPathDir__/Template.html?Queue=__QueueId__&Template=__id__">__id__</a>/TITLE:#'}
1524 .q{,'<a href="__WebPath__/__WebRequestPathDir__/Template.html?Queue=__QueueId__&Template=__id__">__Name__</a>/TITLE:Name'}
1525 .q{,'__Description__'},
1528 =item C<$SuppressInlineTextFiles>
1530 If C<$SuppressInlineTextFiles> is set to a true value, then uploaded
1531 text files (text-type attachments with file names) are prevented
1532 from being displayed in-line when viewing a ticket's history.
1536 Set($SuppressInlineTextFiles, undef);
1538 =item C<$DontSearchFileAttachments>
1540 If C<$DontSearchFileAttachments> is set to a true value, then uploaded
1541 files (attachments with file names) are not searched during full-content
1546 Set($DontSearchFileAttachments, undef);
1550 The L<GD> module (which RT uses for graphs) ships with a builtin font
1551 that doesn't have full Unicode support. You can use a given TrueType font
1552 for a specific language by setting %ChartFont to (language =E<gt> the
1553 absolute path of a font) pairs. Your GD library must have support for
1554 TrueType fonts to use this option. If there is no entry for a language
1555 in the hash then font with 'others' key is used.
1557 RT comes with two TrueType fonts covering most available languages.
1563 'zh-cn' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1564 'zh-tw' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1565 'ja' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf",
1566 'others' => "$RT::BasePath/share/fonts/DroidSans.ttf",
1569 =item C<$ChartsTimezonesInDB>
1571 RT stores dates using the UTC timezone in the DB, so charts grouped
1572 by dates and time are not representative. Set C<$ChartsTimezonesInDB>
1573 to a true value to enable timezone conversions using your DB's
1574 capabilities. You may need to do some work on the DB side to use this
1575 feature, read more in F<docs/timezones_in_charts.pod>.
1577 At this time, this feature only applies to MySQL and PostgreSQL.
1581 Set( $ChartsTimezonesInDB, 0 );
1583 =item C<@Active_MakeClicky>
1585 MakeClicky detects various formats of data in headers and email
1586 messages, and extends them with supporting links. By default, RT
1587 provides two formats:
1589 * 'httpurl': detects http:// and https:// URLs and adds '[Open URL]'
1592 * 'httpurl_overwrite': also detects URLs as 'httpurl' format, but
1593 replace URL with link and *adds spaces* into text if it's longer
1594 then 30 chars. This allow browser to wrap long URLs and avoid
1595 horizontal scrolling.
1597 See F<share/html/Elements/MakeClicky> for documentation on how to add your own.
1601 Set(@Active_MakeClicky, qw());
1603 =item C<$DefaultQueue>
1605 Use this to select the default queue name that will be used for creating new
1606 tickets. You may use either the queue's name or its ID. This only affects the
1607 queue selection boxes on the web interface.
1611 #Set($DefaultQueue, 'General');
1613 =item C<$DefaultTimeUnitsToHours>
1615 Use this to set the default units for time entry to hours instead of minutes.
1619 Set($DefaultTimeUnitsToHours, 0);
1621 =item C<$SimpleSearchIncludeResolved>
1623 By default, the simple ticket search in the top bar excludes "resolved" tickets
1624 unless a status argument is specified. Set this to a true value to include
1629 Set($SimpleSearchIncludeResolved, 0);
1633 =head1 L<Net::Server> (rt-server) Configuration
1637 =item C<$StandaloneMinServers>, C<$StandaloneMaxServers>
1639 The absolute minimum and maximum number of servers that will be created to
1640 handle requests. Having multiple servers means that serving a slow page will
1641 affect other users less.
1645 Set($StandaloneMinServers, 1);
1646 Set($StandaloneMaxServers, 1);
1648 =item C<$StandaloneMinSpareServers>, C<$StandaloneMaxSpareServers>
1650 These next two options can be used to scale up and down the number of servers
1651 to adjust to load. These two options will respect the C<$StandaloneMinServers
1652 > and C<$StandaloneMaxServers options>.
1656 Set($StandaloneMinSpareServers, 0);
1657 Set($StandaloneMaxSpareServers, 0);
1659 =item C<$StandaloneMaxRequests>
1661 This sets the absolute maximum number of requests a single server will serve.
1662 Setting this would be useful if, for example, memory usage slowly crawls up
1667 #Set($StandaloneMaxRequests, 50);
1669 =item C<%NetServerOptions>
1671 C<%NetServerOptions> is a hash of additional options to use for
1672 L<Net::Server/DEFAULT ARGUMENTS>. For example, you could set
1673 reverse_lookups to get the hostnames for all users with:
1675 C<Set(%NetServerOptions, (reverse_lookups => 1));>
1679 Set(%NetServerOptions, ());
1684 =head1 UTF-8 Configuration
1688 =item C<@LexiconLanguages>
1690 An array that contains languages supported by RT's internationalization
1691 interface. Defaults to all *.po lexicons; setting it to C<qw(en ja)> will make
1692 RT bilingual instead of multilingual, but will save some memory.
1696 Set(@LexiconLanguages, qw(*));
1698 =item C<@EmailInputEncodings>
1700 An array that contains default encodings used to guess which charset
1701 an attachment uses if not specified. Must be recognized by
1706 Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii));
1708 =item C<$EmailOutputEncoding>
1710 The charset for localized email. Must be recognized by Encode.
1714 Set($EmailOutputEncoding, 'utf-8');
1719 =head1 Date Handling Configuration
1723 =item C<$DateTimeFormat>
1725 You can choose date and time format. See "Output formatters"
1726 section in perldoc F<lib/RT/Date.pm> for more options. This option can
1727 be overridden by users in their preferences.
1730 C<Set($DateTimeFormat, 'LocalizedDateTime');>
1731 C<Set($DateTimeFormat, { Format => 'ISO', Seconds => 0 });>
1732 C<Set($DateTimeFormat, 'RFC2822');>
1733 C<Set($DateTimeFormat, { Format => 'RFC2822', Seconds => 0, DayOfWeek => 0 });>
1737 Set($DateTimeFormat, 'DefaultFormat');
1739 # Next two options are for Time::ParseDate
1741 =item C<$DateDayBeforeMonth>
1743 Set this to 1 if your local date convention looks like "dd/mm/yy" instead of
1744 "mm/dd/yy". Used only for parsing, not for displaying dates.
1748 Set($DateDayBeforeMonth , 1);
1750 =item C<$AmbiguousDayInPast>, C<$AmbiguousDayInFuture>
1752 Should an unspecified day or year in a date refer to a future or a
1753 past value? For example, should a date of "Tuesday" default to mean
1754 the date for next Tuesday or last Tuesday? Should the date "March 1"
1755 default to the date for next March or last March?
1757 Set $<AmbiguousDayInPast> for the last date, or $<$AmbiguousDayInFuture> for the
1760 The default is usually good.
1764 Set($AmbiguousDayInPast, 0);
1765 Set($AmbiguousDayInFuture, 0);
1769 =head1 Approval Configuration
1771 Configuration for the approval system
1775 =item C<$ApprovalRejectionNotes>
1777 Should rejection notes be sent to the requestors? The default is true.
1781 Set($ApprovalRejectionNotes, 1);
1784 =item C<@ReferrerWhitelist>
1786 This is a list of hostname:port combinations that RT will treat as being
1787 part of RT's domain. This is particularly useful if you access RT as
1788 multiple hostnames or have an external auth system that needs to
1789 redirect back to RT once authentication is complete.
1791 Set(@ReferrerWhitelist, qw(www.example.com:443 www3.example.com:80));
1793 If the "RT has detected a possible cross-site request forgery" error is triggered
1794 by a host:port sent by your browser that you believe should be valid, you can copy
1795 the host:port from the error message into this list.
1799 Set(@ReferrerWhitelist, qw());
1803 =head1 Miscellaneous Configuration
1807 =item C<@ActiveStatus>, C<@InactiveStatus>
1809 You can define new statuses and even reorder existing statuses here.
1810 WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT
1811 will break horribly. The statuses you add must be no longer than
1816 Set(@ActiveStatus, qw(new open stalled));
1817 Set(@InactiveStatus, qw(resolved rejected deleted));
1819 =item C<$LinkTransactionsRun1Scrip>
1821 RT-3.4 backward compatibility setting. Add/Delete Link used to record one
1822 transaction and run one scrip. Set this value to 1 if you want
1823 only one of the link transactions to have scrips run.
1827 Set($LinkTransactionsRun1Scrip, 0);
1829 =item C<$StrictLinkACL>
1831 When this feature is enabled a user needs I<ModifyTicket> rights on both
1832 tickets to link them together, otherwise he can have rights on either of
1837 Set($StrictLinkACL, 1);
1839 =item C<$PreviewScripMessages>
1841 Set C<$PreviewScripMessages> to 1 if the scrips preview on the ticket
1842 reply page should include the content of the messages to be sent.
1846 Set($PreviewScripMessages, 0);
1848 =item C<$UseTransactionBatch>
1850 Set C<$UseTransactionBatch> to 1 to execute transactions in batches,
1851 such that a resolve and comment (for example) would happen
1852 simultaneously, instead of as two transactions, unaware of each
1857 Set($UseTransactionBatch, 1);
1859 =item C<@CustomFieldValuesSources>
1861 Set C<@CustomFieldValuesSources> to a list of class names which extend
1862 L<RT::CustomFieldValues::External>. This can be used to pull lists of
1863 custom field values from external sources at runtime.
1867 Set(@CustomFieldValuesSources, ('RT::CustomFieldValues::Queues'));
1869 =item C<$CanonicalizeRedirectURLs>
1871 Set C<$CanonicalizeRedirectURLs> to 1 to use $C<WebURL> when redirecting rather
1872 than the one we get from C<%ENV>.
1874 If you use RT behind a reverse proxy, you almost certainly want to
1879 Set($CanonicalizeRedirectURLs, 0);
1880 =item C<$EnableReminders>
1882 Hide links/portlets related to Reminders by setting this to 0
1886 Set($EnableReminders,1);
1891 Set C<@Plugins> to a list of external RT plugins that should be enabled (those
1892 plugins have to be previously downloaded and installed).
1895 C<Set(@Plugins, (qw(Extension::QuickDelete RT::FM)));>
1899 Set(@Plugins, (qw(RTx::Calendar
1900 RT::Extension::MobileUI))); #RTx::Checklist ));
1904 =head1 Development Configuration
1910 RT comes with a "Development mode" setting.
1911 This setting, as a convenience for developers, turns on
1912 all sorts of development options that you most likely don't want in
1915 * Turns off Mason's 'static_source' directive. By default, you can't
1916 edit RT's web ui components on the fly and have RT magically pick up
1917 your changes. (It's a big performance hit)
1923 Set($DevelMode, '0');
1928 =head1 Deprecated Options
1932 =item C<$AlwaysUseBase64>
1934 Encode blobs as base64 in DB (?)
1936 =item C<$TicketBaseURI>
1938 Base URI to tickets in this system; used when loading (?)
1940 =item C<$UseCodeTickets>
1942 This option is exists for backwards compatibility. Don't use it.