Email as Evidence in Indian Courts: Section 63 BSA Explained

Introduction

Email has become one of the most common forms of communication in modern legal disputes.

Companies negotiate contracts by email.

Employees receive instructions and termination notices through email.

Borrowers acknowledge dues.

Parties exchange invoices, purchase orders and settlement proposals.

Lawyers correspond with clients.

Government departments issue notices electronically.

And in criminal investigations, email accounts may contain communications that help establish motive, conspiracy, fraud or identity.

This raises an important legal question:

Can an email be used as evidence in an Indian court?

The answer is yes.

Under the Bharatiya Sakshya Adhiniyam, 2023 (BSA), emails are expressly recognised as electronic records. The BSA came into force on 1 July 2024, replacing the Indian Evidence Act, 1872. Section 2 itself includes emails within the illustration of electronic records that qualify as documents. Sections 61, 62 and 63 then provide the legal framework for proving such electronic material.

But producing a printed email or PDF before a court does not automatically prove:

• that the email is genuine;
• that it was actually sent by the person named in the “From” field;
• that it was not altered;
• that the entire email chain is complete;
• or that the contents are true.

These are separate evidentiary questions.

The most important principle is this:

Admissibility, authenticity, authorship and evidentiary weight are not the same thing.

Emails Are Electronic Records Under the BSA

The Bharatiya Sakshya Adhiniyam expressly treats electronic records as documents.

Section 61 states that an electronic or digital record cannot be denied admissibility merely because it is electronic. Subject to Section 63, it has the same legal effect, validity and enforceability as other documents.

Section 62 provides that the contents of electronic records may be proved in accordance with Section 63.

An email may therefore be relevant evidence in:

• civil suits;
• commercial disputes;
• criminal trials;
• arbitration;
• employment disputes;
• matrimonial proceedings;
• consumer cases;
• insolvency proceedings;
• tax disputes; and
• regulatory proceedings.

The method by which the email is produced, however, matters greatly.

What Does Section 63 BSA Do?

Section 63 is the central provision governing admissibility of computer outputs.

It applies where information contained in an electronic record is:

• printed on paper;
• stored;
• recorded;
• copied in optical or magnetic media;
• stored in semiconductor memory; or
• otherwise reproduced in electronic form.

If the statutory conditions are satisfied, the resulting computer output can be treated as a document and admitted without requiring production of the original system itself.

For email evidence, this may include:

• printed emails;
• PDF exports;
• screenshots;
• downloaded .eml files;
• mailbox exports;
• emails copied to a pen drive;
• server records;
• or other electronically reproduced versions.

Is a Section 63 Certificate Required for Emails?

Where a party relies on an email as a computer output or copy, the Section 63 certificate is highly important.

Section 63(4) requires a certificate to be submitted along with the electronic record when it is tendered for admission.

The certificate should:

• identify the electronic record;
• explain how it was produced;
• give relevant particulars of the computer or communication device;
• and address the statutory conditions relating to regular use, storage and proper functioning.

A 2026 Delhi commercial court decision, Satya Narain Gupta v. Puneet Verma, illustrates the practical use of Section 63 certification in relation to email communications relied upon in a commercial suit. The plaintiff produced email conversations along with a Section 63 certificate and supporting affidavit.

What Happens If the Certificate Is Missing?

Failure to comply with the electronic-evidence requirements can seriously weaken or defeat reliance on the email.

In Om Prakash Bansal v. Piyush Gupta, decided in July 2026, a Delhi commercial court reiterated that Section 63 BSA substantially carries forward the old Section 65B framework and treated certification as mandatory for computer-output electronic records.

Similarly, in State v. Somkanya Chandreyee Dass, a Delhi court rejected photocopies of emails and screenshots where there was no proper electronic-evidence certificate and the original devices were not made available for forensic examination. The court emphasised the risk of fabricated or manipulated electronic material.

The practical lesson is clear:

A printout of an email should not be filed casually without addressing Section 63.

Does Every Email Need a Certificate?

The answer depends on how the email is being produced.

The older Supreme Court jurisprudence under Section 65B distinguished between:

• producing the original electronic record or original device; and
• producing a copy or computer output.

That distinction remains relevant because Section 63 substantially continues the earlier framework.

For example, where the original laptop containing the email is itself produced before the court and the email is viewed directly from that device, the situation may differ from filing a printout or PDF copy.

Earlier decisions have recognised that production of the original device may qualify as primary electronic evidence in certain circumstances.

But in ordinary litigation, emails are usually produced as:

• printouts;
• PDFs;
• screenshots;
• downloaded files;
• or exported mailbox records.

In such cases, compliance with Section 63 is the safer and more defensible approach.

The Old Section 65B Cases Still Matter

Section 63 BSA is closely modelled on the former Section 65B of the Indian Evidence Act.

Therefore, major Supreme Court decisions interpreting Section 65B remain important where the underlying principle has been retained.

One foundational case is Anvar P.V. v. P.K. Basheer.

The Supreme Court stressed that electronic records are vulnerable to:

• alteration;
• tampering;
• transposition;
• excision; and
• manipulation.

It held that statutory safeguards concerning electronic evidence are designed to ensure source and authenticity.

The other major authority is Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal, which reaffirmed the central role of the electronic-record certificate for secondary electronic evidence.

These principles continue to guide Section 63 BSA practice.

A Certificate Does Not Prove Who Sent the Email

This is one of the most important distinctions in email evidence.

Suppose a printed email says:

From: rahul@example.com
To: amit@example.com

Does that automatically prove that Rahul personally sent it?

No.

Section 90 BSA creates only a limited presumption regarding electronic messages.

The court may presume that an electronic message forwarded through an electronic mail server corresponds with the message as fed into the computer for transmission.

But the statute expressly says that the court shall not presume the identity of the person who sent the message.

This is extremely important.

An email address is not the same thing as proven authorship.

Why Authorship Can Be Disputed

Email accounts can be:

• hacked;
• shared;
• spoofed;
• used by assistants;
• accessed from multiple devices;
• or compromised through stolen credentials.

Therefore, a party may say:

“That is my email address, but I did not send that email.”

The court must then examine additional evidence.

A 2025 Delhi decision in State v. Somkanya Chandreyee Dass carefully discussed this problem and emphasised that the “From” field alone does not prove the identity of the sender. The court referred to additional evidence such as device information, IP data, witness testimony and authentication records that may help establish the true originator.

How Can Authorship of an Email Be Proved?

Relevant evidence may include:

Admission

The alleged sender admits sending the email.

Reply conduct

The recipient replies and the sender continues the conversation in a manner consistent with authorship.

Email headers

Headers may reveal:

• sending servers;
• message IDs;
• routing information;
• timestamps;
• IP information;
• authentication results; and
• domain data.

Device evidence

The email may be recovered from the sender’s:

• laptop;
• phone;
• email client;
• browser history;
• or mailbox.

Server records

Corporate or service-provider records may show transmission or account activity.

Witness testimony

A secretary, employee or IT administrator may explain who had access to the account.

Circumstantial evidence

The content may contain information known only to the sender.

Authentication protocols

Technical records involving:

• SPF;
• DKIM;
• DMARC;
• and related mail-authentication systems

may help establish whether the message was genuinely transmitted through an authorised domain.

The court in Somkanya Chandreyee Dass specifically referred to such forms of corroborative evidence when discussing originator identity.

What Are Email Headers?

An ordinary email display often shows only:

• sender;
• recipient;
• date;
• subject; and
• message body.

But the message usually contains a larger technical header.

That header may contain:

• Message-ID;
• Return-Path;
• Received lines;
• sending server;
• destination server;
• timestamps;
• IP-related routing information;
• SPF result;
• DKIM signature;
• DMARC result; and
• other technical fields.

In a disputed case, headers can be much more useful than a screenshot.

Why Screenshots Are Weaker Than Original Email Files

A screenshot may show what appeared on a screen.

But it can omit:

• complete headers;
• message IDs;
• attachments;
• routing information;
• metadata;
• full email chain;
• and technical authentication data.

Screenshots are also easy to edit.

A person can potentially change:

• sender name;
• date;
• subject;
• wording;
• recipient;
• or visual layout.

For serious litigation, preserving the original email in its native format is much better than relying only on screenshots.

What Is an .eml File?

An .eml file is a common format used to save an individual email message.

It may preserve:

• message body;
• sender and recipient information;
• technical headers;
• attachments;
• timestamps;
• and other metadata.

For forensic purposes, an .eml or comparable native-format export may provide substantially more information than a PDF or screenshot.

PDF Printout vs Native Email

A PDF generated from an email may be useful for courtroom convenience.

But it may not preserve all technical information.

The best evidentiary practice may therefore be to preserve both:

• the original/native email; and
• a readable PDF or printout.

The native copy supports authentication.

The PDF or printout makes the evidence easier to read.

Can an Email Be an Admission?

Yes.

An email can contain an admission.

For example:

“We acknowledge that ₹8 lakh remains payable.”

If authenticity and authorship are proved, the email may become important evidence in a recovery suit.

Similarly:

“I received the goods but payment will be made next month.”

may be relevant to a commercial dispute.

The legal effect will depend on:

• who sent it;
• their authority;
• context;
• wording;
• and the surrounding evidence.

Can an Employee Bind a Company by Email?

Potentially, depending on authority.

Suppose a junior employee sends:

“We agree to settle the entire dispute for ₹20 lakh.”

That email does not automatically bind the company merely because it came from a corporate email address.

The court may ask whether the employee had:

• actual authority;
• apparent authority;
• delegated authority;
• or a role suggesting authority to make such commitments.

Therefore, proving authorship is only one part of the issue.

The legal capacity of the sender may also matter.

Can an Email Create a Contract?

Yes, potentially.

Indian contract law does not generally require every agreement to be signed on paper.

A valid contract can arise electronically where the essential elements are present, including:

• offer;
• acceptance;
• lawful consideration;
• competent parties;
• free consent;
• lawful object; and
• intention to create legal relations.

An email exchange can therefore help establish a binding agreement.

But this does not mean every negotiation becomes a contract.

For example:

“Please send your best price.”

is not necessarily an offer capable of immediate acceptance.

Similarly, where the law requires:

• registration;
• stamping;
• a formal deed;
• or another statutory formality,

an email exchange may not replace that requirement.

“Subject to Contract” Emails

Commercial negotiations often contain expressions such as:

• “subject to contract”;
• “subject to management approval”;
• “without prejudice”;
• or “draft only.”

These expressions may be highly important.

They can indicate that the parties did not intend to be legally bound until a formal agreement was executed.

The court must therefore consider the entire email chain rather than isolating a single sentence.

Can Emails Prove a Debt?

Yes, potentially.

A series of emails may show:

• invoices sent;
• balance confirmation;
• acknowledgment of liability;
• promises to pay;
• requests for more time;
• or settlement discussions.

However, separate legal questions may arise concerning:

• limitation;
• authority;
• account reconciliation;
• and whether the acknowledgment satisfies the requirements of applicable law.

Can Emails Extend Limitation?

Potentially, but not every email will do so.

An acknowledgment of liability may affect limitation only where the legal requirements of the Limitation Act are satisfied.

The exact wording, timing and authentication of the email matter.

A casual statement such as:

“We will look into the account”

is not the same as:

“We admit ₹5 lakh is due and payable.”

The issue should therefore be assessed carefully.

Business Emails and Commercial Litigation

Emails are especially important in commercial disputes.

They may prove:

• purchase orders;
• negotiations;
• variation of terms;
• delivery disputes;
• complaints;
• acceptance;
• payment obligations;
• settlement discussions;
• breach notices;
• termination;
• and debt acknowledgment.

In Satya Narain Gupta v. Puneet Verma, the plaintiff relied upon a set of email communications in a commercial dispute together with a Section 63 certificate. The case illustrates how ordinary business email chains are now routinely treated as electronic documentary evidence under the BSA framework.

What If the Other Side Does Not Deny the Email?

Admission may simplify proof.

If the other party clearly admits:

• receiving the email;
• sending the email;
• or the contents of the email,

the evidentiary dispute may become narrower.

However, practitioners should be careful about assuming that lack of immediate objection permanently cures a statutory defect in all situations.

The safest course remains proper electronic-evidence compliance.

What About Emails Printed From Gmail or Outlook?

A Gmail or Outlook printout is still a computer output.

Its evidentiary value depends on:

• who produced it;
• what account it came from;
• whether the account was regularly used;
• whether the output accurately reproduces the original;
• and whether the Section 63 conditions are satisfied.

Printing the email directly from Gmail does not automatically eliminate the statutory requirements.

Can You Certify Emails From Your Own Inbox?

Potentially, yes, if you have lawful control of the relevant device or account and can truthfully satisfy the statutory requirements.

For example, a business owner producing emails from an account regularly operated by the business may be able to explain:

• the account;
• device;
• regular use;
• method of download;
• and production of the electronic output.

The certificate must correspond honestly to the actual source and method of production.

What If the Email Is on a Company’s Server?

Corporate email systems may involve multiple components:

• employee devices;
• mail servers;
• cloud providers;
• backup systems;
• security gateways;
• and archives.

Section 63(3) recognises that electronic information may be created, stored or processed across:

• standalone computers;
• networks;
• computer systems;
• storage resources;
• and intermediaries.

The provision treats such interconnected systems as a single computer or communication-device environment for the statutory purpose where the conditions apply.

This is helpful for modern cloud-based business email.

Cloud Email Does Not Mean Evidence Cannot Be Certified

Modern email often exists on remote servers rather than physically on one computer.

For example:

• Gmail;
• Microsoft 365;
• Zoho Mail;
• corporate cloud systems.

Section 63 is broad enough to deal with information processed through networks, computer resources and intermediaries.

Therefore, cloud storage does not make electronic evidence legally impossible.

It simply makes accurate identification of the source and production process more important.

What If an Email Was Forwarded?

A forwarded email should be treated carefully.

Suppose A sends an email to B.

B forwards it to C.

C produces only the forwarded version.

That may prove that C received something forwarded by B, but it may not automatically prove the original message exactly as sent by A.

The stronger evidence would be:

• the original email from A;
• native headers;
• server information;
• or another authenticated copy.

Each forwarding step creates another layer requiring explanation.

Can an Email Attachment Be Evidence?

Yes.

Attachments can include:

• contracts;
• invoices;
• spreadsheets;
• photographs;
• reports;
• PDFs;
• audio;
• video;
• or other electronic records.

But the attachment has its own evidentiary characteristics.

The party may need to prove:

• that it was attached to the email;
• that it is the same file originally sent;
• that it has not been modified;
• and what legal significance it has.

Hash values may be particularly useful for attachments.

Hash Values and Emails

A hash value functions as a digital fingerprint of a file.

If a document or email export is hashed at the time of preservation and later produces the same hash, that supports integrity.

The Section 63 certificate format under the BSA expressly contemplates technical details including hash values.

For high-value commercial or criminal matters, hashing:

• native email exports;
• mailbox files;
• attachments;
• and forensic images

can strengthen the chain of custody.

Email Metadata

Metadata can help answer questions such as:

• when the email was created;
• when it was sent;
• what server processed it;
• whether it contained attachments;
• what message ID it had;
• and where it travelled.

Metadata becomes particularly important when one side alleges:

• fabrication;
• backdating;
• spoofing;
• or editing.

What Is Email Spoofing?

Spoofing occurs when an email is made to appear as though it came from an address or person different from the true sender.

This may be used in:

• phishing;
• business-email compromise;
• fraud;
• impersonation;
• and cybercrime.

Because spoofing is technically possible, the court cannot simply assume that a visible “From” address proves authorship.

This is precisely why Section 90 BSA refuses to create a presumption about who sent an electronic message.

What Are SPF, DKIM and DMARC?

These are technical authentication mechanisms used by modern email systems.

SPF

Helps verify whether the sending server is authorised to send email for a particular domain.

DKIM

Uses cryptographic signatures to help verify that a message was authorised by the domain and was not altered in transit.

DMARC

Builds on SPF and DKIM and provides domain-level policies and reporting.

These systems do not solve every authorship question, but they can provide useful technical evidence in a disputed email case.

Can a Court Presume an Email Is Genuine?

Section 90 BSA creates only a limited presumption.

The court may presume that the message received corresponds with the message fed into the email server for transmission.

But the court cannot presume the identity of the sender merely from the electronic message.

This means the law distinguishes between:

message transmission

and

human authorship.

Email Evidence in Criminal Cases

Emails may become relevant to establish:

• conspiracy;
• threats;
• fraud;
• extortion;
• planning;
• motive;
• financial transactions;
• impersonation;
• or communication among accused persons.

But criminal courts must be particularly cautious where authorship is disputed.

A person should not be convicted merely because a damaging email appears to have come from an account bearing their name.

The prosecution may need to establish:

• account control;
• device access;
• technical origin;
• contextual connection;
• and corroborative evidence.

The 2025 Delhi decision in Somkanya Chandreyee Dass illustrates the danger of relying on uncertified email photocopies where originator identity and authenticity remain unproved.

Email Evidence in Employment Disputes

Emails may prove:

• instructions;
• warnings;
• resignation;
• termination;
• performance concerns;
• harassment complaints;
• salary discussions;
• approval;
• or internal policy communication.

But the full thread should be preserved.

A single isolated email may be misleading if earlier messages show that it was:

• sarcastic;
• conditional;
• withdrawn;
• or written in response to something else.

Email Evidence in Matrimonial Cases

Emails may be relevant in disputes involving:

• cruelty;
• separation;
• financial support;
• admissions;
• communication breakdown;
• or other matrimonial issues.

Again, authenticity and authorship matter.

A spouse alleging that an email was fabricated can challenge:

• the source;
• account access;
• device;
• headers;
• and electronic-evidence certificate.

Email Evidence and Hearsay

Electronic format does not eliminate hearsay concerns.

Suppose an email says:

“Ravi told me that Amit stole the money.”

If the email is offered to prove that Amit actually stole the money, the statement may raise hearsay issues.

By contrast:

“I took the money and will return it tomorrow.”

may operate as an admission if sent by the opposing party and properly proved.

The court must consider why the email is being tendered.

Emails Between Lawyer and Client

Emails between an advocate and client may be protected by legal professional privilege under the BSA, subject to statutory limitations and exceptions.

Merely because a privileged communication exists electronically does not remove privilege.

A party who obtains another person’s lawyer-client email should not assume it can automatically be used in court.

“Without Prejudice” Emails

Settlement emails frequently use the words:

“Without prejudice.”

Such communications may attract protection where they genuinely form part of compromise negotiations.

But merely typing the phrase does not automatically make every email privileged.

The court may examine:

• purpose;
• context;
• whether settlement was genuinely being negotiated;
• and the applicable evidentiary rule.

Confidential Business Emails

Commercial emails may contain:

• trade secrets;
• pricing formulas;
• client information;
• internal strategy;
• confidential negotiations;
• or proprietary technical material.

A court may permit reliance on relevant confidential emails while also using procedural safeguards concerning disclosure or access.

Relevance does not always mean unrestricted public dissemination.

Can Deleted Emails Be Recovered?

Potentially.

Deleting an email from an inbox does not necessarily remove every copy.

It may remain in:

• trash;
• server backups;
• archive systems;
• recipient mailbox;
• forwarded copies;
• forensic images;
• cloud logs;
• or corporate retention systems.

In serious litigation, forensic recovery may be possible.

What If the Other Party Deletes Relevant Emails?

Deliberate destruction of relevant evidence after litigation is anticipated can create serious consequences.

Depending on the facts, a court may consider:

• adverse inference;
• credibility;
• discovery sanctions;
• obstruction-related issues;
• or other procedural consequences.

Businesses should therefore implement litigation holds once a dispute becomes reasonably foreseeable.

Email Preservation for Litigation

Good practice includes preserving:

• the complete email chain;
• native-format emails;
• attachments;
• headers;
• server logs where available;
• mailbox exports;
• account information;
• devices;
• and metadata.

Avoid:

• copying only selected lines;
• deleting earlier parts of a thread;
• editing subject lines;
• or retyping the contents manually.

Example: Strong Email Evidence

A supplier claims ₹20 lakh is outstanding.

The buyer sent an email from its corporate account stating:

“We confirm ₹20 lakh is due and request 30 days for payment.”

The supplier preserves:

• the native email;
• headers;
• complete thread;
• corporate account details;
• invoice records;
• and Section 63 certificate.

The buyer also made a part payment after the email.

This combination creates a much stronger evidentiary foundation than a screenshot standing alone.

Example: Weak Email Evidence

A person produces a JPEG screenshot showing:

“I admit I committed the fraud.”

The screenshot contains:

• no full email address;
• no header;
• no message ID;
• no metadata;
• no original device;
• no Section 63 certificate;
• and no explanation of source.

The alleged sender denies authorship.

The evidentiary value is obviously much weaker.

Example: Spoofed CEO Email

An employee receives an email appearing to come from the company’s CEO instructing an urgent transfer of ₹50 lakh.

The employee makes the payment.

It later emerges that the email was spoofed.

In litigation, the visible “From” field would not itself prove that the CEO sent the instruction.

Technical header analysis, mail-server logs and domain-authentication data may be critical.

Example: Employment Termination

An employer sends:

“Your services stand terminated with immediate effect.”

The employee later claims no termination notice was issued.

If the email can be properly authenticated and delivery established, it may become important evidence.

But separate questions may remain concerning whether:

• the sender had authority;
• termination complied with contract;
• notice requirements were met;
• and applicable labour law was followed.

Example: Contract Negotiation

Party A emails:

“We accept your offer at ₹12 lakh, subject to execution of the final agreement.”

Party B argues that a binding contract already arose.

The words “subject to execution of the final agreement” may become crucial in determining whether there was final contractual intention.

Email evidence proves what was communicated.

It does not automatically determine the legal consequence.

Can a Printout Be Notarised Instead of Using Section 63?

Notarisation does not automatically substitute for statutory electronic-evidence requirements.

A notary may attest that a particular paper was presented before them.

That does not necessarily prove:

• source;
• account control;
• device;
• authenticity;
• or compliance with Section 63.

The correct electronic-evidence foundation still matters.

Does a Digital Signature Make an Email Conclusive?

No.

A valid electronic or digital signature may substantially strengthen authentication.

But it does not automatically prove:

• that every factual statement in the email is true;
• that the sender had authority;
• or that the communication creates a legally binding obligation.

It is one part of the evidentiary picture.

What About Old Emails?

Section 93 BSA creates a presumption concerning certain electronic records that are five years old and produced from proper custody, but the statutory presumption specifically concerns electronic signatures rather than creating a universal presumption that all contents or authorship of an old email are true.

Old age therefore does not automatically cure authenticity problems.

Proceedings Started Before 1 July 2024

The BSA came into force on 1 July 2024.

Proceedings that commenced earlier may continue under the saving provisions applicable to the Indian Evidence Act, depending on their procedural history.

Lawyers should therefore first determine whether the matter is governed by:

• Section 65B of the old Evidence Act; or
• Section 63 BSA.

The underlying electronic-evidence principles are closely related, but the applicable statutory provision should be cited correctly.

Practical Checklist for Email Evidence

Before relying on an email in court, ask:

1. Is the full email preserved?
2. Is the original/native version available?
3. Are complete headers available?
4. Are attachments preserved?
5. Who controlled the email account?
6. Can the alleged sender be identified?
7. Is the complete conversation chain preserved?
8. Is there a Section 63 certificate?
9. Does the certificate accurately identify the source and production method?
10. Is the original device or mailbox still available?
11. Could the account have been shared or compromised?
12. Are SPF, DKIM or DMARC records relevant?
13. Is there corroborative evidence?
14. Is the email privileged or confidential?
15. Is forensic examination required?

Frequently Asked Questions

Are emails admissible in Indian courts?

Yes.

Emails are electronic records and can be admitted subject to the Bharatiya Sakshya Adhiniyam and other applicable evidentiary rules.

Which section of the BSA applies?

Sections 61 and 62 recognise electronic records, while Section 63 contains the primary framework for computer outputs.

Is a Section 63 certificate mandatory?

For email printouts, PDFs and other computer-output copies sought to be admitted under Section 63, certification is extremely important and ordinarily required.

Does an email prove who sent it?

Not automatically.

Section 90 BSA expressly says the court shall not presume who sent an electronic message merely from the message itself.

Can a Gmail screenshot be used?

Potentially, but a screenshot is weaker than a native email with headers and proper Section 63 certification.

Can an email be a contract?

Yes, potentially, if the necessary elements of contract formation are established and no separate statutory formality is required.

Can an email prove an admission of debt?

Yes, potentially, if authorship, authenticity and legal requirements are satisfied.

Can deleted emails be recovered?

Sometimes, through server archives, backups, recipient accounts or forensic examination.

Are forwarded emails reliable evidence?

They can be relevant, but the closer the evidence is to the original message and source account, the stronger the evidentiary foundation.

Can a forged email be challenged?

Yes.

The opposing party may seek:

• header analysis;
• server records;
• forensic examination;
• account-access evidence;
• IP information;
• and other technical proof.

Does an email from a corporate account automatically bind the company?

No.

The sender’s authority and the context must also be established.

Can emails between a lawyer and client be used?

They may be protected by legal professional privilege, subject to applicable exceptions.

The Difference Between Admissibility and Proof

This is perhaps the most important takeaway.

Suppose an email printout satisfies Section 63.

That may allow it to be admitted as an electronic document.

But the opposing party can still argue:

• “I did not send it.”
• “My account was hacked.”
• “The email is incomplete.”
• “The attachment was changed.”
• “The employee had no authority.”
• “The message was part of settlement negotiations.”
• “The email has been taken out of context.”

The court must decide those questions separately.

A certificate helps prove the electronic record.

It does not automatically prove every factual statement contained within that record.

Why Email Authentication Matters More in the AI Era

AI and modern cyber tools make electronic fabrication easier.

A fake email screenshot can now be created within minutes.

Attackers can:

• spoof addresses;
• imitate writing style;
• generate realistic conversations;
• fabricate attachments;
• or produce fake corporate correspondence.

This makes technical authentication increasingly important.

Courts are likely to place greater emphasis on:

• native files;
• complete headers;
• server logs;
• metadata;
• cryptographic authentication;
• hash values;
• device evidence;
• and contextual corroboration.

The simple visual appearance of an email is no longer enough in a serious dispute.

Conclusion

Emails are fully capable of being used as evidence in Indian courts.

The Bharatiya Sakshya Adhiniyam, 2023 expressly recognises emails as electronic records, and Sections 61, 62 and 63 establish the framework through which they can be proved.

But an email is not self-proving.

Where the email is produced as a printout, PDF, screenshot or other computer output, the Section 63 certificate becomes a central part of admissibility.

Even after certification, separate questions remain concerning:

• authenticity;
• authorship;
• completeness;
• authority;
• relevance;
• hearsay;
• privilege;
• and evidentiary weight.

Section 90 BSA makes this distinction especially clear.

A court may presume that an electronic message corresponds with what was transmitted through the email server, but it cannot automatically presume the identity of the person who sent it.

That is why the strongest email evidence combines:

• the original or native email;
• full headers;
• complete message chains;
• attachments;
• proper Section 63 certification;
• metadata;
• technical authentication where necessary;
• and independent corroboration.

For lawyers and litigants, the practical lesson is simple:

Do not treat an email screenshot as though it proves itself. Preserve the native record, authenticate the source, identify the sender, comply with Section 63 and keep the complete context.

As business, personal and professional communication increasingly moves online, email evidence will continue to play a major role in Indian litigation.

The real question before courts will increasingly be not whether emails can be evidence.

They clearly can.

The more important question is whether the particular email placed before the court can be shown to be the genuine, complete and properly authenticated communication it claims to be.

This article reflects the general legal position and publicly available judicial developments up to September 2026. Electronic-evidence requirements can vary depending on how the email is produced and the nature of the proceeding. This article is intended for general legal information and academic discussion and does not constitute legal advice.