[New Feature]: SMTP server role

[dex-code-one]

Description

I've searched the repo for SMTP server role, but I only see the following:
RootDC, FirstChildDC, DC, ADDS, FileServer, WebServer, DHCP, Routing, CaRoot, CaSubordinate, SQLServer2008, SQLServer2008R2, SQLServer2012, SQLServer2014, SQLServer2016, VisualStudio2013, VisualStudio2015, SharePoint2013, SharePoint2016, Orchestrator2012, SQLServer2017, DSCPullServer, Office2013, Office2016, ADFS, ADFSWAP, ADFSProxy, SQLServer2019, FailoverStorage, FailoverNode, Tfs2015, Tfs2017, TfsBuildWorker, Tfs2018, HyperV, AzDevOps, SharePoint2019, SharePoint, WindowsAdminCenter, Scvmm2016, Scvmm2019, ScomManagement, ScomConsole, ScomWebConsole, ScomReporting, ScomGateway, SCOM, DynamicsFull, DynamicsFrontend, DynamicsBackend, DynamicsAdmin, Dynamics, RemoteDesktopGateway, RemoteDesktopWebAccess, RemoteDesktopSessionHost, RemoteDesktopConnectionBroker,
RemoteDesktopLicensing, RemoteDesktopVirtualizationHost, RDS, ConfigurationManager, Scvmm2022, SCVMM, SQLServer2022, SQLServer

Seems pretty trivial to add SMTP role maybe?

[nyanhp]

If you feel it is trivial, we always welcome Pull Requests! But until then, we only have Exchange in our roles, which arguably is not a "trivial" SMTP server.

Exchange is implemented as a "Custom Role", a concept we added a couple of years ago to encourage more participation and a more flexible way of creating roles. You can discover them with Get-LabSnippet -Type CustomRole -Name Exchange* and to use it:

$role = Get-LabInstallationActivity -CustomRole Exchange2019 -Properties @{ OrganizationName = 'Contoso'; IsoPath = "$labSources\ISOs\mu_exchange_server_2019_cumulative_update_2_x64_dvd_29ff50e8.iso" }
Add-LabMachineDefinition -Name E1Ex1 -Memory 6GB -PostInstallationActivity $role

More docs on those roles are here: https://automatedlab.org/en/latest/Wiki/Advanced/customroles/

[stale]

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.