Re: mailbox disabled

Sorry, I see what you mean - my examples of firstname@xxxxxxxxxx on the
recipient side. My mistake with the examples.

To try and clarify (my mistake, not yours), their server only accepts email
for one domain - domain.net. The reciepient policy reflects this. They are
not trying to have, and do not want, any other domains served and their are
no other domains involved.

When the user accounts on the server were initially created the client
wanted first initial, last name. So the email addresses were automatically
the same. NONE of these would work and anyone sending e-mail from outside
the network would receive the "mailbox has been disabled" NDR. Inside the
network, life was good.

As an example - if dallen was the login name then dallen@xxxxxxxxxx would be
the default e-mail address. When the e-mail didn't work from the outside to
those addresses, we also added additional SMTP addresses in the form of
doug@xxxxxxxxxxx For an unknown (to us) reason, this worked with both of the
2 original accounts. They are still successfully using the additional
addresses and mail is still being rejected at the 1stinitiallastname
addresses stating that the mailbox is disabled even though both doug and
dallen type addresses use the same mailbox. I have even tried deleting the
original addresses and then re-adding them - same result.

After a couple of weeks of trying to resolve through the newsgroups and
directly with Microsoft, we were told to re-install. Since the added
addresses were working, and there were no other apparent problems, the client
did not want to do this.

That is how things have been left for several months until other employees
have been recently given network and e-mail accounts. The customer has been
trying to manage the network and they created the accounts. We weren't
contacted again until it became obvious that the new users weren't getting
e-mail and anyone sending from the outside was receiving an NDR.

The accounts appear to be correct but, with the new accounts, even adding
the additional SMTP address doesn't work. I can see nothing glaringly wrong
with the server, the user accounts, mailboxes or Exchange. We have over 50
servers setup identical to this one with no probelms. We have been working
with Exchange servers since 5.5 and have never seen this.

Thanks again,

Doug

"Lanwench [MVP - Exchange]" wrote:

In news:6761E427-BE46-401C-8D8E-B79F562AAE54@xxxxxxxxxxxxx,
Doug <Doug@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Not a silly question at all-

This error message was from my server(domain.com) stating that it had
been told the mailbox was disabled on the recipient
server(domain.net). Hope this clarifies my original post.

Actually, that doesn't really clarify it, alas. I wasn't referring to
mydomain.com - just that you mention domain.com & domain.net in the
*recipient* bits here. Let's start over.

What is in the recipient policy in Exchange on the SBS box in questoin?
And, what e-mail addresses are defined in this recipient's mailbox
properties?




"Lanwench [MVP - Exchange]" wrote:

In news:5C8C8A7B-89A3-4C25-826B-055125AFF4B2@xxxxxxxxxxxxx,
Doug <Doug@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Windows 2003 Small Business Server Service Pack 1
Exchange 2003 Service Pack 2
All updates, patches, etc are up-to-date.

When sending email within the network, everything is fine. When
sending from the outside to several of the accounts inside (not all)
the following message is received-

Your message did not reach some or all of the intended recipients.
Subject: test
Sent: 10/4/2006 8:29 AM
The following recipient(s) cannot be reached:
mbennington@xxxxxxxxxx on 10/4/2006 8:30 AM
The message reached the recipient's e-mail system, but
delivery was refused. Attempt to resend the message. If it still
fails, contact your system administrator.
<mydomain.com #5.2.1 smtp;550 5.2.1
<mbennington@xxxxxxxxxx>... Mailbox disabled for this recipient>

User and e-mail accounts appear to be setup correctly - we have over
50 servers configured as this one with no problems. The mailboxes
are not disabled - internal e-mail works fine. There are currently
only 4 users on this box. Two accounts are working and two are
exibiting this behaviour. The original 2 that are now working had
this identical problem when first setup but we changed the email
addresses from the default firstinitiallastname@xxxxxxxxxx to
firstname@xxxxxxxxxx and they started working correctly although you
will still receive the error if you try to send to the original
address (which still exists on their user account). We tried this
with these two additional accounts and it didn't help.

I originally posted to the newsgroups with the first two users on
this system about 6 month ago (not sure which group - SBS or
Exchange) and after several replies it we could not find the cause
and it was recommended that the server be re-installed. The
customer did not want to do that and since the alternate addresses
were working nothing was done. Now that the company is growing and
additional people are being added, we need a resolution.

Any ideas?

Thanks,
Doug

Silly question, maybe, but the example address in the NDR is
somebody@xxxxxxxxxx - and in your description below that, you've got
somebody@xxxxxxxxxxx Do you use both domain.com and domain.net, and,
if so, are both of those domains set up in your recipient policy,
with the appropriate addresses set on each user's mailbox?




.

Relevant Pages

  • The Esc Character.
    ... I then tried Mac help for the Mac email client that I use with effectivity to find the article I copy and paste below. ... where I selected all of the messages and then clicked on Remove From Server. ... My mailbox is over its quota ... For .Mac or IMAP accounts, click the Size header to find the largest mail folders on your server. ...
    (comp.sys.mac.misc)
  • Re: mailbox disabled
    ... When the user accounts on the server were initially created the client ... e-mail from outside the network would receive the "mailbox has been ... had been told the mailbox was disabled on the recipient ...
    (microsoft.public.exchange.admin)
  • Re: mailbox disabled
    ... POP3 provider was still being used as a backup. ... it was a server problem. ... just from the senders' servers stating that the mailbox was ... I stepped back today to see what the accounts that were working ...
    (microsoft.public.exchange.admin)
  • Re: mailbox disabled
    ... Your POP3 connector question made me realize that the ... we got tunnel vision thinking it was a server problem. ... that the mailbox was disabled. ... I stepped back today to see what the accounts that were working seemed to ...
    (microsoft.public.exchange.admin)
  • Re: How to recover from crashed server?
    ... For each of the accounts, remove its Exchange attributes. ... mailbox on the new server. ... recovery storage group and into the new mailbox. ...
    (microsoft.public.exchange.admin)