Issue with attachments

Everyone,

I am having an issue with attachments being corrupted when I

download them from RT 3. Someone submitted a patch a couple of months
ago but that did not fix the problem. when I try to open the attachment
up in MS Word it asks for a file importer and the text is all messed up.

Help,
Tom Vile
Lille Corp
7 Southwoods Blvd
Albany NY, 12211

Everyone,

I am having an issue with attachments being corrupted when I

download them from RT 3. Someone submitted a patch a couple of months
ago but that did not fix the problem. when I try to open the attachment
up in MS Word it asks for a file importer and the text is all messed up.

  1. What version of RT3?
  2. What OS, Database, web serving technology, etc?
  3. Which patch?
  4. Please, please, please, don’t include a 30k image with your four line
    email message.
    Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

RT 3.0.4
Redhat 9
Mysql 4
Apache 2.0.40-21.5

Try upgrading to RT 3.0.7, or better yet, the release canddiate for
3.0.8.

There was a patch someone posted for the Attachment_Overlay.pm it had to
do with encoding issues.

Everyone,

I am having an issue with attachments being corrupted when I

download them from RT 3. Someone submitted a patch a couple of months
ago but that did not fix the problem. when I try to open the attachment
up in MS Word it asks for a file importer and the text is all messed up.

  1. What version of RT3?
  2. What OS, Database, web serving technology, etc?
  3. Which patch?
  4. Please, please, please, don’t include a 30k image with your four line
    email message.


Tom Vile tom.vile@lillecorp.com
Lille Corp

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

I have custom modifications to the system and don’t want to upgrade
yet. Has anyone heard of this problem?On Fri, 2003-12-19 at 16:52, Jesse Vincent wrote:

On Fri, Dec 19, 2003 at 04:47:40PM -0500, Tom Vile wrote:

RT 3.0.4
Redhat 9
Mysql 4
Apache 2.0.40-21.5

Try upgrading to RT 3.0.7, or better yet, the release canddiate for
3.0.8.

There was a patch someone posted for the Attachment_Overlay.pm it had to
do with encoding issues.

On Fri, 2003-12-19 at 16:38, Jesse Vincent wrote:

On Fri, Dec 19, 2003 at 04:34:19PM -0500, Tom Vile wrote:

Everyone,

I am having an issue with attachments being corrupted when I

download them from RT 3. Someone submitted a patch a couple of months
ago but that did not fix the problem. when I try to open the attachment
up in MS Word it asks for a file importer and the text is all messed up.

  1. What version of RT3?
  2. What OS, Database, web serving technology, etc?
  3. Which patch?
  4. Please, please, please, don’t include a 30k image with your four line
    email message.


Tom Vile tom.vile@lillecorp.com
Lille Corp

Tom Vile tom.vile@lillecorp.com
Lille Corp

I have custom modifications to the system and don’t want to upgrade
yet. Has anyone heard of this problem?

I’m currently experiencing this as well. Have seen some list traffic to
indicate that it’s a fairly widespread problem. I’m suspicious that
something in Redhat 9 might be behind this one as well - if anyone out there
has run into this, please provide system specs.

Mine:

RT 3.0.6
Redhat 9
Mysql 3.23.56
Apache 2.0.40

When I figure out how to properly replicate the issue I’ll upgrade to the
latest and greatest RT and see if it still happens. We’ve got a ticket open
on it :stuck_out_tongue_winking_eye:

There was a patch someone posted for the Attachment_Overlay.pm it had
to do with encoding issues.

I did try this patch, as well, to no avail.

And a sample of the behaviour:

Same attachment, sent twice, first time broken, sent via email client:

content-type: application/octet-stream; name=“xox.doc”
content-disposition: attachment; filename=“xox.doc”
Content-Transfer-Encoding: base64
Content-Length: 26411

Second time sent through RT web interface, working:

Content-Type: application/msword; name=“xox.doc”
Content-Disposition: inline; filename=“xox.doc”
Content-Transfer-Encoding: base64
Content-Length: 23552

Thanks,
Mick Szucs mick@onramp.ca
Onramp Network Services Inc.

RT 3.0.6

Whoops. I lied. RT 3.0.5, that is.

Seasons greetings, eh?
Mick Szucs mick@onramp.ca
Onramp Network Services Inc.

RT 3.0.6

Whoops. I lied. RT 3.0.5, that is.

There’s no real point in being a martyr. Come up to a current version of
the software. This is an issue we know we’ve fixed.

Seasons greetings, eh?

Mick Szucs mick@onramp.ca
Onramp Network Services Inc.


rt-users mailing list
rt-users@lists.fsck.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

RT 3.0.6

Whoops. I lied. RT 3.0.5, that is.

There’s no real point in being a martyr. Come up to a current version of
the software. This is an issue we know we’ve fixed.

That’s right. Martyrdom is for Easter, not Christmas. :stuck_out_tongue:

Upgraded to 3.0.7_1. Not sure what the problem was, or how to replicate it,
so I can’t say for sure that it’s fixed, but your word is good enough for me.

Many thanks,
Mick Szucs mick@onramp.ca
Onramp Network Services Inc.

RT 3.0.6

Whoops. I lied. RT 3.0.5, that is.

There’s no real point in being a martyr. Come up to a current version of
the software. This is an issue we know we’ve fixed.

That’s right. Martyrdom is for Easter, not Christmas. :stuck_out_tongue:

Upgraded to 3.0.7_1. Not sure what the problem was, or how to replicate it,
so I can’t say for sure that it’s fixed, but your word is good enough for me.

FWIW, there have also been numerous improvements on the road to 3.0.8.
We’re running 3.0.8rc1 in production here and expect to push it out as
3.0.8 this week.

-jesse

Many thanks,

Mick Szucs mick@onramp.ca
Onramp Network Services Inc.


rt-users mailing list
rt-users@lists.fsck.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

FWIW, there have also been numerous improvements on the road to 3.0.8.
We’re running 3.0.8rc1 in production here and expect to push it out as
3.0.8 this week.

That’s great, Jesse, thanks. On your recommendation I’m now running 3.0.8rc1.

Question: any idea what these messages in syslog are all about?

Dec 29 13:31:17 rt3 RT: DBD::mysql::st execute failed: You have an error in
your SQL syntax near ‘NULL’ at line 1
at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 410.
(/opt/rt3/lib/RT.pm:247)
Dec 29 13:31:17 rt3 RT: RT::Handle=HASH(0x8c260ac) couldn’t execute the query
'SELECT * FROM Users WHERE Name ?
’ at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 417.
(/opt/rt3/lib/RT.pm:247)

They seem to occur when I logoff, don’t know if they’re occurring elsewhere as
well.

Running SearchBuilder 0.95.

Thanks,
Mick Szucs mick@onramp.ca
Onramp Network Services Inc.

FWIW, there have also been numerous improvements on the road to 3.0.8.
We’re running 3.0.8rc1 in production here and expect to push it out as
3.0.8 this week.

That’s great, Jesse, thanks. On your recommendation I’m now running 3.0.8rc1.

Question: any idea what these messages in syslog are all about?

We’ve seen it too. It’s not a big deal and shouldn’t hurt anything, but
haven’t tracked down the cause yet.

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

Mick Szucs wrote:> On December 29, 2003 12:55 pm, Jesse Vincent wrote:

FWIW, there have also been numerous improvements on the road to 3.0.8.
We’re running 3.0.8rc1 in production here and expect to push it out as
3.0.8 this week.

That’s great, Jesse, thanks. On your recommendation I’m now running 3.0.8rc1.

Question: any idea what these messages in syslog are all about?

Dec 29 13:31:17 rt3 RT: DBD::mysql::st execute failed: You have an error in
your SQL syntax near ‘NULL’ at line 1
at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 410.
(/opt/rt3/lib/RT.pm:247)
Dec 29 13:31:17 rt3 RT: RT::Handle=HASH(0x8c260ac) couldn’t execute the query
’SELECT * FROM Users WHERE Name ?
’ at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 417.
(/opt/rt3/lib/RT.pm:247)

I don’t know if the query above is verbatim, but it looks like it’s
missing an “=” in the WHERE clause (Name=?). That would certainly cause
a database error. :slight_smile:

Drew

Jesse Vincent wrote:

There’s no real point in being a martyr. Come up to a current version of
the software. This is an issue we know we’ve fixed.

I am currently using rt 3.0.7_01 and certain JPEGS are corrupted, they
seem to have extra bytes
added to them. I which version is this known to be fixed?

System
mod_perl-1.99_09-10custom
redhat 9
apache 2

I am currently using rt 3.0.7_01 and certain JPEGS are corrupted, they
seem to have extra bytes
added to them. I which version is this known to be fixed?

Can you try with 3.0.8rc1? And if that doesn’t fix it, can you verify
that the problem is still there with mod_perl1 or at least the current
beta of mod_perl2 (you’re 3 revs out of date)

System
mod_perl-1.99_09-10custom
redhat 9
apache 2


rt-users mailing list
rt-users@lists.fsck.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

Jesse Vincent wrote:

Can you try with 3.0.8rc1? And if that doesn’t fix it, can you verify
that the problem is still there with mod_perl1 or at least the current
beta of mod_perl2 (you’re 3 revs out of date)

Changing line 348 in ‘lib/RT/I18N.pm’ from
my $fallback = ‘iso-8859-1’;
to
my $fallback = ‘UTF-8’;

seems to have solved the problem. But I am still observing this.

Unfortunately, I cannot do an upgrade yet as the machine is in
production and
hence requires planing for that, amd more than that, the benifits of
upgrading sill need to
be looked at.

BTW, the corrupted attachments came from emails without
"content-transfer-ecoding"
header being set for the plain text part of the email…

Jesse Vincent wrote:

Can you try with 3.0.8rc1? And if that doesn’t fix it, can you verify
that the problem is still there with mod_perl1 or at least the current
beta of mod_perl2 (you’re 3 revs out of date)

I have just upgraded to rt 3.0.8 and the problem disappeared for a few
hours, but it
started again.

Jesse Vincent wrote:

Can you try with 3.0.8rc1? And if that doesn’t fix it, can you verify
that the problem is still there with mod_perl1 or at least the current
beta of mod_perl2 (you’re 3 revs out of date)

I have just upgraded to rt 3.0.8 and the problem disappeared for a few
hours, but it
started again.

I have same behaviour here. I am running 3.0.9pre1 and after new
install it seems ok for a while, but then it again starts double
encoding messages and corrupting attachments.

I am running Debian unstable (because of perl 5.8.2), maybe it is some
issue in mod_perl?

O.
Ondřej Surý - technický ředitel SERVERY.CZ
Globe Internet, s.r.o. - http://globe.cz
Pláničkova 1, 162 00 Praha 6 - http://mapa.globe.cz
Tel.: +420 2 35365000 - info@servery.cz

Jesse Vincent wrote:

Can you try with 3.0.8rc1? And if that doesn’t fix it, can you verify
that the problem is still there with mod_perl1 or at least the current
beta of mod_perl2 (you’re 3 revs out of date)

I have just upgraded to rt 3.0.8 and the problem disappeared for a few
hours, but it
started again.

I have same behaviour here. I am running 3.0.9pre1 and after new
install it seems ok for a while, but then it again starts double
encoding messages and corrupting attachments.

Same here (double encoding), but with 3.0.8rc1. After I restart apache, the
problem goes away for some hours.

I am running Debian unstable (because of perl 5.8.2), maybe it is some
issue in mod_perl?

FreeBSD 4.8 RELEASE, Apache 1.3.27, mod_perl-1.27, Perl 5.8.0. One thing that
is not compliant with the recommended setup is mod_perl which is compiled as
a DSO, not statically.

O.

cheers
aurel