On 24 July 2012 00:39, Thomas Sibley <[email protected]> wrote: > On 07/22/2012 05:47 AM, Hesan Yousif wrote: > > Technical details of temporary failure: > > The recipient server did not accept our requests to connect. Learn more > > at http://support.google.com/mail/bin/answer.py?answer=7720 > > [(21) mail.xxx.xx.xx. > > [13x.xxx.xx.xx]:25: Connection timed out] > > Your error is right there: "Connection timed out". Google's mail > servers couldn't connect to your MX on port 25. That's not an RT problem. > > > My logs don't seem to track anything coming in, (syslog of RT, apache > > etc). Trying to send a queue in from the command line of the RT server > > produces this result: > > > > cat /usr/bin/test | /opt/rt4/bin/rt-mailgate --debug --queue > > rt-su-activities --url http://xxx.xxx/rt > > /opt/rt4/bin/rt-mailgate: temp file is '/tmp/WOZb2ZyjA1/8ulux8kHGM' > > /opt/rt4/bin/rt-mailgate: connecting to > > http://xxx.xxx/rt/REST/1.0/NoAuth/mail-gateway > > not ok - Could not load a valid user > > /opt/rt4/bin/rt-mailgate: no message passed on STDIN > > Er, you're passing a _binary_ (/usr/bin/test) into rt-mailgate. What do > you expect to happen? > > "No message passed on STDIN" is correct... you didn't pass a valid > email, just garbage. >
Dude, no need to be harsh! I was trying to set a test into rt-mailgate -if that was incorrect then apologies. Point is any mail sent into RT is not being routed into a queue and mail is receiving a timed out mail delivery failure. Are you able to assist in a constructive manner please? Hesan
