You might also want to check if the URL pointed to by rt-mailgate is accessible. In my case, it was not resolved properly. Was able to know after trying the URL with lynx. Made it work by hardcoding the host address on /etc/hosts. HTH
> At Thursday 11/8/2007 06:48 AM, Stefan Oeser - emendis GmbH wrote: > >Hello, > > > > I ran into problems with setting up RT3 on https. I configured > > some Ticket-Transaction via Mail in RT3. > >With http-Protocol, all things work fine, but rt-mailgate has some > >troubles with the httpS-Protocol. I always get > >an Error: "Connection refused". All needed modules (Crypt::SSLeay) > >are installed. Is it possible, that there are > >some difficulties with the selfsigned certificate? > > > >Using a browser to enter my RT3, I need to accept some Popup-Windows > >and accept the certificate manually, > >perhaps, rt-mailgate doesn't accept the certificate automatically, > >which results in the mentioned error?? > > > >I would be very grateful for some help :) > >Best regards, > >Stefan Oeser > > Hello Stefan, > > The way we've done this is to have apache listen on two ports for SSL > connections. 443 requires certificates, 444 does not (i.e. > username/password access). We use 444 for the mailgate connection. > > Steve _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
