Mail not working

RT Users
1

I can’t figure out why email in to RT has stopped working.

I have this line in /etc/aliases

rt: “|/etc/smrsh/rt-mailgate --queue general --action correspond --url
https://rt.itcs.uiuc.edu/rt/”

The relevant line from maillog is:

Nov 28 09:09:43 rt sendmail[2644]: kASF9ggA002643:
to=“|/etc/smrsh/rt-mailgate --queue general --action correspond --url
https://rt.my.server.edu/rt/”, ctladdr=rt@rt.my.server.edu (8/0),
delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=30949, dsn=4.0.0,
stat=Deferred: prog mailer (/usr/sbin/smrsh) exited with EX_TEMPFAIL

For reference purposes, emailing in to a ticket worked fine when RT was
running at the DocumentRoot but now that I have it moved to /rt/ I can’t
figure out why mail is failing.

John Arends
jarends@uiuc.edu

Network Analyst
ITCS - College of ACES
University of Illinois at Urbana-Champaign

2

I can’t figure out why email in to RT has stopped working.
…
The relevant line from maillog is:

Nov 28 09:09:43 rt sendmail[2644]: kASF9ggA002643:
to=“|/etc/smrsh/rt-mailgate --queue general --action correspond --url
https://rt.my.server.edu/rt/”, ctladdr=rt@rt.my.server.edu (8/0),
delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=30949, dsn=4.0.0,
stat=Deferred: prog mailer (/usr/sbin/smrsh) exited with EX_TEMPFAIL

For reference purposes, emailing in to a ticket worked fine when RT was
running at the DocumentRoot but now that I have it moved to /rt/ I can’t
figure out why mail is failing.

That looks like the error I had one time when using rt-mailgate to

an httpS server. I originally fixed it by letting rt-mailgate talk to a
http server instead.
But, later I got it worked again. Here are my notes:

 # rt-mailgate requires an http connection for some reason
 # probably some conflict between cpan and debian??
 # reinstalling (at least one of) the following fixed it
 # [UPGRADE] libdb4.3 4.3.27-2 -> 4.3.29-6
 # [UPGRADE] libfreezethaw-perl 0.43-2 -> 0.43-3
 # [UPGRADE] libio-socket-ssl-perl 0.96-1 -> 0.994-1
3

Your smrsh link is not set right.

In /etc/smrsh you should have a symlink to rt-mailgate, wherever you
have it located on your system. For example, mine is at
/opt/rt3/bin/rt-mailgate

To locate this file run: find / -name rt-mailgate

If the location was: /opt/rt3/bin/rt-mailgate, create the sym link by
issuing:
ln -s /opt/rt3/bin/rt-mailgate /etc/smrsh/rt-mailgate

Your RT will now be able to handle mail with no problems.

Let me know if you need anything further.

Jason
aka: axelilly

John Arends wrote:

4

Thank you Jon and Jason,

It turns out that my external authentication is actually what is
stopping this from working. /rt is protected, and as long as
authentication is on, sending mail does not work.

This actually has nothing to do with the fact that I moved the
installation from the doc root to /. This is still a development system
so I got a bit ahead of myself.

Do you have any suggestions on how to get around this? It looks like
rt-mailgate needs to talk to RT, but how can I do that if I have our
custom external authentication system wrapped around RT?

My apache config follows:

<Directory "/opt/rt3/share/html">
   Options FollowSymLinks ExecCGI
   AllowOverride All
 </Directory>

<Location /rt >
AuthName “**our custom auth **”
AuthType Basic
Require valid-user

AddDefaultCharset UTF-8
# Adding the following for RT (the ticket tracker)
AddHandler fastcgi-script .fcgi
ScriptAlias /rt /opt/rt3/bin/mason_handler.fcgi

Is there another way I could have done this?

Jon Daley wrote:> On Tue, 28 Nov 2006, John Arends wrote:

I can’t figure out why email in to RT has stopped working.
…
The relevant line from maillog is:

Nov 28 09:09:43 rt sendmail[2644]: kASF9ggA002643:
to=“|/etc/smrsh/rt-mailgate --queue general --action correspond --url
https://rt.my.server.edu/rt/”, ctladdr=rt@rt.my.server.edu (8/0),
delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=30949, dsn=4.0.0,
stat=Deferred: prog mailer (/usr/sbin/smrsh) exited with EX_TEMPFAIL

For reference purposes, emailing in to a ticket worked fine when RT
was running at the DocumentRoot but now that I have it moved to /rt/ I
can’t figure out why mail is failing.

That looks like the error I had one time when using rt-mailgate to

an httpS server. I originally fixed it by letting rt-mailgate talk to a
http server instead.
But, later I got it worked again. Here are my notes:

# rt-mailgate requires an http connection for some reason
# probably some conflict between cpan and debian??
#
# reinstalling (at least one of) the following fixed it
# [UPGRADE] libdb4.3 4.3.27-2 -> 4.3.29-6
# [UPGRADE] libfreezethaw-perl 0.43-2 -> 0.43-3
# [UPGRADE] libio-socket-ssl-perl 0.96-1 -> 0.994-1

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media. Buy
a copy at http://rtbook.bestpractical.com

5

John Arends wrote:

> Do you have any suggestions on how to get around this? It looks like > rt-mailgate needs to talk to RT, but how can I do that if I have our > custom external authentication system wrapped around RT? > Maybe you need the REST and NOAUTH Locations in your httpd.conf file. These should be within your RT virtual host section. These should allow rt-mailgate to communicate with no auth. 
  <Location /REST/1.0/NoAuth>
   satisfy any
   allow from all
  </Location>

  <Location /NoAuth>
   satisfy any
   allow from all
  </Location>

Let me know,
axelilly

6

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf
Of John Arends
Sent: Tuesday, November 28, 2006 10:44 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Mail not working

Thank you Jon and Jason,

It turns out that my external authentication is actually what is
stopping this from working. /rt is protected, and as long as
authentication is on, sending mail does not work.

This actually has nothing to do with the fact that I moved the
installation from the doc root to /. This is still a
development system
so I got a bit ahead of myself.

Do you have any suggestions on how to get around this? It looks like
rt-mailgate needs to talk to RT, but how can I do that if I have our
custom external authentication system wrapped around RT?

John,

Two possible solutions:

  • Make Apache listen on an additional port (444 perhaps) using RT’s
    username/password authentication and have mailgate talk to that URL.

  • Make Apache accept port 80 connections only from the localhost and use the
    localhost URL in the mail config.

Steve

Stephen Turner
Senior Programmer/Analyst - Client Support Services
MIT Information Services and Technology (IS&T)