locked
Bounce back on external email to group RRS feed

  • Question

  • Hello everyone,

    Once again, asking for help. I set up a distro group with external email address. When I email the group internally from the domain, it works fine. but if I email the group externally, I get a bounce back. The rejected server is coming from my server.  I did set up the group to send to internal and external emails.

    *Note: We did upgrade from exchange 2010 to 2016 a month ago and the group is set to send internal and external emails. Not sure what is the causing the issue. Could it be a receive connector

    Error message below:

    ---------- Forwarded message ---------
    From: <postmaster@mycompany.com>
    Date: Mon, Apr 23, 2018, 10:25 AM
    Subject: Undeliverable: Test
    To: <kenny.admin@gmail.com>

    Delivery has failed to these recipients or groups:
    g.c@external.us
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
    d.c@external.us
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
    w.w@external.us
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
    The following organization rejected your message: mail.mycompany.com.


    Diagnostic information for administrators:
    Generating server:mycompany.com
    g.c@external.us
    mail.mycompany.com #554 5.7.1 Relaying denied ##
    d.c@external.us
    mail.mycompany.com #554 5.7.1 Relaying denied ##
    w.w@external.us
    mail.mycompany.com #554 5.7.1 Relaying denied ##
    Original message headers:

    Received: from SA-EXDR-P01.mycompany.local (192.168.122.184) by
     BOEX1.mycompany.local (192.168.127.210) with Microsoft SMTP Server (TLS) id
     14.3.382.0; Mon, 23 Apr 2018 10:23:04 -0500
    Received: from SA-EX-P01.mycompany.local (192.168.122.241) by
     SA-EXDR-P01.mycompany.local (192.168.122.184) with Microsoft SMTP Server
     (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id
     15.1.1261.35; Mon, 23 Apr 2018 10:23:03 -0500
    Received: from mail.mycompany.com (192.168.122.5) by
     SA-EX-P01.mycompany.local (192.168.122.241) with Microsoft SMTP Server
     (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id
     15.1.1261.35 via Frontend Transport; Mon, 23 Apr 2018 10:23:04 -0500
    Received: from mail-wr0-f177.google.com (mail-wr0-f177.google.com
     [209.85.128.177]) by mail.mycompany.com  with ESMTP id
     w3NFOtLB010583-w3NFOtLD010583 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA
     bits=128 verify=NOT) for <tigaproject@mycompany.com>; Mon, 23 Apr 2018
     10:24:56 -0500
    Received: by mail-wr0-f177.google.com with SMTP id v60-v6so42413595wrc.7
            for <tigaproject@mycompany.com>; Mon, 23 Apr 2018 08:24:56 -0700
     (PDT)
    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
            d=gmail.com; s=20161025;
            h=mime-version:from:date:message-id:subject:to;
            bh=nWudKbw3UE7LOU8U1HUxXs+teQDZ8JUUBwrFIrUoiz8=;
            b=PkpodLDtbfKnPphfr3rqbOUh841+2dQX7eHl7Jjgo9IGIwNFtk0HWLz0meaYEVucSX
             JZc9ku7Ap4QW4yYnW7LiIrDwrksRcQpM28yOv2+SzM2sr+JmnBoziwulFF0DF5JLkKTC
             CyXtn9fLkqpZj/AOHFfhPiKd608gq39nDFM/57Atcv0EFqEZJqhkq4aRbUg+HsLmEI/1
             nUSSe6U8qKlcvyEk6QYBjDS6hIifE1izLmsWBzzJ+WWG/3BYh7D4q3bsbmxzGtVz+xhP
             p1S6MPwUBXu+UvoNtk00YNV6snEjdDQPyRXArrXJ/c3FtwLa4hzluHKe7glil1Zy3poH
             OCzQ==
    X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
            d=1e100.net; s=20161025;
            h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
            bh=nWudKbw3UE7LOU8U1HUxXs+teQDZ8JUUBwrFIrUoiz8=;
            b=lL1myleEL3y4Up6hXxFmm2Xne720TWIT9t2pbFhv08GPRvoVnUwgpBmKoZvjXG5J4l
             tufFJaoRg97zYtYliFqNePCFzRBfB3UG0dYO/gTYHsJUMSWjWWegV5NzFOTjTAsTJLhR
             K22EcaRIfiG/B45wLENOib28vdGA4a32WgGr7EH5v787eMudJxgDCevmXPuRVgdwrsLJ
             iSO4vweVB4/SqZf+T4Y4PjyVdHeDTnUptUoDBqEyviCU7qWiqV4lNtwErxKRB5uiATr0
             DX1cm73cxcHyjHPYTP3gUeV1mS3Bo24vzMiJ8/nZ/5dj3GAkP1FCU7hRaougFHRQDIzJ
             mnQg==
    X-Gm-Message-State: ALQs6tBzKUy9dloUftDVvAtfJr7/G3tufNDSbPxtonp25rqZBFMxIS7d
    pjLg+ec26yeuY2GpEPVuuncmGd8lG5/iD70qG3U=
    X-Google-Smtp-Source: AIpwx4/w13L9YbByZR3pRvMNXwSP2LOr2xI3DCmE1MFrjDkK5H4ELarzn6AKnqCY+B9zSsaS3q/iCO/Q3udKOaczH18=
    X-Received: by 10.167.197.83 with SMTP id s19mr11893642edr.139.1524497094976;
     Mon, 23 Apr 2018 08:24:54 -0700 (PDT)
    MIME-Version: 1.0
    From: Kenny Placido <Kenny.admin@gmail.com>
    Date: Mon, 23 Apr 2018 15:24:44 +0000
    Message-ID: <CAPxCpbS5ZvMtHdZ_8N-YNi-NQK=tk_3evQ9ebVTVF_C4B6ZNxA@mail.gmail.com>
    Subject: Test
    To: <tigaproject@mycompany.com>
    Content-Type: multipart/alternative; boundary="883d24f6aed4ceaa90056a85a362"
    X-FEAS-SPF: pass, ip=209.85.128.177, helo=mail-wr0-f177.google.com, mailFrom=kenny.admin@gmail.com
    X-FEAS-DKIM: Valid
    Authentication-Results: mail.mycompany.com;
    spf=pass (mycompany.com: domain of kenny.admin@gmail.com designates 209.85.128.177 as permitted sender) smtp.mailfrom=kenny.admin@gmail.com;
    dkim=pass header.i=@gmail.com
    Return-Path: kenny.admin@gmail.com
    X-Auto-Response-Suppress: DR, OOF, AutoReply

    • Edited by Fenikas Monday, April 23, 2018 4:02 PM
    Monday, April 23, 2018 3:37 PM

Answers

  • Hi,

    Based on your description, I know that you are getting the issue that external users receive the NDR message when sending to the DG.

    Did issue occur for all groups or only one group?

    For troubleshooting:

    1. Please check the group settings in EAC:

    1> Make sure that all senders can send message to the group.

    2> Confirm if the checkbox "Messages sent to this group have to be approved by a moderator" is unchecked. If it is checked, confirm if the moderator rejected the message sent to the group.

     

    2. Check if there is any related transport rules to block the inbound message to the group.

    Regards,

    Manu Meng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by seanmcavinue Tuesday, April 24, 2018 8:00 AM
    • Edited by Manu Meng Tuesday, April 24, 2018 9:10 AM
    • Marked as answer by Fenikas Wednesday, April 25, 2018 3:50 PM
    Tuesday, April 24, 2018 4:41 AM