Subject: Fwd: Undeliverable: Another mistake HFL
From: Ashish Dabral <[email-masked]>
To: Dhirendra <[email-masked]>
Date: Wed, 14 Feb 2018 12:07:34 +0530 (IST)

Regards, 
Ashish Dabral 

From: "Deeksha Dadu" <[email-masked]> 
To: "Ashish Dabral" <[email-masked]> 
Sent: Tuesday, February 13, 2018 8:33:44 PM 
Subject: FW: Undeliverable: Another mistake HFL 

This is the message I am getting, please check what’s happening 

From: Microsoft Outlook < [email-masked] > 
Date: Tuesday, 13 February 2018 at 8:28 PM 
To: " [email-masked] " < [email-masked] > 
Subject: Undeliverable: Another mistake HFL 

DSN 

	Your message to [email-masked] couldn't be delivered. 

	direndra wasn't found at lsmindia.com . 

	deeksha 	Office 365 	direndra 
	Action Required 		Recipient 

	Unknown To address 		

	How to Fix It 
	The address may be misspelled or may not exist. Try one or more of the following: 

    * Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link " To send this message again, click here. " Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send . 
    * Contact the recipient (by phone, for example) to check that the address exists and is correct. 
    * The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly. 
    * Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365 , and then send the message again. Retype the entire recipient address before selecting Send . 

	If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below. 
	
Was this helpful? Send feedback to Microsoft . 

	
More Info for Email Admins 
	Status code: 550 5.1.1 

This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following: 

The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages. 

Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory. 

Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature. 

Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly. 

For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365 . 

	Original Message Details 
	
	Created Date: 	2/13/2018 2:58:40 PM 
	Sender Address: 	[email-masked] 

	Recipient Address: 	[email-masked] 

	Subject: 	Another mistake HFL 
	
Error Details 
	
	Reported error: 	550 5.1.1 < [email-masked] >: Recipient address rejected: lsmindia.com 
	DSN generated by: 	SIXPR04MB0681.apcprd04.prod.outlook.com 
	Remote server: 	mail.lsmindia.com 

	Message Hops 
	HOP 	TIME (UTC) 	FROM 	TO 	WITH 	RELAY TIME 
	1 	2/13/2018 
2:58:40 PM 	SIXPR04MB0842.apcprd04.prod.outlook.com 	SIXPR04MB0842.apcprd04.prod.outlook.com 	mapi 	* 
	2 	2/13/2018 
2:58:41 PM 	SIXPR04MB0842.apcprd04.prod.outlook.com 	SIXPR04MB0681.apcprd04.prod.outlook.com 	Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) 	1 sec 

Original Message Headers 
From: Deeksha Dadu < [email-masked] >
To: " [email-masked] " < [email-masked] >, " [email-masked] "
	< [email-masked] >, Deepak Chauhan < [email-masked] >, Subir
 Chakma < [email-masked] >, Subhojit Hati < [email-masked] >, Uday
 Singh < [email-masked] >, Harsh Srivastava < [email-masked] >,
	" [email-masked] " < [email-masked] >, " [email-masked] "
	< [email-masked] >
CC: "Pritish Nandi[LSM]" < [email-masked] >, " [email-masked] "
	< [email-masked] >
Subject: Another mistake HFL
Importance: high
Date: Tue, 13 Feb 2018 14:58:40 +0000
Accept-Language: en-US
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM

Subject: Another mistake HFL
From: Deeksha Dadu <[email-masked]>
To: "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>, Deepak Chauhan <[email-masked]>, "Subir Chakma" <[email-masked]>, Subhojit Hati <[email-masked]>, "Uday Singh" <[email-masked]>, Harsh Srivastava <[email-masked]>, "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>
Cc: "Pritish Nandi[LSM]" <[email-masked]>, "[email-masked]" <[email-masked]>
Date: Tue, 13 Feb 2018 14:58:40 +0000

We just caught more cases where in agent cancelled the auto ship but never checked when the next shipment is due, resulting in an upset customer and dispute threat. This is when I had sent a reminder just a few days back! What is happening people? All this is clearly mentioned in fresh desk but I am still having to sent repetitive reminders. I need ALL of you to go through backend interface and general FAQ section thoroughly in fresh desk and make sure that these errors don’t occur again. Now onwards, whenever I see a careless mistake like this again, that agent will be simply marked absent for the day. Depending on the gravity of your mistake, penalty could be stricter.

https://lsmindia.freshdesk.com/solution/folders/6000036255

https://lsmindia.freshdesk.com/solution/folders/6000044279

When someone comes to cancel auto ship, you MUST also check when the next shipment is due and inform the customer about it. If it is already processed or is about to be processed in less than 3-4 business days, inform the custom that we usually require 3-4 business days notice to stop the next shipment but you will contact your shipping department to see if it can still be stopped but make it clear that you can't guarantee. Email Deb right away to see if she can stop the shipment and inform customer accordingly. If it is more than 3-4 days then you should be able to stop it but escalate to Deb immediately. If it is already shipped, you must inform the customer   If it is less than that or if the next shipment is already shipped out, again politely inform the customer that you usually require 3-4 business days notice to stop a shipment. If they are upset, try telling them to keep the order and you are authorised to refund 50% (the same way we do in case of returns). if they agree, again inform Deb to refund 50%. If they are too upset, don't even try that and straight away, tell them to refuse the shipment and ask Deb to process full refund.

Regards,
Deeksha