Exchange 2007 Rules

2009-10-27 Thread McCready, Rob
I tried to setup a rule for one of our mailboxes that auto-replied to every 
email sent to it, something like

Thank you for contacting the complaint department, we really care, blah blah 
blah.

However, it appears to only work internally.

I think there's a setting somewhere on Exchange 2007 that says...Do not 
auto-forward outside the company.

Is it possible to turn this option off on an individual mailbox basis, or is it 
an all or nothing thing?

Thanks.

Rob




Exchange Design Recomendation

2009-10-27 Thread Mayo, Shay

We are about to merge our 2000 user sister company into our Active Directory. 
We have always had a single domain architecture and now are wanting to move to 
a multidomain architecture so the sister company's admins can still manage 
their resources. So I am looking for design ideas.

I think the best approach would be to install all of the exchange servers in 
the same domain and delegate administration to certain Exchange servers to the 
sister company admins, but I have to present other approaches such as 
installing the sister company's Exchange servers in their sub domain and 
discuss why this would or wouldn't be a good idea.

So if anyone has any input or can point me to a good article, it would be 
greatly appreciated!


This will be all Exchange 2007 servers.

Shay


CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain 
privileged and/or confidential
information and is intended only for the review of the party to whom it is 
addressed.   If you have 
received this transmission in error, please immediately return it to the 
sender, delete it  and destroy 
it without reading it.  Unintended transmission shall not constitute the waiver 
of the attorney-client 
or any other privilege.


Re: Retrivein old e-mails mentioning a specific user Exchange 2007

2009-10-27 Thread Graeme Carstairs
HI there,

Thanks for the info.

I have informed the client, and we are awaiting word from their solictors to
see what the next step is.

Graeme


2009/10/23 James Wells jam...@gmail.com

 I'd recommend calling a forensic service (I almost always use Iron
 Mountain). Given enough of your config information, they can restore
 tapes much faster than you can, and feed them into a discovery engine,
 exporting only the emails you need to PST.

 They can also sign off on chain of custody, secure transport, etc if
 required

 --James


 On 10/23/09, Michael B. Smith mich...@owa.smithcons.com wrote:
  yes, you can do that.
 
  i am, in fact, doing that for a number of my own customers right now.
 
  you work out a rhythm after a while...
 
  
  From: Graeme Carstairs [loonyto...@gmail.com]
  Sent: Friday, October 23, 2009 11:17 AM
  To: MS-Exchange Admin Issues
  Subject: Retrivein old e-mails mentioning a specific user Exchange 2007
 
  Hi All,
 
  One of our customers has just found out why we recommended and quoted
 them
  an e-mail archival system.
 
  One of their employees has left and has since started proceedings for
  constructive dismissal.
 
  HIs lawyer requested copies of every e-mail that mentions his name, and
 the
  client passed the request to the users who would have been cited as being
  involved 1st.
 
  They retrieved all the e-mails they could and they were passed to his
  lawyer.
 
 
  Of course you can all guess what happened next, he claims that he knows
 for
  a fact there were other e-mails sent by these people that mentioned him,
  that haven't bee passed on and therefore these people have deliberately
  deleted them so as to avoid incriminating themselves.
 
  So now we get called in to see what we can do for them.
 
  They have a single mailbox server Exchange 2007 setup, and it is backed
 up
  fully to tape every night, they keep there weekly tapes for a year and
 there
  monthly tapes indefinitely.
 
  My thinking is to do this in a way that would be seen as safe, would be
 to
  setup a lab with a DC and and exchange server restored form the original
  site backups, and then go back to the 1st tape available after the start
  date that the e-mail is requested from, (it is looking like 8 months)
 then
  restoring the AD, and then the Exchange databases.
 
  I am not sure if we can then force the undeletion of all deleted items,
 and
  then search the store for all mails with his name in the subject, to,
 from,
  cc, bcc and message body fields.
 
  Moving that into an archive PST file, and then lather rinse repeat for
 each
  and every tape.
 
  Putting the files onto a USB HDD and giving it to the lawyer.
 
  Is this a workable solution, or does anyone have any better ideas.
 
  Of course once completed the e-mail archiver quote is getting reissued
  immediately.
 
  TIA
 
  Graeme
 
 
  --
  Good news everyone, you have just received and e-mail from me!
 
  Ted Turnerhttp://www.brainyquote.com/quotes/authors/t/ted_turner.html
  -
  Sports is like a war without the killing.
 

 --
 Sent from my mobile device




-- 
Good news everyone, you have just received and e-mail from me!

Ogden Nash http://www.brainyquote.com/quotes/authors/o/ogden_nash.html  -
The trouble with a kitten is that when it grows up, it's always a cat.


Auto-Discovery Service Not Working

2009-10-27 Thread John Bowles
My laptop is currently in a workgroup setting.  When I try and setup my Outlook 
2007 client the auto discovery service seems to fail and I can only setup the 
profile manually.

Anyone have any idea as to what might be preventing the AD service from working 
properly?

Thank you,

John Bowles



RE: Auto-Discovery Service Not Working

2009-10-27 Thread Campbell, Rob
Does your domain restrict anonymous access?

From: John Bowles [mailto:john.bow...@wlkmmas.org]
Sent: Tuesday, October 27, 2009 10:52 AM
To: MS-Exchange Admin Issues
Subject: Auto-Discovery Service Not Working

My laptop is currently in a workgroup setting.  When I try and setup my Outlook 
2007 client the auto discovery service seems to fail and I can only setup the 
profile manually.

Anyone have any idea as to what might be preventing the AD service from working 
properly?

Thank you,

John Bowles

**
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**


Re: Exchange Design Recomendation

2009-10-27 Thread Don Ely
What kind of management is required on the Exchange servers is required by
the admins in the sister company?

On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay shay.m...@absg.com wrote:



 We are about to merge our 2000 user sister company into our Active
 Directory. We have always had a single domain architecture and now are
 wanting to move to a multidomain architecture so the sister company’s admins
 can still manage their resources. So I am looking for design ideas.



 I think the best approach would be to install all of the exchange servers
 in the same domain and delegate administration to certain Exchange servers
 to the sister company admins, but I have to present other approaches such as
 installing the sister company’s Exchange servers in their sub domain and
 discuss why this would or wouldn’t be a good idea.



 So if anyone has any input or can point me to a good article, it would be
 greatly appreciated!





 This will be all Exchange 2007 servers.



 Shay



 CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain 
 privileged and/or confidential
 information and is intended only for the review of the party to whom it is 
 addressed.   If you have
 received this transmission in error, please immediately return it to the 
 sender, delete it  and destroy
 it without reading it.  Unintended transmission shall not constitute the 
 waiver of the attorney-client
 or any other privilege.




Exchange 2007 SP2

2009-10-27 Thread Stefan Jafs
I know SP2 has been out for a while, is there any reason not to upgrade?
Looks like I need to expand the schema first!


___
Stefan Jafs



BES People...your help, please...

2009-10-27 Thread Sean Rector
I'm trying to properly create a Certificate on my BES 5 server for the Web 
Desktop  Admin Service websites to use.  It is running on Windows Server 2003 
R2 Standard.  I am running Server 2008 R2 certificate services.  I have 
verified permissions on the templates to allow Authenticated users Enroll 
capability.  To generate the CSR, I used the Keytool utility following the 
steps listed at Port3101.org, in the Article, BES 5.0 - Installing an SSL 
Certificate for BAS/WDM.  Every time I try to submit the certificate through 
the AD Cert. Svcs. Website, it fails with an Error 53 in Event Viewer.  I've 
tried several workarounds and still have not been able to get this certificate 
generated.  I've looked at TechNet article, Event ID 53 - AD CS Certificate 
Request (Enrollment) Processing, dated July 8, 2009, and followed the steps 
listed to no avail.

Your assistance is requested and greatly appreciated.

Sean Rector, MCSE

Information Technology Manager
Virginia Opera Association

E-Mail: sean.rec...@vaopera.orgmailto:sean.rec...@vaopera.org
Phone:(757) 213-4548 (direct line)
{+}

Virginia Opera's 35th Anniversary Seasonhttp://www.vaopera.org The One You 
Love
Celebrate with a 2009-2010 Subscription: La 
Boh?mehttp://www.vaopera.org/html/currentoperas/opera1.cfm, The Daughter of 
the Regimenthttp://www.vaopera.org/html/currentoperas/opera2.cfm, Don 
Giovannihttp://www.vaopera.org/html/currentoperas/opera3.cfm and Porgy and 
BessSMhttp://www.vaopera.org/html/currentoperas/opera4.cfm
Visit us online at www.vaopera.orghttp://www.vaopera.org or call 
1-866-OPERA-VA

The vision of Virginia Opera is to enrich lives through the powerful 
integration of music, voice and human drama

This e-mail and any attached files are confidential and intended solely for the 
intended recipient(s). Unless otherwise specified, persons unnamed as 
recipients may not read, distribute, copy or alter this e-mail. Any views or 
opinions expressed in this e-mail belong to the author and may not necessarily 
represent those of Virginia Opera. Although precautions have been taken to 
ensure no viruses are present, Virginia Opera cannot accept responsibility for 
any loss or damage that may arise from the use of this e-mail or attachments.

{*}


Weird problem

2009-10-27 Thread David W. McSpadden

I have Exchange 2003.
We use it for internal email only.  We connect to it using Outlook 2003.

I have a mail provider, mailanyone.net.
We use it for external email only.  We connect to it using Outlook Express, 
pop.imcu.com and smtp.imcu.com.


I have an ironport that sits on the edge of my network.
Currently if I set up an smtp address in Outlook 2003 I can get my email 
sent out the ironport device from exchange.

I can not get any mail into exchange through the ironport.


I have a requirement to keep the two clients but send all the smtp and 
receive all the pop mail through the ironport.
If that means relaying off of the exchange that is fine or not even using it 
is also fine.


Does anyone know of away to do this?





RE: Exchange Design Recomendation

2009-10-27 Thread Mayo, Shay
For the most part, we want them to be able to fully admin their exchange 
servers. I think we want them to be able to manage their servers but make sure 
they can't screw up the entire org.

From: Don Ely [mailto:don@gmail.com]
Sent: Tuesday, October 27, 2009 11:23 AM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Design Recomendation

What kind of management is required on the Exchange servers is required by the 
admins in the sister company?
On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay 
shay.m...@absg.commailto:shay.m...@absg.com wrote:

We are about to merge our 2000 user sister company into our Active Directory. 
We have always had a single domain architecture and now are wanting to move to 
a multidomain architecture so the sister company's admins can still manage 
their resources. So I am looking for design ideas.

I think the best approach would be to install all of the exchange servers in 
the same domain and delegate administration to certain Exchange servers to the 
sister company admins, but I have to present other approaches such as 
installing the sister company's Exchange servers in their sub domain and 
discuss why this would or wouldn't be a good idea.

So if anyone has any input or can point me to a good article, it would be 
greatly appreciated!


This will be all Exchange 2007 servers.

Shay


CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain 
privileged and/or confidential

information and is intended only for the review of the party to whom it is 
addressed.   If you have

received this transmission in error, please immediately return it to the 
sender, delete it  and destroy

it without reading it.  Unintended transmission shall not constitute the waiver 
of the attorney-client

or any other privilege.


CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain 
privileged and/or confidential
information and is intended only for the review of the party to whom it is 
addressed.   If you have 
received this transmission in error, please immediately return it to the 
sender, delete it  and destroy 
it without reading it.  Unintended transmission shall not constitute the waiver 
of the attorney-client 
or any other privilege.


RE: Auto-Discovery Service Not Working

2009-10-27 Thread Carol Fee
If you are in a workgroup, then you are not authenticated .

CFee
From: John Bowles [mailto:john.bow...@wlkmmas.org]
Sent: Tuesday, October 27, 2009 11:52 AM
To: MS-Exchange Admin Issues
Subject: Auto-Discovery Service Not Working

My laptop is currently in a workgroup setting.  When I try and setup my Outlook 
2007 client the auto discovery service seems to fail and I can only setup the 
profile manually.

Anyone have any idea as to what might be preventing the AD service from working 
properly?

Thank you,

John Bowles



Re: Exchange Design Recomendation

2009-10-27 Thread Don Ely
But what does fully admin mean to you?  Is it create and manage users?  Do
you want them creating transport rules?  Do you just want them to be able
start and stop services?  What is it you want them to have the ability to
do?  I work with around 20 IT staff that have the ability to manage?admin
exchange in a way that fits within the organizations needs.  Do they have
full, carte blanche access?  Nope, not in a million years.  But they have a
level of admin access that they feel is full admin access to them...

On Tue, Oct 27, 2009 at 11:04 AM, Mayo, Shay shay.m...@absg.com wrote:

  For the most part, we want them to be able to fully admin their exchange
 servers. I think we want them to be able to manage their servers but make
 sure they can’t screw up the entire org.



 *From:* Don Ely [mailto:don@gmail.com]
 *Sent:* Tuesday, October 27, 2009 11:23 AM
 *To:* MS-Exchange Admin Issues
 *Subject:* Re: Exchange Design Recomendation



 What kind of management is required on the Exchange servers is required by
 the admins in the sister company?

 On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay shay.m...@absg.com wrote:



 We are about to merge our 2000 user sister company into our Active
 Directory. We have always had a single domain architecture and now are
 wanting to move to a multidomain architecture so the sister company’s admins
 can still manage their resources. So I am looking for design ideas.



 I think the best approach would be to install all of the exchange servers
 in the same domain and delegate administration to certain Exchange servers
 to the sister company admins, but I have to present other approaches such as
 installing the sister company’s Exchange servers in their sub domain and
 discuss why this would or wouldn’t be a good idea.



 So if anyone has any input or can point me to a good article, it would be
 greatly appreciated!





 This will be all Exchange 2007 servers.



 Shay



 CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain 
 privileged and/or confidential

 information and is intended only for the review of the party to whom it is 
 addressed.   If you have

 received this transmission in error, please immediately return it to the 
 sender, delete it  and destroy

 it without reading it.  Unintended transmission shall not constitute the 
 waiver of the attorney-client

 or any other privilege.



 CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain 
 privileged and/or confidential
 information and is intended only for the review of the party to whom it is 
 addressed.   If you have
 received this transmission in error, please immediately return it to the 
 sender, delete it  and destroy
 it without reading it.  Unintended transmission shall not constitute the 
 waiver of the attorney-client
 or any other privilege.




RE: Weird problem

2009-10-27 Thread Carl Houseman
Usually, anti-spam devices that sit on the network edge talk SMTP, not POP, for 
inbound mail delivery.

Check your Ironport spec sheet to be sure, or look in the configuration menus 
for setting up POP mail retrieval, and if you don't find that capability, you 
can't get there from here.

Carl

-Original Message-
From: David W. McSpadden [mailto:dav...@imcu.com] 
Sent: Tuesday, October 27, 2009 1:54 PM
To: MS-Exchange Admin Issues
Subject: Weird problem

I have Exchange 2003.
We use it for internal email only.  We connect to it using Outlook 2003.

I have a mail provider, mailanyone.net.
We use it for external email only.  We connect to it using Outlook Express, 
pop.imcu.com and smtp.imcu.com.

I have an ironport that sits on the edge of my network.
Currently if I set up an smtp address in Outlook 2003 I can get my email 
sent out the ironport device from exchange.
I can not get any mail into exchange through the ironport.


I have a requirement to keep the two clients but send all the smtp and 
receive all the pop mail through the ironport.
If that means relaying off of the exchange that is fine or not even using it 
is also fine.

Does anyone know of away to do this?
 







RE: Auto-Discovery Service Not Working

2009-10-27 Thread John Bowles
I can't remember off the top of my head.  But is anonymouse auth a default 
setting in GPO?  Cause that would make a world of sense if it is.   I guess I 
need to configure Outlook Anywhere if I want these features and not access it 
via TCP/IP.


John Bowles


From: Carol Fee [c...@massbar.org]
Sent: Tuesday, October 27, 2009 2:10 PM
To: MS-Exchange Admin Issues
Subject: RE: Auto-Discovery Service Not Working

If you are in a workgroup, then you are not authenticated .

CFee
From: John Bowles [mailto:john.bow...@wlkmmas.org]
Sent: Tuesday, October 27, 2009 11:52 AM
To: MS-Exchange Admin Issues
Subject: Auto-Discovery Service Not Working

My laptop is currently in a workgroup setting.  When I try and setup my Outlook 
2007 client the auto discovery service seems to fail and I can only setup the 
profile manually.

Anyone have any idea as to what might be preventing the AD service from working 
properly?

Thank you,

John Bowles



Re: Weird problem

2009-10-27 Thread David W. McSpadden
Would I set my internal dns to have pop.imcu.com and smtp.imcu.com point to 
the smtp relay of the ironport?
That way when the outlook express accounts resolved their addresses they 
would be forced to come through the ironport?
I can set up the ASA to funnel all port 25 and port 110 traffic to go 
through the ironport?


Current:

 - ---
--
/ Internet E-Mail\-/ASA FireWall\---/Outlook Express\
 -
-

Proposed:

 - ---- 
  --- 
/ Internet E-Mail\-/ASA 
FireWall\---/Ironport\---/Outlook Express\
 - 
   -



--
From: Carl Houseman c.house...@gmail.com
Sent: Tuesday, October 27, 2009 2:26 PM
To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
Subject: RE: Weird problem

Usually, anti-spam devices that sit on the network edge talk SMTP, not 
POP, for inbound mail delivery.


Check your Ironport spec sheet to be sure, or look in the configuration 
menus for setting up POP mail retrieval, and if you don't find that 
capability, you can't get there from here.


Carl

-Original Message-
From: David W. McSpadden [mailto:dav...@imcu.com]
Sent: Tuesday, October 27, 2009 1:54 PM
To: MS-Exchange Admin Issues
Subject: Weird problem

I have Exchange 2003.
We use it for internal email only.  We connect to it using Outlook 2003.

I have a mail provider, mailanyone.net.
We use it for external email only.  We connect to it using Outlook 
Express,

pop.imcu.com and smtp.imcu.com.

I have an ironport that sits on the edge of my network.
Currently if I set up an smtp address in Outlook 2003 I can get my email
sent out the ironport device from exchange.
I can not get any mail into exchange through the ironport.


I have a requirement to keep the two clients but send all the smtp and
receive all the pop mail through the ironport.
If that means relaying off of the exchange that is fine or not even using 
it

is also fine.

Does anyone know of away to do this?












RE: Exchange 2007 SP2

2009-10-27 Thread Michael B. Smith
the schema expansion has been the #1 blocker for sp2 deployments.

there are no new issues that i am aware of introduced by sp2. the world-wide 
interwebs have been very quiet on that front...


From: Stefan Jafs [sj...@amico.com]
Sent: Tuesday, October 27, 2009 1:14 PM
To: MS-Exchange Admin Issues
Subject: Exchange 2007 SP2

I know SP2 has been out for a while, is there any reason not to upgrade?
Looks like I need to expand the schema first!


___
Stefan Jafs



RE: Weird problem

2009-10-27 Thread Jason Gurtz
If you already have an email server (Exchange) and all the other necessary
items why not simplify and just (get rid of Outlook Express):

 Public IP   Private IP
  
Internet--ASA--Ironport--Exchange--Outlook
  ^^
  ||
Mail Gateway -+|
(DNS MX record)|
   |
Mail Relay +

Am I missing something?

the ASA will do PAT of port 25 to/from the Ironport (so public MX record
actually points to ASA public IP). Best practice would be to have the ASA
block port 25 to and from anything other than the Ironport (clients should
not ever send directly to the Internet); Exchange box will use Ironport as
the smarthost.  Configure the Ironport to LDAP lookups against a domain
controller to avoid delivery to non-existent users.  If you really want to
retain OL Express, enable POP/IMAP and point your OL Express at the
Exchange box.  At any rate, the Ironport is an smtp relay only; you cannot
enable a client access protocol such as POP or IMAP on it.

Your Co. is paying a lot of money for the Ironport; utilize the support
resources to help you get the configuration done right.  There are many
small details involved, but thankfully most only have to be dealt with
once, when it's first set up.

~JasonG

 -Original Message-
 From: David W. McSpadden [mailto:dav...@imcu.com]
 Sent: Tuesday, October 27, 2009 14:37
 To: MS-Exchange Admin Issues
 Cc: David McSpadden
 Subject: Re: Weird problem
 
 Would I set my internal dns to have pop.imcu.com and smtp.imcu.com point
 to
 the smtp relay of the ironport?
 That way when the outlook express accounts resolved their addresses they
 would be forced to come through the ironport?
 I can set up the ASA to funnel all port 25 and port 110 traffic to go
 through the ironport?
 
 Current:
 
   - ---
--
 
 / Internet E-Mail\-/ASA FireWall\---/Outlook Express\
  -
---
 --
 
 Proposed:
 
   - ---
--
 ---
---
 / Internet E-Mail\-/ASA
 FireWall\---/Ironport\---/Outlook Express\
  -
---
 -
 -
 
 
 --
 From: Carl Houseman c.house...@gmail.com
 Sent: Tuesday, October 27, 2009 2:26 PM
 To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
 Subject: RE: Weird problem
 
  Usually, anti-spam devices that sit on the network edge talk SMTP, not
  POP, for inbound mail delivery.
 
  Check your Ironport spec sheet to be sure, or look in the
configuration
  menus for setting up POP mail retrieval, and if you don't find that
  capability, you can't get there from here.
 
  Carl
 
  -Original Message-
  From: David W. McSpadden [mailto:dav...@imcu.com]
  Sent: Tuesday, October 27, 2009 1:54 PM
  To: MS-Exchange Admin Issues
  Subject: Weird problem
 
  I have Exchange 2003.
  We use it for internal email only.  We connect to it using Outlook
 2003.
 
  I have a mail provider, mailanyone.net.
  We use it for external email only.  We connect to it using Outlook
  Express,
  pop.imcu.com and smtp.imcu.com.
 
  I have an ironport that sits on the edge of my network.
  Currently if I set up an smtp address in Outlook 2003 I can get my
 email
  sent out the ironport device from exchange.
  I can not get any mail into exchange through the ironport.
 
 
  I have a requirement to keep the two clients but send all the smtp and
  receive all the pop mail through the ironport.
  If that means relaying off of the exchange that is fine or not even
 using
  it
  is also fine.
 
  Does anyone know of away to do this?
 
 
 
 
 
 
 
 





RE: Exchange 2007 Rules

2009-10-27 Thread KevinM
you have to allow auto replies on the send connector.

Kevinm | WLKMMAS | This message is Certified Swine Flu Free | 
http://www.hedonists.ca

-Original Message-
From: McCready, Rob [mailto:rob.mccrea...@dplinc.com]
Sent: Tuesday, October 27, 2009 7:41 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2007 Rules

I tried to setup a rule for one of our mailboxes that auto-replied to every 
email sent to it, something like

Thank you for contacting the complaint department, we really care, blah blah 
blah.

However, it appears to only work internally.

I think there's a setting somewhere on Exchange 2007 that says...Do not 
auto-forward outside the company.

Is it possible to turn this option off on an individual mailbox basis, or is it 
an all or nothing thing?

Thanks.

Rob






Re: Weird problem

2009-10-27 Thread David W. McSpadden

Thanks Jason.
I would love to get rid of OL Express but it is a Legacy thing.  I have 
promoted this beast because of my fears of viruses in the past.  Now I have 
been so convincing that nobody will allow me to change their stance on 
internal mail and external mail.



--
From: Jason Gurtz jasongu...@npumail.com
Sent: Tuesday, October 27, 2009 3:14 PM
To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
Subject: RE: Weird problem


If you already have an email server (Exchange) and all the other necessary
items why not simplify and just (get rid of Outlook Express):

Public IP   Private IP
  
Internet--ASA--Ironport--Exchange--Outlook
 ^^
 ||
Mail Gateway -+|
(DNS MX record)|
  |
Mail Relay +

Am I missing something?

the ASA will do PAT of port 25 to/from the Ironport (so public MX record
actually points to ASA public IP). Best practice would be to have the ASA
block port 25 to and from anything other than the Ironport (clients should
not ever send directly to the Internet); Exchange box will use Ironport as
the smarthost.  Configure the Ironport to LDAP lookups against a domain
controller to avoid delivery to non-existent users.  If you really want to
retain OL Express, enable POP/IMAP and point your OL Express at the
Exchange box.  At any rate, the Ironport is an smtp relay only; you cannot
enable a client access protocol such as POP or IMAP on it.

Your Co. is paying a lot of money for the Ironport; utilize the support
resources to help you get the configuration done right.  There are many
small details involved, but thankfully most only have to be dealt with
once, when it's first set up.

~JasonG


-Original Message-
From: David W. McSpadden [mailto:dav...@imcu.com]
Sent: Tuesday, October 27, 2009 14:37
To: MS-Exchange Admin Issues
Cc: David McSpadden
Subject: Re: Weird problem

Would I set my internal dns to have pop.imcu.com and smtp.imcu.com point
to
the smtp relay of the ironport?
That way when the outlook express accounts resolved their addresses they
would be forced to come through the ironport?
I can set up the ASA to funnel all port 25 and port 110 traffic to go
through the ironport?

Current:

  - ---

--


/ Internet E-Mail\-/ASA FireWall\---/Outlook Express\
 -

---

--

Proposed:

  - ---

--

---
   ---
/ Internet E-Mail\-/ASA
FireWall\---/Ironport\---/Outlook Express\
 -

---

-
-


--
From: Carl Houseman c.house...@gmail.com
Sent: Tuesday, October 27, 2009 2:26 PM
To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
Subject: RE: Weird problem

 Usually, anti-spam devices that sit on the network edge talk SMTP, not
 POP, for inbound mail delivery.

 Check your Ironport spec sheet to be sure, or look in the

configuration

 menus for setting up POP mail retrieval, and if you don't find that
 capability, you can't get there from here.

 Carl

 -Original Message-
 From: David W. McSpadden [mailto:dav...@imcu.com]
 Sent: Tuesday, October 27, 2009 1:54 PM
 To: MS-Exchange Admin Issues
 Subject: Weird problem

 I have Exchange 2003.
 We use it for internal email only.  We connect to it using Outlook
2003.

 I have a mail provider, mailanyone.net.
 We use it for external email only.  We connect to it using Outlook
 Express,
 pop.imcu.com and smtp.imcu.com.

 I have an ironport that sits on the edge of my network.
 Currently if I set up an smtp address in Outlook 2003 I can get my
email
 sent out the ironport device from exchange.
 I can not get any mail into exchange through the ironport.


 I have a requirement to keep the two clients but send all the smtp and
 receive all the pop mail through the ironport.
 If that means relaying off of the exchange that is fine or not even
using
 it
 is also fine.

 Does anyone know of away to do this?


















Re: Weird problem

2009-10-27 Thread Eric Woodford
:)

Do viruses spread slower because they are attached to an email in a POP
mailbox vs passing through an Exchange server?

I agree with Jason, you paid for the IronPort to scan your incoming mail,
get rid of the OE client and simplify. When no new mail shows up in their OE
mailbox, but appears in Outlok, they'll be pleasantly pleased.

On Tue, Oct 27, 2009 at 12:21 PM, David W. McSpadden dav...@imcu.comwrote:

 Thanks Jason.
 I would love to get rid of OL Express but it is a Legacy thing.  I have
 promoted this beast because of my fears of viruses in the past.  Now I have
 been so convincing that nobody will allow me to change their stance on
 internal mail and external mail.


 --
 From: Jason Gurtz jasongu...@npumail.com
 Sent: Tuesday, October 27, 2009 3:14 PM

 To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
 Subject: RE: Weird problem

 If you already have an email server (Exchange) and all the other necessary
 items why not simplify and just (get rid of Outlook Express):

Public IP   Private IP
   
 Internet--ASA--Ironport--Exchange--Outlook
 ^^
 ||
 Mail Gateway -+|
 (DNS MX record)|
  |
 Mail Relay +

 Am I missing something?

 the ASA will do PAT of port 25 to/from the Ironport (so public MX record
 actually points to ASA public IP). Best practice would be to have the ASA
 block port 25 to and from anything other than the Ironport (clients should
 not ever send directly to the Internet); Exchange box will use Ironport as
 the smarthost.  Configure the Ironport to LDAP lookups against a domain
 controller to avoid delivery to non-existent users.  If you really want to
 retain OL Express, enable POP/IMAP and point your OL Express at the
 Exchange box.  At any rate, the Ironport is an smtp relay only; you cannot
 enable a client access protocol such as POP or IMAP on it.

 Your Co. is paying a lot of money for the Ironport; utilize the support
 resources to help you get the configuration done right.  There are many
 small details involved, but thankfully most only have to be dealt with
 once, when it's first set up.

 ~JasonG

 -Original Message-
 From: David W. McSpadden [mailto:dav...@imcu.com]
 Sent: Tuesday, October 27, 2009 14:37
 To: MS-Exchange Admin Issues
 Cc: David McSpadden
 Subject: Re: Weird problem

 Would I set my internal dns to have pop.imcu.com and smtp.imcu.com point
 to
 the smtp relay of the ironport?
 That way when the outlook express accounts resolved their addresses they
 would be forced to come through the ironport?
 I can set up the ASA to funnel all port 25 and port 110 traffic to go
 through the ironport?

 Current:

  - ---

 --

 
 / Internet E-Mail\-/ASA FireWall\---/Outlook Express\
  -

 ---

 --

 Proposed:

  - ---

 --

 ---
   ---
 / Internet E-Mail\-/ASA
 FireWall\---/Ironport\---/Outlook Express\
  -

 ---

 -
-


 --
 From: Carl Houseman c.house...@gmail.com
 Sent: Tuesday, October 27, 2009 2:26 PM
 To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
 Subject: RE: Weird problem

  Usually, anti-spam devices that sit on the network edge talk SMTP, not
  POP, for inbound mail delivery.
 
  Check your Ironport spec sheet to be sure, or look in the

 configuration

  menus for setting up POP mail retrieval, and if you don't find that
  capability, you can't get there from here.
 
  Carl
 
  -Original Message-
  From: David W. McSpadden [mailto:dav...@imcu.com]
  Sent: Tuesday, October 27, 2009 1:54 PM
  To: MS-Exchange Admin Issues
  Subject: Weird problem
 
  I have Exchange 2003.
  We use it for internal email only.  We connect to it using Outlook
 2003.
 
  I have a mail provider, mailanyone.net.
  We use it for external email only.  We connect to it using Outlook
  Express,
  pop.imcu.com and smtp.imcu.com.
 
  I have an ironport that sits on the edge of my network.
  Currently if I set up an smtp address in Outlook 2003 I can get my
 email
  sent out the ironport device from exchange.
  I can not get any mail into exchange through the ironport.
 
 
  I have a requirement to keep the two clients but send all the smtp and
  receive all the pop mail through the ironport.
  If that means relaying off of the exchange that is fine or not even
 using
  it
  is also fine.
 
  Does anyone know of away to do this?
 
 
 
 
 
 
 
 










RE: Weird problem

2009-10-27 Thread Tom Cass
Ditto!


From: Eric Woodford [mailto:ericwoodf...@gmail.com]
Sent: Tuesday, October 27, 2009 3:35 PM
To: MS-Exchange Admin Issues
Subject: Re: Weird problem

:)

Do viruses spread slower because they are attached to an email in a POP mailbox 
vs passing through an Exchange server?

I agree with Jason, you paid for the IronPort to scan your incoming mail, get 
rid of the OE client and simplify. When no new mail shows up in their OE 
mailbox, but appears in Outlok, they'll be pleasantly pleased.
On Tue, Oct 27, 2009 at 12:21 PM, David W. McSpadden 
dav...@imcu.commailto:dav...@imcu.com wrote:
Thanks Jason.
I would love to get rid of OL Express but it is a Legacy thing.  I have 
promoted this beast because of my fears of viruses in the past.  Now I have 
been so convincing that nobody will allow me to change their stance on internal 
mail and external mail.


--
From: Jason Gurtz jasongu...@npumail.commailto:jasongu...@npumail.com
Sent: Tuesday, October 27, 2009 3:14 PM

To: MS-Exchange Admin Issues 
exchangelist@lyris.sunbelt-software.commailto:exchangelist@lyris.sunbelt-software.com
Subject: RE: Weird problem
If you already have an email server (Exchange) and all the other necessary
items why not simplify and just (get rid of Outlook Express):

   Public IP   Private IP
  
Internet--ASA--Ironport--Exchange--Outlook
^^
||
Mail Gateway -+|
(DNS MX record)|
 |
Mail Relay +

Am I missing something?

the ASA will do PAT of port 25 to/from the Ironport (so public MX record
actually points to ASA public IP). Best practice would be to have the ASA
block port 25 to and from anything other than the Ironport (clients should
not ever send directly to the Internet); Exchange box will use Ironport as
the smarthost.  Configure the Ironport to LDAP lookups against a domain
controller to avoid delivery to non-existent users.  If you really want to
retain OL Express, enable POP/IMAP and point your OL Express at the
Exchange box.  At any rate, the Ironport is an smtp relay only; you cannot
enable a client access protocol such as POP or IMAP on it.

Your Co. is paying a lot of money for the Ironport; utilize the support
resources to help you get the configuration done right.  There are many
small details involved, but thankfully most only have to be dealt with
once, when it's first set up.

~JasonG
-Original Message-
From: David W. McSpadden [mailto:dav...@imcu.commailto:dav...@imcu.com]
Sent: Tuesday, October 27, 2009 14:37
To: MS-Exchange Admin Issues
Cc: David McSpadden
Subject: Re: Weird problem

Would I set my internal dns to have pop.imcu.comhttp://pop.imcu.com/ and 
smtp.imcu.comhttp://smtp.imcu.com/ point
to
the smtp relay of the ironport?
That way when the outlook express accounts resolved their addresses they
would be forced to come through the ironport?
I can set up the ASA to funnel all port 25 and port 110 traffic to go
through the ironport?

Current:

 - ---
--

/ Internet E-Mail\-/ASA FireWall\---/Outlook Express\
 -
---
--

Proposed:

 - ---
--
---
  ---
/ Internet E-Mail\-/ASA
FireWall\---/Ironport\---/Outlook Express\
 -
---
-
   -


--
From: Carl Houseman c.house...@gmail.commailto:c.house...@gmail.com
Sent: Tuesday, October 27, 2009 2:26 PM
To: MS-Exchange Admin Issues 
exchangelist@lyris.sunbelt-software.commailto:exchangelist@lyris.sunbelt-software.com
Subject: RE: Weird problem

 Usually, anti-spam devices that sit on the network edge talk SMTP, not
 POP, for inbound mail delivery.

 Check your Ironport spec sheet to be sure, or look in the
configuration
 menus for setting up POP mail retrieval, and if you don't find that
 capability, you can't get there from here.

 Carl

 -Original Message-
 From: David W. McSpadden [mailto:dav...@imcu.commailto:dav...@imcu.com]
 Sent: Tuesday, October 27, 2009 1:54 PM
 To: MS-Exchange Admin Issues
 Subject: Weird problem

 I have Exchange 2003.
 We use it for internal email only.  We connect to it using Outlook
2003.

 I have a mail provider, mailanyone.nethttp://mailanyone.net/.
 We use it for external email only.  We connect to it using Outlook
 Express,
 pop.imcu.comhttp://pop.imcu.com/ and smtp.imcu.comhttp://smtp.imcu.com/.

 I have an ironport that sits on the edge of my network.
 Currently if I set up an smtp address in Outlook 2003 I can get my
email
 sent out the ironport 

RE: Exchange 2007 Rules

2009-10-27 Thread Dahl, Peter
That is an org level setting on the properties of the entries on the Remote 
Domains tab.  It can be allowed for specific external domains or all domains 
but I am not aware of a way to allow it only for an individual sender to many 
domains.

-Original Message-
From: McCready, Rob [mailto:rob.mccrea...@dplinc.com] 
Sent: Tuesday, October 27, 2009 10:41 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2007 Rules

I tried to setup a rule for one of our mailboxes that auto-replied to every 
email sent to it, something like

Thank you for contacting the complaint department, we really care, blah blah 
blah.

However, it appears to only work internally.

I think there's a setting somewhere on Exchange 2007 that says...Do not 
auto-forward outside the company.

Is it possible to turn this option off on an individual mailbox basis, or is it 
an all or nothing thing?

Thanks.

Rob






Re: Weird problem

2009-10-27 Thread David W. McSpadden
But right now they are breaking the law and have the email segregated. Internal 
only in Outlook and external only in OE.
They are happy that way.


From: Eric Woodford 
Sent: Tuesday, October 27, 2009 3:34 PM
To: MS-Exchange Admin Issues 
Subject: Re: Weird problem


:)

Do viruses spread slower because they are attached to an email in a POP mailbox 
vs passing through an Exchange server? 

I agree with Jason, you paid for the IronPort to scan your incoming mail, get 
rid of the OE client and simplify. When no new mail shows up in their OE 
mailbox, but appears in Outlok, they'll be pleasantly pleased. 


On Tue, Oct 27, 2009 at 12:21 PM, David W. McSpadden dav...@imcu.com wrote:

  Thanks Jason.
  I would love to get rid of OL Express but it is a Legacy thing.  I have 
promoted this beast because of my fears of viruses in the past.  Now I have 
been so convincing that nobody will allow me to change their stance on internal 
mail and external mail.


  --
  From: Jason Gurtz jasongu...@npumail.com
  Sent: Tuesday, October 27, 2009 3:14 PM 

  To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
  Subject: RE: Weird problem


If you already have an email server (Exchange) and all the other necessary
items why not simplify and just (get rid of Outlook Express):

   Public IP   Private IP
  
Internet--ASA--Ironport--Exchange--Outlook
^^
||
Mail Gateway -+|
(DNS MX record)|
 |
Mail Relay +

Am I missing something?

the ASA will do PAT of port 25 to/from the Ironport (so public MX record
actually points to ASA public IP). Best practice would be to have the ASA
block port 25 to and from anything other than the Ironport (clients should
not ever send directly to the Internet); Exchange box will use Ironport as
the smarthost.  Configure the Ironport to LDAP lookups against a domain
controller to avoid delivery to non-existent users.  If you really want to
retain OL Express, enable POP/IMAP and point your OL Express at the
Exchange box.  At any rate, the Ironport is an smtp relay only; you cannot
enable a client access protocol such as POP or IMAP on it.

Your Co. is paying a lot of money for the Ironport; utilize the support
resources to help you get the configuration done right.  There are many
small details involved, but thankfully most only have to be dealt with
once, when it's first set up.

~JasonG


  -Original Message-
  From: David W. McSpadden [mailto:dav...@imcu.com]
  Sent: Tuesday, October 27, 2009 14:37
  To: MS-Exchange Admin Issues
  Cc: David McSpadden
  Subject: Re: Weird problem

  Would I set my internal dns to have pop.imcu.com and smtp.imcu.com point
  to
  the smtp relay of the ironport?
  That way when the outlook express accounts resolved their addresses they
  would be forced to come through the ironport?
  I can set up the ASA to funnel all port 25 and port 110 traffic to go
  through the ironport?

  Current:

   - ---

--

  
  / Internet E-Mail\-/ASA FireWall\---/Outlook Express\
   -

---

  --

  Proposed:

   - ---

--

  ---
---
  / Internet E-Mail\-/ASA
  FireWall\---/Ironport\---/Outlook Express\
   -

---

  -
 -


  --
  From: Carl Houseman c.house...@gmail.com
  Sent: Tuesday, October 27, 2009 2:26 PM
  To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
  Subject: RE: Weird problem

   Usually, anti-spam devices that sit on the network edge talk SMTP, not
   POP, for inbound mail delivery.
  
   Check your Ironport spec sheet to be sure, or look in the

configuration

   menus for setting up POP mail retrieval, and if you don't find that
   capability, you can't get there from here.
  
   Carl
  
   -Original Message-
   From: David W. McSpadden [mailto:dav...@imcu.com]
   Sent: Tuesday, October 27, 2009 1:54 PM
   To: MS-Exchange Admin Issues
   Subject: Weird problem
  
   I have Exchange 2003.
   We use it for internal email only.  We connect to it using Outlook
  2003.
  
   I have a mail provider, mailanyone.net.
   We use it for external 

Re: Auto-Discovery Service Not Working

2009-10-27 Thread Micheal Espinola Jr
AD service?  That would only be applicable if your system belonged to a
domain - for which you don't appear to be.  You should be able to set up a
mail profile manually, and supply credentials that you can also save.
--
ME2


On Tue, Oct 27, 2009 at 11:51 AM, John Bowles john.bow...@wlkmmas.orgwrote:

   My laptop is currently in a workgroup setting.  When I try and setup my
 Outlook 2007 client the auto discovery service seems to fail and I can only
 setup the profile manually.

 Anyone have any idea as to what might be preventing the AD service from
 working properly?

 Thank you,

 John Bowles




Re: Weird problem

2009-10-27 Thread David W. McSpadden
I want to so bad.


From: Tom Cass 
Sent: Tuesday, October 27, 2009 3:37 PM
To: MS-Exchange Admin Issues 
Subject: RE: Weird problem


Ditto!

 




From: Eric Woodford [mailto:ericwoodf...@gmail.com] 
Sent: Tuesday, October 27, 2009 3:35 PM
To: MS-Exchange Admin Issues
Subject: Re: Weird problem

 

:)

 

Do viruses spread slower because they are attached to an email in a POP mailbox 
vs passing through an Exchange server? 

 

I agree with Jason, you paid for the IronPort to scan your incoming mail, get 
rid of the OE client and simplify. When no new mail shows up in their OE 
mailbox, but appears in Outlok, they'll be pleasantly pleased. 

On Tue, Oct 27, 2009 at 12:21 PM, David W. McSpadden dav...@imcu.com wrote:

Thanks Jason.
I would love to get rid of OL Express but it is a Legacy thing.  I have 
promoted this beast because of my fears of viruses in the past.  Now I have 
been so convincing that nobody will allow me to change their stance on internal 
mail and external mail.


--
From: Jason Gurtz jasongu...@npumail.com
Sent: Tuesday, October 27, 2009 3:14 PM 


To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
Subject: RE: Weird problem

If you already have an email server (Exchange) and all the other necessary
items why not simplify and just (get rid of Outlook Express):

   Public IP   Private IP
  
Internet--ASA--Ironport--Exchange--Outlook
^^
||
Mail Gateway -+|
(DNS MX record)|
 |
Mail Relay +

Am I missing something?

the ASA will do PAT of port 25 to/from the Ironport (so public MX record
actually points to ASA public IP). Best practice would be to have the ASA
block port 25 to and from anything other than the Ironport (clients should
not ever send directly to the Internet); Exchange box will use Ironport as
the smarthost.  Configure the Ironport to LDAP lookups against a domain
controller to avoid delivery to non-existent users.  If you really want to
retain OL Express, enable POP/IMAP and point your OL Express at the
Exchange box.  At any rate, the Ironport is an smtp relay only; you cannot
enable a client access protocol such as POP or IMAP on it.

Your Co. is paying a lot of money for the Ironport; utilize the support
resources to help you get the configuration done right.  There are many
small details involved, but thankfully most only have to be dealt with
once, when it's first set up.

~JasonG

-Original Message-
From: David W. McSpadden [mailto:dav...@imcu.com]
Sent: Tuesday, October 27, 2009 14:37
To: MS-Exchange Admin Issues
Cc: David McSpadden
Subject: Re: Weird problem

Would I set my internal dns to have pop.imcu.com and smtp.imcu.com point
to
the smtp relay of the ironport?
That way when the outlook express accounts resolved their addresses they
would be forced to come through the ironport?
I can set up the ASA to funnel all port 25 and port 110 traffic to go
through the ironport?

Current:

 - ---

--


/ Internet E-Mail\-/ASA FireWall\---/Outlook Express\
 -

---

--

Proposed:

 - ---

--

---
  ---
/ Internet E-Mail\-/ASA
FireWall\---/Ironport\---/Outlook Express\
 -

---

-
   -


--
From: Carl Houseman c.house...@gmail.com
Sent: Tuesday, October 27, 2009 2:26 PM
To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com
Subject: RE: Weird problem

 Usually, anti-spam devices that sit on the network edge talk SMTP, not
 POP, for inbound mail delivery.

 Check your Ironport spec sheet to be sure, or look in the

configuration

 menus for setting up POP mail retrieval, and if you don't find that
 capability, you can't get there from here.

 Carl

 -Original Message-
 From: David W. McSpadden [mailto:dav...@imcu.com]
 Sent: Tuesday, October 27, 2009 1:54 PM
 To: MS-Exchange Admin Issues
 Subject: Weird problem

 I have Exchange 2003.
 We use it for internal email only.  We connect to it using Outlook
2003.

 I have a mail provider, mailanyone.net.
 We use it for external email only.  We connect to it using Outlook
 Express,
 pop.imcu.com and smtp.imcu.com.

 I have an ironport that sits on the edge of my network.
 Currently if I set up an smtp address in Outlook 2003 I can get my
email
 sent out the ironport device from exchange.
 I can not get any mail into exchange through the ironport.


 I have a requirement 

RE: Exchange 2007 Rules

2009-10-27 Thread Michael B. Smith
Yeah, if you want it for only one user/many domains, you are going to need to 
create a transport rule, not a mailbox rule (and without checking, I can't 
remember in exchange 2007 whether that might need to be an Edge rule instead of 
a Hub rule - in exchange 2010, the Hub can do them all).


From: Dahl, Peter [peter.d...@yum.com]
Sent: Tuesday, October 27, 2009 3:37 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2007 Rules

That is an org level setting on the properties of the entries on the Remote 
Domains tab.  It can be allowed for specific external domains or all domains 
but I am not aware of a way to allow it only for an individual sender to many 
domains.

-Original Message-
From: McCready, Rob [mailto:rob.mccrea...@dplinc.com]
Sent: Tuesday, October 27, 2009 10:41 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2007 Rules

I tried to setup a rule for one of our mailboxes that auto-replied to every 
email sent to it, something like

Thank you for contacting the complaint department, we really care, blah blah 
blah.

However, it appears to only work internally.

I think there's a setting somewhere on Exchange 2007 that says...Do not 
auto-forward outside the company.

Is it possible to turn this option off on an individual mailbox basis, or is it 
an all or nothing thing?

Thanks.

Rob



RE: Exchange Design Recomendation

2009-10-27 Thread Michael B. Smith
That doesn't require a subdomain.

It simply requires that you put a particular user as a local administrator on 
the Exchange server and delegate them permissions for a particular OU full of 
users.

Really, truly, there are rarely reasons for subdomains anymore.


From: Mayo, Shay [shay.m...@absg.com]
Sent: Tuesday, October 27, 2009 2:04 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Design Recomendation

For the most part, we want them to be able to fully admin their exchange 
servers. I think we want them to be able to manage their servers but make sure 
they can’t screw up the entire org.

From: Don Ely [mailto:don@gmail.com]
Sent: Tuesday, October 27, 2009 11:23 AM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Design Recomendation

What kind of management is required on the Exchange servers is required by the 
admins in the sister company?
On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay 
shay.m...@absg.commailto:shay.m...@absg.com wrote:

We are about to merge our 2000 user sister company into our Active Directory. 
We have always had a single domain architecture and now are wanting to move to 
a multidomain architecture so the sister company’s admins can still manage 
their resources. So I am looking for design ideas.

I think the best approach would be to install all of the exchange servers in 
the same domain and delegate administration to certain Exchange servers to the 
sister company admins, but I have to present other approaches such as 
installing the sister company’s Exchange servers in their sub domain and 
discuss why this would or wouldn’t be a good idea.

So if anyone has any input or can point me to a good article, it would be 
greatly appreciated!


This will be all Exchange 2007 servers.

Shay


CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain 
privileged and/or confidential

information and is intended only for the review of the party to whom it is 
addressed.   If you have

received this transmission in error, please immediately return it to the 
sender, delete it  and destroy

it without reading it.  Unintended transmission shall not constitute the waiver 
of the attorney-client

or any other privilege.


CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain 
privileged and/or confidential
information and is intended only for the review of the party to whom it is 
addressed.   If you have
received this transmission in error, please immediately return it to the 
sender, delete it  and destroy
it without reading it.  Unintended transmission shall not constitute the waiver 
of the attorney-client
or any other privilege.



Re: Exchange Design Recomendation

2009-10-27 Thread Don Ely
Exactly

On 10/27/09, Michael B. Smith mich...@owa.smithcons.com wrote:
 That doesn't require a subdomain.

 It simply requires that you put a particular user as a local administrator
 on the Exchange server and delegate them permissions for a particular OU
 full of users.

 Really, truly, there are rarely reasons for subdomains anymore.

 
 From: Mayo, Shay [shay.m...@absg.com]
 Sent: Tuesday, October 27, 2009 2:04 PM
 To: MS-Exchange Admin Issues
 Subject: RE: Exchange Design Recomendation

 For the most part, we want them to be able to fully admin their exchange
 servers. I think we want them to be able to manage their servers but make
 sure they can’t screw up the entire org.

 From: Don Ely [mailto:don@gmail.com]
 Sent: Tuesday, October 27, 2009 11:23 AM
 To: MS-Exchange Admin Issues
 Subject: Re: Exchange Design Recomendation

 What kind of management is required on the Exchange servers is required by
 the admins in the sister company?
 On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay
 shay.m...@absg.commailto:shay.m...@absg.com wrote:

 We are about to merge our 2000 user sister company into our Active
 Directory. We have always had a single domain architecture and now are
 wanting to move to a multidomain architecture so the sister company’s admins
 can still manage their resources. So I am looking for design ideas.

 I think the best approach would be to install all of the exchange servers in
 the same domain and delegate administration to certain Exchange servers to
 the sister company admins, but I have to present other approaches such as
 installing the sister company’s Exchange servers in their sub domain and
 discuss why this would or wouldn’t be a good idea.

 So if anyone has any input or can point me to a good article, it would be
 greatly appreciated!


 This will be all Exchange 2007 servers.

 Shay


 CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain
 privileged and/or confidential

 information and is intended only for the review of the party to whom it is
 addressed.   If you have

 received this transmission in error, please immediately return it to the
 sender, delete it  and destroy

 it without reading it.  Unintended transmission shall not constitute the
 waiver of the attorney-client

 or any other privilege.


 CONFIDENTIALITY NOTICE.  This electronic mail transmission may contain
 privileged and/or confidential
 information and is intended only for the review of the party to whom it is
 addressed.   If you have
 received this transmission in error, please immediately return it to the
 sender, delete it  and destroy
 it without reading it.  Unintended transmission shall not constitute the
 waiver of the attorney-client
 or any other privilege.



-- 
Sent from my mobile device




IMCEAEX

2009-10-27 Thread Steve Hart
We've recently migrated a bunch of users from an SBS system on to our Exchange 
2007 system. The users had previously existed as contacts in Exchange.

We deleted the contacts and created new users. Everything works great except 
for the expected errors from cached internal Outlook addresses.

Here's an example:

Delivery has failed to these recipients or distribution lists:

Gene 
Snitkermailto:imceaex-_o%3dwright%2b20business%2b20graphics_ou%3dwrightbg_cn%3drecipients_cn%3dgenesnit...@wrightbg.com

The recipient's e-mail address was not found in the recipient's e-mail system. 
Microsoft Exchange will not try to redeliver this message for you. Please check 
the e-mail address and try resending this message, or provide the following 
diagnostic text to your system administrator.



Sent by Microsoft Exchange Server 2007



When I've had occasional problems like this before, I've added an X500 address. 
In this case, I added:

o=wright+20business+20graphics_ou=wrightbg_cn=recipients_cn=genesnit...@wrightbg.commailto:o=wright+20business+20graphics_ou=wrightbg_cn=recipients_cn=genesnit...@wrightbg.com



Email is still bouncing with the same NDR.

Do I have the format wrong, or is something else going on?



Steve




RE: IMCEAEX

2009-10-27 Thread Michael B. Smith
First, this can take up to 2 hours to take effect.

Second, the last cn should be cn=GeneSnitker, not 
cn=genesnit...@wrightbg.commailto:cn=genesnit...@wrightbg.com.


From: Steve Hart [sh...@wrightbg.com]
Sent: Tuesday, October 27, 2009 6:55 PM
To: MS-Exchange Admin Issues
Subject: IMCEAEX

We've recently migrated a bunch of users from an SBS system on to our Exchange 
2007 system. The users had previously existed as contacts in Exchange.

We deleted the contacts and created new users. Everything works great except 
for the expected errors from cached internal Outlook addresses.

Here's an example:

Delivery has failed to these recipients or distribution lists:

Gene 
Snitkermailto:imceaex-_o%3dwright%2b20business%2b20graphics_ou%3dwrightbg_cn%3drecipients_cn%3dgenesnit...@wrightbg.com

The recipient's e-mail address was not found in the recipient's e-mail system. 
Microsoft Exchange will not try to redeliver this message for you. Please check 
the e-mail address and try resending this message, or provide the following 
diagnostic text to your system administrator.



Sent by Microsoft Exchange Server 2007



When I've had occasional problems like this before, I've added an X500 address. 
In this case, I added:

o=wright+20business+20graphics_ou=wrightbg_cn=recipients_cn=genesnit...@wrightbg.commailto:o=wright+20business+20graphics_ou=wrightbg_cn=recipients_cn=genesnit...@wrightbg.com



Email is still bouncing with the same NDR.

Do I have the format wrong, or is something else going on?



Steve




RE: Exchange 2007 SP2

2009-10-27 Thread Leedy, Andy
We did, no problems here.

-Andy

From: Stefan Jafs [mailto:sj...@amico.com]
Sent: Tuesday, October 27, 2009 1:14 PM
To: MS-Exchange Admin Issues
Subject: Exchange 2007 SP2

I know SP2 has been out for a while, is there any reason not to upgrade?
Looks like I need to expand the schema first!


___
Stefan Jafs


**
CONFIDENTIALITY NOTICE:  The information transmitted in this message is 
intended only for the person or entity to which it is addressed and may contain 
confidential and/or privileged material.  Any review, retransmission, 
dissemination or other use of this information by persons or entities other 
than the intended recipient is prohibited.  If you received this in error, 
please contact the sender and destroy all copies of this document.  Thank you.  
Butler Animal Health Supply
**