TEAM,
PFA: NOI INDEX 2 FOR CASE CLOSURE
Aradhana Rai
NOI Coordinator | One Legal +91 8888706969
earlier mails quoted below
On Tue, 15 Sept 2026 at 12:09, NOI ICICIHFC < icicihfcnoi@ezdocs.co.in > wrote:

TEAM

PFA DOWNLOADED E FILING FOR YOUR REFERENCE

Aradhana Rai
NOI Coordinator | One Legal  +91 8888706969

On Fri, 11 Sept 2026 at 13:07, NOI ICICIHFC < icicihfcnoi@ezdocs.co.in > wrote:

Team

PFA Challan for your reference.

Aradhana Rai
NOI Coordinator | One Legal  +91 8888706969

On Fri, 11 Sept 2026 at 12:58, Avinas Bari  /DISTP/ICICIHFC/JLGN < avinas.bari@icicihfc.com > wrote:

TEAM

PFA

Thanks & Regards,

AVINASH V BARI

CREDIT ASSOCIATE JALGAON BR

From:  NOI ICICIHFC < icicihfcnoi@ezdocs.co.in >

Sent:  Friday, September 11, 2026 11:27 AM

To:  Yogesh Ramole /DIST/ICICIHFC/DHULE < yogesh.ramole@icicihfc.com >; Vijay Wahul / /ICICIHFC/ICICIHFC TOWER < vijay.wahul@icicihfc.com >; Akshay Kamerkar / /ICICIHFC/ICICIHFC TOWER < akshay.kamerkar@icicihfc.com >; Siddesh Ajvilkar / /ICICIHFC/ICICIHFC TOWER
< siddesh.ajvilkar@icicihfc.com >; Parshuram Kandurakar /EXT/OPER/ICICIHFC/ICICIHFC TOWER < parshuram.kandurakar@ext.icicihfc.com >

Cc:  Prashant Chavan /DISTP/ICICIHFC/DHULE < prashant.chavan@icicihfc.com >; Avinas Bari /DISTP/ICICIHFC/JLGN < avinas.bari@icicihfc.com >; Deepak Mahajan /DIST/ICICIHFC/DHULE < deepak.mahajan@icicihfc.com >

Subject:  Re: APPL- 77000313534 - APPLICANT NAME - RAKHI VIRU HADARE | PROCESS CHALLAN OF 0.3% & 0.5% AND NOI FILING

CAUTION:  External Email Warning - Do not click on any attachment or links/URL in this email unless sender is reliable.

Team

Kindly share the technical report and sanction letter to process the challan.

Aradhana Rai

NOI Coordinator | One Legal
+91 8888706969

On Thu, 10 Sept 2026 at 20:22, Yogesh Ramole /DIST/ICICIHFC/DHULE < yogesh.ramole@icicihfc.com > wrote:
Your message to  yogesh.ramole@icicihfc.com  couldn't be delivered.

yogesh.ramole  wasn't found at  icicihfc.com .

icicihfcnoi

Office 365

yogesh.ramole

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.10 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.10

This error occurs because the sender sent a message to an email address hosted by 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.

Recipient has a valid license  - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).

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 5.1.10 in Office 365 .

Original Message Details

Created Date:
10/1/2026 7:34:20 AM

Sender Address:
icicihfcnoi@ezdocs.co.in

Recipient Address:
yogesh.ramole@icicihfc.com

Subject:
Re: APPL- 77000313534 - APPLICANT NAME - RAKHI VIRU HADARE | PROCESS CHALLAN OF 0.3% & 0.5% AND NOI FILING

Error Details

Error:

550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient yogesh.ramole@icicihfc.com not found by SMTP address lookup

Message rejected by:
PN0PR01MB7767.INDPRD01.PROD.OUTLOOK.COM

Notification Details

Sent by:

PN0PR01MB7767.INDPRD01.PROD.OUTLOOK.COM

Message Hops

HOP
TIME (UTC)
FROM
TO
WITH
RELAY TIME

1
10/1/2026
7:40:42 AM

mail-wm2-f13.google.com
SMTP
6 min, 22 sec

2
10/1/2026
7:40:42 AM
mail-wm2-f13.google.com
MA1PEPF000072B3.mail.protection.outlook.com
Microsoft SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384)
*

3
10/1/2026
7:40:43 AM
MA1PEPF000072B3.INDPRD01.PROD.OUTLOOK.COM
MA5PR01CA0014.outlook.office365.com
Microsoft SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384)
1 sec

4
10
Keys
