Lorraine Johnson wrote:
* I noticed that mails sent outside rt are not being delivered in the system.
I think my RT- mailgate is not working. Autopreply messages are also not being
received.
*
* Kindly help if you have an idea.
*
* thank you
You’ve got the function of
Goodmorning all,
I noticed that mails sent outside rt are not being delivered in the system.
I think my RT- mailgate is not working. Autopreply messages are also not
being received.
Kindly help if you have an idea.
thank you
Ok; I figured out what it is but I don't know why.
"Time Management for System Administrators" - page 30 "Some general advice" -
#7 - "The strangest problems often turn out to be misconfigured DNS."
If I use the IP address for the server versus the FQDN, tickets flow in
perfectly. If I use
Thomas - You are correct. It wouldn't be so bad if the RT site wasn't working.
If I use the exact same address I use for the web server in the rt-mailgate
scripts it fails. If I put that address into a web browser, I can use the
system as expected. I'm trying to figure out what the "disconnect"
Hi,
Stephen Cena asked:
* Ive been beating my head against this for days now and cant figure this
out. I original had
* (as much as possible) a clone of our production environment in a lab. I
reached a point
* where I was forced to re-IP the lab environment which went well. Now,
I've been beating my head against this for days now and can't figure this out.
I original had (as much as possible) a clone of our production environment in a
lab. I reached a point where I was forced to re-IP the lab environment which
went well. Now, rt-mailgate simply doesn't work. Outbound
All,
It appears that the problem is even more widespread. The system will not
accept any email. The errors appear to point to missing subjects and from
addresses but the process worked before the upgrade. ANY help will be
appreciated. I am out of ideas.
-Dale
From: Poulter, Dale
Sent:
We upgraded to 4.2.12 and everything looked ok. However, we are now unable to
submit tickets via email using rt-mailgate. I have seen many posts but none of
the proposed solutions seem to work. We are using the same command as we did
in 3.8.7 for sendmail . Here is our setup.
Perl: 5.16.3
Ok, I'm inching closer. I found out that it works if I run it from the
command line, but not when sendmail fires it off. (This probably gave
me the false sense that it worked by switching to HTTP.)
I turned on debug level logging in RT. It logged a bunch of stuff when
run from the command
Figured it out. I created a catch-all address in virtusertable. Unknown
to me, virtusertable gets processed before aliases, so it was hitting
the catch-all and never made it to aliases.
Joseph D. Wagner
On 09/06/2015 12:13 PM, Alex Vandiver wrote:
On Sun, Sep 06, 2015 at 12:31:28AM -0700,
On Sat, Sep 05, 2015 at 11:22:48PM -0700, Joseph D. Wagner wrote:
> I had apache set to allow rt over https only. Trying over http would fail.
>
> rt-mailgate was working perfectly fine over https when using
> "--action correspond". However, when using "--action comment", it
> fails saying it
Here it is. I left everything intact except the url.
prc:"|/usr/bin/rt-mailgate --queue 'Performance Review'
--action correspond --url https://./rt;
prc-staff: "|/usr/bin/rt-mailgate --queue 'Performance Review'
--action comment--url https://./rt;
Joe
On Sun, Sep 06, 2015 at 12:31:28AM -0700, Joseph D. Wagner wrote:
> Here it is. I left everything intact except the url.
> [snip]
Those look fine. Double-check that you have not multiply-defined
prc-staff elsewhere in aliases, and that you've run `newaliases`.
Short of that, my only suggestion
I'm setting up a new RT server, and I'm having some trouble getting rt-mailgate to accept email piped from postfix.
`Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
Permission denied`
Best I can tell, it's likely to be a permissions issue. What owner, group and
mode
On my system, the application is world executable. I don't recall if that's
the default or I changed it. I'm sure someone here will say that's a bad
idea, security wise.
At a minimum, it needs to be executable by whatever user ID postfix is
running as. If you want to lock down the executable,
On Tue, Jun 16, 2015 at 11:54:52AM -0400, Matt Brennan wrote:
On my system, the application is world executable. I don't recall if that's
the default or I changed it. I'm sure someone here will say that's a bad
idea, security wise.
At a minimum, it needs to be executable by whatever user ID
It is chrooted, but when I s/-/n for all the chrooted processes in master.cf
and restarted postfix, it didn't make any difference. I just swapped the
original master.cf back in.
I'll update to add that my aliases were quoted incorrectly to begin with, and
having changed that, the full error
I figured this out. I was using this project as an opportunity to try out
plenv, but used /root/.plenv to set global Perl. When we set /root +x, it
started working. Now I just need to figure out how best to fix it long-term.
Thanks, all.
On Tue, Jun 16, 2015 at 12:39:15PM -0700, Aaron C. de
It's Debian Wheezy. No SELinux in this case.
On Tue, Jun 16, 2015 at 09:25:02PM +0200, Joop wrote:
On 16-6-2015 17:33, Jeff Melton wrote:
I'm setting up a new RT server, and I'm having some trouble getting
rt-mailgate to accept email piped from postfix.
`Command output: local: fatal:
AppArmor? (Or is that just Ubuntu?)
Also, is the postfix process running in a chroot?
Check /etc/postfix/master.cf to see if the service that is doing the
rt-mailgate delivery has a 'y' in the chroot column.
-A
On Tue, Jun 16, 2015 at 12:29 PM, Jeff Melton j...@ifworld.com wrote:
It's Debian
On 16-6-2015 17:33, Jeff Melton wrote:
I'm setting up a new RT server, and I'm having some trouble getting
rt-mailgate to accept email piped from postfix.
`Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
Permission denied`
You don't state which OS you're using but if you're
Fixed it. Apparently --no-verify-ssl only deals with the hostname on
the certificate.
I added the following to the 'use' section at the top of rt-mailgate:
use IO::Socket::SSL;
and then in the get_useragent function, I added the following ssl_opts line:
$ua-ssl_opts( SSL_verify_mode =
Mailgate has been driving me nuts. I downloaded 4.2.10 and set it up
on a bright, shiny new server.
I'm running fetchmail on my RT box using the following to send tickets to RT:
poll mail.mydomain.tld with protocol pop3
username engineering password -redacted- mda
/opt/rt4/bin/rt-mailgate
On Wed, Aug 06, 2014 at 09:44:40PM +, Richards, Matthew E ERDC-RDE-CERL-IL
wrote:
If you're going to the localhost, I'm not actually sure why you're
involving SSL, but that's a separate issue.
Actually, that was the issue. You're right, there's no need to use SSL
with localhost. We
On Mon, Aug 04, 2014 at 08:29:02PM +, Richards, Matthew E ERDC-RDE-CERL-IL
wrote:
443 is listening on localhost. As you suggested, we tried curl from
the localhost with both the FQDN and localhost URLs. We had limited
success (without any message content), but it still fails with rt-
If you're going to the localhost, I'm not actually sure why you're
involving SSL, but that's a separate issue.
Actually, that was the issue. You're right, there's no need to use SSL with
localhost. We have a rewrite from 80 to 443 for all interfaces and it always
forces us to use https. I
On Thu, Jul 31, 2014 at 09:03:16PM +, Richards, Matthew E ERDC-RDE-CERL-IL
wrote:
I increased the timeout from 180 to 750 added extra debugging to the code to
get more information. I replaced our URL with localhost for security:
Are you actually listening with SSL on localhost? Is your
Hi Kevin,
Thank you for the reply.
Are you actually listening with SSL on localhost? Is your webserver
configured to listen and allow that through to RT?
443 is listening on localhost. As you suggested, we tried curl from the
localhost with both the FQDN and localhost URLs. We had
We are fighting an issue after updating RT from 4.2.3 to 4.2.6 and rt-mailgate.
We also updated our OS to Ubuntu 14.04. Everything seems to be working in RT
except rt-mailgate. I've isolated it to an LWP::Protocol::https::Socket:
Timeout error returned from the post to the RESTful service:
Hi rt-users
I am trying to install rt 4.2.6 and I am getting this error when I send
email to rt-mailgate.
I am using
centos 6.5
postfix
rt 4.2.6 with smime enabled
https
Can anyone help point me to what might be wrong?
Thanks,
-Dan
(temporary failure.
On 07/18/2014 05:23 PM, Dan Mcqueen wrote:
Hi rt-users
I am trying to install rt 4.2.6 and I am getting this error when I send
email to rt-mailgate.
I am using
centos 6.5
postfix
rt 4.2.6 with smime enabled
https
Can anyone help point me to what might be wrong?
That was the tip I needed, I had a trailing /rt/, which was incorrect, on
on my mailgate --url
Thanks!
On Fri, Jul 18, 2014 at 2:37 PM, Alex Vandiver ale...@bestpractical.com
wrote:
On 07/18/2014 05:23 PM, Dan Mcqueen wrote:
Hi rt-users
I am trying to install rt 4.2.6 and I am
Thanks for your time Peter.
Currently in the received mail i need to add the username which took
action over the ticket, nothing more
On 7/8/2014 3:26 AM, Alex Peters wrote:
From your description, it seems that the managers are currently
watching the ticket as AdminCCs.
Can you please give
A list of useful template snippets can be found on the wiki:
http://requesttracker.wikia.com/wiki/TemplateSnippets#People
It seems that you would get the desired information by adding this to the
appropriate templates:
{ $Transaction-CreatorObj-Name }
In your case, you probably want to add
Thanks Alex - it worked.
ps: excuse my previous mail since i mistaken your name
BR
On 7/8/2014 2:01 PM, Alex Peters wrote:
A list of useful template snippets can be found on the wiki:
http://requesttracker.wikia.com/wiki/TemplateSnippets#People
It seems that you would get the desired
hey guys,
i have again (probably) silly question. Is there any chance when using
RT web interface, when replying the rt-mailgate to attach the username
who did the action. Now, when replying to a ticket, via email we receive
only the actual information written by user plus link to the ticket. I'm
From your description, it seems that the managers are currently watching
the ticket as AdminCCs.
Can you please give an example of the information that you need in the
emails that are sent to the managers?
The emails already show the name and email address of the person adding
correspondence to
Hello,
I have following problem:
root@rt:~# rt-mailgate --debug --action correspond --url=
https://localhost/rt --queue General /root/test.msg
/usr/bin/rt-mailgate: temp file is '/tmp/4iP43YcvGf/qapxKbbAkW'
/usr/bin/rt-mailgate: connecting to
https://localhost/rt/REST/1.0/NoAuth/mail-gateway
An
Hello,
I have following problem:
root@rt:~# rt-mailgate --debug --action correspond --url=
https://localhost/rt --queue General /root/test.msg
/usr/bin/rt-mailgate: temp file is '/tmp/4iP43YcvGf/qapxKbbAkW'
/usr/bin/rt-mailgate: connecting to
https://localhost/rt/REST/1.0/NoAuth/mail-gateway
An
Replace in the URL parameter to rt-mailgate localhost with the FQDN.
Chris
Am 30.06.2014 11:17, schrieb DD DD:
Hello,
I have following problem:
root@rt:~# rt-mailgate --debug --action correspond
--url=https://localhost/rt --queue General /root/test.msg
/usr/bin/rt-mailgate: temp file
Please keep replies to the list.
Which RT version are you using?
Because your apache making a redirect and rt-mailgate following
redirects only in RT 4.2.4 and newer.
Chris
Am 30.06.2014 12:09, schrieb DD DD:
root@rt:~# wget https://HIDDEN/rt
--2014-06-30 12:04:42-- https://HIDDEN/rt
on old and new server there runs 4.0.7
new machine:
root@rt:~# wget https://127.0.0.1/rt
--2014-06-30 12:24:15-- https://127.0.0.1/rt
Connecting to 127.0.0.1:443... connected.
The certificate's owner does not match hostname `127.0.0.1'
root@rt:~# wget https://localhost/rt
--2014-06-30
On Sun, May 25, 2014 at 08:02:24PM -0700, Jeevan wrote:
When I first started working on Request Tracker, the concept was simple
cause I was working in a local environment where a mail message would be
sent directly to a predefined RT queue e.g. que...@rt.example.com or just
queue1. However,
Hi there,
When I first started working on Request Tracker, the concept was simple
cause I was working in a local environment where a mail message would be
sent directly to a predefined RT queue e.g. que...@rt.example.com or just
queue1. However, now I want to do something like this in which a
On Fri, Feb 14, 2014 at 09:14:08AM +0200, Yavor Marinov wrote:
Additional information won't hurt anyway. The only regexp which is
configured in
RT_Siteconfig.pm is
Set($RTAddressRegexp , '^r...@domain.com$');
What should be Regexp in order to detect the [] anywhere in the
I've manage to solve this with RT-Interface-Email-Filter-CheckMessageId
http://cpan.poldownload.com/modules/by-module/RT/NANARDON/RT-Interface-Email-Filter-CheckMessageId-0.2.tar.gz
extension.
On 02/13/2014 12:29 PM, Yavor Marinov wrote:
Hello,
i have the following configs for getmail:
On Thu, Feb 13, 2014 at 04:47:42PM +0200, Yavor Marinov wrote:
I've manage to solve this with [1]RT-Interface-Email-Filter-CheckMessageId
extension.
I'm glad that this fixed your issues, however for the archives, RT
works just fine and has for years with the subject tag (the [XX]
part)
Additional information won't hurt anyway. The only regexp which is
configured in RT_Siteconfig.pm is
Set($RTAddressRegexp , '^r...@domain.com$');
What should be Regexp in order to detect the [] anywhere in the
Subject field
---
Find out about our new Cloud service - Cloudware.bg
Hi Folks
We have just installed RT4.0.13 in our environment. Our foremost
requirement is ticket creation via email. In our setup we already have
postfix running on separate server.
On RT we are having exim which is acting as relay server and using
postfix mail server as master.
Now I want to
On 07/23/2013 04:53 AM, Rajat toshniwal wrote:
Hi Folks
We have just installed RT4.0.13 in our environment. Our foremost
requirement is ticket creation via email. In our setup we already have
postfix running on separate server.
On RT we are having exim which is acting as relay server and using
This happens when email has encoding defined, but it's not correct value.
Newer versions convert such cases to application/octet-stream. Change is
in 4.0.9rc1.
On Fri, Apr 5, 2013 at 6:00 AM, charlyc...@yahoo.com.ar
charlyc...@yahoo.com.ar wrote:
Hi,
I've been running rt-mailgate to
.
De: Ruslan Zakirov r...@bestpractical.com
Para: charlyc...@yahoo.com.ar charlyc...@yahoo.com.ar
CC: rt-users@lists.bestpractical.com rt-users@lists.bestpractical.com
Enviado: viernes, 5 de abril de 2013 5:04
Asunto: Re: [rt-users] rt-mailgate Unknown encoding 'charset=utf-8'
This happens when
@lists.bestpractical.com
*Enviado:* viernes, 5 de abril de 2013 5:04
*Asunto:* Re: [rt-users] rt-mailgate Unknown encoding 'charset=utf-8'
This happens when email has encoding defined, but it's not correct value.
Newer versions convert such cases to application/octet-stream. Change is
in 4.0.9rc1.
On Fri
Hi,
I've been running rt-mailgate to download my emails and today I started getting
this error message on the fetchmail log.
RT server error.
The RT server which handled your email did not behave as expected. It
said:
Unknown encoding 'charset=utf-8' at /data/rt4/sbin/../lib/RT/I18N.pm line
On 02/12/2013 08:00 PM, Thomas Klump wrote:
I’m working on implementing RT with OpenID. I started with a basic
installation of RT and I created some test tickets from within the webui
and via email. Everything worked great. I then started to implement
OpenID for authentication. I tried using the
On 02/13/2013 10:10 AM, Thomas Klump wrote:
Tim,
Thanks, adding a section to the virtualhost configuration for NoAuth having no
authentication worked like a charm. The webpage I found the solution on is:
http://requesttracker.wikia.com/wiki/WebExternalAuth
Thanks,
Thomas
It's usually a
-users] rt-mailgate error 302 with WebExternalAuth and Apache
OpenID module
On 02/12/2013 08:00 PM, Thomas Klump wrote:
I'm working on implementing RT with OpenID. I started with a basic
installation of RT and I created some test tickets from within the
webui and via email. Everything worked
I'm working on implementing RT with OpenID. I started with a basic installation
of RT and I created some test tickets from within the webui and via email.
Everything worked great. I then started to implement OpenID for authentication.
I tried using the RT OpenID plugin but I was never able to
I'm working on implementing RT with OpenID. I started with a basic installation
of RT and I created some test tickets from within the webui and via email.
After everything was working I started to implement OpenID for authentication.
I tried using the RT OpenID plugin but I was never able to
Hi,
I am switched from using LDAP to CAS for authentication, and now because it
redirects to the login screen, mailgate isn't working. I was wondering if
anyone had a workaround or solution to this?
Thanks,
Tom
Hi Tom,
Sounds like you may missing a Location section from your apache config.
Something like...
Location /REST/1.0/NoAuth
Order Allow,Deny
Allow from 127.0.0.1
/Location
Best Regards
Martin Wheldon
On 2013-01-16 16:38, Thomas Misilo wrote:
Hi,
I am switched from using LDAP to
Hi,
I would like to known if they are any solution to have a fallback solution
about rt-mailgate with procmail.
Actually I've something like in the .procmailrc
#
# Spam
#
:0: # spam
* ^X-Spam-Status: YES*
!
I think what you want to do is add a rule like this right below your
pipe to rt-mailgate rule. This tells procmail to trap the error from the
failed rt-mailgate delivery and retry later:
# If RT delivery failed, return it to the mail queue, the MTA
# will retry delivery later (75 is the value
On 12/04/2012 01:12 AM, Albert Shih wrote:
:0:
|/usr/bin/rt-mailgate --queue Support --action correspond --url
https://ULR_OF_RT
the problem is sometime the RT website is down (power failure) and in that
case the mail is lost.
How can I tell rt-mailgate (or procmail) to
Hiya folks,
Since a few days ago I'm having the following error:
rt-mailgate: connecting to http://xxx.xxx.xxx.xxx//REST/1.0/NoAuth/mail-gateway
An Error Occurred = 500 read timeout
/path/to/my/rt/bin/rt-mailgate: undefined server error
This is happening since I did migrate
On 12/03/2012 01:27 AM, Carlos Fuentes Bermejo wrote:
Hiya folks,
Since a few days ago I'm having the following error:
rt-mailgate: connecting to
http://xxx.xxx.xxx.xxx//REST/1.0/NoAuth/mail-gateway An Error
Occurred = 500 read timeout
/path/to/my/rt/bin/rt-mailgate:
Hi Thomas,
Nothing on the web server logs.
Cheers,
Carlos
El 03/12/2012, a las 19:53, Thomas Sibley escribió:
On 12/03/2012 01:27 AM, Carlos Fuentes Bermejo wrote:
Hiya folks,
Since a few days ago I'm having the following error:
rt-mailgate: connecting to
Hello,
The rt-mailgate program acts differently between v 3.8.8 and v 4.0.6. The v
3.8.8 version works
fine using https, and even when I have v 4.0.6 running with the /etc/aliases
point to the v 3.8.8 version of rtmailgate, email
get sent to the queue. But the v 4.0.6 version fails with
On 21.8.2012 15:59, Ethier, Michael wrote:
Hello,
The rt-mailgate program acts differently between v 3.8.8 and v 4.0.6.
The v 3.8.8 version works
fine using https, and even when I have v 4.0.6 running with the
/etc/aliases point to the v 3.8.8 version of rtmailgate, email
get sent
, August 21, 2012 10:11 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate problem - certificate verify failure ?
On 21.8.2012 15:59, Ethier, Michael wrote:
Hello,
The rt-mailgate program acts differently between v 3.8.8 and v 4.0.6.
The v 3.8.8 version works
fine
On 21.8.2012 16:16, Ethier, Michael wrote:
Hi Martin,
Thanks for the suggestion but if I enable --no-ssl I will be creating a
security
vulnerability no ?
Thanks,
Mike
Hi,
that's for sure. This was a suggestion for a development machine (the
name testrt.rc.fas.harvard.edu suggest that
On 08/21/2012 08:03 AM, Martin Drasar wrote:
If you want to avoid this step then you have to have a valid certificate
for testrt.rc.fas.harvard.edu signed by a certificate authority that is
in the ca bundle you are passing to rt-mailgate.
Martin's referring to the --ca-file argument you can
...@lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Wednesday, March 14, 2012 4:49 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate 302 Error. No, not Plack.
On Wed, Mar 14, 2012 at 09:43:47PM +, Jourdan Perla wrote:
An Error Occurred
=
302 Found
On 15 Mar 2012, at 17:44, Jourdan Perla wrote:
Using 3.8 since there are no RT4 packages for Ubuntu 10.4 LTS. Attempts to
manually install RT4 on Lucid would result in a whole 'nother ticket.
I'm running 4.0.5 on Lucid. Wasn't really a problem; I just don't use the
packaged version and let
Please - keep list replies on the list.
Sorry, will do.
Thought I had this licked, but now as I build a *clean* production image, I'm
running into the same error again..
$ cat mbox | /usr/bin/rt-mailgate --queue general --action correspond --url
http://rt.myserver.com /rt -debug
On Wed, Mar 14, 2012 at 09:43:47PM +, Jourdan Perla wrote:
An Error Occurred
=
302 Found
/usr/bin/rt-mailgate: undefined server error
This is Apache issuing a 302 before it gets to RT
Grep all my logs for what happens at the same time and
apache2/access.log:
Please - keep list replies on the list.
On Fri, Feb 24, 2012 at 10:24:52PM +, Jourdan Perla wrote:
Fixed it. I was missing an Auth exclusion for the /REST/1.0/NoAuth
directory
As for the RT logs, can't find them. And can't find out where they're
configured.
Search in RT_Config.pm for
Install of RT3.8 on Ubuntu 10.4 LTS.
I'm getting that pesky 302 Found error as I'm trying to push mail into my
queues using rt-mailqueue.
I've done the usual Googling and wiki hunts, and I've run out of options.
- Aliases are working fine, it's a rt-mailgate error.
- Plack is up to date
On Fri, Feb 24, 2012 at 08:54:00PM +, Jourdan Perla wrote:
Install of RT3.8 on Ubuntu 10.4 LTS.
I'm getting that pesky 302 Found error as I'm trying to push mail into
my queues using
rt-mailqueue.
I've done the usual Googling and wiki hunts, and I've run out of options.
-
Hi
We let Apache authenticate under SSL but had problems with rt-mailgate.
Our work around was to configure httpd.conf as below so that rt-mailgate
could operate under port 80. No doubt there are better ways, but this is
working for us.
### Force SSL for RT except the NoAuth and REST
On Mon, Jan 23, 2012 at 2:38 PM, Allen allen+rtl...@crystalfontz.comwrote:
Landon wrote:
We simply use mod_rewrite to redirect everyone *except* the server itself
to https. This way when rt-mailgate calls http://rt.ourdomain/com it is
not forced to use https while everyone else is.
Landon
On 01/20/2012 02:38 PM, Robert Nesius wrote:
I figured out a work around for this issue. I was suspicious that
LWP::UserAgent could not reach the cert for the CA that signed the cert
being presented by the web server. I learned there are some environment
variables that I can leverage to
I tried several things to get the cert path into the environment for LWP,
none worked:
1. Adding this to /etc/fetchmailrc
mda env PERL_LWP_SSL_CA_PATH=/etc/ssl/certs /usr/bin/rt-mailgate-4 ...
does NOT work to get the right cert to LWP through the environment:
root@web0:/etc# service
On 9 January 2012 10:34, Robert Nesius nes...@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
We simply use mod_rewrite to redirect everyone *except* the server itself
to https. This way when rt-mailgate calls http://rt.ourdomain/com it is
not forced to use https while everyone else is.
Thanks. That is an easy, maintainable solution until the next version of
rt-mailgate that will let
I figured out a work around for this issue. I was suspicious that
LWP::UserAgent could not reach the cert for the CA that signed the cert
being presented by the web server. I learned there are some environment
variables that I can leverage to influence where LWP::UserAgent looks even
though it's
Hello,
I verified my certificates, openssl says they're OK.
--Mark
Sorry, left out the -CApath flag, and this is just for illustration:
root@xxx:/var/www/servers# openssl verify -CApath /etc/ssl/certs/
/usr/share/ca-certificates/mozilla/DST_ACES_CA_X6.crt
Make sure you have Crypt::SSLeay, Net::SSL, LWP::UserAgent,
LWP::Protocol::https, and Mozilla::CA installed.
We didn't have Mozilla::CA Crypt::SSLeay installed, but still didn't
help:
rt ls -t 59
Query:Status!='resolved' and Status!='rejected'
rt: Server error: Can't connect to
I have rt4 installed manually in /opt/rt4 but when I ran dpkg I got:
www:/etc/ssl/certs# dpkg --list | grep reques
ii libapache2-mod-apreq22.08-5+b1 generic
Apache request library - Apache modu
ii libapache2-request-perl 2.08-5+b1 generic
pc request-tracker3.6 3.6.7-5+lenny6 Extensible trouble-ticket
tracking system
pc rt3.6-db-postgresql 3.6.7-5+lenny6 PostgreSQL database backend
for request-trac
p in first column means already marked for purging.
c in second column means configuration files from those are still present
Hello,
I've had the same issues and am only now getting around to figuring it
out. Everything works fine in browser, but not thru rt-mailgate.
Every other service that uses the SSL keys are working; puzzled.
If I find something worthy of note, I'll post it.
--Mark
Thanks for the suggestions
...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Mark Story
Sent: Wednesday, January 11, 2012 1:04 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate
Hello,
I've had the same issues and am only now getting around to figuring it out.
Everything
...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Izz Abdullah
Sent: Wednesday, January 11, 2012 1:14 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate
Have you guys checked to ensure the linux box itself, I presume it is linux
On 01/11/2012 02:04 PM, Mark Story wrote:
I've had the same issues and am only now getting around to figuring it
out. Everything works fine in browser, but not thru rt-mailgate.
Every other service that uses the SSL keys are working; puzzled.
We have a branch (not yet merged) that improves
On Tue, Jan 10, 2012 at 1:05 PM, Robert Nesius nes...@gmail.com wrote:
500 Can't connect to
request.domain.com:443 (certificate
verify failed)
/opt/rt4/bin/rt-mailgate: undefined server error
Yes, I got the same problem Monday after installing an Extended
Validation SSL certificate on the
On Wed, Jan 11, 2012 at 11:22 AM, Izz Abdullah izz.abdul...@hibbett.com wrote:
root@xxx:/var/www/servers# openssl verify -CApath /etc/ssl/certs/
/usr/share/ca-certificates/mozilla/DST_ACES_CA_X6.crt
/usr/share/ca-certificates/mozilla/DST_ACES_CA_X6.crt: OK
Yes, that is the same output I get
://MyRT
)
My $0.02 worth as well. :)
-Original Message-
From: rt-users-boun...@lists.bestpractical.com [mailto:
rt-users-boun...@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
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
)
My $0.02 worth as well. :)
-Original Message-
From: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@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
Hello,
Some users send an email to email address of the queue to open tickets,
but we are getting this error on user creation, since we are using
ExternalAuth (RT4.0.2 + ExternalAuth 0.09):
Sat Oct 29 12:37:42 2011] [crit]: User creation failed in mailgateway:
Name in use
1 - 100 of 201 matches
Mail list logo
