Re: [rt-users] rt-mailgate https - problem
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 12:28:22-- https://localhost/rt Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:443... connected. GnuTLS: A TLS warning alert has been received. Unable to establish SSL connection. root@rt:~# Why occurs a TLS warning? This comes not from the certificate (I also tried it with --no-check-certificate) 2014-06-30 12:21 GMT+02:00 Christian Loos : > 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 > > Resolving HIDDEN (HIDDEN)... HIDDEN > > Connecting to HIDDEN (HIDDEN)|HIDDEN|:443... connected. > > HTTP request sent, awaiting response... 301 Moved Permanently > > Location: https://HIDDEN/rt/ [following] > > --2014-06-30 12:04:42-- https://HIDDEN/rt/ > > Reusing existing connection to HIDDEN:443. > > HTTP request sent, awaiting response... 200 OK > > Length: unspecified [text/html] > > Saving to: `rt' > > > > [ > > <=> > > ] 4,064 --.-K/s in 0.01 > > > > 2014-06-30 12:04:43 (324 KB/s) - `rt' saved [4064] > > > > root@rt:~# > > > > It seems that Apache doesn't listen correct, but the hosts entry is > correct. > -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] rt-mailgate https - problem
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 > Resolving HIDDEN (HIDDEN)... HIDDEN > Connecting to HIDDEN (HIDDEN)|HIDDEN|:443... connected. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: https://HIDDEN/rt/ [following] > --2014-06-30 12:04:42-- https://HIDDEN/rt/ > Reusing existing connection to HIDDEN:443. > HTTP request sent, awaiting response... 200 OK > Length: unspecified [text/html] > Saving to: `rt' > > [ > <=> > > ] 4,064 --.-K/s in 0.01 > > 2014-06-30 12:04:43 (324 KB/s) - `rt' saved [4064] > > root@rt:~# > > It seems that Apache doesn't listen correct, but the hosts entry is correct. -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] rt-mailgate https - problem
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 is '/tmp/4iP43YcvGf/qapxKbbAkW' > /usr/bin/rt-mailgate: connecting to > https://localhost/rt/REST/1.0/NoAuth/mail-gateway > An Error Occurred > = > > 500 Can't connect to localhost:443 > > /usr/bin/rt-mailgate: undefined server error > root@rt:~# > > On my RT-server I can't checkin the tickets via https (https website via > browser works fine - certificte is ok) - via http it works fine! > > The Apache errorlog is empty. what does this error mean? > > Best Regards > > -- RT Training - Boston, September 9-10 http://bestpractical.com/training
[rt-users] rt-mailgate https - problem
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 Error Occurred = 500 Can't connect to localhost:443 /usr/bin/rt-mailgate: undefined server error root@rt:~# On my RT-server I can't checkin the tickets via https (https website via browser works fine - certificte is ok) - via http it works fine! The Apache errorlog is empty. what does this error mean? Best Regards -- RT Training - Boston, September 9-10 http://bestpractical.com/training
[rt-users] rt-mailgate https - problem
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 Error Occurred = 500 Can't connect to localhost:443 /usr/bin/rt-mailgate: undefined server error root@rt:~# On my RT-server I can't checkin the tickets via https (https website via browser works fine - certificte is ok) - via http it works fine! The Apache errorlog is empty. what does this error mean? Best Regards -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] rt-mailgate HTTPS
That little hint was what I needed , thanks Ruslan It was not intentional, trust me !!! Although everything was working using the GUI, I had numerous ownership and permission confusion throughout my install. The most glaring, carrying over the apache user in my rt group as it was on my original system and now running lighttpd as a different user name. Thanks to you all , for your help and patience. >>> "Ruslan Zakirov" <[EMAIL PROTECTED]> 2008-01-20 13:35 >>> This output suggest me that you've disabled mason for /NoAuth/... paph. Best regards, Ruslan. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] rt-mailgate HTTPS
This output suggest me that you've disabled mason for /NoAuth/... paph.
On Jan 20, 2008 8:06 PM, Roy Sowa <[EMAIL PROTECTED]> wrote:
> Thanks James,
>i have provided the info below, and while still stuggling, I have tried to
> set things up to use either HTTPS or HTTP
>Ihave that going now, and either one works fine with the GUI.
>Still cannot get an email through .
>That is why you will see one http alias in the list.
> So I am still working my way backwards...
>Thanks for your time
>If you need more info just ask ( also this is all new to me so I might not
> always know how to get what you ask for )
>
> Error from a bounce;
>
> RT server error.
>
> The RT server which handled your email did not behave as expected. It
> said:
>
> %# BEGIN BPS TAGGED BLOCK {{{
> <%flags>
> inherit => undef # inhibit UTF8 conversion done in /autohandler
>
> <%ARGS>
> $queue => 1
> $action => "correspond"
> $ticket => undef
>
> <%init>
> $m->comp('/Elements/Callback', _CallbackName => 'Pre', %ARGS);
> use RT::Interface::Email ();# It's an exporter, but we don't care
> $r->content_type('text/plain; charset=utf-8');
> $m->error_format('text');
> my ( $status, $error, $Ticket ) = RT::Interface::Email::Gateway( \%ARGS );
> if ( $status == 1 ) {
> $m->out('ok');
> if ( $Ticket->Id ) {
> $m->out( 'Ticket: ' . ($Ticket->Id || '') );
> $m->out( 'Queue: ' . ($Ticket->QueueObj->Name || '') );
> $m->out( 'Owner: ' . ($Ticket->OwnerObj->Name || '') );
> $m->out( 'Status: ' . ($Ticket->Status || '') );
> $m->out( 'Subject: ' . ($Ticket->Subject|| '') );
> $m->out(
> 'Requestor: ' . ($Ticket->Requestors->MemberEmailAddressesAsString ||
> '') );
> }
> }
> else {
> $RT::Logger->error( "Could not record email: " . $error );
> if ( $status == -75 ) {
> $m->out( "temporary failure - " . $error );
> }
> else {
> $m->out( 'not ok - ' . $error );
> }
> }
> $m->abort();
>
>
> "|/opt/rt3/bin/rt-mailgate --queue 'X' --action correspond --url
> https://XXX/";... Deferred: prog mailer (/bin/sh) exited with
> EX_TEMPFAIL
> Warning: message still undelivered after 4 hours
>
> +
> I saw that about the Crypt::SSLeay , so I installed
> Crypt-SSLeay-0.57
> stop started everything this did not help
>
> Aliases:
> Ticket_ELS: "|/opt/rt3/bin/rt-mailgate --queue 'NAME1' --action
> correspond --url https://xxx/";
> ELS_MSG:"|/opt/rt3/bin/rt-mailgate --queue 'Name2' --action
> correspond --url https:///";
> Ticket_EHIVE: "|/opt/rt3/bin/rt-mailgate --queue 'Name3' --action
> correspond --url http://xx/";
>
>
>
> >>> James Moseley <[EMAIL PROTECTED]> 2008-01-20 11:24 >>>
>
> First of all, what error messages were generated when you tried to send
> email to the RT address via bounced emails or from RT/mail logs?
>
> Secondly, rt-mailgate works just fine with HTTPS only installs - you've got
> to make sure that all your SSL related PERL modules have been installed,
> namely Crypt::SSLeay
>
> Lastly, what do your aliases look like?
>
>
> James Moseley
>
>
>
>
>
> "Roy Sowa"
> <[EMAIL PROTECTED]
> c.gc.ca> To
> Sent by:
> rt-users-bounces@ cc
> lists.bestpractic
> al.comSubject
>[rt-users] rt-mailgate HTTPS
>
> 01/20/2008 08:11
> AM
>
>
>
>
>
>
>
> I have seen list reference to email tickets not working with HTTPS
> configurations.
> Some indicate that a local http connection must exist for the rt-mailgate
> to work
>
> my current install is 3.6.5 using Lighttpd
>
> Everything is working fine using the GUI.
> but I cannot get emails to open tickets.
> I have verified that I can actually receive smtp mail sent to a user on the
> box.
>
> - I redirect my http to https
> - my /etc/aliases point to the htt
Re: [rt-users] rt-mailgate HTTPS
The aliases appear to be correct. Do you have the following required RT
Mailgate Perl modules installed:
MAILGATE dependencies:
Pod::Usage...found
HTML::TreeBuilder...found
Getopt::Long...found
HTML::FormatText...found
LWP::UserAgent...found
You've also forced Lighty to redirect port 80 requests over to 443. Why
don't you back out of that and try to get this working via port 80 first
and take SSL out of the mix?
Lastly, I remember from last week this was a new install and you were
switching from Apache to Lighty. I might be worth your while to get this
working with Apache and then move on to the Lighty. At least then you know
RT is fine and any errors that crop up are due to the Lighty config or
issues between RT and Lighty. You've introduced quite a few variables into
the equation...
James Moseley
"Roy Sowa"
<[EMAIL PROTECTED]
c.gc.ca> To
<[EMAIL PROTECTED]>
01/20/2008 11:06 cc
AM,
<[EMAIL PROTECTED]
al.com>
Subject
Re: [rt-users] rt-mailgate HTTPS
Thanks James,
i have provided the info below, and while still stuggling, I have tried
to set things up to use either HTTPS or HTTP
Ihave that going now, and either one works fine with the GUI.
Still cannot get an email through .
That is why you will see one http alias in the list.
So I am still working my way backwards...
Thanks for your time
If you need more info just ask ( also this is all new to me so I might
not always know how to get what you ask for )
Error from a bounce;
RT server error.
The RT server which handled your email did not behave as expected. It
said:
%# BEGIN BPS TAGGED BLOCK {{{
<%flags>
inherit => undef # inhibit UTF8 conversion done in /autohandler
<%ARGS>
$queue => 1
$action => "correspond"
$ticket => undef
<%init>
$m->comp('/Elements/Callback', _CallbackName => 'Pre', %ARGS);
use RT::Interface::Email ();# It's an exporter, but we don't care
$r->content_type('text/plain; charset=utf-8');
$m->error_format('text');
my ( $status, $error, $Ticket ) = RT::Interface::Email::Gateway( \%ARGS );
if ( $status == 1 ) {
$m->out('ok');
if ( $Ticket->Id ) {
$m->out( 'Ticket: ' . ($Ticket->Id || '') );
$m->out( 'Queue: ' . ($Ticket->QueueObj->Name || '') );
$m->out( 'Owner: ' . ($Ticket->OwnerObj->Name || '') );
$m->out( 'Status: ' . ($Ticket->Status || '') );
$m->out( 'Subject: ' . ($Ticket->Subject|| '') );
$m->out(
'Requestor: ' . ($Ticket->Requestors->MemberEmailAddressesAsString ||
'') );
}
}
else {
$RT::Logger->error( "Could not record email: " . $error );
if ( $status == -75 ) {
$m->out( "temporary failure - " . $error );
}
else {
$m->out( 'not ok - ' . $error );
}
}
$m->abort();
"|/opt/rt3/bin/rt-mailgate --queue 'X' --action correspond --url
https://XXX/";... Deferred: prog mailer (/bin/sh) exited with
EX_TEMPFAIL
Warning: message still undelivered after 4 hours
+
I saw that about the Crypt::SSLeay , so I installed
Crypt-SSLeay-0.57
stop started everything this did not help
Aliases:
Ticket_ELS: "|/opt/rt3/bin/rt-mailgate --queue 'NAME1' --action
correspond --url https://xxx/";
ELS_MSG:"|/opt/rt3/bin/rt-mailgate --queue 'Name2' --action
correspond --url https:///";
Ticket_EHIVE: "|/opt/rt3/bin/rt-mailgate --queue 'Name3' --action
correspond --url http://xx/";
>
Re: [rt-users] rt-mailgate HTTPS
more info... I saw this on the list ... same scenario ... I am moving to new hardware/versions and trying to do SSL so I tried this as well... my error: Connecting to http://x/REST/1.0/NoAuth/mail-gateway at /opt/rt3/bin/rt-mailgate line 102, <> line 1. ---from the list below ( not me) tried to move our RT installation to a new server (New: Debian Etch. Old: Debian Sarge). Copied the DB content and RT_SiteConfig. Everything looks fine, but the mailgate does not work. When testing rt-mailgate manually I get the error: cat mail | /usr/local/rt3/bin/rt-mailgate --debug --queue RT_Test --action correspond --url https://rt.ponton.local/ Connecting to https://rt.ponton.local//REST/1.0/NoAuth/mail-gateway at /usr/local/rt3/bin/rt-mailgate line 100, <> line 1. Segmentation fault The file mail contains: From: foo[at]bar.com To: rt[at]ponton Subject: Test Test ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] rt-mailgate HTTPS
Thanks James,
i have provided the info below, and while still stuggling, I have tried to
set things up to use either HTTPS or HTTP
Ihave that going now, and either one works fine with the GUI.
Still cannot get an email through .
That is why you will see one http alias in the list.
So I am still working my way backwards...
Thanks for your time
If you need more info just ask ( also this is all new to me so I might not
always know how to get what you ask for )
Error from a bounce;
RT server error.
The RT server which handled your email did not behave as expected. It
said:
%# BEGIN BPS TAGGED BLOCK {{{
<%flags>
inherit => undef # inhibit UTF8 conversion done in /autohandler
<%ARGS>
$queue => 1
$action => "correspond"
$ticket => undef
<%init>
$m->comp('/Elements/Callback', _CallbackName => 'Pre', %ARGS);
use RT::Interface::Email ();# It's an exporter, but we don't care
$r->content_type('text/plain; charset=utf-8');
$m->error_format('text');
my ( $status, $error, $Ticket ) = RT::Interface::Email::Gateway( \%ARGS );
if ( $status == 1 ) {
$m->out('ok');
if ( $Ticket->Id ) {
$m->out( 'Ticket: ' . ($Ticket->Id || '') );
$m->out( 'Queue: ' . ($Ticket->QueueObj->Name || '') );
$m->out( 'Owner: ' . ($Ticket->OwnerObj->Name || '') );
$m->out( 'Status: ' . ($Ticket->Status || '') );
$m->out( 'Subject: ' . ($Ticket->Subject|| '') );
$m->out(
'Requestor: ' . ($Ticket->Requestors->MemberEmailAddressesAsString || '')
);
}
}
else {
$RT::Logger->error( "Could not record email: " . $error );
if ( $status == -75 ) {
$m->out( "temporary failure - " . $error );
}
else {
$m->out( 'not ok - ' . $error );
}
}
$m->abort();
"|/opt/rt3/bin/rt-mailgate --queue 'X' --action correspond --url
https://XXX/";... Deferred: prog mailer (/bin/sh) exited with EX_TEMPFAIL
Warning: message still undelivered after 4 hours
+
I saw that about the Crypt::SSLeay , so I installed
Crypt-SSLeay-0.57
stop started everything this did not help
Aliases:
Ticket_ELS: "|/opt/rt3/bin/rt-mailgate --queue 'NAME1' --action correspond
--url https://xxx/";
ELS_MSG:"|/opt/rt3/bin/rt-mailgate --queue 'Name2' --action correspond
--url https:///";
Ticket_EHIVE: "|/opt/rt3/bin/rt-mailgate --queue 'Name3' --action correspond
--url http://xx/";
>>> James Moseley <[EMAIL PROTECTED]> 2008-01-20 11:24 >>>
First of all, what error messages were generated when you tried to send
email to the RT address via bounced emails or from RT/mail logs?
Secondly, rt-mailgate works just fine with HTTPS only installs - you've got
to make sure that all your SSL related PERL modules have been installed,
namely Crypt::SSLeay
Lastly, what do your aliases look like?
James Moseley
"Roy Sowa"
<[EMAIL PROTECTED]
c.gc.ca> To
Sent by:
rt-users-bounces@ cc
lists.bestpractic
al.comSubject
[rt-users] rt-mailgate HTTPS
01/20/2008 08:11
AM
I have seen list reference to email tickets not working with HTTPS
configurations.
Some indicate that a local http connection must exist for the rt-mailgate
to work
my current install is 3.6.5 using Lighttpd
Everything is working fine using the GUI.
but I cannot get emails to open tickets.
I have verified that I can actually receive smtp mail sent to a user on the
box.
- I redirect my http to https
- my /etc/aliases point to the https url
-my lighttpd.conf is below;
$SERVER["socket"] == "xx.xx.xx.xx:80" {
#server.document
Re: [rt-users] rt-mailgate HTTPS
First of all, what error messages were generated when you tried to send
email to the RT address via bounced emails or from RT/mail logs?
Secondly, rt-mailgate works just fine with HTTPS only installs - you've got
to make sure that all your SSL related PERL modules have been installed,
namely Crypt::SSLeay
Lastly, what do your aliases look like?
James Moseley
"Roy Sowa"
<[EMAIL PROTECTED]
c.gc.ca> To
Sent by:
rt-users-bounces@ cc
lists.bestpractic
al.comSubject
[rt-users] rt-mailgate HTTPS
01/20/2008 08:11
AM
I have seen list reference to email tickets not working with HTTPS
configurations.
Some indicate that a local http connection must exist for the rt-mailgate
to work
my current install is 3.6.5 using Lighttpd
Everything is working fine using the GUI.
but I cannot get emails to open tickets.
I have verified that I can actually receive smtp mail sent to a user on the
box.
- I redirect my http to https
- my /etc/aliases point to the https url
-my lighttpd.conf is below;
$SERVER["socket"] == "xx.xx.xx.xx:80" {
#server.document-root= "/"
server.document-root= "/opt/rt3/share/html/"
url.redirect = (
"^/(.*)" => "https://mysite/$1";
)
}
$SERVER["socket"] == "xx.xx.xx.xx:443" {
server.document-root= "/opt/rt3/share/html/"
url.rewrite = (
"^(.*)/Ticket/Attachment/(.*)" => "/$1/Ticket/Attachment/$2/"
)
fastcgi.map-extensions = ( ".css" => ".html", ".js" => ".html",
"/" => ".html" )
ssl.engine = "enable"
ssl.pemfile = "/etc/lighttpd/ssl/domain.com/server.pem"
$HTTP["useragent"] =~ ".*MSIE.*" {server.max-keep-alive-requests = 0 }
}
I do not know where best to try and resolve this ...( web config or
rt-mailgate )
I would be very grateful if someone could point me in the right direction
on what or where to go from here.
Thanks
Roy
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
[rt-users] rt-mailgate HTTPS
I have seen list reference to email tickets not working with HTTPS
configurations.
Some indicate that a local http connection must exist for the rt-mailgate to
work
my current install is 3.6.5 using Lighttpd
Everything is working fine using the GUI.
but I cannot get emails to open tickets.
I have verified that I can actually receive smtp mail sent to a user on the box.
- I redirect my http to https
- my /etc/aliases point to the https url
-my lighttpd.conf is below;
$SERVER["socket"] == "xx.xx.xx.xx:80" {
#server.document-root= "/"
server.document-root= "/opt/rt3/share/html/"
url.redirect = (
"^/(.*)" => "https://mysite/$1";
)
}
$SERVER["socket"] == "xx.xx.xx.xx:443" {
server.document-root= "/opt/rt3/share/html/"
url.rewrite = (
"^(.*)/Ticket/Attachment/(.*)" => "/$1/Ticket/Attachment/$2/"
)
fastcgi.map-extensions = ( ".css" => ".html", ".js" => ".html", "/" =>
".html" )
ssl.engine = "enable"
ssl.pemfile = "/etc/lighttpd/ssl/domain.com/server.pem"
$HTTP["useragent"] =~ ".*MSIE.*" {server.max-keep-alive-requests = 0 }
}
I do not know where best to try and resolve this ...( web config or
rt-mailgate )
I would be very grateful if someone could point me in the right direction on
what or where to go from here.
Thanks
Roy
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
