[rt-users] RT-Mailgate timeout error after upgrade to 4.2.6

[Richards, Matthew E ERDC-RDE-CERL-IL]

Hi Kevin,

Thank you for the reply.  

>  Are you actually listening with SSL on localhost?  Is your webserver
>  configured to listen and allow that through to RT?

443 is listening on localhost.  As you suggested, we tried curl from the localhost with both the FQDN and localhost URLs.  We had limited success (without any message content), but it still fails with rt-mailgate.  I suspect we need some content to test it further with curl.  Do you have a sample curl command line with post params for testing?

user at rt:~$ curl -I https://rt.fully.qualified.domain.name/REST/1.0/NoAuth/mail-gateway
HTTP/1.1 200 OK
Date: Mon, 04 Aug 2014 17:09:29 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Frame-Options: DENY
Vary: Accept-Encoding
Content-Type: text/plain; charset=utf-8

user at rt:~$ curl -I https://localhost/REST/1.0/NoAuth/mail-gateway
HTTP/1.1 200 OK
Date: Mon, 04 Aug 2014 17:10:29 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Frame-Options: DENY
Vary: Accept-Encoding
Content-Type: text/plain; charset=utf-8

Running rt-mailgate with fetchmail:

2 messages for RTUSER at hostmaster.fully.qualified.domain.name (36925 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 34826
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message RTUSER at hostmaster.fully.qualified.domain.name:1 of 2 (34826 octets) #**********************************.***********************************.********************************.*************.*************.*************.*************.*************.*************.*************.**************.*************.*************.*************.*************.*************.*************.*************.**************.*************.*************.*************.*************.*************.*************.*************.**************.*************.*************.*************.*************.*************.*************.**************.*************.*************.*************.*************.*****/opt/rt4/bin/rt-mailgate: temp file is '/tmp/63WuokOupY/OIpKtEaLCc'
/opt/rt4/bin/rt-mailgate: connecting to https://rt.fully.qualified.domain.name /REST/1.0/NoAuth/mail-gateway
HTTP request failed: 500 Can't connect to rt.fully.qualified.domain.name:443. Your webserver logs may have more information or there may be a network problem.

/opt/rt4/bin/rt-mailgate: undefined server error
fetchmail: MDA returned nonzero status 75
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 2099
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK


Again, when we added some additional debugging messages and the actual error is:
LWP::Protocol::https::Socket: Timeout at /usr/share/perl5/LWP/Protocol/http.pm line 41.