Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 78
  • Last Modified:

public folder email address no longer exists after disabling/enabling in exchange

Recently, one of our public folders was flooded with spam and I needed to disable mail settings in the exchange console (we are using 2013).

After correcting the issue and enabling mail settings, I am able to send to the public folder from an external address, but when I try to send from an internal address, I get a bounce back stating that the mailbox cannot be found.

Any ideas?
0
zito2000
Asked:
zito2000
  • 3
  • 2
3 Solutions
 
Simon Butler (Sembee)ConsultantCommented:
Mail disabling the folder and then re-enabling it means it is basically a new address as far as Exchange is concerned. External email uses SMTP, internal does not.
You would need to build an X.500 address from the NDR to add to the folder, or just select it fresh from the GAL, rather than use the auto complete field.
1
 
Todd NelsonSystems EngineerCommented:
Like Simon stated, the email address is not the same eventhough it may be spelled exactly the same.  As a result, I assume that when you attempt to use Outlook, you get the NDR internally, right?

You should be able to create an X500 address.  Or you might be able to delete the autocomplete (name cache) name that pops up as you are typing the address in the "To:" field in Outlook. After you delete it, type the complete address again and it should send fine.

Refer to this article about send issues with recreated mailboxes ... https://oddytee.wordpress.com/2014/08/22/imceaex-ndrs-after-migrating-psts-to-office-365/)
0
 
zito2000Author Commented:
Thank you Simon and Todd.  I was hoping it was going to be as easy as deleting the autocomplete and sending an email from the GAL, but it didn't work.  
I'm trying to add the X500 address, but not having any luck there. Do you know how I can make sure I'm adding the X500 address correctly?
I'm trying to do some internet searching, but I'm seeing a lot of different feedback.

Thank you again for your time.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Todd NelsonSystems EngineerCommented:
The article here (https://support.microsoft.com/en-us/kb/2807779) is linked in the article I referenced and provides exactly how the address needs to be created.

I know it refers to O365 but the resolution is the same.
0
 
zito2000Author Commented:
That article was great, and it looks like I have everything right, but the problem still exists.  I took:
IMCEAEX-_O=USA_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=SERVICE885F33974B762EE1DECCC29508FABA37456FE5@DOMAIN.com

And converted it to:
x500:/O=USA/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=SERVICE885F33974B762EE1DECCC29508FABA37456FE5

I thought that this was the issue, but I'm still having the problem.  I'm making sure to delete my Autocomplete and pick the address from the GAL every time, but I'm getting bouncebacks.  It works FINE from Outlook Web Access and external senders.
0
 
zito2000Author Commented:
Thanks to you all, the problem is resolved.

The one important note is:
Make sure you replicate your domain controllers after you make the change
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now