Rt-mailgate

RT Users
1

Good Morning. I am trying to set up RT for the first time and have run in
to a problem with the mail gateway. I have added the line:

rt: |“/path/to/lrt/bin/rt-mailgate general correspond”

to /etc/aliases as per the readme. /etc/sendmail.cf is set to look at
/etc/aliases. When I send mail to rt@myhost.mydomain.com it is returned
undeliverable with the following message:

----- The following addresses had permanent fatal errors -----
|“/opt/rt/bin/rt-mailgate general correspond”
(expanded from: rt@myhost.mydomain.com)

----- Transcript of session follows -----
sh: rt-mailgate not available for sendmail programs
554 |“/opt/rt/bin/rt-mailgate general correspond”… Service unavailable

Any ideas as to what I am missing?

Thanks,
Billy Gunn
Unix Sys Admin
Interadnet, Inc.
919-657-4350

2

I once found some documentation (somewhere) on rt-mailgate, the different
-options for it, and how to setup the various email aliases, etc.
I am unable to find this information again, can anybody point me in the
right direction?
Thanks,
Shane

3

the README file, and rt-mailgate --help
should get you started
-jOn Thu, Apr 19, 2001 at 09:54:00AM -0400, shane wrote:

I once found some documentation (somewhere) on rt-mailgate, the different
-options for it, and how to setup the various email aliases, etc.
I am unable to find this information again, can anybody point me in the
right direction?
Thanks,
Shane

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

T'waS br|ll1G 4|||> 7#e sl1T#Y T0v3s D1|> gYR3 4nd Gimb@1 1|| 7#E //A83
all |/|1|/|53Y W3R3 d4 60r0GR0V3s @|||> |>4 M0MES wr47H oUTGR4b3.

4

I could use some help with troubleshooting what I think is an rt-mailgate problem. Here’s the current config I have in place:

RedHat 8.0
Sendmail 8.12.5.7
Mysql 4.0.12
Apache 1.3 / Modperl1

I can send email out to external addresses when I generate a ticket from within rt, but I cannot generate a ticket via email in to rt. Here is what I see in the mailog:

Jun 2 17:13:49 rttracker sendmail[801]: h52LDnQS000801: from=rcassily@DENOVIS.COM, size=541, class=0, nrcpts=1, msgid=<B5A4987C50
B02D4B8DB479C5796346243ECC11@exchsrvr-1.ehealthdirect.com>, proto=ESMTP, daemon=Daemon0, relay=exchsrvr-1.ehealthdirect.com [172.16.
5.112]
Jun 2 17:13:50 rttracker sendmail[803]: h52LDnQS000801: to=monitor@rttracker.denovis.com, delay=00:00:01, xdelay=00:00:00, mailer
=relay, pri=30537, relay=exchsrvr-1.denovis.com [172.16.5.112], dsn=2.0.0, stat=Sent ( <B5A4987C50B02D4B8DB479C5796346243ECC11@exchs
rvr-1.ehealthdirect.com> Queued mail for delivery)
Jun 2 17:13:50 rttracker sendmail[804]: h52LDoQS000804: from=rcassily@DENOVIS.COM, size=1048, class=0, nrcpts=1, msgid=<B5A4987C5
0B02D4B8DB479C5796346243ECC11@exchsrvr-1.ehealthdirect.com>, proto=ESMTP, daemon=Daemon0, relay=exchsrvr-1.ehealthdirect.com [172.16
.5.112]
Jun 2 17:13:50 rttracker sendmail[806]: h52LDoQS000804: to=monitor@rttracker.denovis.com, delay=00:00:00, xdelay=00:00:00, mailer
=relay, pri=31044, relay=exchsrvr-1.denovis.com [172.16.5.112], dsn=2.0.0, stat=Sent ( <B5A4987C50B02D4B8DB479C5796346243ECC11@exchs
rvr-1.ehealthdirect.com> Queued mail for delivery)
Jun 2 17:13:50 rttracker sendmail[807]: h52LDoQS000807: from=rcassily@DENOVIS.COM, size=1437, class=0, nrcpts=1, msgid=<B5A4987C5
0B02D4B8DB479C5796346243ECC11@exchsrvr-1.ehealthdirect.com>, proto=ESMTP, daemon=Daemon0, relay=exchsrvr-1.ehealthdirect.com [172.16
.5.112]
Jun 2 17:13:50 rttracker sendmail[809]: h52LDoQS000807: to=monitor@rttracker.denovis.com, delay=00:00:00, xdelay=00:00:00, mailer
=relay, pri=31433, relay=exchsrvr-1.denovis.com [172.16.5.112], dsn=2.0.0, stat=Sent ( <B5A4987C50B02D4B8DB479C5796346243ECC11@exchs
rvr-1.ehealthdirect.com> Queued mail for delivery)

Here is what I have placed in the aliases file:

Monitor: “|/opt/rt3/bin/rt-mailgate --queue Monitor --action correspond --url http://localhost/”
Monitor-comment: “|/opt/rt3/bin/rt-mailgate --queue Monitor --action comment --url http://localhost/”

Is there a way to test rt-mailgate to see if it is working properly? Thanks in advance for your help.

5

Out of curiosity, have you set permissions for the everyone group so
that they can create tickets? I recently setup rt for the first time and
I neglected to set permissions at first. The clue was log entries in the
syslog file, not in mail.log.

JenOn Mon, Jun 02, 2003 at 06:06:55PM -0400, Cassily, Ryan wrote:

I could use some help with troubleshooting what I think is an rt-mailgate problem. Here’s the current config I have in place:

RedHat 8.0
Sendmail 8.12.5.7
Mysql 4.0.12
Apache 1.3 / Modperl1

I can send email out to external addresses when I generate a ticket from within rt, but I cannot generate a ticket via email in to rt. Here is what I see in the mailog:

Jun 2 17:13:49 rttracker sendmail[801]: h52LDnQS000801: from=rcassily@DENOVIS.COM, size=541, class=0, nrcpts=1, msgid=<B5A4987C50
B02D4B8DB479C5796346243ECC11@exchsrvr-1.ehealthdirect.com>, proto=ESMTP, daemon=Daemon0, relay=exchsrvr-1.ehealthdirect.com [172.16.
5.112]
Jun 2 17:13:50 rttracker sendmail[803]: h52LDnQS000801: to=monitor@rttracker.denovis.com, delay=00:00:01, xdelay=00:00:00, mailer
=relay, pri=30537, relay=exchsrvr-1.denovis.com [172.16.5.112], dsn=2.0.0, stat=Sent ( <B5A4987C50B02D4B8DB479C5796346243ECC11@exchs
rvr-1.ehealthdirect.com> Queued mail for delivery)
Jun 2 17:13:50 rttracker sendmail[804]: h52LDoQS000804: from=rcassily@DENOVIS.COM, size=1048, class=0, nrcpts=1, msgid=<B5A4987C5
0B02D4B8DB479C5796346243ECC11@exchsrvr-1.ehealthdirect.com>, proto=ESMTP, daemon=Daemon0, relay=exchsrvr-1.ehealthdirect.com [172.16
.5.112]
Jun 2 17:13:50 rttracker sendmail[806]: h52LDoQS000804: to=monitor@rttracker.denovis.com, delay=00:00:00, xdelay=00:00:00, mailer
=relay, pri=31044, relay=exchsrvr-1.denovis.com [172.16.5.112], dsn=2.0.0, stat=Sent ( <B5A4987C50B02D4B8DB479C5796346243ECC11@exchs
rvr-1.ehealthdirect.com> Queued mail for delivery)
Jun 2 17:13:50 rttracker sendmail[807]: h52LDoQS000807: from=rcassily@DENOVIS.COM, size=1437, class=0, nrcpts=1, msgid=<B5A4987C5
0B02D4B8DB479C5796346243ECC11@exchsrvr-1.ehealthdirect.com>, proto=ESMTP, daemon=Daemon0, relay=exchsrvr-1.ehealthdirect.com [172.16
.5.112]
Jun 2 17:13:50 rttracker sendmail[809]: h52LDoQS000807: to=monitor@rttracker.denovis.com, delay=00:00:00, xdelay=00:00:00, mailer
=relay, pri=31433, relay=exchsrvr-1.denovis.com [172.16.5.112], dsn=2.0.0, stat=Sent ( <B5A4987C50B02D4B8DB479C5796346243ECC11@exchs
rvr-1.ehealthdirect.com> Queued mail for delivery)

Here is what I have placed in the aliases file:

Monitor: “|/opt/rt3/bin/rt-mailgate --queue Monitor --action
correspond --url http://localhost/”
Monitor-comment: “|/opt/rt3/bin/rt-mailgate --queue Monitor --action
comment --url http://localhost/”

Is there a way to test rt-mailgate to see if it is working properly? Thanks in advance for your help.

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

6

I added the hostname of the machine to the local-host-names file. It looks like sendmail is now trying to deliver the mail to rt but the service is unavailable. I have attached part of the log. The first part is the successful ticket created and emailed out from the web interface, the next is the failure when sending an email from the exchange server.From: Michael van Elst [mailto:mlelstv@dev.de.cw.net]
Sent: Monday, June 02, 2003 6:32 PM
To: Cassily, Ryan
Subject: Re: [rt-users] rt-mailgate

Jun 2 17:13:50 rttracker sendmail[803]: h52LDnQS000801: to=monitor@rttracker.denovis.com, delay=00:00:01, xdelay=00:00:00, mailer
=relay, pri=30537, relay=exchsrvr-1.denovis.com [172.16.5.112], dsn=2.0.0, stat=Sent ( <B5A4987C50B02D4B8DB479C5796346243ECC11@exchs
rvr-1.ehealthdirect.com> Queued mail for delivery)

This says that the mail was forwarded to exchsrvr-1.denovis.com, which
seems to be a mail hub (MS exchange ?).

I guess that you want the mail to be delivered locally. You need to
configure sendmail to accept and deliver mails to rttracker.denovis.com.
This is normally done by adding a line with this hostname to the
sendmail.cw file.

Is there a way to test rt-mailgate to see if it is working properly? Thanks in advance for your help.

Just pipe a mail in standard (RFC2822) format to rt-mailgate. I.e.

cat my-mail | rt-mailgate --action correspond --queue xyz --url http://localhost/

Greetings,
,eM"“=. a”-. Michael van Elst
dWWMWM" - :GM==; mlelstv@dev.de.cw.net
:WWMWMw=–. "W=’ cable & wireless
9WWMm==-.
“-Wmw-” CABLE & WIRELESS

log.txt (2.24 KB)

7

I added the hostname of the machine to the local-host-names file. It looks like sendmail is now trying to deliver the mail to rt but the service is unavailable. I have attached part of the log. The first part is the successful ticket created and emailed out from the web interface, the next is the failure when sending an email from the exchange server.

‘Service unavailable’ comes from many places.

Please check wether rt-mailgate can be executed by the mailer.

,eM""=.            a"-.                         Michael van Elst

dWWMWM" - :GM==; mlelstv@dev.de.cw.net
:WWMWMw=–. "W=’ cable & wireless
9WWMm==-.
“-Wmw-” CABLE & WIRELESS

8

I executed the following and it did create tickets in the proper queue.

cat test | ./rt-mailgate --action correspond --queue monitor --url http://localhost/-----Original Message-----
From: Michael van Elst [mailto:mlelstv@dev.de.cw.net]
Sent: Tuesday, June 03, 2003 10:57 AM
To: Cassily, Ryan
Cc: Rt-Users@Lists. Fsck. Com (E-mail)
Subject: Re: [rt-users] rt-mailgate

On Tue, Jun 03, 2003, Cassily, Ryan wrote:

I added the hostname of the machine to the local-host-names file. It looks like sendmail is now trying to deliver the mail to rt but the service is unavailable. I have attached part of the log. The first part is the successful ticket created and emailed out from the web interface, the next is the failure when sending an email from the exchange server.

‘Service unavailable’ comes from many places.

Please check wether rt-mailgate can be executed by the mailer.

,eM""=.            a"-.                         Michael van Elst

dWWMWM" - :GM==; mlelstv@dev.de.cw.net
:WWMWMw=–. "W=’ cable & wireless
9WWMm==-.
“-Wmw-” CABLE & WIRELESS

9

Hi all,

When a user open a ticket using rt-mailgate with correspond address, he receives
a confirmation with a reply-to set to correspond address. So he cannot comment
it using a reply in his mail client.

correspond address :
cds_rt: “|/opt/rt/3.0.6/bin/rt-mailgate --queue TEST --action correspond --url
http://domain.com/”

comment address :
cds_tr: “|/opt/rt/3.0.6/bin/rt-mailgate --queue TEST --action comment --url
http://domain.com/”

Is it possible to set a reply-to to comment address ? How to do that ?

Regards

Franck

10

Hi,

I want to set an other RT on an other machine.

I need to know if the alias “rt” used in /etc/aliases could be changed
to rt-test for exemple ?
Or does Request Tracker is waiting for an “rt” occurrence only ?

Thanks for help.

11

I want to set an other RT on an other machine.

I need to know if the alias “rt” used in /etc/aliases could be changed
to rt-test for exemple ?
Or does Request Tracker is waiting for an “rt” occurrence only ?

It’s not completely clear what you’re after, but no, the alias you
choose to catch mail for rt need not be any specific string.

I thought you had to match that string with a setting in RT_Config, but
I don’t see it (I’m fairly new to RT, myself).

Now, if your RT machines are not the direct mail-catchers for your
domain, you’ll have to deal with forwarding the messages that come in
appropriately, but that’s a separate issue.

Cheers,
– jra
Jay R. Ashworth jra@baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274

  If you can read this... thank a system administrator.  Or two.  --me
12

I want to set an other RT on an other machine.

I need to know if the alias “rt” used in /etc/aliases could be changed
to rt-test for exemple ?
Or does Request Tracker is waiting for an “rt” occurrence only ?
I am new to RT, but as part of my testing I submitted tickets using
rt-mailgate on the command line (sending pseudo email as input). Not
necessarily a recommended way to do things, but as I did not bother to
put a To: header in, I can say pretty confidently that rt-mailgate does
not care what the to address is. Any use of “rt” in the alias name is
for convenience of humans administering it.

I thought you had to match that string with a setting in RT_Config, but
I don’t see it (I’m fairly new to RT, myself).
I believe that is so that RT does not get into loops: e.g. I reply to email
from RT about a request I sent, perhaps cc’ing rt. We do not want rt to
send mail to the rt alias generating another comment (which then sends mail
to the rt alias, ad infinitum).

This certainly should be done, but will not (immediately) break things if
not done.

Now, if your RT machines are not the direct mail-catchers for your
domain, you’ll have to deal with forwarding the messages that come in
appropriately, but that’s a separate issue.
Or you just install rt-mailgate on your domain incoming SMTP servers, and
install the aliases on those servers, each specifying different options to
rt-mailgate (e.g. different URLs).

13

Thomas M. Payerle wrote:

I want to set an other RT on an other machine.

I need to know if the alias “rt” used in /etc/aliases could be changed
to rt-test for exemple ?
Or does Request Tracker is waiting for an “rt” occurrence only ?

I am new to RT, but as part of my testing I submitted tickets using
rt-mailgate on the command line (sending pseudo email as input). Not
necessarily a recommended way to do things, but as I did not bother to
put a To: header in, I can say pretty confidently that rt-mailgate does
not care what the to address is. Any use of “rt” in the alias name is
for convenience of humans administering it.

I thought you had to match that string with a setting in RT_Config, but
I don’t see it (I’m fairly new to RT, myself).

I believe that is so that RT does not get into loops: e.g. I reply to
email
from RT about a request I sent, perhaps cc’ing rt. We do not want rt to
send mail to the rt alias generating another comment (which then sends
mail
to the rt alias, ad infinitum).

I think you mean the
Set($ParseNewMessageForTicketCcs , 1);
Set($RTAddressRegexp , ‘^rt@example.com$’);
portions. This is not something we do, although we probably should.
Thankfully, most of our users are not in the habit of CCing anyone
except their supervisors.

Set($RTAddressRegexp ,
‘^net(support|staff)@(outside|rtbox).domain.edu’); is what we should
be using, I think. Until I get a chance to test it on a non-production
box, I don’t know for sure that this is the case. Better explanations
of the address are below. Hopefully that will clear up the syntax I’m
using.

This certainly should be done, but will not (immediately) break things if
not done.

Now, if your RT machines are not the direct mail-catchers for your
domain, you’ll have to deal with forwarding the messages that come in
appropriately, but that’s a separate issue.

Or you just install rt-mailgate on your domain incoming SMTP servers, and
install the aliases on those servers, each specifying different
options to
rt-mailgate (e.g. different URLs).

For us, our netsupport|netstaff@outside.domain.edu accounts forward to
netsupport|netstaff@rtbox.domain.edu. The rt-mailgate resides on that
host, watching for netsupport|netstaff@rtbox.domain.edu. That is also
the correspond|comment address, so all replies route directly back to
that box.

The rt-users Archives

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Drew Barnes
Applications Analyst
Raymond Walters College
University of Cincinnati

14

This might be more of a MTA question, but we’re using rt-mailgate set
up in /etc/aliases with postfix. httpd stopped working on our RT
server, so obviously new mail couldn’t be put into RT.

My question is would the mail queue up anywhere to be reprocessed? RT
is so robust that I can’t image this hasn’t been considered and dealt
with, just not sure of postfix or rt-mailgate would be the one
handling that.

15

This might be more of a MTA question, but we’re using rt-mailgate set
up in /etc/aliases with postfix. httpd stopped working on our RT
server, so obviously new mail couldn’t be put into RT.

My question is would the mail queue up anywhere to be reprocessed? RT
is so robust that I can’t image this hasn’t been considered and dealt
with, just not sure of postfix or rt-mailgate would be the one
handling that.

RT Mailgate exits with a code telling postfix to hang onto the mail. The
key to google on is ‘TEMPFAIL’
-j

16

rt-users-bounces@lists.bestpractical.com wrote:> On Sun, Feb 24, 2008 at 10:03:22AM -0500, Steve Cochran wrote:

This might be more of a MTA question, but we’re using rt-mailgate set
up in /etc/aliases with postfix. httpd stopped working on our RT
server, so obviously new mail couldn’t be put into RT.

My question is would the mail queue up anywhere to be reprocessed? RT
is so robust that I can’t image this hasn’t been considered and dealt
with, just not sure of postfix or rt-mailgate would be the one
handling that.

RT Mailgate exits with a code telling postfix to hang onto
the mail. The key to google on is ‘TEMPFAIL’
-j

Following on from which, once fixed, look at using postqueue -s to
reattempt delivery immediately, rather than waiting for a retry.

Stef
Stefan Morrell | Operations Director
Tel: 0845 3452820 | Alpha Omega Computers Ltd
Fax: 0845 3452830 | Incorporating Level 5 Internet
stef@aoc-uk.com | stef@l5net.net

Alpha Omega Computers Ltd, Unit 57, BBTC, Grange Road, Batley, WF17 6ER.
Registered in England No. 3867142. VAT No. GB734421454

17

I made a recently change to how my apache2 server was configured to
redirect all requests through https. Now emails are not flowing through to
RT - I tracked the issue down to rt-mailgate complaining about not being
able to verify the certificate. I’m a little perplexed on how to proceed
or how to verify what certs/CAs rt-mailgate is using, or if there is an
issue with the Crypt::SSLeay module (which I had to force install due to a
failing test). I only have one openssl install on the system, and I
thought Crypt::SSLeay would reach through to those configs for things like
CA certs, etc…

Perhaps an easy workaround, since the mail server and apache2 server are on
the same machine, would be to configure a “localhost:80” virtual host
within apache2 and bypass SSL when accessing RT via that url.

Any helpful hints/suggestions would be greatly appreciated. I’ve been
google-ing away but haven’t had any luck yet.

-Rob

18

I made a recently change to how my apache2 server was configured to redirect
all requests through https. Now emails are not flowing through to RT - I
tracked the issue down to rt-mailgate complaining about not being able to
verify the certificate. I’m a little perplexed on how to proceed or how to
verify what certs/CAs rt-mailgate is using, or if there is an issue with the
Crypt::SSLeay module (which I had to force install due to a failing test).
I only have one openssl install on the system, and I thought Crypt::SSLeay
would reach through to those configs for things like CA certs, etc…

Perhaps an easy workaround, since the mail server and apache2 server are on
the same machine, would be to configure a “localhost:80” virtual host within
apache2 and bypass SSL when accessing RT via that url.

Any helpful hints/suggestions would be greatly appreciated. I’ve been
google-ing away but haven’t had any luck yet.

  AFAIK, rt-mailgate connects to RT using RT's web interface; it

should use whatever cert you have defined in the virtual host entry
for RT. Here is how my fetchmailrc calls rt-mailgate:

mda “/usr/bin/perl /usr/bin/rt-mailgate --url https://localhost/rt
–queue support --action correspond”

19

And if that doesn’t work, since I have a certificate with a domain name (although signed by our internal CA which all of our PCs trust), I had to put in below where Mauricio put in https://localhost, I actually needed to use my dns name in which the certificate is assigned (e.g. https://MyRT)

My $0.02 worth as well. :)From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Mauricio Tavares
Sent: Monday, January 09, 2012 4:02 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate

I made a recently change to how my apache2 server was configured to
redirect all requests through https. Now emails are not flowing
through to RT - I tracked the issue down to rt-mailgate complaining
about not being able to verify the certificate. I’m a little
perplexed on how to proceed or how to verify what certs/CAs
rt-mailgate is using, or if there is an issue with the Crypt::SSLeay module (which I had to force install due to a failing test).
I only have one openssl install on the system, and I thought
Crypt::SSLeay would reach through to those configs for things like CA certs, etc…

Perhaps an easy workaround, since the mail server and apache2 server
are on the same machine, would be to configure a “localhost:80”
virtual host within
apache2 and bypass SSL when accessing RT via that url.

Any helpful hints/suggestions would be greatly appreciated. I’ve
been google-ing away but haven’t had any luck yet.

  AFAIK, rt-mailgate connects to RT using RT's web interface; it should use whatever cert you have defined in the virtual host entry for RT. Here is how my fetchmailrc calls rt-mailgate:

mda “/usr/bin/perl /usr/bin/rt-mailgate --url https://localhost/rt \ –queue support --action correspond”

-Rob

RT Training Sessions (http://bestpractical.com/services/training.html)

  • Boston March 5 & 6, 2012
20

Thanks for the suggestions guys.

I finally just turned off my re-write rule that was re-directing http to
https and side-stepped the rt-mailgate ssl failure all together. Not
ideal, but in practice very few of my users log into RT directly so it’s a
configuration I can live with short term while I figure out the real issue.

I’ve configured postfix to hand messages to the aliases for my queues
directly to rt-mailgate. It is rt-mailgate that cannot verify the ssl
certificate that my web server is presenting it. None of my web browsers
have trouble with it, so it feels like an rt-mailgate configuration issue.
I can repro the issue on the command line…

root@linux:~# /opt/rt4/bin/rt-mailgate --debug --queue ‘general’ --action
correspond --url https://request.domain.com/ < ~/test.msg
/opt/rt4/bin/rt-mailgate: temp file is ‘/tmp/XOCrOYAr8p/vkVDTmoszI’
/opt/rt4/bin/rt-mailgate: connecting to
https://request.domain.com//REST/1.0/NoAuth/mail-gateway
An Error Occurred

500 Can’t connect to
request.domain.com:443 (certificate
verify failed)

/opt/rt4/bin/rt-mailgate: undefined server error

-RobOn Mon, Jan 9, 2012 at 4:08 PM, Izz Abdullah Izz.Abdullah@hibbett.comwrote:

And if that doesn’t work, since I have a certificate with a domain name
(although signed by our internal CA which all of our PCs trust), I had to
put in below where Mauricio put in https://localhost, I actually needed
to use my dns name in which the certificate is assigned (e.g. https://MyRT
)

My $0.02 worth as well. :slight_smile:

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] On Behalf Of Mauricio Tavares
Sent: Monday, January 09, 2012 4:02 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate

On Mon, Jan 9, 2012 at 1:34 PM, Robert Nesius nesius@gmail.com wrote:

I made a recently change to how my apache2 server was configured to
redirect all requests through https. Now emails are not flowing
through to RT - I tracked the issue down to rt-mailgate complaining
about not being able to verify the certificate. I’m a little
perplexed on how to proceed or how to verify what certs/CAs
rt-mailgate is using, or if there is an issue with the Crypt::SSLeay
module (which I had to force install due to a failing test).
I only have one openssl install on the system, and I thought
Crypt::SSLeay would reach through to those configs for things like CA
certs, etc…

Perhaps an easy workaround, since the mail server and apache2 server
are on the same machine, would be to configure a “localhost:80”
virtual host within
apache2 and bypass SSL when accessing RT via that url.

Any helpful hints/suggestions would be greatly appreciated. I’ve
been google-ing away but haven’t had any luck yet.

 AFAIK, rt-mailgate connects to RT using RT's web interface; it should

use whatever cert you have defined in the virtual host entry for RT. Here
is how my fetchmailrc calls rt-mailgate:

mda “/usr/bin/perl /usr/bin/rt-mailgate --url https://localhost/rt
–queue support --action correspond”

-Rob

RT Training Sessions (http://bestpractical.com/services/training.html)

  • Boston - March 5 & 6, 2012

RT Training Sessions (http://bestpractical.com/services/training.html)

  • Boston March 5 & 6, 2012

RT Training Sessions (http://bestpractical.com/services/training.html)

  • Boston March 5 & 6, 2012