Re: [rt-users] Sending attachment via comment not coming back
-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 sending a large attachment through your regular email client to the same person? Matt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFHWWpfmFeRJ0tjIxERAoYQAKCN0P8w84Y8ofbr/1rBNkof4OQnDQCdHuyv s6ToJrakE86l8b79+FNMm3Q= =MRT3 -END PGP SIGNATURE- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. 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 not generating email for CCs/AdminCCs
-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. According to my mail logs, there isn't even an attempt at sending messages to CC/AdminCC users. I've gone through the new RT_Config.pm and don't see any configuration options that directly relate to this. I'd considered that the $RedistributeAutoGeneratedMessages setting might affect this, but the AdminCCs and CCs being added are all manually created RT users with privileges. Do we just have the wrong expectation for how RT should be behaving here? I've done a bit of googling around for this, but didn't have much luck. Does this sound familiar to anyone? My (slightly sanitized) RT_SiteConfig.pm is included below. My appreciation for any suggestions. Matt Set($rtname, 'Foo'); Set($Organization, Foo); Set($Timezone, 'America/Toronto'); Set($OWnerEmail, '[EMAIL PROTECTED]'); Set($LogToFile, 'debug'); @LogToSyslogConf = (socket='inet'); Set($WebBaseURL, https://ticket.foo.ca;); Set($RedistributeAutoGeneratedMessages, 'privileged'); @ActiveStatus = qw( new open patched tested stalled ); Set($WebSessionClass , 'Apache::Session::File'); 1; -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFHWBbmmFeRJ0tjIxERAoySAKCM+Lh3iXrU5AbM3PNa7fKgZzLVIACfdG25 aoOd1ZGAUIbOh9t+QUDxQ2k= =c6aC -END PGP SIGNATURE- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. 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 not generating email for CCs/AdminCCs
-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 listed.
That will give us a good start on finding out what is going on.
Sorry.. to be more specific, I meant to say that I wouldn't know how
to debug malfunctioning scrips. Figuring out which ones are there
and *should* be doing things is pretty straight-forward.
Having gone to do that, It's starting to look to me like our problem
is a combination of two things:
1) Incorrect assumptions about the default behaviour of the CC field
2) Inconsistent use of CC and AdminCC by my users (and imprecise
problem reporting)
I've been a bit more direct in my questioning of users, and dug
around a bit more, and here's what I've found:
It seems that my interpretation of the default On
{Comment,Correspond} Notify Other Recipients as.. scrips was wrong
- -- I'd assumed Other Recipients would include CC'd users, and it
looks like it doesn't. Does that sound correct to you?
On top of that, my users seem to be trying to use CC and AdminCC
interchangeably, resulting in inconsistent behaviour with regard to
mail going out (which might be my fault since I wasn't even clear on
the difference).
I think the fix here might simply be writing up some simple process
for the developers/testers to follow.
Thanks for the pointers!
Matt
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (Darwin)
iD8DBQFHWEX2mFeRJ0tjIxERAitvAJ90TSHh+3zmpmgaU9yqNhs0D2jF4gCfZS28
d+FB9Z4eHju9WgmNZAG7wYY=
=YYGL
-END PGP SIGNATURE-
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31, we'll take
up to 20 percent off the price. This sale won't last long, so get in touch today.
Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745.
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] Recurring signin with 3.6.4
-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 session data because the database didn't work. I posted a few messages about that a couple of weeks ago, but didn't find any solutions to the problem. We were seeing something similar to Kenn.. basically, people would be logged out randomly as RT failed to get their current session cookie from the database. http://lists.bestpractical.com/pipermail/rt-users/2007-November/ 048776.html Matt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFHVusomFeRJ0tjIxERAhi/AJ9i/GqGsf7+O+ePqf3SQLt4si3PBACbBxMY 3ft9zjRzzM4mK/5yM4AWh3U= =l16U -END PGP SIGNATURE- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. 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] Re: corrupted attaches
-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 noting that this bug is in the schema.mysql file, which should probably be fixed for the next release. Cheers, Matt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFHSw7PmFeRJ0tjIxERAoKVAJ9ZB9CGV8wjgiZgNRJusEzP+6CUBgCeO9L8 N43kbc8py6wSeKdt4uPRdkw= =yG2w -END PGP SIGNATURE- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. 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] Unexpected session timeouts, RT 3.6.5
-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 environmental information, in case someone somewhere down the road runs into the same thing and is interested in debugging it further than I did. So... Using RT 3.6.5 built from Ports on FreeBSD 6.2-RELEASE-p8, built to use FastCGI. This is a single web server (no load balancing) with a single MySQL database on localhost. The problem: It appears that RT is randomly ignoring the session information returned to it by MySQL, and is initiating a new session, which forces the user back to the login screen. The problem can be reproduced by clicking around the interface until you are unexpectedly presented with the login screen. Watching HTTP headers: Under normal behaviour, the web browser sends the session cookie to the web server and it responds with no new cookie, and whatever content was requested. Periodically it unexpectedly responds with a new session cookie and the login page. Watching MySQL query logs: When RT unexpectedly presents the user with a login page, the query logs show that RT has done a lock, then select for the session ID, an unlock, as usual.. but then it inserts a new session row as if the query for the old session ID had failed. Manually running this query at this time succeeds and returns the session data. Watching RT error log: Set to debug level, the RT error log shows nothing when this happens. Watching web server error logs: The web server error logs also show nothing out of the ordinary when this occurs. I did some digging into the db-based session handling in order to drop in some overrides in ./rt3/local to add debugging output, but didn't get very far before trying the workaround mentioned at the beginning of this email. Since that workaround is sufficient for my uses here, I'm sticking with it for now and abandoning further debugging. However, if anyone (Jesse?) has some suggestions I'm happy to try them out and report back the results. Matt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFHRJ1AmFeRJ0tjIxERAqiQAJ4tDwIzGCEh1grFU06MtRHrxQj3dgCgi1/m g570Gs2e1MjP7OW7dxkUhrs= =Snks -END PGP SIGNATURE- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users SAVE THOUSANDS OF DOLLARS ON RT SUPPORT: If you sign up for a new RT support contract before December 31, we'll take up to 20 percent off the price. This sale won't last long, so get in touch today. Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745. 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
