Email / best practise for "correct" attachements

Post any question you may have in regards to GoAnywhere Director and let our talented support staff and other users assist you.

Email / best practise for "correct" attachements

Postby welchb » Thu Dec 05, 2013 6:09 am

Hi All,

This is not so much a 'technical' problem (or it may be not sure), we have a requirment within our organisation to send "attachements" via email.

In itself this is fine, however we need to ensure from an upstream system, the "attachement" -- that the correct thing get's sent to the correct receipent's,

e.g. if we have client A and client B, what's the best way to ensure that client A will only ever get the correct attachement and client B the same ?

I realise this comes down to "set-up" however is the some best practise someone could share, something like doing a "match" on attachement meta data vrs GoAnyWhere profiles set-up ?

Hope this is clear and hope someone can advise ?

Thanks
welchb
 
Posts: 2
Joined: Thu Nov 28, 2013 10:16 am

Re: Email / best practise for "correct" attachements

Postby Support_Rick » Thu Dec 05, 2013 8:37 am

There are many ways this can happen to "ensure" the validity of attachment to client. Not knowing the source of the attachments and how your business needs are addressed, it would be hard to actually define that here in a Forum.

I'll be glad to discuss this with you and give you some options if desired. Just send an email to Support@Linoma.com to my attention, then we can setup a time to go over the ways this could be done.
Rick Elliott
Sr. Product Specialist
(402) 944.4242
(800) 949-4696
Support_Rick
Support Specialist
 
Posts: 156
Joined: Tue Jul 17, 2012 2:12 pm

Re: Email / best practise for "correct" attachements

Postby welchb » Tue Dec 10, 2013 5:12 am

Thanks Rick,

I will email you as suggested and agree a date/time. Much appreciated.

regards,

Brian
welchb
 
Posts: 2
Joined: Thu Nov 28, 2013 10:16 am


Return to Community Forum

Who is online

Users browsing this forum: No registered users and 2 guests

cron