Your message did not reach some or all of the intended recipients.

Discussion in 'Windows Small Business Server' started by MLA!, Sep 21, 2005.

  1. MLA!

    MLA! Guest

    Hi,
    I have a problem with one user (honestly I forgot to ask couple others who
    may need to distribute product update to multiple recepients).

    When he sends a message to bunch of recepients he gets the message below
    for each name.
    Here no error code. I found some KB with the same message but there is error
    code and a situation is different.
    I even switched from smart host to DNS resolution.
    But now it's clear I have Exchange issue.
    Please help. This is marketing guy an he needs to do his job.

    Michael.


    Your message did not reach some or all of the intended recipients.

    Subject: New Product Announcement: Active VGA Balun Kit (500035,
    500036)

    Sent: 9/19/2005 9:48 AM


    The following recipient(s) could not be reached:

    Jeff Herman on 9/19/2005 9:48 AM

    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.

    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
     
    MLA!, Sep 21, 2005
    #1
    1. Advertisements

  2. Hello Michael,

    Thank you for posting in the SBS newsgroup.

    From the current error information:

    The following recipient(s) could not be reached:

    Jeff Herman on 9/19/2005 9:48 AM

    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.

    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO

    To narrow down this issue, please answer and perform the following
    questions and steps:

    Does this issue occur when you send internal or external recipients? Please
    help me re-confirm the specific Jeff Herman is internal or external
    recipient?

    - If this issue only occurs with the specific recipient Jeff Herman,
    this issue could be caused by the recipient is set to received email only
    from limited users or the sender account has issue. To narrow down this
    issue, I would like to suggest following test and troubleshoot it.

    1) Please open Server Management and navigate to Users node. Open the
    properties page of "Jeff Herman". In the Exchange General tab, please
    click "Delivery Restrictions" button. In the Message restrictions, please
    confirm from everyone is checked.

    2) Please check if the problematic user can send emails to external
    (internet) recipients?

    3) Please create a new user and check if the new user can send emails to
    these recipients.

    4) Please check if this user has valid email addresses (SMTP, X.400) in
    the email addresses tab of user properties page.

    5) Please check if this issue is correctly listed in the Global Address
    list, if you manually type the email address of the Jeff Herman, and then
    check if the issue can be reproduced.

    6) Do you have Recovery Storage group enabled on the SBS server?

    7) Please try to create a new Outlook profile for Jeff Herman, then check
    if the issue can be reproduced:

    829918 OL2003: How to create a new e-mail profile in Outlook 2003
    http://support.microsoft.com/default.aspx?scid=KB;EN-US;829918

    8) Use the message tracking feature to track the problematic message.
    Provide me with a screen of the results. For additional information, refer
    to the following Knowledge Base Article:

    823864 Improved Message Tracking Features in Exchange Server 2003
    http://support.microsoft.com/?id=823864
    Note: You need to enable Message Tracking first. To do so, on the General
    tab in the server's Properties dialog box, select the Enable message
    tracking check box.

    - If it is not the case, please help me collect more information:

    1) What's the common issue of the problematic external recipients?

    2) Please kindly paste the all contents of these NDR in your reply.

    3) Use the message tracking feature to track the problematic message.
    Provide me with a screen of the results.

    4) Enable Diagnostic Logging to determine the root of the transport issue.
    To enable Diagnostic Logging on the MSExchangeTransport service:

    a. Start Exchange System Manager.

    b. Navigate to the server object.

    c. Right-click <Server object>, and then click Properties.

    d. Click the Diagnostic Logging tab.

    e. Under Categories, click MSExchangeTransport.

    f. Under Logging Level, choose maximum for all the items. Restart the
    server.

    g. Let a user send an outbound message and copy all Exchange relative
    events in Event Viewer.

    For more information regarding how to troubleshoot Exchange problems,
    please refer to the following article:

    General troubleshooting for transport issues in Exchange 2000 Server and in
    Exchange Server 2003
    http://support.microsoft.com/?id=257265

    5). Enable SMTP logging and gather SMTP log to troubleshoot the issue:

    A. Open Exchange System Manager, expand Servers -> <Server name> ->
    Protocols -> SMTP, right-click "Default SMTP Virtual Server" and click
    Properties.

    B. Under the General tab, check the option "Enable Logging".

    C. With "W3C Extended Log File Format", click "Properties".

    D. Under "General Properties", make sure "Use local time for file naming
    and rollover" is CHECKED.

    E. Switch to the "Extended Properties", and then select to enable All the
    logging Options.

    F. Click OK to apply the modification.

    G. Right-click Default SMTP Virtual Server and click Stop.

    H. Right-click Default SMTP Virtual Server and click Start to restart the
    SMTP server.

    I. Reproduce the issue, repeat step G to stop Default SMTP Virtual Server,
    copy out or zip the SMTP log files in the
    "%systemroot%\system32\logfiles\SmtpSvc1" folder, and then restart the
    "Default SMTP Virtual Server".

    I appreciate your time and cooperation. If anything is unclear, please feel
    free to let me know. I am looking forward to hearing from you.

    Best regards,

    Nathan Liu (MSFT)
    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security
    ======================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    ======================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
     
    Nathan Liu [MSFT], Sep 22, 2005
    #2
    1. Advertisements

  3. MLA!

    MLA! Guest

    Nathan,
    thank you for trying to help me.
    I will start over. Because now I have more info. My user is in remote office.
    So I collect info bit by bit.
    The sender is my Jeff Herman.
    He creates a message in ACT this message goes to Outlook 2003 the draft
    folder, he sends it from the draft folder.
    I asked him to make a test.
    He copied 30 addresses into Word. After pasted to BCC line. And he typed one
    address in To line. Message gone.
    So Exchange doesn't prevent him to send to multiple addresses.
    Before SBS 2003 implementation (August) he used Eudora mail server with
    Outlook 2000 and the same version of ACT(6).
    Now he asks me why he cannot work with Exchange.
    He always sends a message in the same manner.
    In To line he types his e-mail address. In BCC multiple outside recepients
    addresses
    I switche from smart host to DNS resolution in case that ISP rejects bulk
    e-mails.

    Now it's clear for me that my Exchange doesn't "like" messages created in ACT.

    ACT was installed after Outlook2003.
    If you have other questions I will give you more answers.

    In the mean time how I can track why Exchange gives all this:

    From: System Administrator
    Sent: Monday, September 19, 2005 9:48 AM
    To: Jeff Herman
    Subject: Undeliverable:New Product Announcement: Active VGA Balun Kit
    (500035, 500036)
    Your message did not reach some or all of the intended recipients.
    Subject: New Product Announcement: Active VGA Balun Kit (500035,
    500036)
    Sent: 9/19/2005 9:48 AM
    The following recipient(s) could not be reached:
    Jeff Herman on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Bass Home Electronics, Inc on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Burcaw Company on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at C.R. Kennedy on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Cabletel Technologies (BC on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    ' at Cabletel Technologies (NS)' on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    ' at Cabletel Technologies (ON)' on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    ' at Cabletel Technologies (QC)' on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Cabling Technologies on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at CCTV Security Products Division on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Chesapeake Smart Homes on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Coaxial Systems Assoc., Inc. on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Hi-Fi Heaven on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at HMR Security & Sound on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at I.D.M.C. INc. on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Inmac on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at M.A.R. Corp. on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at MODERN SYSTEMS on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Rancilio Associates INc. on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Rancilio Associates, Inc. on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at S/R Marketing on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Sandone Electric on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Security and Safety Consultants on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO
    at Security and Safety Consultants on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO




    By the way

     
    MLA!, Sep 23, 2005
    #3
  4. MLA!

    MLA! Guest

    Nathan,
    I found that this thing could be weird for Exchange:
    see second recepient. what is "at Bass Home Electronics, Inc"
    it comes from ACT...
    at Bass Home Electronics, Inc on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO


    The following recipient(s) could not be reached:
    Jeff Herman on 9/19/2005 9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO



    at Bass Home Electronics, Inc on 9/19/2005
    9:48 AM
    You do not have permission to send to this recipient. For
    assistance, contact your system administrator.
    MSEXCH:MSExchangeIS:/DC=local/DC=setco:JUNO


     
    MLA!, Sep 23, 2005
    #4
  5. Hi Michael,

    Thank you for your detailed reply.

    To narrow down this issue, please help me re-confirm the following
    information:

    1. Does this issue only occur when you are using the third-party software
    (ACT! 6┬ĘC Contact & Customer Management Software) with Outlook 2003 to send
    outbound emails? If you only use the Outlook and manually input the
    recipients' email addresses, and try again to check if the issue can be
    reproduced.

    2. This issue could most likely be related to the third-party software,
    please also try to contact the software vendor to require help. Thanks for
    understanding.

    Additionally, I suggest you also perform the following tests to check if
    the issue can be reproduced:

    1. Please use Add User Wizard to create a new user account.

    2. Create a new profile and use the new user account
    =====================
    I suggest you create a new email profile with a new PST file. Test the
    issue in the new profile. Please refer to the following article to create a
    new email profile. Please start in the new profile and provide me with the
    result.
    How to create a new e-mail profile in Outlook 2003
    http://support.microsoft.com/?id=829918

    Test 1: Safe Mode
    ==============
    Safe Mode will disable all add-ins and extensions that will not start, as
    well as all corrupted resources, files, registries and templates.
    1. Close Outlook by turn off the Outlook process using Task manager.
    2. Click Start-->Run, type "Outlook /Safe" (Quotation marks are not
    included and there is a space between Outlook and /safe) and press Enter.
    Let me know if the issue persists in the Outlook Safe Mode.
    If Safe Mode resolves the problem, please disable the Add-ins by the
    following steps:
    1. Click Tools, click Options, click Other tab.
    2. Click Advanced options button, click COM add-ins, uncheck all the
    available options.
    3. Test the issue again.

    Test 2: Clean Cache
    =================
    If the problem still occurs, it is probable that the Outlook cache files
    are corrupted. Let's perform the following steps to solve the problem.
    1. Perform a search on your computer to find the following files:
    - extend.dat
    - outcmd.dat
    - frmcache.dat
    - views.dat
    2. Rename these files to .old extension if you can find them.

    I appreciate your time and cooperation. If anything is unclear, please feel
    free to let me know. I am looking forward to hearing from you.

    Best regards,

    Nathan Liu (MSFT)
    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security
    ======================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    ======================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
     
    Nathan Liu [MSFT], Sep 23, 2005
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.