Commit 4f8fcec3 authored by lpsolit%gmail.com's avatar lpsolit%gmail.com

Bug 383851: FAQ points to non-existing file for handling of bug creation through…

Bug 383851: FAQ points to non-existing file for handling of bug creation through email - Patch by samfw <sam.folkwilliams@gmail.com> r=LpSolit
parent e043bc7c
...@@ -29,13 +29,6 @@ This directory includes: ...@@ -29,13 +29,6 @@ This directory includes:
database into a Bugzilla database. Contributed by database into a Bugzilla database. Contributed by
Tom Schutter <tom@platte.com> Tom Schutter <tom@platte.com>
bug_email.pl -- A perl script that can receive email containing
bug reports (email-interface). Contributed by
Klaas Freitag <freitag@SuSE.de>
README.Mailif -- Readme describing the mail interface.
bugmail_help.html -- User help page for the mail interface.
yp_nomail.sh -- Script you can run via cron that regularly updates yp_nomail.sh -- Script you can run via cron that regularly updates
the nomail file for terminated employees the nomail file for terminated employees
......
...@@ -1025,15 +1025,18 @@ password=mypassword ...@@ -1025,15 +1025,18 @@ password=mypassword
</qandaentry> </qandaentry>
<qandaentry> <qandaentry>
<question id="faq-email-mailif"> <question id="faq-email-in">
<para> <para>
How do I set up the email interface to submit/change bugs via email? How do I set up the email interface to submit or change bugs via email?
</para> </para>
</question> </question>
<answer> <answer>
<para> <para>
You can find an updated README.mailif file in the contrib/ directory Bugzilla 3.0 and later offers the ability submit or change
of your Bugzilla distribution that walks you through the setup. bugs via email, using the <filename>email_in.pl</filename>
script within the root directory of the Bugzilla installation.
More information on the script can be found in
<ulink url="api/email_in.html">docs/html/api/email_in.html</ulink>.
</para> </para>
</answer> </answer>
</qandaentry> </qandaentry>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment