sword12
asked on
Email Attachment Management Tools
Hi all
i need advice to buy commercial tool which meet this requirements
1- take the received attachment files to shared file system (( local in our network not cloud ))
2- our end user know nothing about IT and we want the end user to feel like he do normal attachment procedure as he used too . so if he get link or html notification or text notification this for us not good . we need the user to see the type of attachment like pdf - JPG - doc - etc not URL link for the file location even if the file store in shared file system .
we have code two rule pro and this tool has feature called Strip and dump attachments i tested it but my manager said this not good for our end user
that i have to search for better tool
i checked online most of the tools use cloud like box
our target to reduce the exchange data base size but at the same time we don't want to put restriction for our end users
we have also another type of problem for sending big attachments files for external users out side our exchange organization
we also think about solution for this case
if you can give some me some ideas or advice i will be grateful
thanks
Sword
i need advice to buy commercial tool which meet this requirements
1- take the received attachment files to shared file system (( local in our network not cloud ))
2- our end user know nothing about IT and we want the end user to feel like he do normal attachment procedure as he used too . so if he get link or html notification or text notification this for us not good . we need the user to see the type of attachment like pdf - JPG - doc - etc not URL link for the file location even if the file store in shared file system .
we have code two rule pro and this tool has feature called Strip and dump attachments i tested it but my manager said this not good for our end user
that i have to search for better tool
i checked online most of the tools use cloud like box
our target to reduce the exchange data base size but at the same time we don't want to put restriction for our end users
we have also another type of problem for sending big attachments files for external users out side our exchange organization
we also think about solution for this case
if you can give some me some ideas or advice i will be grateful
thanks
Sword
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
sorry admin i want to divide the points between all but by mistake i give them to one expert
so if you can just give the all experts who answer this question exact amount of points
thanks again
sword
so if you can just give the all experts who answer this question exact amount of points
thanks again
sword
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for sword12's comment #a40934246
Assisted answer: 250 points for Qlemo's comment #a40926602
Assisted answer: 250 points for irweazelwallis's comment #a40928108
for the following reason:
i don't select my answer
Accepted answer: 0 points for sword12's comment #a40934246
Assisted answer: 250 points for Qlemo's comment #a40926602
Assisted answer: 250 points for irweazelwallis's comment #a40928108
for the following reason:
i don't select my answer
As its seems, Simon is correct to a certain extent, but omitted any proof or reference. Exchange 2013 supports stubbing, and that feature is used in conjunction with SharePoint. He is also correct about MS not recommending it, but that refers to using 3rd-party tools, as I read it. http://windowsitpro.com/blog/stubbing-ok-when-microsoft-does-it-exchange-2013-site-mailboxes discusses that point.
But we do not know whether you talk about Exchange 2013.
Anyway, your choice of "answers" seems to be arbitrary. Would you mind to explain?
But we do not know whether you talk about Exchange 2013.
Anyway, your choice of "answers" seems to be arbitrary. Would you mind to explain?
ASKER
Hi
Qlemo and irweazelwallis talk about that single instance storage does not exist in versions of exchange past 2010 and exist in 2013
and this is the main point for me for this i gave 250 for Qlemo and 250 for irweazelwallis
you are right if i have to be fair i have to give 500 to Qlemo because he is the first one gave the right answer but irweazelwallis also talk about the same topic but in different description
wish you good day
Hussam
Qlemo and irweazelwallis talk about that single instance storage does not exist in versions of exchange past 2010 and exist in 2013
and this is the main point for me for this i gave 250 for Qlemo and 250 for irweazelwallis
you are right if i have to be fair i have to give 500 to Qlemo because he is the first one gave the right answer but irweazelwallis also talk about the same topic but in different description
wish you good day
Hussam
To me that is a reasonable explanation. Thank you.
ASKER
thank you Qlemo for your understanding .
wish you good day
sword
wish you good day
sword
Microsoft don't recommend stubbing with Exchange. It causes problems with the Exchange database because it is confused.
The only options you have are the ones that you have outlined, where the attachment is removed completely.
As for sending large attachments, there are a lot of solutions for that around.
I haven't used this service, but this is the kind of thing you need:
http://www.dropsend.com/
Simon.