Are there any others running an external postfix mail server and RT? I
have been through all of the wiki/google hits and only see examples of
how to setup RT in an exchange domain or with postfix/sendmail on the RT
box. I have an existing domain with postfix/dovecot running on its own
machine. RT is a totally separate machine (actually a Xen VM). I am at a
loss as to even how to begin to get mail delivered to the RT machine and
tickets created from that. I have the following setup on the RT box:
However mail cannot be sent to rt@rt.domain.tld or
rt-comment@rt.domain.tld due to failing DNS resolution that we do not
have control over. I have setup rt.domain.tld in our internal DNS
though. How have others accomplished this? I have thought about
fetchmail on the RT box but not sure if there was a better solution than
that. Thanks for any and all input.
machine (actually a Xen VM). I am at a loss as to even how to begin
to get mail delivered to the RT machine and tickets created from
that. I have the following setup on the RT box:
However mail cannot be sent to rt@rt.domain.tld or
rt-comment@rt.domain.tld due to failing DNS resolution that we do
How about rt@[ip.address.here]
not have control over. I have setup rt.domain.tld in our internal
DNS though. How have others accomplished this? I have thought about
fetchmail on the RT box but not sure if there was a better solution
than that. Thanks for any and all input.
You can either get your central postfix server to relay to you, use
fetchmail or run rt-mailgate on the central postfix server.
All you need to do on your external postfix server is add the email
address/alias you’ve created to the postfix transport(5) file and they
will be relayed to the RT server.
Are there any others running an external postfix mail server and RT? I
have been through all of the wiki/google hits and only see examples of
how to setup RT in an exchange domain or with postfix/sendmail on the
RT
box. I have an existing domain with postfix/dovecot running on its own
machine. RT is a totally separate machine (actually a Xen VM). I am at
a
loss as to even how to begin to get mail delivered to the RT machine
and
tickets created from that. I have the following setup on the RT box:
However mail cannot be sent to rt@rt.domain.tld or
rt-comment@rt.domain.tld due to failing DNS resolution that we do not
have control over. I have setup rt.domain.tld in our internal DNS
though. How have others accomplished this? I have thought about
fetchmail on the RT box but not sure if there was a better solution
than
that. Thanks for any and all input.
Donny B.
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited. If you are not the intended recipient of this
message, please contact the sender and delete this material from this computer.
I’m not clear if we’re using a similar type of setup to what you’re referring to, but I’ll fill in how we do it and hopefully it’ll help you…
We have:
RT box running exim. Exim is setup to smarthost through our front facing mail server, and to integrate with RT queue names. It has a local dnsname of hostname.faredge.com.au .
Qmail frontend server which is configured to forward any matching mails for the specific aliases to queuename@ourrtserver, and handles external mail. It also forwards any messages for exchange users to the exchange server.
An Exchange server which has contacts setup for each queue in question so that a message for "Queue" is correctly forwarded through to queuename@ourrtserver. The exchange domain is the local windows domain (as opposed to "faredge.com.au")
It’s a bit more complicated than it needs to be, but is in place mainly for historical reasons and as it works well so far there and hasn’t introduced a huge overhead there’s no great pressure to change it.
So Donny, I’m not sure about the postfix side of what you’re trying to do - basically make sure you have aliases that relate to each queue that live at your RT server for example:
I’m not clear if we’re using a similar type of setup to what you’re
referring to, but I’ll fill in how we do it and hopefully it’ll help
you…
We have:
-RT box running exim. Exim is setup to smarthost through our front
facing mail server, and to integrate with RT queue names. It has a
local dnsname of hostname.faredge.com.au .
-Qmail frontend server which is configured to forward any matching
mails for the specific aliases to queuename@ourrtserver, and handles
external mail. It also forwards any messages for exchange users to the
exchange server.
-An Exchange server which has contacts setup for each queue in
question so that a message for “Queue” is correctly forwarded through
to queuename@ourrtserver. The exchange domain is the local windows
domain (as opposed to “faredge.com.au”)
It’s a bit more complicated than it needs to be, but is in place
mainly for historical reasons and as it works well so far there and
hasn’t introduced a huge overhead there’s no great pressure to change it.
So Donny, I’m not sure about the postfix side of what you’re trying to
do – basically make sure you have aliases that relate to each queue
that live at your RT server for example:
Thanks for all the input everyone. I ended up installing the rt-mailgate
on our postfix machine and just letting it handle all the forwarding to
the other machine. I have a basic system setup and functioning. Now I am
evaluating what all “features” we need to enable on the RT box. I do
appreciate all the input and various ways that was suggested. I just
figured that this was the easiest with minimal configuration needed.