avoid sending mail to itself. It will also hide RT addresses from the list of
"One-time Cc" and Bcc lists on ticket reply.
+If you have a number of addresses configured in your RT database already, you
+can generate a naive first pass regexp by using
+
+ perl etc/upgrade/generate-rtaddressregexp
+
=cut
Set($RTAddressRegexp , undef);
+=item C<$IgnoreCcRegexp>
+
+C<$IgnoreCcRegexp> is a regexp to exclude addresses from automatic addition
+to the Cc list. Use this for addresses that are I<not> received by RT but
+are sometimes added to Cc lists by mistake. Unlike C<$RTAddressRegexp>,
+these addresses can still receive email from RT otherwise.
+
+=cut
+
+Set($IgnoreCcRegexp, undef);
+
=item C<$CanonicalizeEmailAddressMatch>, C<$CanonicalizeEmailAddressReplace>
RT provides functionality which allows the system to rewrite
Set($CanonicalizeOnCreate, 0);
-=item C<$SenderMustExistInExternalDatabase>
-
-If C<$SenderMustExistInExternalDatabase> is true, RT will refuse to
-create non-privileged accounts for unknown users if you are using
-the C<$LookupSenderInExternalDatabase> option.
-Instead, an error message will be mailed and RT will forward the
-message to C<$RTOwner>.
-
-If you are not using C<$LookupSenderInExternalDatabase>, this option
-has no effect.
-
-If you define an AutoRejectRequest template, RT will use this
-template for the rejection message.
-
-=cut
-
-Set($SenderMustExistInExternalDatabase , undef);
-
=item C<$ValidateUserEmailAddresses>
If C<$ValidateUserEmailAddresses> is true, RT will refuse to create users with
Set($ValidateUserEmailAddresses, undef);
+=item C<$NonCustomerEmailRegexp>
+
+Normally, when a ticket is linked to a customer, any requestors on that
+ticket that didn't previously have customer memberships are linked to
+the customer also. C<$NonCustomerEmailRegexp> is a regexp for email
+addresses that should I<not> automatically be linked to a customer in
+this way.
+
+=cut
+
+Set($NonCustomerEmailRegexp, undef);
+
=item C<@MailPlugins>
C<@MailPlugins> is a list of auth plugins for L<RT::Interface::Email>
Note that you should remove the '-t' from C<$SendmailArguments>
if you use 'sendmail' rather than 'sendmailpipe'
+For testing purposes, or to simply disable sending mail out into the 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 afterwards.
+
=cut
Set($MailCommand , 'sendmailpipe');
=item C<$OverrideOutgoingMailFrom>
C<$OverrideOutgoingMailFrom> is used for overwriting the Correspond
-address of the queue. The option is a hash reference of queue name to
-email address.
+address of the queue as it is handed to sendmail -f. This helps force
+the From_ header away from www-data or other email addresses that show
+up in the "Sent by" line in Outlook.
+
+The option is a hash reference of queue name to email address.
If there is no ticket involved, then the value of the C<Default> key will be
used.
=item C<$FriendlyToLineFormat>
-C<sprintf()> format of the friendly 'From:' header; its arguments
+C<sprintf()> format of the friendly 'To:' header; its arguments
are WatcherType and TicketId.
=cut
Set($AttachmentUnits, undef);
+=item C<$EditCustomFieldsSingleColumn>
+
+When displaying a list of Ticket Custom Fields for editing, RT defaults
+to a 2 column list. If you set this to 1, it will instead display the
+Custom Fields in a single column.
+
+=cut
+
+Set($EditCustomFieldsSingleColumn, 0);
+
=item C<$RedistributeAutoGeneratedMessages>
Should RT redistribute correspondence that it identifies as
Set($SearchResultsRefreshInterval, 0);
+=item C<$ResolveDefaultUpdateType>
+
+Set the default Update Type when clicking the Resolve link in the Ticket
+links tab.
+
+ Comment Comments (Not sent to requestors)
+ Respond Reply to requestors
+
+=cut
+
+Set($ResolveDefaultUpdateType, 'Comment');
+
+=item C<$SuppressAutoOpenOnUpdate>
+
+When users click Comment or Reply on a new ticket in the web UI, the default
+status for the ticket gets set to 'open' if the status is currently 'new'.
+Setting this option to 1 will suppress that behavior and leave the default
+status as 'new'. This option can be overridden by users in their preferences.
+
+=cut
+
+Set($SuppressAutoOpenOnUpdate, 0);
+
=item C<$OldestTransactionsFirst>
By default, RT shows newest transactions at the bottom of the ticket
'<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject',
Customer,
Status,
- QueueName,
+ QueueName,
OwnerName,
Priority,
'__NEWLINE__',
- '',
- '<small>__Requestors__</small>',
'',
+ '<small>__Requestors__</small>',
+ '<small>__CustomerTags__</small>',
'<small>__CreatedRelative__</small>',
'<small>__ToldRelative__</small>',
'<small>__LastUpdatedRelative__</small>',
=item C<$ChartsTimezonesInDB>
-Dates are stored using UTC timezone in the DB, so charts groupped
+RT stores dates using the UTC timezone in the DB, so charts grouped
by dates and time are not representative. Set C<$ChartsTimezonesInDB>
-to a true value to enable timezones conversions using DB's
-capabilities. You may need to do some work on DB side to use this
+to a true value to enable timezone conversions using your DB's
+capabilities. You may need to do some work on the DB side to use this
feature, read more in F<docs/timezones_in_charts.pod>.
+At this time, this feature only applies to MySQL and PostgreSQL.
+
=cut
Set( $ChartsTimezonesInDB, 0 );
Set($DefaultTimeUnitsToHours, 0);
+=item C<$SimpleSearchIncludeResolved>
+
+By default, the simple ticket search in the top bar excludes "resolved" tickets
+unless a status argument is specified. Set this to a true value to include
+them.
+
+=cut
+
+Set($SimpleSearchIncludeResolved, 0);
+
=back
=head1 L<Net::Server> (rt-server) Configuration
=head1 Approval Configuration
-Configration for the approvl system
+Configuration for the approval system
=over 4
=cut
-Set(@Plugins, (qw(RTx::Calendar))); #RTx::Checklist ));
+Set(@Plugins, (qw(RTx::Calendar
+ RT::Extension::MobileUI))); #RTx::Checklist ));
=back
projects / freeside.git / blobdiff