Re: Server Logic
- From: "Asher_N" <compguy666@xxxxxxxxxxx>
- Date: Sun, 01 Jan 2006 07:34:08 -0800
Solving those kinds of human problem is /not/ the ourpose of technology.
In your case, the solution is simple, get rid of the .pst files and go
MAPI. If the users refuse, an there are no real reasons other than 'we
are used to this way', than NO, it is not feasible AND it is not
technologies place to solve that kind of problem.
"=?Utf-8?B?UGhpbA==?=" <Phil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:D29F691C-E506-48DF-9B19-1BEA7BD6AB19@xxxxxxxxxxxxx:
> Is that not the purpose of technology? But that will take us out of
> the topic for this group. I will take your 'No' to mean that it is
> not technically possible to strip an attachment from an email, save it
> to a file and replace the attachment with a link all within the
> exhange server.
>
> Thanks for the responses.
>
> "Asher_N" wrote:
>
>> No.
>>
>> You aer trying to use technology to solve a human problem. It doesn't
>> work.
>>
>>
>> "=?Utf-8?B?UGhpbA==?=" <Phil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> news:3C11791C-9AE0-46B2-BA94-E7808A8C543A@xxxxxxxxxxxxx:
>>
>> > Thanks for the suggestion but my users seem to be married to thier
>> > pst files.
>> > I guess it masked some performance issues that the previous IT guy
>> > was
>> > unable to deal with. In a perfect world.... Anyways I am looking
>> > to ease the users down a better road, security blankets in hand.
>> > That is why I am looking for alternatives, is there a way to do
>> > what I am proposing?
>> >
>> > "Asher_N" wrote:
>> >
>> >> OK. If a link will do, I assume that these users are local. Then
>> >> it begs the question, why the .pst??
>> >>
>> >> Go MAPI. External access can be by OWA, VPN or RPC over HTTP.
>> >>
>> >> "=?Utf-8?B?UGhpbA==?=" <Phil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> news:E0323B82-F8B7-4FC4-8945-D95CF6AC8292@xxxxxxxxxxxxx:
>> >>
>> >> > The issues that I have are two fold, first the users are having
>> >> > their emails delivered to pst files that are grwoing rapidly and
>> >> > are corrupting. Secondly, the management has not yet decided
>> >> > that this is a problem so I am trying to avert serious
>> >> > client-side issues that I will have to deal with over and over
>> >> > again. Yes an educated user is the ideal solution but I don't
>> >> > have the political clout to make that happen, so I work beneath
>> >> > the radar.
>> >> >
>> >> > "Asher_N" wrote:
>> >> >
>> >> >> "=?Utf-8?B?UGhpbA==?=" <Phil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> >> >> in news:083A5E57-8BF0-449F-B10F-2EDDE9674C27@xxxxxxxxxxxxx:
>> >> >>
>> >> >> > I am using exchange 2003 and have users that send large
>> >> >> > attachments to a number of receipients within the
>> >> >> > organization.
>> >> >> > I would like to set up some server side logic to minimize
>> >> >> > the
>> >> >> > impact of sending these large attachments. The scheme that I
>> >> >> > have in mind is to have the users address thier email to a
>> >> >> > specialized mailbox, with the actual receipients in the cc
>> >> >> > field. The special mailbox would strip the attachment from
>> >> >> > the email and place it on our intranet then replace it with a
>> >> >> > link that the receipients can click on to view the
>> >> >> > attachment. All recipients would receive the link only. Can
>> >> >> > this be done? Any ideas about a how? any alternatives you can
>> >> >> > think of?
>> >> >> >
>> >> >>
>> >> >> The attachement will only reside in your store once. There is
>> >> >> no major impact with sending internal attachments. Or you could
>> >> >> try to educate the users to send links instead of files.
>> >> >>
>> >> >
>> >>
>> >>
>> >
>>
>>
>
.
- Follow-Ups:
- Re: Server Logic
- From: Phil
- Re: Server Logic
- Prev by Date: RE: Exchange 2003 integration with existing OS X server environmen
- Next by Date: Re: Design Question - Multiple domains/2003 Migration.
- Previous by thread: RE: Exchange 2003 integration with existing OS X server environmen
- Next by thread: Re: Server Logic
- Index(es):
Relevant Pages
|
