Skip to content

Conversation

Jared314
Copy link
Contributor

The existing SES integration reuses the SMTP integration, thus requiring an SMTP endpoint and extra credentials for deployment. Switching to direct SES client usage removes that dependency.

catch (Exception ex)
{
var error = string.Format(CultureInfo.InvariantCulture, Texts.SMTP_Exception, ex.Message);
throw new DomainException(error, ex);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Domain exception are potentially shown to the user. I am not surre if you always want to do that.

{
var r = Convert(context, request);
var response = await amazonSES.SendRawEmailAsync(r, ct);
if (response.HttpStatusCode != System.Net.HttpStatusCode.OK)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please import namespaces if there are not conflicts.

FillContext(context);
try
{
var r = Convert(context, request);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please no appreviations like "r"...call it "rawRequest"?


smtpMessage.Subject = request.Subject;

using (var messageStream = new MemoryStream())
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be implemented without the memory stream, e.g. by writing to the request directly?

@Jared314 Jared314 closed this May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants