Email attachment forwarding problem

It would appear that replying to a request via email with an
attachment results in the attachment being stored in RT but not
being sent to the requestor.

Can anyone suggest a reason? Is there any way to ensure that
attachments get forwarded to the requestor (and possibly CCs)?

Thanks,
Mike

Mike Hobbs
IPTV Technical Support Engineer
Tel +44 (0) 1223 518522
Pace Micro Technology, Cambridge, CB5 8PB

This email and any attachments hereto are strictly confidential and
intended solely for the addressee(s). If you are not an intended
addressee please notify the sender by return and delete the message.
You must not disclose, forward or copy this email or attachments to
any third party without the prior consent of the sender.

Mike Hobbs:

Can anyone suggest a reason?

Yes; basically, this is what happens by default.

Is there any way to ensure that
attachments get forwarded to the requestor (and possibly CCs)?

In the contrib section, there’s a NotifyWithAttachment scrip.

“Keeping UUCP running is starting to seem a lot like keeping a 130-year-old
man who smokes 4 packs a day on life support because he’s the last person
on Earth who knows how to do the cha-cha, but he won’t tell anyone.”

  • Ryan Tucker, in a.s.r

“MH” == Mike Hobbs michael.hobbs@pace.co.uk writes:

MH> It would appear that replying to a request via email with an
MH> attachment results in the attachment being stored in RT but not
MH> being sent to the requestor.

IMHO, this is the biggest POLA violation in RT. There is a scrip in
the contrib area that does the right thing. I personally think that
should be the default…

Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

You need to install the NotifyWithAttachment add-on available
in the contrib directory. Then, you need to change the
On Correspond… scrip to use this new action instead
of NotifyAllWatchers.

ttfn,
kevin-----Original Message-----
From: Mike Hobbs [mailto:michael.hobbs@pace.co.uk]
Sent: Wednesday, September 18, 2002 7:21 AM
To: rt-users@lists.fsck.com
Subject: [rt-users] Email attachment forwarding problem

It would appear that replying to a request via email with an
attachment results in the attachment being stored in RT but not
being sent to the requestor.

Can anyone suggest a reason? Is there any way to ensure that
attachments get forwarded to the requestor (and possibly CCs)?

Thanks,
Mike

Mike Hobbs
IPTV Technical Support Engineer
Tel +44 (0) 1223 518522
Pace Micro Technology, Cambridge, CB5 8PB

This email and any attachments hereto are strictly confidential and
intended solely for the addressee(s). If you are not an intended
addressee please notify the sender by return and delete the message.
You must not disclose, forward or copy this email or attachments to
any third party without the prior consent of the sender.

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

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

“MH” == Mike Hobbs michael.hobbs@pace.co.uk writes:

MH> It would appear that replying to a request via email with an
MH> attachment results in the attachment being stored in RT but not
MH> being sent to the requestor.

IMHO, this is the biggest POLA violation in RT. There is a scrip in
the contrib area that does the right thing. I personally think that
should be the default…

Augh, no! Our support and bugs queues regularly get mailed 15-20MB
logfiles, and there’s no way I want a dozen copies of those sitting in
my mail queue when they get mailed to the watchers.

What would be nice is a way to say “Send this particular attachment
along” – maybe only when it comes from the Owner of a ticket.

-Rich

Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | http://zapatopi.net/treeoctopus.html
rich@lafferty.ca -----------±----------------------------------------------