Duplicated attachments with RT 3.2.0 e-mail history feature?

In testing a fresh install of RT 3.2.0 (not an upgrade from a previous
version), I noted that the Attachments box for a ticket lists several
instances of each attachment – one by the user who uploaded it and
then several by RT_System.

I suspect this is because when RT records the mail it’s sending to
ticket watchers, the attachments are duplicated there.

Is this by design, or should the attachments for the “Outgoing email
recorded” transactions actually just refer to the original one? With
lots of attachments, this could end up taking quite a bit of space –
not to mention the cluttered Attachments box on the ticket display.

RT 3.2.0 looks great – thanks to everyone who contributed to it!

Thanks in advance,

–Bret

In testing a fresh install of RT 3.2.0 (not an upgrade from a previous
version), I noted that the Attachments box for a ticket lists several
instances of each attachment – one by the user who uploaded it and
then several by RT_System.

I suspect this is because when RT records the mail it’s sending to
ticket watchers, the attachments are duplicated there.

Interesting. When last I tested that, it didn’t record the attachments.
So, is the right thing for us to do to double-record the attachments as
they go out or to strip them from the outgoing message? I don’t htink
single-instance-store would be doable in the current world order.

Strip them! Maybe record an MD5 sum of the attachement that was
sent?

-ToddOn Thu, Jul 08, 2004 at 01:16:59PM -0400, Jesse Vincent wrote:

On Thu, Jul 08, 2004 at 12:51:56PM -0400, Bret Martin wrote:

In testing a fresh install of RT 3.2.0 (not an upgrade from a previous
version), I noted that the Attachments box for a ticket lists several
instances of each attachment – one by the user who uploaded it and
then several by RT_System.

I suspect this is because when RT records the mail it’s sending to
ticket watchers, the attachments are duplicated there.

Interesting. When last I tested that, it didn’t record the attachments.
So, is the right thing for us to do to double-record the attachments as
they go out or to strip them from the outgoing message? I don’t htink
single-instance-store would be doable in the current world order.


The rt-users Archives

Be sure to check out the RT wiki at http://wiki.bestpractical.com

Interesting. When last I tested that, it didn’t record the attachments.
So, is the right thing for us to do to double-record the attachments as
they go out or to strip them from the outgoing message? I don’t htink
single-instance-store would be doable in the current world order.

Strip them! Maybe record an MD5 sum of the attachement that was
sent?

I think stripping them from the stored copy of the outgoing message is
reasonable, and maybe just recording the attachment name somehow so you
know that it was included in the mail.

But no stripping from the actual sent message – that’s one of the
things I’m really happy is easier to handle in RT 3 vs. RT 2. It was
very confusing to (internal) users that attachments were recorded in the
system but not forwarded on to the ticket watchers.

–Bret