BarakoCMS.Email.Smtp 4.0.0

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package BarakoCMS.Email.Smtp --version 4.0.0
                    


                    

                
NuGet\Install-Package BarakoCMS.Email.Smtp -Version 4.0.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="BarakoCMS.Email.Smtp" Version="4.0.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="BarakoCMS.Email.Smtp" Version="4.0.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="BarakoCMS.Email.Smtp" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add BarakoCMS.Email.Smtp --version 4.0.0
                    


                    

                
#r "nuget: BarakoCMS.Email.Smtp, 4.0.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package BarakoCMS.Email.Smtp@4.0.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=BarakoCMS.Email.Smtp&version=4.0.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=BarakoCMS.Email.Smtp&version=4.0.0
                    


                            Install as a Cake Tool

<div align="center"> <h1>BarakoCMS.Email.Smtp</h1> <p><em>SMTP email provider for barakoCMS.</em></p> </div>

Implements barakoCMS's IEmailService over any SMTP relay, so features that send email (registration, passwordless OTP sign-in, MFA notices, workflow emails) deliver for real instead of hitting the built-in mock.

If you self-host, you very likely already have SMTP credentials from your host, from Google Workspace, from Amazon SES or from a corporate relay. This is the provider that uses them.

Sending is MailKit, not System.Net.Mail.SmtpClient, which Microsoft's own documentation tells you not to use in new code.

Enable it

dotnet add package BarakoCMS.Email.Smtp

builder.Services.AddBarakoCMS(builder.Configuration);

var app = builder.Build();
app.UseBarakoCMS();

The package reference plus a restart is the install. AddBarakoCMS finds every module in the application's dependency context, and BarakoCMS:Modules:Enabled decides which of them run (BarakoCMS__Modules__Enabled=Email.Smtp). Unset, every referenced module runs and the API logs one warning saying so. To name it by hand instead, put modules.Add(new BarakoCMS.Email.Smtp.SmtpEmailModule()) in the AddBarakoCMS callback; discovery skips a type the host already added. See MODULES.md in the repository.

barakoCMS registers its mock email service with TryAdd, so this module's registration wins.

Configure

Settings live in the module's own section, Modules:Email.Smtp:

{
  "Modules": {
    "Email.Smtp": {
      "Host": "smtp.example.com",
      "Port": 587,
      "User": "postmaster@example.com",
      "Password": "…",
      "From": "MyApp <no-reply@example.com>",
      "Security": "StartTls"
    }
  }
}

As environment variables that is Modules__Email.Smtp__Host and so on: __ stands in for the separator, and the dot in the module name is part of the key rather than one.

The dot means the name is not a valid shell identifier, so export Modules__Email.Smtp__Host=... fails in bash and zsh. It works anywhere the name is passed as data rather than declared: a compose environment: list, a Kubernetes env: entry, or env 'Modules__Email.Smtp__Host=smtp.example.com' dotnet run. For a local shell, user-secrets is the easier route.

Keep the password in user-secrets, an environment variable or a mounted secret, never in source.

Setting Description
Host The relay. No host means the module registers nothing, see below.
Port Submission port. Default 587.
User, Password Omit both for a relay that does not authenticate.
From Sender. A from address stored in the admin at Settings, Email wins over this.
Security StartTls, SslOnConnect or None. Unset picks by port.

It is inert until you configure it

With no Host the module registers no IEmailService at all, so whatever was there before still sends: another provider module, or the mock. Adding the package to an existing deployment and configuring nothing changes nothing.

The alternative would be worse than it sounds. A module that registered itself unconfigured would take email over from a working provider and then fail every send, and it would read as the relay being down rather than as the upgrade.

The security default will not fall back to plaintext

Unset Security means implicit TLS on port 465 and STARTTLS on every other port. If the relay does not offer STARTTLS, the send fails.

That is deliberate, and it is not what MailKit's own Auto does: Auto off port 465 resolves to StartTlsWhenAvailable, which sends the password in the clear against a relay that stopped advertising STARTTLS, and nothing anywhere says so. Plaintext is still available by asking for it by name, "Security": "None", for a relay on a network you already trust.

There is no setting that turns off certificate validation. If your relay's certificate does not validate, fix the certificate or trust the CA on the host.

What this module does not get from the admin

barakoCMS has an email settings screen at Settings, Email, and it holds an API key and a from address. That shape was built for Resend, and it is what a provider gets from IEmailSettingsProvider. SMTP needs a host, a port, a user, a password and a TLS mode, and none of those fit in it.

So:

  • The from address does carry across. A sender typed into the admin wins over Modules:Email.Smtp:From, because that field is not provider-specific and somebody set it there most recently.
  • The credentials do not. Host, port, user and password are a deployment decision for this module, changed where the deployment is configured and picked up on the next send.
  • The test-send button refuses. Settings, Email, Send a test to myself checks for an API key before it sends, so with SMTP registered it answers "No API key is set" even when SMTP is configured and working. Ordinary sends are unaffected. Making that button provider-neutral means changing IEmailSettingsProvider, which is a change to the core contract rather than a module.

Requires

barakoCMS ≥ 4.0.0. Targets .NET 10.

License

MPL-2.0 © BaryoDev

If barakoCMS is useful to you, a star on the repository helps other people find it.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.0.0 97 9/7/2026