Tar.gz attachment strangeness -- rt-2-0-13

Hi, I cannot seem to figure this out, basically I can send almost any
attachment, except for certain tar.gz that contain text, well, sorta, I
can’t seem to correlate it to one thing (content type, filename,
extension, etc.) let me try to explain:

the alias is simple:

iij-project-admin: “|/var/www/rt2/bin/rt-mailgate --queue iij-project
–action correspond”, test

test is appended just to test the attachment problem, he does get all
the attachments.

in test’s mailbox I see:

Content-Disposition: attachment; filename=delpart.exe
Content-Type: application/x-ms-dos-executable; name=delpart.exe

the above makes it into RT

Content-Disposition: attachment; filename=putty.zip
Content-Type: application/zip; name=putty.zip

also makes it

Content-Disposition: attachment; filename=iij-patch.21828.tar.gz
Content-Type: application/x-gzip; name=iij-patch.21828.tar.gz

DOES NOT MAKE IT!!! it just isn’t there…

this file contains a tar file, which then contains a few text files and
some jar files…

I’ve changed the file name, zipped it, still nothing, ie:

Content-Disposition: attachment; filename=iij-patch-21828.tar.gz.zip
Content-Type: application/zip; name=iij-patch-21828.tar.gz.zip

still does not make it into RT!

Content-Disposition: attachment; filename=rsync.bat.tar.gz
Content-Type: application/x-gzip; name=rsync.bat.tar.gz

this DOES make it into RT, it’s another text file, that’s tarred and
gzipped…

If anyone could shed some light on this, it would be greatly appreciated

Thanks!

–Dave

Dave Young wrote:

Hi, I cannot seem to figure this out, basically I can send almost any
attachment, except for certain tar.gz that contain text, well, sorta, I
can’t seem to correlate it to one thing (content type, filename,
extension, etc.) let me try to explain:

How about size? Check your config.pm for $MaxAttachmentSize, as well
as mysql’s “max_allowed_packet” (assuming you do use mysql).

How about size? Check your config.pm for $MaxAttachmentSize, as well
as mysql’s “max_allowed_packet” (assuming you do use mysql).

It can’t possibly be that simple, look at all the work I put into
narrowing down the problem!!!

oh wait, it is that simple

I had:

[mysqldump]

set-variable = max_allowed_packet=16M

instead of:

[mysqld]

ummm, duh.

sorry list…

Thanks Phil!!!

–Dave

How about size? Check your config.pm for $MaxAttachmentSize, as well
as mysql’s “max_allowed_packet” (assuming you do use mysql).

It can’t possibly be that simple, look at all the work I put into
narrowing down the problem!!!

oh wait, it is that simple

I had:

[mysqldump]

set-variable = max_allowed_packet=16M

instead of:

[mysqld]

ummm, duh.

sorry list…

Thanks Phil!!!

–Dave