---
title: SMTP overview
summary: Which service this proxy calls, who consumes it, and what it is used for.
status: draft
owner: SAIF.Core documentation
last_reviewed: 2026-09-24
---

# SMTP overview

`SMTP` is a generated svcutil proxy for the SAIF-internal ASMX mail service `clsSAIFMessage`†, but no repository source constructs the generated `internal` client, and there is no authored wrapper. It is present and compiled into `SAIF.Services.Web.Proxies` but is entirely unreachable, including from downstream package consumers.

## Purpose
- Send SMTP mail messages (plain text, with attachments, or with linked resources and HTML body) through the `clsSAIFMessage` ASMX service — as declared by the contract; this repository does not exercise the capability.

## Business context

The service the contract describes is a mail-sending capability, but this repository does not use it: email in this repository goes through `IEmailService` instead (for example `SubpoenaLabelService.SendEmailForInvalidAddress` → `IEmailService.SendEmail`, using `System.Net.Mail.MailMessage`), a path unrelated to this proxy.

| Attribute | Value |
| --- | --- |
| Business capability | Not applicable — no in-repository capability depends on this proxy |
| Owning team of the called service | Not determined from source |
| Criticality to the consumer | Not determined from source — the proxy has no consumer in this repository |
| Fallback when unavailable | Not applicable — nothing calls it |

## Consumers

| Consumer | Call site | Operations used | Notes |
| --- | --- | --- | --- |
| *(none)* | — | — | No repository source constructs `clsSAIFMessageSoapClient` or references `Proxies.SMTP`. The generated types are `internal` with no `InternalsVisibleTo`, so no downstream consumer of the shipped package can reach them either. |

## Capability summary

The full declared surface (`SendMailAsText`, `SendMail`, `SendWithAttach`, `SendWithAttachAsText`, `SendEmail`) is documented on [Contract](contract.md); none of it is used by this repository, so no capability summary row applies here.

## Generation provenance

| Aspect | Finding |
| --- | --- |
| Generated by | `svcutil` (Service Reference) |
| Generated from | `Services/SAIF.Services.Web.Proxies/Service References/SMTP/clsSAIFMessage1.wsdl` |
| Discovery document | `Services/SAIF.Services.Web.Proxies/Service References/SMTP/clsSAIFMessage1.disco` |
| Generated namespace | `SAIF.Services.Web.Proxies.SMTP` |
| Namespace matches the consuming project | Yes — rooted in `SAIF.Services.Web.Proxies`, the project that carries the file |
| Regeneration risk | None beyond the ordinary — there is no hand edit or hand-written wrapper depending on the generated shape |

The `1` suffix on `clsSAIFMessage1.wsdl`/`.disco` suggests the reference was regenerated or renamed at least once*.

## Non-documented artifacts

- `Reference.cs`, its serialization attributes, and any `…Async`/`…Completed` event scaffolding are svcutil tool output and are not narrated in this document set; the contract is documented from `clsSAIFMessage1.wsdl` alone, since there is no call site to draw usage from.

## Related documentation
- [Client index](index.md)
- [Architecture](architecture.md)
- [Contract](contract.md)
- [Operation map](operation-map.md)
- [Client reference](reference.md)
- [Consumption](consumption.md)
- [Dependencies](dependencies.md)
- [Tech debt](tech-debt.md)

> **Note:** Statements marked with `†` are derived from dependency library
> documentation via the Legends CLI. Statements marked with `*` were inferred
> from code structure or contextual evidence.

## Sources
- `Services/SAIF.Services.Web.Proxies/Service References/SMTP/Reference.cs`
- `Services/SAIF.Services.Web.Proxies/Service References/SMTP/Reference.svcmap`
- `Services/SAIF.Services.Web.Proxies/Service References/SMTP/clsSAIFMessage1.wsdl`
- `Services/SAIF.Services/Legal/Subpoenas/SubpoenaLabelService.cs`