[rt-users] Inbound E-mail to server

[Eric Chatham]

On Thursday, August 20, 2009 11:05, Drew Barnes wrote,

> Try changing your subject line to [$Organization #ticket_id]

No go.  I even tried $rtname.

> On 8/20/09 10:59 AM, "Eric Chatham" <echatham at broadvox.com> wrote:
>
>> On Thursday, August 20, 2009 10:29, Jerrad Pierce wrote,
>>
>>>> <VirtualHost 172.16.5.74:80>
>>>>    ServerName clehbrtrckr01.broadvox.local
>>>
>>> /opt/rt3/bin/rt-mailgate --queue MIS --action correspond --url
>>> http://clehbrtrckr01.broadvox.local/
>>>
>>> 127.0.0.1 - - [19/Aug/2009:17:38:14 -0400] "POST
>>> //REST/1.0/NoAuth/mail-gateway HTTP/1.1" 404 320 "-"
>>> "libwww-perl/5.830"
>>>
>>> See the problem? Apache's listening on 172... and rt-mailgate's
>>> connecting on loopback.
>>
>> I see it, thanks.  I had both IPs in /etc/hosts.  I hashed out the loopback
>in
>> /etc/hosts, keeping the server IP listed there.  I re-ran the command with
>no
>> 404 error.  This time there was a 200, which I'm assuming is HTTP 200 Ok.
>>
>> 172.16.5.74 - - [20/Aug/2009:10:51:24 -0400] "POST
>> //REST/1.0/NoAuth/mail-gateway HTTP/1.1" 200 36 "-" "libwww-perl/5.830"
>>
>> Will this correct the issue trying to send e-mail to the system and having
>it
>> parse into the ticket?  I just tried sending an e-mail to RT, having [QUEUE
>> #TICKET NUM] in the subject line.  It still doesn't work and parse the
>> information into the ticket. :/
>>
>> CONFIDENTIAL.  This e-mail and any attached files are confidential and
>should
>> be destroyed and/or returned if you are not the intended and proper
>recipient.
>> _______________________________________________
>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>>
>> Community help: http://wiki.bestpractical.com
>> Commercial support: sales at bestpractical.com
>>
>>
>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
>> Buy a copy at http://rtbook.bestpractical.com
>
>--
>Drew Barnes
>Applications Analyst
>Network Resources Dept.
>Raymond Walters College
>


CONFIDENTIAL.  This e-mail and any attached files are confidential and should be destroyed and/or returned if you are not the intended and proper recipient.