X-Git-Url: http://git.freeside.biz/gitweb/?a=blobdiff_plain;f=rt%2Fetc%2FRT_Config.pm.in;h=498e53c71e16c2c00a94c97035d3df04177ee63b;hb=008524b8e963831999983769f7fec11f55a72f16;hp=925f0cabed7c9bc3e0bfc57fd73a2f78f13aab73;hpb=43a06151e47d2c59b833cbd8c26d97865ee850b6;p=freeside.git diff --git a/rt/etc/RT_Config.pm.in b/rt/etc/RT_Config.pm.in index 925f0cabe..498e53c71 100644 --- a/rt/etc/RT_Config.pm.in +++ b/rt/etc/RT_Config.pm.in @@ -121,7 +121,7 @@ installed). Example: -C +C =cut @@ -296,8 +296,9 @@ Set(@LogToSyslogConf, ()); =item C<$EmailSubjectTagRegex> This regexp controls what subject tags RT recognizes as its own. If -you're not dealing with historical C<$rtname> values, you'll likely -never have to change this configuration. +you're not dealing with historical C<$rtname> values, or historical +queue-specific subject tags, you'll likely never have to change this +configuration. Be B with it. Note that it overrides C<$rtname> for subject token matching and that you should use only "non-capturing" @@ -348,15 +349,11 @@ Set($StoreLoops, undef); =item C<$MaxAttachmentSize> C<$MaxAttachmentSize> sets the maximum size (in bytes) of attachments -stored in the database. - -For MySQL and Oracle, we set this size to 10 megabytes. If you're -running a PostgreSQL version earlier than 7.1, you will need to drop -this to 8192. (8k) +stored in the database. This setting is irrelevant unless one of +$TruncateLongAttachments or $DropLongAttachments (below) are set. =cut - Set($MaxAttachmentSize, 10_000_000); =item C<$TruncateLongAttachments> @@ -392,9 +389,10 @@ already, you can generate a naive first pass regexp by using: perl etc/upgrade/generate-rtaddressregexp -If left blank, RT will generate a regexp for you, based on your -comment and correspond address settings on your queues; this comes at -a small cost in start-up speed. +If left blank, RT will compare each address to your configured +C<$CorrespondAddress> and C<$CommentAddress> before searching for a +Queue configured with a matching "Reply Address" or "Comment Address" +on the Queue Admin page. =cut @@ -483,11 +481,28 @@ accordingly. =cut -Set($ExtractSubjectTagMatch, qr/\[.+? #\d+\]/); +Set($ExtractSubjectTagMatch, qr/\[[^\]]+? #\d+\]/); Set($ExtractSubjectTagNoMatch, ( ${RT::EmailSubjectTagRegex} ? qr/\[(?:${RT::EmailSubjectTagRegex}) #\d+\]/ : qr/\[\Q$RT::rtname\E #\d+\]/)); +=item C<$CheckMoreMSMailHeaders> + +Some email clients create a plain text version of HTML-formatted +email to help other clients that read only plain text. +Unfortunately, the plain text parts sometimes end up with +doubled newlines and these can then end up in RT. This +is most often seen in MS Outlook. + +Enable this option to have RT check for additional mail headers +and attempt to identify email from MS Outlook. When detected, +RT will then clean up double newlines. Note that it may +clean up intentional double newlines as well. + +=cut + +Set( $CheckMoreMSMailHeaders, 0); + =back @@ -511,9 +526,19 @@ world, you can set C<$MailCommand> to 'testfile' which writes all mail to a temporary file. RT will log the location of the temporary file so you can extract mail from it afterward. +On shutdown, RT will clean up the temporary file created when using +the 'testfile' option. If testing while the RT server is still running, +you can find the files in the location noted in the log file. If you run +a tool like C however, or if you look after stopping the server, +the files will have been deleted when the process completed. If you need to +keep the files for development or debugging, you can manually set +C<< UNLINK => 0 >> where the testfile config is processed in +F. + =cut -Set($MailCommand, "sendmailpipe"); +#Set($MailCommand, "sendmailpipe"); +Set($MailCommand, "sendmail"); =item C<$SetOutgoingMailFrom> @@ -523,6 +548,14 @@ Correspond mail address of the ticket's queue. Warning: If you use this setting, bounced mails will appear to be incoming mail to the system, thus creating new tickets. +If the value contains an C<@>, it is assumed to be an email address and used as +a global envelope sender. Expected usage in this case is to simply set the +same envelope sender on all mail from RT, without defining +C<$OverrideOutgoingMailFrom>. If you do define C<$OverrideOutgoingMailFrom>, +anything specified there overrides the global value (including Default). + +This option only works if C<$MailCommand> is set to 'sendmailpipe'. + =cut Set($SetOutgoingMailFrom, 0); @@ -538,7 +571,8 @@ The option is a hash reference of queue name to email address. If there is no ticket involved, then the value of the C key will be used. -This option is irrelevant unless C<$SetOutgoingMailFrom> is set. +This option only works if C<$SetOutgoingMailFrom> is enabled and +C<$MailCommand> is set to 'sendmailpipe'. =cut @@ -644,6 +678,9 @@ Set($NotifyActor, 0); By default, RT records each message it sends out to its own internal database. To change this behavior, set C<$RecordOutgoingEmail> to 0 +If this is disabled, users' digest mail delivery preferences +(i.e. EmailFrequency) will also be ignored. + =cut Set($RecordOutgoingEmail, 1); @@ -734,7 +771,8 @@ C =cut -Set($SendmailArguments, "-oi -t"); +#Set($SendmailArguments, "-oi -t"); +Set($SendmailArguments, "-oi"); =item C<$SendmailBounceArguments> @@ -892,14 +930,17 @@ Set($CanonicalizeRedirectURLs, 0); A list of JavaScript files to be included in head. Removing any of the default entries is not suggested. +If you're a plugin author, refer to RT->AddJavaScript. + =cut Set(@JSFiles, qw/ jquery-1.4.2.min.js jquery_noconflict.js jquery-ui-1.8.4.custom.min.js + jquery-ui-timepicker-addon.js jquery-ui-patch-datepicker.js - ui.timepickr.js + jquery.cookie.js titlebox-state.js util.js userautocomplete.js @@ -928,6 +969,8 @@ directory, or from http://www.crockford.com/javascript/jsmin.html A list of additional CSS files to be included in head. +If you're a plugin author, refer to RT->AddStyleSheets. + =cut Set(@CSSFiles, qw//); @@ -1122,7 +1165,12 @@ user's customized homepage ("RT at a glance"). =cut -Set($HomepageComponents, [qw(QuickCreate Quicksearch MyCalendar MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards SavedSearches)]); +Set( + $HomepageComponents, + [ + qw(QuickCreate Quicksearch MyCalendar MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards SavedSearches ) # loc_qw + ] +); =back @@ -1189,7 +1237,7 @@ Set ($DefaultSearchResultFormat, qq{ OwnerName, Priority, '__NEWLINE__', - '', + '__NBSP__', '__Requestors__', '__CustomerTags__', '__CreatedRelative__', @@ -1231,6 +1279,18 @@ Set(%FullTextSearch, Indexed => 0, ); +=item C<$DontSearchFileAttachments> + +If C<$DontSearchFileAttachments> is set to 1, then uploaded files +(attachments with file names) are not searched during content +search. + +Note that if you use indexed FTS then named attachments are still +indexed by default regardless of this option. + +=cut + +Set($DontSearchFileAttachments, undef); =item C<$OnlySearchActiveTicketsInSimpleSearch> @@ -1690,9 +1750,11 @@ Set(@Active_MakeClicky, qw()); If C<$ParseNewMessageForTicketCcs> is set to 1, RT will attempt to divine Ticket 'Cc' watchers from the To and Cc lines of incoming -messages. Be forewarned that if you have I addresses which forward -mail to RT automatically and you enable this option without modifying -C<$RTAddressRegexp> below, you will get yourself into a heap of trouble. +messages that create new Tickets. This option does not apply to replies +or comments on existing Tickets. Be forewarned that if you have I +addresses which forward mail to RT automatically and you enable this +option without modifying C<$RTAddressRegexp> below, you will get +yourself into a heap of trouble. =cut @@ -1762,12 +1824,12 @@ Set($ForceApprovalsView, 0); =head1 Extra security -=over 4 - This is a list of extra security measures to enable that help keep your RT safe. If you don't know what these mean, you should almost certainly leave the defaults alone. +=over 4 + =item C<$DisallowExecuteCode> If set to a true value, the C right will be removed from @@ -1789,8 +1851,60 @@ This disables RT's clickjacking protection. Set($Framebusting, 1); +=item C<$RestrictReferrer> + +If set to a false value, the HTTP C (sic) header will not be +checked to ensure that requests come from RT's own domain. As RT allows +for GET requests to alter state, disabling this opens RT up to +cross-site request forgery (CSRF) attacks. + +=cut + +Set($RestrictReferrer, 1); + +=item C<$RestrictLoginReferrer> + +If set to a false value, RT will allow the user to log in from any link +or request, merely by passing in C and C parameters; setting +it to a true value forces all logins to come from the login box, so the +user is aware that they are being logged in. The default is off, for +backwards compatability. + +=cut + +Set($RestrictLoginReferrer, 0); + +=item C<@ReferrerWhitelist> + +This is a list of hostname:port combinations that RT will treat as being +part of RT's domain. This is particularly useful if you access RT as +multiple hostnames or have an external auth system that needs to +redirect back to RT once authentication is complete. + + Set(@ReferrerWhitelist, qw(www.example.com:443 www3.example.com:80)); + +If the "RT has detected a possible cross-site request forgery" error is triggered +by a host:port sent by your browser that you believe should be valid, you can copy +the host:port from the error message into this list. + +Simple wildcards, similar to SSL certificates, are allowed. For example: + + *.example.com:80 # matches foo.example.com + # but not example.com + # or foo.bar.example.com + + www*.example.com:80 # matches www3.example.com + # and www-test.example.com + # and www.example.com + +=cut + +Set(@ReferrerWhitelist, qw()); + =back + + =head1 Authorization and user configuration =over 4 @@ -1856,10 +1970,9 @@ Set($AutoCreate, undef); =item C<$WebSessionClass> -C<$WebSessionClass> is the class you wish to use for managing -Sessions. It defaults to use your SQL database, but if you are using -MySQL 3.x and plans to use non-ascii Queue names, uncomment and add -this line to F to prevent session corruption. +C<$WebSessionClass> is the class you wish to use for managing sessions. +It defaults to use your SQL database, except on Oracle, where it +defaults to files on disk. =cut @@ -2095,7 +2208,7 @@ Set(%GnuPGOptions, # 'auto-key-locate' => 'keyserver', # enables the automatic retrieving of keys when verifying signatures -# 'auto-key-retrieve' => undef, +# 'keyserver-options' => 'auto-key-retrieve', ); =back @@ -2206,6 +2319,14 @@ be changed to this value. When an approval is denied, the status of depending tickets will be changed to this value. +=item reminder_on_open + +When a reminder is opened, the status will be changed to this value. + +=item reminder_on_resolve + +When a reminder is resolved, the status will be changed to this value. + =back =head2 Transitions between statuses and UI actions @@ -2229,10 +2350,11 @@ all possible transitions in each lifecycle using the following format: =head3 Statuses available during ticket creation -By default users can create tickets with any status, except -deleted. If you want to restrict statuses available during creation -then describe transition from '' (empty string), like in the example -above. +By default users can create tickets with a status of new, +open, or resolved, but cannot create tickets with a status of +rejected, stalled, or deleted. If you want to change the statuses +available during creation, update the transition from '' (empty +string), like in the example above. =head3 Protecting status changes with rights @@ -2352,6 +2474,8 @@ Set(%Lifecycles, on_merge => 'resolved', approved => 'open', denied => 'rejected', + reminder_on_open => 'open', + reminder_on_resolve => 'resolved', }, transitions => { @@ -2425,6 +2549,8 @@ Set(%Lifecycles, defaults => { on_create => 'new', on_merge => 'resolved', + reminder_on_open => 'open', + reminder_on_resolve => 'resolved', }, transitions => { @@ -2529,7 +2655,7 @@ Set(%AdminSearchResultFormat, Queues => q{'__id__/TITLE:#'} .q{,'__Name__/TITLE:Name'} - .q{,__Description__,__Address__,__Priority__,__DefaultDueIn__,__Disabled__}, + .q{,__Description__,__Address__,__Priority__,__DefaultDueIn__,__Disabled__,__Lifecycle__}, Groups => q{'__id__/TITLE:#'} @@ -2681,6 +2807,8 @@ Set($LinkTransactionsRun1Scrip, 0); This option has been deprecated. You can configure this site-wide with L (see L). +=back + =cut 1;