Search results for query: *

I don't think Exchange 2003 can do this without any third party software. Ex 2007 can achieve this using transport rules, I guess...

I had this issue two months ago. We could receive all emails except one domain. Finally the admin at the other side used the second outgoing line (they have two Interent connections with two different firewalls) and the problem had gone. It appeared the compatible issue between our firewalls...

I used to rename the account when user was replaced. However it ended up spending more time to fix problem. I found creating a new account is always the easiest/most efficient way

Just checked outlook 2003 rules. It only has Cc not Bcc option for sent items. Curious how this can be done..

Hi Msworld, Zelandakh's plan was: 1. Install a second exchange server in your organization 2. move all users' mailbox to the second server 3. Shutdown the first server and repair it 4. When server1 is back up, move all user mailboxes back 5. Remove second server from the Org During this...

You may want to send a few test emails and then go to message tracking center to see where the forwarding stucks...

What if you forward emails to other domains, like gmail, does it work? If you want to forward ALL emails to your domain, you may create a connector on abc server that configure def as smart host. Then relay all emails sent to abc to def. But you don't have a copy in abc though..

How do you want to share the emails? The users send emails on behalf of that address or the users all check the emails to that address? Public folder might be your solution here...

What to backup depends on the roles of the server. For mailbox server, you need to backup mailbox database, transaction logs, some registry settings using system state backup; for client access server, backup \client access folder, IIS metabase, etc; for edge transport server, use...

Use nslookup to verify your MX record >nslookup >set type=mx >xyz.com .... What do you see here? Usually you setup two records for your email. First, the mx record, for example, abc.com point to mail.abc.com server. Second, the A record for the mail.abc.com server. Then other servers can...

I have seen this kind of problem before. The following is what I did. I don't find any better solution yet. 1. Use exmerge to export all that user's emails 2. completely delete the user's mailbox 3. create a new clean mailbox 4. Import back all emails The corrupt email items will disappear...

Thanks for the reply. That's what I did to find out who has that address... I was just thinking if there is a better way :)

Does anybody have any idea? Thanks for your help in advance.

Maybe the safest way is to create a new storage group, move everything over and then delete the old one.

On the server. In AD, the user's properties - Exchange General - Delivery options - forward to You can only put one entry there. So if you have to forward the emails to this user to multiple people, you need to put them in a group.

Configure forwarding on that user's account. If you need to forward to multiple people, you have to put those users in a group and then forward to that group.

Hello, I was wondering if there is an efficient way to search who receives the email, for example abc@mydomain.com, when we don't have the user called abc, but we have that email address? Thank you for your help.

Exchange 2007 is pretty good on this. 2003 has limited searching function in Message Tracking center.

Never try this but I think it's here: First Admin Group - Routing group - Connector Right click the SMTP connector and properties - Delivery restrictions - reject emails from The users being added there can't send Internet emails.

Running Exchange on DC is not recommended, but I have seen it on many small business. So don't too worry about it. I used to recover exchange servers on DC, from scrach. Completely reload OS and promte to DC, install exchange and restore database....They were okay. Technology is used to serve...