The administrator's e-mail address. This is mainly prompted to the user in case of errors that might require the intervention of the system administrator. For example, SQL errors. firstname.lastname@example.org
The webmaster's e-mail address. This address is displayed in the bottom of all MantisBT pages. email@example.com
The email address to be used as the source of all emails sent by MantisBT. firstname.lastname@example.org
Email address to receive bounced emails.
Set to ON to enable email notifications, OFF to disable them. Default is ON. Note that disabling email notifications has no effect on emails generated as part of the user signup process. When set to OFF, the password reset feature is disabled. Additionally, notifications of administrators updating accounts are not sent to users.
Associated with each action a list of flags to control who should be notified.The default will be used if the action is not included in $g_notify_flags or if the flag is not included in the specific action definition. The list of actions include: new, assigned, resolved, bugnote, reopened, closed, deleted, feedback.The default is: $g_default_notify_flags = array('reporter' => ON, 'handler' => ON, 'monitor' => ON, 'bugnotes' => ON, 'explicit' => ON, 'threshold_min' => NOBODY, 'threshold_max' => NOBODY); threshold_min and threshold_max are used to send messages to all members of the project whose status is greater than or equal to "threshold_min" and less than or equal to "threshold_max". Sending messages to everyone would set "threshold_min" to ANYBODY and "threshold_max to "NOBODY". To send to all DEVELOPERS and above (as 0.17.5), use DEVELOPER and NOBODY respectively.
Defines the notification flags that are different from the defaults that are defined in $g_default_notify_flags. The following code overrides the default by disabling notifications to bugnote authors and users monitoring the bug on submitting a new bug: $g_notify_flags['new'] = array('bugnotes' => OFF, 'monitor' => OFF); Available actions include:
'new': a new bug has been added
'reopened': the bug has been reopened
'deleted': a bug has been deleted
'owner': the bug has been assigned a new owner
'bugnote': a bugnote has been added to a bug
'sponsor': the sponsorship for the bug has changed (added, deleted or updated)
'relation': a relationship for the bug has changed (added, deleted or updated)
'monitor': a user is added to the monitor list.
This defines whether users should receive emails for their own actions. This option is defaulted to OFF, hence, users do not receive email notification for their own actions. This can be a source for confusions for users upgrading from MantisBT 0.17.x versions, since in these versions users used to get notified of their own actions.
Set to OFF to disable email checking. Default is ON.
Set to OFF to disable email checking. Default is OFF.
If ON, allows the user to omit an email address field. If you allow users to create their own accounts, they must specify an email at that point, no matter what the value of this option is. Otherwise they wouldn't get their passwords.
Only allow and send email to addresses in the given domain. This is useful as a security feature and it is also useful in cases like Sourceforge where its servers are only limited to send emails to SourceForge email addresses in order to avoid spam. $g_limit_email_domain = 'users.sourceforge.net';
This specifies the access level that is needed to have user names hyperlinked with mailto: links. The default value is NOBODY, hence, even administrators won't have this feature enabled.
If use_x_priority is set to ON, what should the value be? Urgent = 1, Not Urgent = 5, Disable = 0 . Default is 3 Some MTAs interpret X-Priority = 0 to mean 'Very Urgent'
Select the method to send mail:
PHPMAILER_METHOD_MAIL for use of mail() function,
PHPMAILER_METHOD_SENDMAIL for sendmail (or postfix),
PHPMAILER_METHOD_SMTP for SMTP,
This option specifies the SMTP server to submit messages to. The SMTP server (MTA) then takes on the responsibility of delivering messages to their final destinations.
To use the local SMTP (if available) set this to 'localhost', otherwise use the fully qualified domain name of the remote SMTP server.
It can be either a single hostname, or multiple semicolon-delimited hostnames. You can specify for each host a port other than the default, using format: hostname:port (e.g. "smtp1.example.com:25;smtp2.example.com").
Hosts will be tried in the given order.
This is only used with PHPMAILER_METHOD_SMTP (see $g_phpmailer_method).
The default is 'localhost'.
The default SMTP port to use. This can be overridden individually for specific hosts. (see $g_smtp_host).
Typical SMTP ports are 25 and 587.
The default is 25.
Allow secure connection to the SMTP server. Valid values are:
'' (empty string): No encryption. This is the default.
SMTP Server Authentication user
Allows the use of SMTP Authentication when using a remote SMTP host.
must be set to '' (empty string) if the SMTP host does not require authentication.
Default is ''.
This is the password that is used in SMTP Authentication. Not used when $g_smtp_username = ''
Default is ''.
Disables sending of emails as soon as an action is performed. Emails are instead queued and must be sent by running scripts/send_emails.php periodically. This script can only be executed from the CLI, not from the web interface, for security reasons.
Enabling this option can help with performance problems if large numbers of emails are generated or mail delivery is slow by not delaying page execution when sending emails.
Specify whether e-mails should be sent with the category set or not. This is tested with Microsoft Outlook. More testing for this feature + other formats will be added in the future. OFF, EMAIL_CATEGORY_PROJECT_CATEGORY (format: [Project] Category). Default is OFF.
Default is str_pad('', 70, '='); This means 70 equal signs.
Default is str_pad('', 70, '-'); This means 70 minus signs.
Default is 28.
MantisBT uses flags and a threshold system to generate emails on events. For each new event, email is sent to:
the reporter, qualified by the notify flag 'reporter' below
the handler (or Assigned to), qualified by the notify flag 'handler' below
anyone monitoring the bug, qualified by the notify flag 'monitor' below
anyone who has ever added a bugnote the bug, qualified by the notify flag 'bugnotes' below
anyone assigned to the project whose access level is greater than or equal to the notify flag 'threshold_min' and less than or equal to the notify flag 'threshold_max' below
From this list, those recipients who meet the following criteria are eliminated:
the originator of the change, if $g_email_receive_own is OFF
the recipient either no longer exists, or is disabled
the recipient has turned their email_on_<new status> preference OFF
the recipient has no email address entered