my RT3.0.9 install came from “apt-get install request-tracker3” on a
Debian Sarge box. All went fine with a little modifications here and there.
but what i am stuck with right now is that i cannot seem to create a
ticket from an email source being sent to my RT system specifiically to
a queue for sysads.
tested creating ticket via WebUI… successful
updates to the ticket (comment/correspond) are sent to the users in RT
who belong to SysAds queue
manually created ticket via rt-mailgate commandline … sucessful
/usr/bin/rt-mailgate --debug -queue SysAds --action correspond
–url http://rt.mydomain.com/rt < /root/testmsg
using email client… create and send an email for sysads@rt.mydomain.com…FAILED (no ticket is created inside RT)
am pretty sure that from w/in the RT box… i can create the ticket via
WebUI and create a ticket via email (using rt-mailgate directly)… so am
guessing that either external mails dont find their way to my rt box or
my rt box does receive them but dont know how to pass it on to rt-mailgate.
using email client… create and send an email for sysads@rt.mydomain.com…FAILED (no ticket is created inside RT)
am pretty sure that from w/in the RT box… i can create the ticket via
WebUI and create a ticket via email (using rt-mailgate directly)… so
am guessing that either external mails dont find their way to my rt
box or my rt box does receive them but dont know how to pass it on to
rt-mailgate.
Is there something I overlooked?
you’ve done some good testing (checking the mailgate from the command
line), but if you want us to offer suggestions you’ll have to include
the alias line you’re using, and the appropriate part of exim’s logs.
now i did a google on the “pipe_transport unset in system_aliases router” error
message just now… i saw this from http://lists.fsck.com/pipermail/rt-
users/2004-February/020779.html…
the newest package for exim4 on debian has pipes disabled by default in
the /etc/aliases b default, which means Your favorite request tracker
won’t get any mails anymore.
then i tracked down Debian Bug #229052 (http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=229052) which gave some workarounds… now am not very
familiar with exim so am very confused on which of the 3 solutions he mentioned
to use.
I want to stick with exim4 since this is the recommended Debian MTA that came
with the RT3.0.9 installation. But if it’d make things easier, we could replace
exim4 with Sendmail or Qmail instead (but am also not familiar with these).
What’s your take on this matter?
R=system_aliases defer (-30): pipe_transport unset in system_aliases router
then i tracked down Debian Bug #229052 (http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=229052) which gave some workarounds… now am
not very familiar with exim so am very confused on which of the 3
solutions he mentioned to use.
I want to stick with exim4 since this is the recommended Debian MTA
that came with the RT3.0.9 installation. But if it’d make things
easier, we could replace exim4 with Sendmail or Qmail instead (but
am also not familiar with these). What’s your take on this matter?
You should use whatever you understand best. Of the solutions
mentioned in that debian bug report:
(1) is an automatic thing that does not require filling in
/etc/aliases, and instead queries the database for allowed
queues.
(2) just allows pipes for rt-mailgate, nothing special or automatic.
(3) is an updated form of the automatic thing I stuck in the old rtfm
you could also downgrade exim to exim3.
If you don’t want to learn much about exim, and just want it to to
behave like it used to, you should probably just go with (2).
and edited my /etc/exim4/conf.d/router/400_exim4-config_system_aliases
to look like this:
system_aliases:
debug_print = "R: system_aliases for $local_part@$domain"
driver = redirect
domains = +local_domains
allow_fail
allow_defer
data = ${lookup{$local_part}lsearch{/etc/aliases}}
user = list
group = mail
file_transport = address_file
pipe_transport = address_pipe
pipe_transport = request_tracker3_pipe
directory_transport = address_directory
then i restarted exim4. and tried emailing RT again… but RT WebUI still
doesn’t register any new tickets. Should i be modifying other exim4
files to tell it to use the request_tracker3_pipe?
i may need a little more hand-holding on setting option (2) up. I’ve
created the ff…
my time is fairly limited.
(2) /etc/exim4/conf.d/transport/30_request-tracker3
and edited my /etc/exim4/conf.d/router/400_exim4-config_system_aliases
with a quick glance, they both looks okay.
then i restarted exim4. and tried emailing RT again… but RT WebUI
still doesn’t register any new tickets. Should i be modifying other
exim4 files to tell it to use the request_tracker3_pipe?
I don’t think you need to modify anything else. did you restart exim? what’s
in the logs? the errors are usually pretty descriptive.
here’s the data: