Pages

Search

Move Mailbox Recomendations - Microsoft Exchange

Move Mailbox Recomendations - Microsoft Exchange

Move Mailbox Recomendations

Posted: 11 May 2005 08:30 AM PDT

then you should be OK to move them all in large groups...
"Fred Yarbrough" <com> wrote in message
news:phx.gbl... 
Transaction 
of 
one 

Mailbox management policy: runs only one of three policies

Posted: 11 May 2005 05:31 AM PDT


But I thought MM policies would run in a sequence, one after another -
according to their priority. Isn't that supposed to be like that?

ypal



"Andy David - MVP" <com> ???????/????????
? ???????? ?????????: news:com... 
Recipients -- 
resides 
the 
other 

WHY EXCHANGE???

Posted: 10 May 2005 03:02 PM PDT

If you're already running Exchange it seems to me that the client should be
the one who has to make the case for changing.

-GT
"neomodo" <microsoft.com> wrote in message
news:com... 

OWA Access for 2nd Exchange 2003 Server

Posted: 10 May 2005 10:27 AM PDT

Nope. Looked at that already. The knowledge base has nothing on this.

Sylvan Jonas

"Leif Pedersen [MVP]" <dk> wrote in message
news:phx.gbl... 

Exchange issue with Outlook 2k3 outbox

Posted: 10 May 2005 08:43 AM PDT

Not sure I understand. Do you mean anyone sending mail to a mailbox that is
not on the cluster or do you mean when connecting to a mailbox with outlook
that isn't on the cluster and sending and receiving with that mailbox? I did
receive a response from a seperate post regarding Firewall issue, I turned
off the Windows Firewall and everything sped up. I was then confused on why
when connecting with a 5.5 mail server we didn't see these problems, but when
connecting to a 2k3 server we did. Different ports maybe?

Thanks for your help,
Jeremey

"Todd J Heron" wrote:
 

5.5 - 2003 Emailing public folders

Posted: 10 May 2005 12:01 AM PDT

Hi,

The problem may be caused by that Categorizer recognized the email address of
the public folder as an outside E-mail address, then it passed it to SMTP virtual
server for outgoing routing. Apparently, this causes an NDR since this address is
not available in internet. So the root cause may be that public folder hierarchy
has not been completely synced to the Exchange 2003 server.

We can try this step first:

Open ESM 2003, open the properties pane of "Mailbox Store" in Exchange 2003
server, and set the default public folder store to the store on Exchange 5.5
server. And then check the issue again.

If now you can send to the public folders, then we can narrow down the problem
as a public hierarchy replication issue.

Hierarchy replication events occur every 5 minutes. If sending a message to a
Public Folder that resides on an Exchange 5.5 server, you must install and
configure a Public Folder Connection Agreement.

281223 Understanding Connection Agreements in Exchange
http://support.microsoft.com/?id=281223

1) Using the information above, apply this to your environment and determine
where the message should be routed.

2) Send a test email to the Public Folder in question.

3) Send a test email to the Public folder store where you expect the message to
be delivered.
Example: com
To locate the email address of the Public folder store, locate the ProxyAddress
attribute of the Public Folder store using ADSIEdit or LDP.

4) If you still encounter 5.1.0 error code, please refer to this KB article:
290204 XCON: 5.1.0 NDRs When You Send from Exchange 2000 to Exchange
Server 5.5

http://support.microsoft.com/?id=290204

5) Gather more information using the Event Viewer and Diagnostic Logging (set
on the properties of the Exchange server within ESM)
Set the following to maximum:
For Hierarchy Replication -
Services: MSExchangeIS\Public Folder
Categories: All Categories

For Mail Flow -
Service: MSExchangeTransport
Categories: All Categories


6) If the test message is sitting in the local delivery queue, look for errors or
warnings in the Application log.

821910 How to troubleshoot for Exchange Server 2003 transport issues
http://support.microsoft.com/?id=821910

Hope the info helps.

Regards,

Pat Cai
Microsoft Online Partner Support

550 sometimes but not others

Posted: 09 May 2005 02:59 PM PDT

Yes. It is possible.

Sounds like there is an issue at the end he is sending too. Often in my
experience secondary SMTP servers at ISPs are misconfigured to reject email,
maybe the 550 is happening when the sending server switchs to a secondary
mail server.

Mal Osborne
MCSE MVP Mensa

"bobk" <com> wrote in message
news:phx.gbl... 

Recovering email stored on crashed Exchange?

Posted: 08 May 2005 09:03 PM PDT

I'd love to rebuild the server. However, the first step is to add NNTP
to IIS. This fails, with the "Overlapped I/O operation in progress."
error message. I've found nothing that gets me past that error, and
Excahnge won't install if NNTP has not been installed. I'm stuck!

None of the commercial programs you mentioned are feasible from a cost
viewpoint. PowerControls lets me see the messages without problem, and
other than having some historical value, there were no pending things
that these emails were critical to.

On Sun, 8 May 2005 18:38:15 -1000, "Jim McBee [MVP Exchange]"
<spambegone.net> wrote:
 

PeterD, the Darkstar Network
To email, fix my address!
ExpertZone!

E2K3 - messages delivered to wrong mailboxes

Posted: 07 May 2005 05:37 AM PDT

Hi Gary

Based on your very helpful information, I did a bit of digging. It would
appear that what I need is the envelope journaling functionality in E2K3 -
this will allow me to read every P1 header (envelope) for every mailbox that
I wish and then evaluate them at my leisure
(http://www.msexchange.org/tutorials/Implementing-Exchange-2003-Message-Journaling.html)

There is a performance hit, but it is acceptable for my needs and volume of
email. I think this is the correct approach, if not, please let me know
your thoughts.

Thanks

"Gary McDonnell" <com> wrote in message
news:phx.gbl... 

smtp Virtual server share address space Help!

Posted: 07 May 2005 05:05 AM PDT

On Sat, 7 May 2005 14:05:03 +0200, "Guy P." <co.il>
wrote:
 

As I understand it you can't deploy a 2nd SBS into a pre-existing SBS
Forest. I'f I'm wrong then you would simply install the server and
Exchange into the organisation and you'd be able to move the mailboxes
and balance the load around. You wouldn't need to try and configure
Exchange.
If I'm right then you can use SBS to deploy the SQL and Windows
standard with Exchange standard or enterprise for the Exchange. Once
thing I do know is that you can have additional member servers with
retail Exchange in an SBS Forest.
That would seem to be the more cost effective of the solutions.

Can't see why you'd want to cludge it up and have two SBS Forests.
Sounds like a total PITA

no OWA account

Posted: 06 May 2005 09:16 AM PDT

On Fri, 6 May 2005 13:42:01 -0700, "jojo"
<microsoft.com> wrote:
 
If HTTP is definitely enabled then check the user rights on the
account. Perhaps he can't log on to the server concerned. What
differences are there between his and another working account?