Let’s say someone emails a pdf (or some other kind of binary)
file as an attachment to a ticket through rt. If i access the said
attachment trough the rt web interface it works fine. But if I get the
ticket through email (ticket is being forwarded to the AdminCC:
members) and then download the attachment to see it, a lot of times is
corrupted. FYI, we received a 889K PDF and the copy forwarded to
AdminCC is corrupted. However a 74K .pdf file we received just after
it works fine. I do not know if that is an issue with the attachment
size, but I thought by having the following set on RT_SiteConfig.pm,
Set($MaxAttachmentSize, 26214400);
Set($DropLongAttachments, undef);
Set($TruncateLongAttachments, undef);
I would not have a size issue here. The fact RT has no problems witht
he file if you access it using its web interface makes me think
something is going on in the routing that calls to have something mime
encoded. Which function should I be checking?
Let's say someone emails a pdf (or some other kind of binary)
file as an attachment to a ticket through rt. If i access the said
attachment trough the rt web interface it works fine. But if I get the
ticket through email (ticket is being forwarded to the AdminCC:
members) and then download the attachment to see it, a lot of times is
corrupted. FYI, we received a 889K PDF and the copy forwarded to
AdminCC is corrupted. However a 74K .pdf file we received just after
it works fine. I do not know if that is an issue with the attachment
size, but I thought by having the following set on RT_SiteConfig.pm,
Can you tell us a bit more about your RT? Often the Configuration →
Tools → System Information page is the easiest way to capture the
various bits of metadata we really need to help you figure out what’s
going on.
-j
Sorry for the delay; I was sidetracked in other non rt-related weidness.
Jesse Vincent wrote:
Let's say someone emails a pdf (or some other kind of binary)
file as an attachment to a ticket through rt. If i access the said
attachment trough the rt web interface it works fine. But if I get the
ticket through email (ticket is being forwarded to the AdminCC:
members) and then download the attachment to see it, a lot of times is
corrupted. FYI, we received a 889K PDF and the copy forwarded to
AdminCC is corrupted. However a 74K .pdf file we received just after
it works fine. I do not know if that is an issue with the attachment
size, but I thought by having the following set on RT_SiteConfig.pm,
Can you tell us a bit more about your RT? Often the Configuration →
Tools → System Information page is the easiest way to capture the
various bits of metadata we really need to help you figure out what’s
going on.
-j
I am sending the request info as an attachment. Incidentally, I am
running 3.6.7. I know right now it is rather old on the tooth (thanks
ubuntu!) but since I have not upgraded it since I installed it, I would
think that eliminates those kind of errors.
moo (10.3 KB)
Here is an update in my sending corrupt attachments issue:
o We got a 3MB test image and made a 600K and a 1.6G version of it. The
600K went fine but the 1.4G one got corrupted all the time.
o So, we wrote a wrapper to make a copy of the email that is being sent
from RT to the mail program we were using, ssmtp. The attachment at this
point was fine down to matching MD5 checksums. But the one sent by ssmtp
had issues.
Therefore, the problem is not on RT but on ssmtp. It seems it cannot
handle larger attachments for whatever reason. Maybe that is the price
for using so light weight program. I guess we now need to find a good
replacement for it today. I like postfix but think for this application
it is a bit of an overkill. But, I do not know what else to do. Suggestions?
At least now we know where the problem is. =)