Subject: Undeliverable: Re: Process Violation - Manual CIR AWB Creation Issue
From: <[email-masked]>
To: <[email-masked]>
Date: Mon, 7 Jun 2021 15:22:57 +0000

[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to [email-masked] couldn't be delivered.
The group HB.CCCKSA only accepts messages from people in its organization or on its allowed senders list, and your email address isn't on the list.
niren.dsouza    Office 365      HB.CCCKSA
Sender          Action Required
Sender not allowed

How to Fix It
It appears you aren't in the same organization as the group (or a sub-group) you're sending to or your email address isn't on the group's allowed senders list. Ask the owner of the group to grant you permission to send to it, and then try again. If the group belongs to a different organization than yours, contact the organization's customer service department for assistance. If the group is in your organization and you don't know who the group owner is, you can find it by doing the following in either Outlook on the web or Outlook:

  *   Open your Sent folder and select the original message.
  *   If you're using Outlook on the web, select the group name located on the To or CC line. If you're using Outlook, double-click the group name located on the To or CC line.
  *   In Outlook on the web, from the pop-up dialog box, choose Owner. In Outlook, choose Contact. The owner's name is listed under Owner.

The owner of the group may have intentionally chosen to restrict who can send messages to it, and they may not want to adjust the existing restriction. In this case, you'll have to contact the group members by some other means, such as sending an email message to their individual email addresses or contacting them by phone.

Was this helpful? Send feedback to Microsoft<https://go.microsoft.com/fwlink/?LinkId=615007>.
________________________________

More Info for Email Admins
Status code: 550 5.7.133

This error occurs when the distribution group, security group, or Microsoft 365 group is configured to accept messages only from authenticated senders (senders in the same organization or those added to the group's allowed senders list).

To fix the issue, the recipient's email admin or the group owner must add the sender's email address to the group's allowed senders list or change the group's delivery management setting to accept messages from senders inside and outside of the organization.

Usually this issue can only be fixed by the recipient's email admin or the group owner.

For more information and steps to fix this error, see Fix email delivery issues for error code 5.7.133 in Office 365<https://go.microsoft.com/fwlink/p/?LinkId=615127>.

Original Message Details
Created Date:   6/7/2021 3:22:51 PM
Sender Address: [email-masked]
Recipient Address:      [email-masked]
Subject:        Re: Process Violation - Manual CIR AWB Creation Issue

Error Details
Reported error: 550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup; authentication required; Delivery restriction check failed because the sender was not authenticated when sending to this group
DSN generated by:       AS8PR09MB4536.eurprd09.prod.outlook.com

Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       6/7/2021
3:22:51 PM      mail.lsmindia.com       mail.lsmindia.com       ESMTP   *
2       6/7/2021
3:22:51 PM      mail.lsmindia.com       localhost       ESMTP   *
3       6/7/2021
3:22:52 PM      localhost       mail.lsmindia.com       ESMTP   1 sec
4       6/7/2021
3:22:52 PM      mail.lsmindia.com       localhost       ESMTP   *
5       6/7/2021
3:22:53 PM      localhost       mail.lsmindia.com       ESMTP   1 sec
6       6/7/2021
3:22:55 PM      mail.lsmindia.com       DB5EUR03FT003.mail.protection.outlook.com       Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    2 sec
7       6/7/2021
3:22:55 PM      DB5EUR03FT003.eop-EUR03.prod.protection.outlook.com     DB6PR07CA0007.outlook.office365.com     Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *
8       6/7/2021
3:22:55 PM      DB6PR07CA0007.eurprd07.prod.outlook.com AS8PR09MB4536.eurprd09.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *

Original Message Headers

Date: Mon, 7 Jun 2021 08:22:51 -0700 (MST)
From: Niren  Dsouza <[email-masked]>
To: Yahia Taha <[email-masked]>
CC: Layan Shehadeh <[email-masked]>,
        Raneem Alqutub <[email-masked]>,
        Nada Hattar <[email-masked]>,
        Rozan Abdelraziq <[email-masked]>,
        "HB.CCCKSA" <[email-masked]>,
        ArishLaila <[email-masked]>,
        Karim Asklany <[email-masked]>,
        Mohammad Ayaz <[email-masked]>,
        Ramesh Gottimukkala <[email-masked]>,
        Jessie Caparas <[email-masked]>,
        Mustehsan Siddiqui <[email-masked]>,
        Alexander Gomes <[email-masked]>,
        saurabh <[email-masked]>,
        Hasan Razakhan <[email-masked]>
Subject: Re: Process Violation - Manual CIR AWB Creation Issue
 =?utf-8?B?S2phOTdHZGdZcjk4UDJzVTQrdFlRNlhMQ0FCVGdnUlV0TGdnS3QyNDJXSVZO?=
 =?utf-8?B?dHVRaGFLZWtZRDFGQ29GL3UxdlVZbk1HSlZsSC9VRDJNWXp0bEE2T1FHZDYz?=
 =?utf-8?B?RlJ0ckx4MnljMDVBRFpqdkVvdEEzWElLSDRQUlloWWRhRlNSa2sxUzZzUEts?=
 =?utf-8?B?Ung3YUdNL3VLcVBDb2NWNEkweitvekdCMkVOd1k1YWFSNlN0d2x3b2JrZ0lY?=
 =?utf-8?B?WDB5Q2J1QnFiVEhLNFJGM1g2WjRiS3dwejhiNllWUzkvaEF1OUlNUyt5engw?=
 =?utf-8?B?aXd2RENFS21aRzB0L0NGSW5rZW5sSkEzMzdkcnVEVjkrYmI1amdrZGhmdCti?=
 =?utf-8?B?QTdzWXdqQml5bTNOQnQrcm9iUndibndUbVJWQjdRQk5MdzhQOHIvNHNRNkhX?=
 =?utf-8?B?UVFqSnF1eWN0d0lPNVE9PQ==?=
X-Forefront-Antispam-Report: CIP:108.170.60.122;CTRY:US;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:mail.lsmindia.com;PTR:InfoDomainNonexistent;CAT:NONE;SFS:(4636009)(26005)(36756003)(86362001)(83380400001)(66574015)(166002)(81166007)(356005)(54906003)(7696005)(53546011)(956004)(30864003)(75640400001)(5660300002)(336012)(4006050)(15974865002)(45080400002)(450100002)(4326008)(2616005)(1096003)(8676002)(426003)(6266002)(33964004)(44832011)(6862004)(54256004)(72826004);DIR:INB;

Subject: Re: Process Violation - Manual CIR AWB Creation Issue
From: Niren Dsouza <[email-masked]>
To: Yahia Taha <[email-masked]>
Cc: Layan Shehadeh <[email-masked]>, Raneem Alqutub <[email-masked]>, Nada Hattar <[email-masked]>, Rozan Abdelraziq <[email-masked]>, "HB.CCCKSA" <[email-masked]>, ArishLaila <[email-masked]>, Karim Asklany <[email-masked]>, Mohammad Ayaz <[email-masked]>, Ramesh Gottimukkala <[email-masked]>, Jessie Caparas <[email-masked]>, Mustehsan Siddiqui <[email-masked]>, Alexander Gomes <[email-masked]>, saurabh <
Date: Mon, 7 Jun 2021 08:22:51 -0700 (MST)

External email sender, please take precaution.

Hi Yahia,

Duly noted and informed.

Niren D'Souza
Team Manager
[email-masked]

________________________________
From: "Yahia Taha" <[email-masked]>
To: "Layan Shehadeh" <[email-masked]>, "Raneem Alqutub" <[email-masked]>, "Nada Hattar" <[email-masked]>, "Rozan Abdelraziq" <[email-masked]>, "Niren Dsouza" <[email-masked]>, "HB.CCCKSA" <[email-masked]>
Cc: "ArishLaila" <[email-masked]>, "Karim Asklany" <[email-masked]>, "Mohammad Ayaz" <[email-masked]>, "Ramesh Gottimukkala" <[email-masked]>, "Jessie Caparas" <[email-masked]>, "Mustehsan Siddiqui" <[email-masked]>, "Alexander Gomes" <[email-masked]>, "saurabh" <[email-masked]>, "Hasan Razakhan" <[email-masked]>
Sent: Monday, June 7, 2021 6:44:21 PM
Subject: RE: Process Violation - Manual CIR AWB Creation Issue

Dear team

Please check below update and inform your team to follow the same, strictly not allowed to create manual AWBS.

Best Regards
Yahia Taha
Customer Care Team Leader - Home box
800-1110888
Ext: 3457
Riyadh Gallery Mall I PO Box 91861 | Riyadh 11643 l Saudi Arabia
www.homeboxstores.com<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.homeboxstores.com%2F&data=02%7C01%7Cyahia.taha%40landmarkgroup.com%7Cec28e3c31ccf444c531008d85f08dafa%7C1f9b09b4197c4f1cb0c5571a6ccc96c8%7C0%7C0%7C637363838960986330&sdata=CzDg2vAtQD5CTi%2Bv9vKUiECOF5VcIbuwGzDWImDgzd0%3D&reserved=0> | www.landmarkgroup.com<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.landmarkgroup.com%2F&data=02%7C01%7Cyahia.taha%40landmarkgroup.com%7Cec28e3c31ccf444c531008d85f08dafa%7C1f9b09b4197c4f1cb0c5571a6ccc96c8%7C0%7C0%7C637363838960996327&sdata=1M6qxxiDpPF8W8JPP0QPEQUfhqD3HGw%2BSIsCuXQLGI8%3D&reserved=0>
[lg][hb]

From: Alexander Gomes <[email-masked]>
Sent: Monday, June 7, 2021 2:50 PM
To: Yahia Taha <[email-masked]>; Momen Elmassry <[email-masked]>; Mohamad Wassim <[email-masked]>; Mustehsan Siddiqui <[email-masked]>
Cc: ArishLaila <[email-masked]>; Karim Asklany <[email-masked]>; Mohammad Ayaz <[email-masked]>; Ramesh Gottimukkala <[email-masked]>; Hisham Hamdy <[email-masked]>; Jessie Caparas <[email-masked]>
Subject: RE: Process Violation - Manual CIR AWB Creation Issue

Gentlemen,

We observe some of our agents are creating “Manual AWBs” even though system driven AWBs are available.

It is recommended that only Customer should be requested to create return request than we creating it thru our Customer Support agents.

This will eliminate wrong return from customer and complain as well as duplicate RMA numbers in System.

@Mustehsan Siddiqui<mailto:[email-masked]> – do let us know implications of removing Hybris manual RVP creation option from team.

Regards

Alex

From: Mohammad Ayaz <[email-masked]<mailto:[email-masked]>>
Sent: Saturday, June 5, 2021 12:36 PM
To: Ramesh Gottimukkala <[email-masked]<mailto:[email-masked]>>
Cc: Alexander Gomes <[email-masked]<mailto:[email-masked]>>; ArishLaila <[email-masked]<mailto:[email-masked]>>; Karim Asklany <[email-masked]<mailto:[email-masked]>>
Subject: RE: Process Violation - Manual CIR AWB Creation Issue
Importance: High

Dear @Ramesh Gottimukkala<mailto:[email-masked]>,

We are facing a lot of difficulties due to manually AWB creation from Customer support.

Many shipments in KSA Ecom Returns are pending due to this issue and also we are keep on facing it on daily basis. (Attached is a fresh example for it)

While raising it to IT, As per them they are not having resolution for reflecting it in Sahla and shipments are piling up rapidly.

Its also impacting Customer refunds and increasing Freshdesk tickets against KSA Returns which is challenging.

Please need your support to take up this issue to avoid further impact on Returns.

Regards,
Mohammad Ayaz

From: Mohammad Ayaz
Sent: Thursday, May 20, 2021 5:44 PM
To: Ramesh Gottimukkala <[email-masked]<mailto:[email-masked]>>
Subject: Process Violation - Manual CIR AWB Creation Issue
Importance: High

Dear @Ramesh Gottimukkala<mailto:[email-masked]>,

This email is to highlight the  major issue which we are facing for return shipments “Not in Sahla” is manual CIR AWB creation from CS team.

We have raised concern to IT and in working session with @Jagmohan Urmaliya (TCS)<mailto:[email-masked]> along with CS @Jessie Caparas<mailto:[email-masked]> noticed this issue and pending at Returns in bulk also for fresh returns we are facing this.

Note : Because of manual CIR AWB creation,  The AWB available on the physical shipment is invalid, While there is another AWB reflecting pending in system for same order. Therefore CIR shipments are getting pending at Returns and Customer refunds are getting pending, Increasing CS complaints as well.

Below sample Details for your reference.

6276524836 - Physical Shipment Details.
AWB : 46576299464
Order : 6276524836

6276524836 - Pending in System
AWB : 46412087562
Order : 6276524836

Regards,
Mohammad Ayaz

This e-mail message (which includes attachment/s thereto, if any, and the information therein), is legally privileged, proprietary, strictly confidential and exempt from disclosure, which is not waived or lost by mis-transmission or error. If you are not the original intended recipient of this message, it may be unlawful and illegal for you to read, print, retain, copy, disseminate, disclose or otherwise use this message, or take any action in reliance on it, and the same is prohibited and forbidden. If you have received this email in error, please notify the sender immediately by return reply and delete the message from your system without printing or making a copy. Neither the sender nor we are liable for any loss or damage as a result of this message, or for any delay, interception, corruption, virus, error, omission, improper or incomplete transmission thereof. www.landmarkgroup.com