On Mon, Jan 9, 2012 at 1:34 PM, Robert Nesius <[email protected]> wrote: > I made a recently change to how my apache2 server was configured to redirect > all requests through https. Now emails are not flowing through to RT - I > tracked the issue down to rt-mailgate complaining about not being able to > verify the certificate. I'm a little perplexed on how to proceed or how to > verify what certs/CAs rt-mailgate is using, or if there is an issue with the > Crypt::SSLeay module (which I had to force install due to a failing test). > I only have one openssl install on the system, and I thought Crypt::SSLeay > would reach through to those configs for things like CA certs, etc... > > Perhaps an easy workaround, since the mail server and apache2 server are on > the same machine, would be to configure a "localhost:80" virtual host within > apache2 and bypass SSL when accessing RT via that url. > > Any helpful hints/suggestions would be greatly appreciated. I've been > google-ing away but haven't had any luck yet. > AFAIK, rt-mailgate connects to RT using RT's web interface; it should use whatever cert you have defined in the virtual host entry for RT. Here is how my fetchmailrc calls rt-mailgate:
mda "/usr/bin/perl /usr/bin/rt-mailgate --url https://localhost/rt \ --queue support --action correspond" > -Rob > > -------- > RT Training Sessions (http://bestpractical.com/services/training.html) > * Boston — March 5 & 6, 2012 -------- RT Training Sessions (http://bestpractical.com/services/training.html) * Boston March 5 & 6, 2012
