<?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 (11) TMI 465 - Supreme Court</title>
    <link>https://www.taxtmi.com/caselaws?id=167654</link>
    <description>In preventive detention matters, all relevant material bearing on the detaining authority&#039;s satisfaction must be placed before the authority before the order is made. A detenu&#039;s retraction letter, delivered to a responsible Customs officer and reaching the appropriate departmental channel before the detention order, was material to the custodial explanation and could not be withheld. The failure to consider that communication vitiated the detention order, which was liable to be quashed.</description>
    <language>en-us</language>
    <pubDate>Wed, 16 Nov 2005 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 31 Dec 2014 17:17:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=372550" rel="self" type="application/rss+xml"/>
    <item>
      <title>2005 (11) TMI 465 - Supreme Court</title>
      <link>https://www.taxtmi.com/caselaws?id=167654</link>
      <description>In preventive detention matters, all relevant material bearing on the detaining authority&#039;s satisfaction must be placed before the authority before the order is made. A detenu&#039;s retraction letter, delivered to a responsible Customs officer and reaching the appropriate departmental channel before the detention order, was material to the custodial explanation and could not be withheld. The failure to consider that communication vitiated the detention order, which was liable to be quashed.</description>
      <category>Case-Laws</category>
      <law>Customs</law>
      <pubDate>Wed, 16 Nov 2005 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=167654</guid>
    </item>
  </channel>
</rss>