Great plan John, at least from where I sit ☺ Going to steal that next time I get in this bind.
From: [email protected] [mailto:[email protected]] On Behalf Of John Matteson Sent: Wednesday, March 15, 2017 2:59 PM To: [email protected] Subject: Re: [Exchange] RE: Shared Mailbox with Outside Agencies If what they are looking for is nothing more than access to a mailbox, you can create a mailbox with the address, then provide accounts to the various organizations that have READ ONLY Access to the mailbox via OWA. In ADUC for the accounts going to outside organizations, you set the allowed log in to NONE (blank out the workstation list). This prevents the users from accessing any systems on the internal network. They can access via OWA because they are not "logging in" only using AD for credentials authentication, not access. At least that is what I see as a possible solution from where I sit. John M. On Wed, Mar 15, 2017 at 9:54 AM, Kennedy, Jim <[email protected]<mailto:[email protected]>> wrote: So I get something similar to this from time to time. What my staff don’t know or think about is that a mailbox is an Active Directory account also. So they have access (though limited) to our ‘network’ as they call it. When I point that out, the pushback usually diminishes greatly. Auto copy to a Gmail mailbox? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Mayo, Bill Sent: Wednesday, March 15, 2017 9:51 AM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] RE: Shared Mailbox with Outside Agencies The comments are well-taken and appreciated. It is basically what I tell my staff—find out what they are trying to accomplish and determine the best way to do that within our standards. You are correct that this client is dictating the solution (to at least a certain extent). I won’t get into any extended details, but suffice it to say that this is a case where there will be pushback on that and it is a road well-traveled. I also used poor wording in my original query and follow-up in indicating how much I understand what they are after. While it is true that there may be a better way to do what they want than some kind of mailbox, we don’t currently have anything else in place that I could offer as a solution (we have several ways to accomplish if everyone was internal to our organization). The person is wanting to publish an email address to the public for a certain type of request. This person will actively monitor the mailbox, but wants others in and outside of our organization to be able to see the message without their intervention. They indicated that, in some cases, they would ask a particular entity (or entities) to just reference the mailbox for some specific message. They don’t want to forward the messages to the others. I mostly want to do a reality check that I am correct that there is not a good way to do this in Exchange. If not, is there some kind of free/cheap way to do this through a 3rd party email service. I did some research in that area, but all I found was sharing calendars or providing delegate-type access in the free realm. It does look like there are add-on services/software that do that for gMail (for example), but no names I have heard of before. Again, thanks for the feedback to everyone. If the above provides any fodder for a recommendation, I would appreciate it. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Wednesday, March 15, 2017 8:29 AM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] RE: Shared Mailbox with Outside Agencies What Michael and Andrew are alluding to is it sounds like you have been given a solution to their problem by them, as is often the case. Dig in, get details on the work flow and processes and what is going on. Once you understand the problem and goals you are far more qualified to suggest a tech solution than they are. For example you could just auto forward all the emails for this mailbox to an address they set up on their systems. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andrew S. Baker Sent: Tuesday, March 14, 2017 5:39 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Exchange] RE: Shared Mailbox with Outside Agencies I think you should get clarity on what they are trying to accomplish so that you can accurately assess the risks and determine the solutions. Regards, ASB http://XeeMe.com/AndrewBaker<http://xeeme.com/AndrewBaker> Providing Expert Technology Consulting Services for the SMB market… GPG: 860D 40A1 4DA5 3AE1 B052 8F9F 07A1 F9D6 A549 8842 Sent with Mixmax<https://mixmax.com/s/WMB47Rd39yDNPFfWo?utm_source=mixmax&utm_medium=email&utm_campaign=signature_link&utm_content=sent_with_mixmax> [Image removed by sender.] On Tue, Mar 14, 2017 5:08 PM, Mayo, Bill [email protected]<mailto:[email protected]> wrote: To the best of my understanding, they just want people to be able to read/view what is in the mailbox. I do not believe they want them to be able to delete or reply to the messages, although I can see them changing their mind about the latter at least in the future. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, March 14, 2017 4:44 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Shared Mailbox with Outside Agencies What do they want to DO? That’s an important question… From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mayo, Bill Sent: Tuesday, March 14, 2017 2:19 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Shared Mailbox with Outside Agencies We have a request to have a mailbox setup that will allow outside agencies to access. From my perspective, creating accounts for these outside agencies is a non-starter. I know that there are some things you can do to allow external, anonymous access to a public folder, but I am not particularly crazy about going that route either. We are on Exchange 2010, hosted entirely at our site. I don’t think there are really any viable options here. Am I correct? If so, are there are any free/cheap 3rd party alternatives that folks have used for this and are happy with? Bill Mayo
