<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [rt-users] reply with attachment</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Thanks, that's the recommendation I was looking for - the files don't change much, but they're just unique to each queue.<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jerrad Pierce <jpierce@cambridgeenergyalliance.org><BR>
To: Mchugh, Sean<BR>
CC: rt-users@lists.bestpractical.com <rt-users@lists.bestpractical.com><BR>
Sent: Sat Mar 14 18:48:08 2009<BR>
Subject: Re: [rt-users] reply with attachment<BR>
<BR>
On Sat, Mar 14, 2009 at 18:29, Mchugh, Sean <SMchugh@grey.com> wrote:<BR>
> Definitely a valid approach which we use internally. However, we are<BR>
> dealing with a few external entities on the other end that have highly<BR>
> restricted internet access and arranging for that access is not always<BR>
> timely.<BR>
Well then, assuming http file service is also out, by "a variety of files" do<BR>
you mean "many" or that they change? (Although if they change you're<BR>
going to have to have a complicated scrip to handle the responses). If it's<BR>
just to attach many, I'd precompose a MIME message with attachments,<BR>
and use that as my template. A little work up front, but it also saves the<BR>
server from repeatedly encoding the same content.<BR>
<BR>
--<BR>
Cambridge Energy Alliance: Save money. Save the planet.<BR>
</FONT>
</P>
</BODY>
</HTML>