new mailbox cannot receive messages from the internet - Microsoft Exchange |
- new mailbox cannot receive messages from the internet
- Offline database defrag
- Undeliverable Meeting Requests
- distributing incoming emails
- Write DACL inherit - How to remove
- Outlook prompting for credentials after DC removed from Exchange S
- Applying local holiday file on a user mailbox or resource.
- Backing up an Exchange 2007 VM (VMware)
- Appointments Lost
- Exchange Databse Recovery
- I need to relay messages
- How To Determine Which Exch03 SP2 Post SP Hotfixes are Installed
- OWA attachment issue
- the message with restricted permissions cannot be viewed
- Multi-site Exchange CCR
new mailbox cannot receive messages from the internet Posted: 15 Jan 2009 11:02 AM PST When I create a new mailbox for a new or existing user, the mailbox cannot receive messages from the internet (tried gmail, yahoomail). Error message: 554 554 <(newmailboxaddress)>: Recipient address rejected: Access denied (state 14). Internal email works fine. Can send to external addresses. Is there something I need to do to enable the ability to receive external email? |
Posted: 14 Jan 2009 10:54 AM PST It looks like you're missing some quotes there. eseutil /d "f:\Storage Group 2 - fs\Mailbox Database 2" /t g:\temp_mailbox This assumes that what's inside the quotes "f:\Storage Group 2 - fs\Mailbox Database 2" is a valid path. I don't believe it is because there's no .edb on it. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Mike W" <microsoft.com> wrote in message news:com... |
Undeliverable Meeting Requests Posted: 14 Jan 2009 07:18 AM PST Yes Erik is a legit user and is an internal user. "Martin Blackstone [MVP]" wrote: |
Posted: 14 Jan 2009 02:08 AM PST Thanks Lanwench :-) I couldn't find a free one. Was going to suggest looking at CRM4 for the Sales side of things. Oliver |
Write DACL inherit - How to remove Posted: 13 Jan 2009 11:27 AM PST We have only one domain so that clarified it. I was also not using the Exchange Management Shell. I received the following message after running the command: Remove-ADPermission : Cannot remove ACE on object "DC=sagrescorp,DC=local" for account "SAGRESNET\Exchange Servers" because it is not present. At line:1 char:20 + Remove-ADPermission <<<< "dc=sagrescorp,dc=local" -user "sagrescorp.local\Ex change Servers" -AccessRights WriteDACL -InheritedObjectType Group Best Practices yzer still shows the old server on the list of servers under "First Administrative Group" but it did not have the Write DACL Inherit issue listed any more. "Michael Dragone" wrote: |
Outlook prompting for credentials after DC removed from Exchange S Posted: 13 Jan 2009 05:58 AM PST On Tue, 13 Jan 2009 09:41:09 -0500, Andy David {MVP} <com> wrote: Oh and BTW, the credential prompting is probably related to: http://support.microsoft.com/kb/927612 But that doesnt change the fact that running DCPROMO is not supported on an Exchange Server. I still recommend calling support to ensure things get fixed up correctly on that server. |
Applying local holiday file on a user mailbox or resource. Posted: 12 Jan 2009 11:49 PM PST I suppose you could use Invoke-Item to run Outlook with the proper switches... "outlook.exe /hol <path>\outlook.hol" John "Anders Jensen" <com> wrote in message news:phx.gbl... |
Backing up an Exchange 2007 VM (VMware) Posted: 12 Jan 2009 02:06 PM PST Good Morning Martin Yes, we have a SAN. Sounds like I'm on the right track, I just wanted to see what others were doing. Cheers Greg "Martin Blackstone [MVP]" wrote: |
Posted: 12 Jan 2009 10:20 AM PST I wish this were true, but I have verified that the user is indeed sending the appointment and it is not showing up on calendar. This is very disturbing because people are missing meetings. Any other thoughts or suggestions? "Ed Crowley [MVP]" wrote: |
Posted: 11 Jan 2009 09:27 AM PST Once you repair the hardware, you may want to reconsider your storage. In addition to a write penalty that's just plain too high, RAID 5 sets have issues with rebuild. It used to be that you had a lot of small 9GBish disks (the last of the breed that actually physically mapped 64 sectors per track) in a RAID 5 set of say 8 or so members, and if one failed rebulding 9GB of data wasn't too tough on the remaining drives. These days, people go out and buy 3 1TB SATA disks a slap then in a RAID 5 set thinking it will solve all their problems; it won't. When a drive fails, and is rebuilt on a hot spare, you have to reconstruct the data on the new drive from the data and parity stripes residing on the surviving drives. Now all tree drives are going to be increadibly busy reading the 2TB of surviving data and writing 1TB to the new drive. It's not uncomon for second drive to fail on rebuild. It doesn't matter if it was a hard error or a transient soft error on the second drive failure; you're toast. Add to the failure/rebuild woes the same old performance issues with RAID 5 when used for random small block workloads with a low read/write ratio. Once you figure in the write penalty, a mirror will outperform a 4 drive RAID 5 set. It gets worse when you ran out and bout those big slow SATA drives because, well, the're slow; a third or a quarter of the IOPS for random small block workloads that you would get from SCSI. SAS actually performs a lot better. If I had a choice between SAS and SATA, I'd go for SAS every time. So what are those big slow SATA drives, and RAID 5 for that matter, good for? Workloads that tend to be more sequential (full stroke) and are read more often than they are written. UC Santa Cruz did a study on user home directories in an Engineering company environment. Seems on average, 95% or so of files written to a home directory was only read twice and one of those times was almost immediately after it was written (user check to make sure it's ther or Office application autosave behaviour - take your pick). Big sequential files, rarely accessed, and read more than they are written. Now there's a use for those 1TB SATA drives. I'd still go RAID 6 though to address the second failure on rebuild issue. John "Miguel" <microsoft.com> wrote in message news:com... |
Posted: 09 Jan 2009 03:46 PM PST 127.0.0.1 is the loopback address of any network card and therefore the equivalent of the IP address of the server it is in, there would be no need to allow this address to relay because messages generated by the server will automatically be allowed.. James. -- James Yeomans, BSc, MCSE Ask me directly at: http://www.justaskjames.co.uk "Javier" wrote: |
How To Determine Which Exch03 SP2 Post SP Hotfixes are Installed Posted: 08 Jan 2009 05:24 AM PST You will be safe skipping the italicized lines. They do not apply to you. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Scott" <microsoft.com> wrote in message news:com... |
Posted: 07 Jan 2009 06:23 PM PST This has been resolved. Thanks for the reply "Lee Derbyshire [MVP]" wrote: |
the message with restricted permissions cannot be viewed Posted: 02 Jan 2009 12:54 PM PST Hi Ed, No they are not. The sender can resend the email and the reicipeint receives it then. Thanks, Mark "Ed Crowley [MVP]" wrote: |
Posted: 01 Jan 2009 05:57 PM PST "Elissa" <com> wrote in message news:%phx.gbl... One method is to use WNLB which is fully supported both for the CAS and HT role. I've written a couple of articles on this subject. You cna find them here: http://www.mchange.org/articles_tutorials/exchange-server-2007/planning-architecture/load-balancing-exchange-2007-sp1-hub-transport-servers-windows-network-load-balancing-technology-part1.html http://www.mchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/load-balancing-exchange-2007-client-access-servers-windows-network-technology-part1.html You can use WNLB since the E2K7 servers in both datacenters will belong to the same AD site (requirement in a Geo-CCR scenario). -- Henrik Walther Exchange MVP | MCM: Exchange 2007 Mchange.org | Exchange-faq.dk |
You are subscribed to email updates from TextNData Forums - Microsoft Exchange To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States |