<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.taxtmi.com/rss_sitemap/rss_feed_blog.xsl?v=1750492856"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>2018 (6) TMI 1868 - BOMBAY HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=464772</link>
    <description>Service of notice under Order XXI Rule 22 CPC was treated as sufficient where the WhatsApp message and PDF attachment were delivered to and opened on the respondent&#039;s mobile number. The court relied on the service record, which showed delivery and opening of the communication, and noted that the respondent was evading service. On that basis, the WhatsApp communication together with the printouts was accepted as valid service, and the notice was made absolute in favour of the applicant.</description>
    <language>en-us</language>
    <pubDate>Mon, 11 Jun 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 13 Nov 2025 15:15:08 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=864518" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (6) TMI 1868 - BOMBAY HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=464772</link>
      <description>Service of notice under Order XXI Rule 22 CPC was treated as sufficient where the WhatsApp message and PDF attachment were delivered to and opened on the respondent&#039;s mobile number. The court relied on the service record, which showed delivery and opening of the communication, and noted that the respondent was evading service. On that basis, the WhatsApp communication together with the printouts was accepted as valid service, and the notice was made absolute in favour of the applicant.</description>
      <category>Case-Laws</category>
      <law>Indian Laws</law>
      <pubDate>Mon, 11 Jun 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=464772</guid>
    </item>
  </channel>
</rss>