I actually don't think you have to worry about recipients receiving mail from the internet if they only have im_dom1.indianafcu.com addresses. im_dom1.indianafcu.com isn't valid because of the underscore, is it? (Unrelated - You might want to purchase indianafcu.com and let it sit - just for safety's sake.)
On Fri, Jun 25, 2010 at 9:17 AM, Richard Stovall <rich...@gmail.com> wrote: > Have a look at http://www.msexchange.org/tutorials/MF009.html and > http://www.msexchange.org/tutorials/MF025.html and see where they take > you. I haven't set up this configuration before, but it seems > straightforward enough. Perhaps some of our esteemed MVPs have > easier/better methods or links. > > On Fri, Jun 25, 2010 at 9:08 AM, David W. McSpadden <dav...@imcu.com>wrote: > >> Perfect. >> >> Now how to accomplish this. >> >> >> ------------------------------ >> >> *From:* Richard Stovall [mailto:rich...@gmail.com] >> *Sent:* Friday, June 25, 2010 9:08 AM >> >> *To:* MS-Exchange Admin Issues >> *Subject:* Re: Stop SMTP mail >> >> >> >> Starting to make sense. Joe and Jane should be able to send mail to >> internal recipients only, and should never be able to send a message outside >> your Exchange organization? Bossfolk should be able to send anywhere, but >> always have imcu.com show as the sender? >> >> On Fri, Jun 25, 2010 at 9:02 AM, David W. McSpadden <dav...@imcu.com> >> wrote: >> >> Jane and Joe only get one, internal mail only. >> >> Bossman and Bosslady get two, internal and external. They have had them >> forever. Now we are taking control of both. >> >> Now in ADUC the accounts look like this: >> >> Jane smtp:j...@im_dom1.indianafcu.com<smtp%3aj...@im_dom1.indianafcu.com>set >> as primary >> >> Joe smtp:j...@im_dom1.indianafcu.com <smtp%3a...@im_dom1.indianafcu.com>set >> as primary >> >> Bossman >> smtp:boss...@im_dom1.indianafcu.com<smtp%3aboss...@im_dom1.indianafcu.com>, >> smtp:boss...@imcu.com <smtp%3aboss...@imcu.com> set as primary >> >> Bosslady >> smtp:bossl...@im_dom1.indianafcu.com<smtp%3abossl...@im_dom1.indianafcu.com>, >> smtp:bossl...@imcu.com <smtp%3abossl...@imcu.com> set as primary >> >> >> >> Default SMTP connector is set to forward * smtp mail to the Ironport. The >> Ironport is getting all the IM_DOM1 traffic and cannot make a DNS connection >> to MX of IM_DOM1 and is rejecting all IM_DOM1 traffic. So I am just trying >> to keep the IM_DOM1 traffic local to exchange and not have it travel up to >> the Ironport in the first place?? >> >> Does this make any sense? >> >> >> ------------------------------ >> >> *From:* Richard Stovall [mailto:rich...@gmail.com] >> *Sent:* Friday, June 25, 2010 8:54 AM >> >> >> *To:* MS-Exchange Admin Issues >> *Subject:* Re: Stop SMTP mail >> >> >> >> So Joe and Jane each have two e-mail addresses? Do you want them to have >> one account/inbox, or complete separation between the two? >> >> >> >> On Fri, Jun 25, 2010 at 8:45 AM, David W. McSpadden <dav...@imcu.com> >> wrote: >> >> I think so but also I don’t want joetel...@im_dom1.indianafcu.com to be >> able to send to the Internet I do however want joeteller to be able to send >> to janeteller but that should use the mapi client of exchange correct?? >> >> >> >> >> ------------------------------ >> >> *From:* Richard Stovall [mailto:rich...@gmail.com] >> *Sent:* Friday, June 25, 2010 8:42 AM >> >> >> *To:* MS-Exchange Admin Issues >> *Subject:* Re: Stop SMTP mail >> >> >> >> So the issue is what shows up as the *sender's* address on outbound >> messages that originate on your Exchange server? >> >> On Fri, Jun 25, 2010 at 8:36 AM, David W. McSpadden <dav...@imcu.com> >> wrote: >> >> That is the default smtp address for all users on this exchange server. >> >> We have in the past not wanted anyone with that address to be able to sent >> mail to the Internet. >> >> We had a second smtp address from an Internet based email provider that we >> are currently migrating into Exchange. >> >> Once all the pop accounts have been completely imported into Exchange we >> are going to switch the DNS to point to our firewall. >> >> Not everyone in the org has a second smtp address. So we want those >> individuals to stay within the org and not be able to send those not >> qualified emails to the internet and allow the second smtp address to send >> and receive at will. >> >> So I have a default connector currently that points to the Ironport * all >> smtp traffic from the exchange server. >> >> I set up the second connector and set it to point to [127.0.0.1] for all >> im_dom1.indianafcu.com traffic but I was able to send to my yahoo account >> from the im_dom1.indianafcu.com account base. >> >> ???? >> >> >> ------------------------------ >> >> *From:* Richard Stovall [mailto:rich...@gmail.com] >> *Sent:* Friday, June 25, 2010 8:30 AM >> >> >> *To:* MS-Exchange Admin Issues >> >> *Subject:* Re: Stop SMTP mail >> >> >> >> I don't think an SMTP connector should be necessary, and to be honest it >> sounds like a strange solution given the information I've seen so far. Can >> you tell us more about the desired result? Do the people with email >> addresses in that domain have accounts on your Exchange server? Is it your >> desire to have the Exchange server host mail for that domain? >> >> On Fri, Jun 25, 2010 at 8:23 AM, David W. McSpadden <dav...@imcu.com> >> wrote: >> >> Ok I did that and ran rebuild now in Recipient Update Services. >> But im_dom1.indianafcu.com can still send to the Internet??? >> >> >> -----Original Message----- >> From: Jay Dale [mailto:jay.d...@3-gig.com] >> Sent: Thursday, June 24, 2010 4:09 PM >> To: MS-Exchange Admin Issues >> Subject: RE: Stop SMTP mail >> >> You could create an SMTP connector and put in the domain name, then point >> the smart host to 127.0.0.1. >> >> Jay Dale >> I.T. Manager, 3GiG >> Mobile: 713.299.2541 >> Email: jay.d...@3-gig.com >> >> Confidentiality Notice: This e-mail, including any attached files, may >> contain confidential and/or privileged information for the sole use of the >> intended recipient. If you are not the intended recipient, you are hereby >> notified that any review, dissemination or copying of this e-mail and >> attachments, if any, or the information contained herein, is strictly >> prohibited. If you are not the intended recipient (or authorized to >> receive >> information for the intended recipient), please contact the sender by >> reply >> e-mail and delete all copies of this message. >> >> >> -----Original Message----- >> From: David W. McSpadden [mailto:dav...@imcu.com] >> Sent: Thursday, June 24, 2010 3:06 PM >> To: MS-Exchange Admin Issues >> Subject: Stop SMTP mail >> >> I have an Exchange 2003 Standard sp2 server. >> I have some legacy smtp addresses laying around in ADUC of >> n...@im_dom1.indianafcu.com. >> I would like Exchange to not relay those emails to the Internet. Just >> keep >> them in house. >> Is there a way to not allow *...@im_dom1.indianafcu.com to relay to the >> Internet addresses??? >> >> >> >> >> >> >> >> >> >> >> >> >> > >
