Hi,
I’d like to install RT on a host and not have an SMTP-daemon listening
on that host, but have rt-mailgate installed on the mailserver and
deliver the messages via http to the RT-server.
I thought this is possible since rt3 - but I found no documentation how
to achieve this.
I don’t want to do a complete install of RT3 on the mailserver, due to
the enormous amount of additional Perl-Modules.
Just a minimal install, so that rt-mailgate works.
Any help appreciated.
cheers,
Rainer
You may try using fetchmail to retrieve the mail from your server:
Here is a wiki page that mentions it:
http://wiki.bestpractical.com/index.cgi?POP3Mailgate
Hopefully that will help you someOn Fri, 16 Jul 2004 02:03:31 +0200, Rainer Duffner rainer@ultra-secure.de wrote:
Hi,
I’d like to install RT on a host and not have an SMTP-daemon listening
on that host, but have rt-mailgate installed on the mailserver and
deliver the messages via http to the RT-server.
I thought this is possible since rt3 - but I found no documentation how
to achieve this.
I don’t want to do a complete install of RT3 on the mailserver, due to
the enormous amount of additional Perl-Modules.
Just a minimal install, so that rt-mailgate works.Any help appreciated.
cheers,
Rainer
Be sure to check out the RT wiki at http://wiki.bestpractical.com
Randy Oswald wrote:
You may try using fetchmail to retrieve the mail from your server:
Here is a wiki page that mentions it:
Hopefully that will help you some
OK, so I still need to have some sort of SMTP-daemon running on the
RT-system (wanted to avoid that).
But why does RT-Mailgate talk HTTP to RT then ? 
Thanks,
Rainer
At 06:07 PM 7/19/2004, Rainer Duffner wrote:
OK, so I still need to have some sort of SMTP-daemon running on the
RT-system (wanted to avoid that).
You don’t need to have an SMTP daemon on the same host as RT.
But why does RT-Mailgate talk HTTP to RT then ?
Exactly for the purpose of having the mailgate and the web UI on separate
machines.
To use just the mailgate, grab and unpack the tarball. Run configure with
the appropriate options. Run ‘perl sbin/rt-test-dependencies -v’ and make
sure you satisfy the mailgate dependencies. You can probably get away with
running ‘make bin-install && make lib-install’ but I don’t have a machine
to test that on at the moment.
Michael
Michael S. Liebman m-liebman@northwestern.edu
http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”
Michael S. Liebman wrote:
At 06:07 PM 7/19/2004, Rainer Duffner wrote:
OK, so I still need to have some sort of SMTP-daemon running on the
RT-system (wanted to avoid that).You don’t need to have an SMTP daemon on the same host as RT.
But why does RT-Mailgate talk HTTP to RT then ?
Exactly for the purpose of having the mailgate and the web UI on separate
machines.To use just the mailgate, grab and unpack the tarball. Run configure with
the appropriate options. Run ‘perl sbin/rt-test-dependencies -v’ and make
sure you satisfy the mailgate dependencies. You can probably get away with
running ‘make bin-install && make lib-install’ but I don’t have a machine
to test that on at the moment.Michael
OK,
now that I have read it, it looks stupid that I didn’t find this
solution myself.
I’ve tried it and it seems to work.
OTOH, a little hint in the documentation wouldn’t have been bad - I’ll
try to write one or two sentences in the wiki about this, once I’m sure
I didn’t make a serious mistake.
Thanks a lot.
RT3 looks very good.
cheers,
Rainer
Hopefully that will help you some
hi
I’d like to comment here that I still would suggest a local delivery
smtp-spool-process (like a dumb sendmail sitting on localhost) as if something
in this fetchmail-using-rtmailgate-as-mail-transfer-agent situation fails
(especially rt-mailgate eg. not being able to talk to the rt-webapplication),
I’d not bet that delivery is being retried by fetchmail, but it definitely would
be retried by sendmail - just in case.
maybe someone can comment on fetchmail-behaviour in case of failure?
regrads
hk