<?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>2005 (7) TMI 652 - Supreme Court</title>
    <link>https://www.taxtmi.com/caselaws?id=173725</link>
    <description>Duly effected service in the special leave petitions satisfied the notice requirement where the records showed dasti service and registered post acknowledgments. Applying the proviso to Rule 11 of Order XVI of the Supreme Court Rules, 1966, the Court held that no fresh notice was required after leave was granted when the respondent had already been served, entered caveat, or taken notice. The applicants were therefore treated as properly served, and the appeals could proceed without further notice.</description>
    <language>en-us</language>
    <pubDate>Fri, 15 Jul 2005 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 29 Sep 2018 13:19:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=398168" rel="self" type="application/rss+xml"/>
    <item>
      <title>2005 (7) TMI 652 - Supreme Court</title>
      <link>https://www.taxtmi.com/caselaws?id=173725</link>
      <description>Duly effected service in the special leave petitions satisfied the notice requirement where the records showed dasti service and registered post acknowledgments. Applying the proviso to Rule 11 of Order XVI of the Supreme Court Rules, 1966, the Court held that no fresh notice was required after leave was granted when the respondent had already been served, entered caveat, or taken notice. The applicants were therefore treated as properly served, and the appeals could proceed without further notice.</description>
      <category>Case-Laws</category>
      <law>Indian Laws</law>
      <pubDate>Fri, 15 Jul 2005 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=173725</guid>
    </item>
  </channel>
</rss>