Bugzilla/OldInstructions

You probably don't really want to be here.
This page contains the install instructions for older versions of Bugzilla. If forsome reason you really need to install an ancient version of Bugzilla, these are the instructions as they evolved over time. You really shouldn't run an older version of Bugzilla on Dreamhost, however, as most of them contain unpatched security bugs which have been fixed in newer versions. Go to Bugzilla for the current instructions.

Installing 2.18
As of May 12, 2006, installing Bugzilla 2.18 does not require any additional or updated modules. Just use the latest .tar.gz and follow the instructions as above.

Installing 2.20
As of May 12, 2006, installing Bugzilla 2.20 does not require any additional or updated modules. Just use the latest .tar.gz and follow the instructions as above.

Installing 2.22
As of May 12, 2006, installing Bugzilla 2.22 does not require any additional or updated modules. Just use the latest .tar.gz and follow the instructions as above.

Installing 3.0
Bugzilla 3.0 requires a couple of CPAN modules that are not installed by default. After executing checksetup.pl you will probably see a message indicating that you need to install Email::Send and Email::MIME::Modifier. Follow the instructions on the CPAN page to install a local copy of cpan and then execute the following commands: $ cpan cpan> install Email::Send cpan> install Email::MIME::Modifier cpan> bye

You will need to add the following lines (replacing username with your actual user name, and assuming you used perlmods as suggested on the CPAN page) to the top of Bugzilla/Mailer.pm use lib qw( /home/username/perlmods/lib/perl/5.8 /home/username/perlmods/lib/perl/5.8.4            /home/username/perlmods/share/perl/5.8 /home/username/perlmods/share/perl/5.8.4 );

It's important that the above lines get put before the 'use Email::Send' and 'use Email::MIME::Modifier' lines that are already in the file.

Now re-execute checksetup.pl and you can continue the installation as above.

Making email work
To get Bugzilla to send email you will need to go to the Email configuration page in Bugzilla and set your mail_delivery_method to SMTP, your smtpserver to smarty.dreamhost.com, and your mailfrom to a valid email address you have created in the Dreamhost panel.

I'm told using the above method (smarty.dreamhost.com) has limits on how many emails you can send per hour, to prevent runaway processes (or infected machines) from sending lots of spam. If you have a small Bugzilla without a lot of people using it, you'll probably be fine. If your Bugzilla winds up getting a lot of traffic, you'll probably want to set up SMTP authentication on your assigned mail server, which as of Bugzilla 3.0, still requires some code modification to Bugzilla:

On the Email configuration page in Bugzilla, set your smtpserver to mail.yourdomain.com where yourdomain.com is your domain name.

Now, find these lines in Mailer.pm: if ($method eq "SMTP") { push @args, Host => Bugzilla->params->{"smtpserver"}, Hello => $hostname And add the following immediately after them (substitute the password for the account you used above for password below): username => $from, password => "password"

Installing 3.2 & 3.4
Bugzilla 3.2/4 requires a couple of CPAN modules that are not installed by default. However you won't need any of the workarounds listed above for Bugzilla 3.0. All of the scripts included with Bugzilla 3.2 already have a use lib statement allowing them to load modules from a lib/ subdirectory under Bugzilla. You can use the install-modules.pl script included with Bugzilla (as instructed by checksetup.pl) to install these modules directly into the lib/ directory, and you don't need to set up CPAN to do it!

From version 3.2, Bugzilla also directly supports authenticated SMTP, so you won't need to do anything special to make email work (other than configure it). Follow the same configuration instructions as above in the 3.0 section, but you won't need to modify any code.

Unfortunately, the built-in suexec support hasn't made it yet, so you'll still need to do step 10 to fix the file permissions.