On 5/1/15 7:15 AM, II GG wrote:
After importing the MySQL database data from the old server I used the
rt-setup-database script. This errors:
[1324] [Fri May 1 10:45:28 2015] [warning]: Resolver
RT::URI::fsck_com_rt could not parse fsck.com-rt://Vaioni/ticket/0,
maybe Organization config was ch
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 => IO
Alex Vandiver wrote:
> Which database? In your original mail, you said:
>
> > p5-DBD-mysql-4.031
> > [...]
> > postgresql-9.4.1
>
> Which database are you using?
PostgreSQL 9.4.1. And p5-DBD-postgresql-3.5.1 was missing in my list.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.
On Fri, 1 May 2015 10:01:02 +0200 m...@netbsd.org (Emmanuel Dreyfus)
wrote:
> In database, I have in both cases
Which database? In your original mail, you said:
> p5-DBD-mysql-4.031
> [...]
> postgresql-9.4.1
Which database are you using?
- Alex
Our goal is to create a Ticket in RT using VBA using the WinHttpRequest
object. We understand that there are 2 login pages involved with RT.
So, first we log into the first RT login page using using a "POST" request
and passing the username and password using the SetCredentials function of
the Wi
Hi
I liked the ancient 3.6.x look of RT, but it is not available in latest
releases. Is there a theme to bring it back?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
I have inherited a very old RT installation. I plan to upgrade from 3.8.8
to the latest RT 4.2.x version included with Debian stable.
I started with a full working installation of RT 4.2.8.
After importing the MySQL database data from the old server I used the
rt-setup-database script. This error
Emmanuel Dreyfus wrote:
> The generated HTML for creating and updating looks similar, hence I
> assume it is the server-side handling that differ.
In database, I have in both cases
contenttype: text/plain
contentencoding: quoted-printable
An attachment that displays correctly (added by updating
