[rt-users] Upgrade question
Hello, I currently have RT v4.0.7 installed on a Debian server (RT was installed from Debian repositories). For various reasons, I need to put RT onto a new server, and was going to stick with Debian, but instead of using RT from the repositories, I am planning on doing a source install (the repositories are not updated very often, and doing a source install will be easier to keep RT updated, IMO) I am wondering what the best way to go about this is. I am seeing two ways to do this: 1.) Install RT v4.0.7 on the new server, then import current configs and database. Once confirmed all is working properly, perform upgrade to v4.0.17. Or 2.) Install RT v4.0.17 on new server. Import configs and database from current 4.0.7 server. Jump to the database schema upgrade part of the upgrade instructions The second option would of course be easier and more efficient, as it eliminates a step, and it seems to me that it should work, since it seems the biggest part of upgrading RT seems to be the database schema part; I just don;t know if there might be any gotchas doing it that way. What would be the best/recommended way to go? Thanks! :-) -Alan RT Training in New York, October 8th and 9th: http://bestpractical.com/training
[rt-users] Question about the RT Mail Loop detection
Good day, on a local RT 4.0.7 installation (Debian Stable Packages) we have intermittent problems of RT detecting Mails as bounces (in general plausible). Unfortunately (Thanks to Exchange ;-)) we are having a bit of a problem in tracking it down. RT sends a simple RT thinks this message may be a bounce with a simple text attachment with the mail content. It is indeed plausible, that it is a bounce, as it is a mail sent by RT during ticket creation, which immediately (1 minute later via cron) gets back to RT. My problem here is that I am having great difficulty to narrow down, what exactly is happening here. Is there a way to get RT to give me the details of the bounced mail instead of only the content. Especially I would be interested in the full E-Mail Headers of the mail that came in and was detected as bounce. That would give me the chance to look into the question where it actually came from. Any help would be greatly appreciated. Best regards Torben Nehmer --- Torben Nehmer Diplom Informatiker (FH) Business System Developer CANCOM GmbH Messerschmittstr. 20 89343 Scheppach Germany Tel.: +49 8225 - 996-1118 Fax: +49 8225 - 996-41118 torben.neh...@cancom.demailto:torben.neh...@cancom.de www.cancom.dehttp://www.cancom.de/ CANCOM GmbH Sitz der Gesellschaft: Jettingen-Scheppach HRB 10653 Memmingen Geschäftsführer: Rudolf Hotter (Vorsitzender), Ralf Binder, Jacques Diaz, Frank Richter Diese E-Mail und alle mitgesendeten Dateien sind vertraulich und ausschließlich für den Gebrauch durch den Empfänger bestimmt! This e-mail and any files transmitted with it are confidential intended solely for the use of the addressee! RT Training in New York, October 8th and 9th: http://bestpractical.com/training
Re: [rt-users] Upgrade question
On Wed, Sep 11, 2013 at 11:51:52PM -0700, Alan Murrell wrote: source install (the repositories are not updated very often, and doing a source install will be easier to keep RT updated, IMO) 4.0.17 was actually added to unstable and testing at the end of August. The Debian packager for RT works quite hard. 2.) Install RT v4.0.17 on new server. Import configs and database from current 4.0.7 server. Jump to the database schema upgrade part of the upgrade instructions This is what I would do. It's a new server, so you even have plenty of opportunity to do a test upgrade first. -kevin pgpJOuyQ9HUbL.pgp Description: PGP signature -- RT Training in New York, October 8th and 9th: http://bestpractical.com/training
