[rt-users] Upgraded from 3.6.5 to 4.0.17, and mailgate has lost its way

[Beachey, Kendric]

I upgraded from 3.6.5 to 4.0.17 today.  The 3.6.5 had been installed the Ubuntu way (meaning, /etc/request-tracker3.6, /usr/local/share/request-tracker3.6 and so forth, and perl modules installed one by one via apt-get), but the 4.0.17 has been installed the tarball-and-CPAN way (meaning /opt/rt4 for everything except the apache config).  The database schema updates were a real blast...  ;-)

I've got the web interface coming up and working great.  I can create tickets through it, and thanks to RT::Authen::ExternalAuth, I can authenticate against our AD server, just like before.

The one thing that hasn't come back to life is email.  If I send an email in, or if RT wants to send an email out to a watcher, I get errors like this coming out of rt-mailgate:


/opt/rt4/bin/rt-mailgate: temp file is '/tmp/8gwnmwSHM5/3i1mLgbHBF'
/opt/rt4/bin/rt-mailgate: connecting to http://localhost/rt//REST/1.0/NoAuth/mail-gateway
An Error Occurred
=================

404 Not Found

/opt/rt4/bin/rt-mailgate: undefined server error


I googled around and the closest things I found were people having problems with their SSL certificates, but that's not what I'm getting here.  It's a plain old 404, like it can't find the REST service at all.  When I try going to http://localhost/rt//REST/1.0/NoAuth/mail-gateway myself (changing the localhost to point to the RT server), it thinks for a minute, ends up at https://rt.company.com/rt/y and gives a (rather nice looking) 404 page.

Have I goofed up my apache config somehow?  If it helps, I can send that along, or /etc/aliases, or RT_SiteConfig.pm, or anything else that would help pin this down.

Thanks much!
--
Kendric Beachey


________________________________

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.