-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2007-Dec-07, at 09:20, Asrai khn wrote:
Any idea how to make rt to deliever emails have attachments
size upto 10mb?
It could be your mail server, not RT, that's imposing the limit
(actually, I think it's very likely). Have you tried just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We've just recently upgraded our RT install to version 3.6.5. It
looks like, under the new version, CC users and AdminCC users aren't
receiving email about ticket updates. Requesters *are* getting
email, so I know RT is capable of sending.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2007-Dec-06, at 13:21, Kenneth Crocker wrote:
Matt,
Navigate to CongifurationGlobalScrips and tell me what scrips
are listed. Then, navigate to CongifurationQueues(select the
queue we are discussing)Scrips and tell me what scrips are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2007-Dec-05, at 08:49, Kenneth Marshall wrote:
Craig and Kenn,
I am curious. What are your reasons for storing the session
information
in a file and not in the database?
I'm not sure about Craig and Kenn, but we're using local files for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2007-Nov-26, at 10:34, Nikita Gubenko wrote:
Problem fixed by
ALTER TABLE Attachments CHANGE Content Content LONGBLOB NULL;
Thanks, this fixed a similar issue on RT 3.6.5 that I've been seeing,
but hadn't had time to track down yet.
Worth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, so I've temporarily given up on trying to debug this. I'm
using the workaround of forcing RT back to using
Apache::Session::File, which has appeared to work.
For posterity, here's everything I know about the problem along with
some
