Canmove, confirm
345
edits
Changes
Move In "Bugzilla Email"
on your Bugzilla installation,
and follow the recommended security guidelines found in The Bugzilla Guide.
=Email=
==I have a user who doesn't want to receive any more email from Bugzilla. How do I stop it entirely for this user?==
The user can stop Bugzilla from sending any mail by unchecking all boxes on the 'Preferences' -> 'Email Preferences' page.
(As of 2.18, this is made easier by the addition of a 'Disable All Mail' button.)
Alternately, an administrator can disable all bugmails for this user from the administrative pages. This will override their personal preferences, and they will never be sent mail again.
==I'm evaluating/testing Bugzilla, and don't want it to send email to anyone but me. How do I do it?==
To disable email,
set the mail_delivery_method parameter to none (2.20 and later), or
$enableSendMail
parameter to '0' in either BugMail.pm (2.18 and later)
or processmail (up to 2.16.x).
Up to 2.16.x, changing
$enableSendMail
will only affect bugmail; email related to password changes,
email address changes, bug imports, flag changes, etc. will still be sent out.
As of the final release of 2.18, however,
the above step will disable all mail sent from Bugzilla for any purpose.
To have bugmail (and only bugmail) redirected to you
instead of its intended recipients, leave
$enableSendMail
alone; instead, edit "template/en/default/email/newchangedmail.txt.tmpl" as follows:
*Replace "To:" with "X-Real-To:"
*Add a "To: <your_email_address>"
== I want whineatnews.pl to whine at something other than new and reopened bugs. How do I do it?==
For older versions of Bugzilla,
you may be able to apply Klaas Freitag's patch for "whineatassigned",
which can be found in
[https://bugzilla.mozilla.org/show_bug.cgi?id=6679 bug 6679].
Note that this patch was made in 2000,
so it may take some work to apply cleanly to any releases of Bugzilla
newer than that, but you can use it as a starting point.
An updated (and much-expanded) version of this functionality
is due to be released as part of Bugzilla 2.20;
see [https://bugzilla.mozilla.org/show_bug.cgi?id=185090 bug 185090]
for the discussion, and for more up-to-date patches if you just can't wait.
==How do I set up the email interface to submit/change bugs via email?==
On older versions, you can find an updated README.mailif file in the contrib/ directory of your Bugzilla distribution that walks you through the setup.
On Version 3.0.x, read [http://www.bugzilla.org/docs/3.0/html/api/email_in.html this API documentation] about using email_in.pl. the script receives a message file as a command line parameter, and processes it.
==Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. What gives?==
If you are using sendmail, try enabling sendmailnow in editparams.cgi.
For earlier versions of sendmail,
one could achieve significant performance improvement in the UI
(at the cost of delaying the sending of mail) by setting this parameter to off.
Sites with sendmail version 8.12 (or higher) should leave this on,
as they will not see any performance benefit.
If you are using an alternate
[http://www.bugzilla.org/docs/tip/html/glossary.html#gloss-mta MTA],
make sure the options given in Bugzilla/BugMail.pm and any other place
where sendmail is called are correct for your MTA.
==How come email from Bugzilla changes never reaches me?==
Double-check that you have not turned off email in your user preferences.
Confirm that Bugzilla is able to send email by visiting the "Log In" link
of your Bugzilla installation and clicking the "Submit Request" button
after entering your email address.
If you never receive mail from Bugzilla,
chances are you do not have sendmail in "/usr/lib/sendmail".
Ensure sendmail lives in, or is symlinked to, "/usr/lib/sendmail".
If you are using an MTA other than sendmail
the sendmailnow param must be set to on or no mail will be sent.
[[category:Bugzilla|F]]
