Allow SMTP auth to be nil

[KesterTan]

Description

Resolves #2172

Previously, users had no way of specifying smtp authentication in smtp config to be nil. However, with this fix, users can do so by clicking the option and not specifying a username and password.

How Has This Been Tested?

1. To test this out, configure a local SMTP without auth. To do so, I ran this command:
   sudo python -m smtpd -n -c DebuggingServer localhost:25.
2. You then fill in the Mail Server Address as localhost, Mail Server Port as 25 and click none for authentication. You can leave the rest of the fields as default.
3. Try out a test email and see that it is it dumped to the console.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have run rubocop and erblint for style check. If you haven't, run overcommit --install && overcommit --sign to use pre-commit hook for linting
• My change requires a change to the documentation, which is located at Autolab Docs
• I have updated the documentation accordingly, included in this PR

[coderabbitai]

Walkthrough

Walkthrough

The changes in this pull request involve updates to the SMTP configuration handling within the application. Specifically, the authentication parameter now allows for a nil value, providing users the option to configure an SMTP server without authentication. Additionally, the user interface has been updated to reflect this new option, and documentation has been revised to include the new authentication method.

Changes

File	Change Summary
app/controllers/smtp_config_controller.rb	Modified params_to_settings method to set authentication, user_name, and password to nil under specific conditions.
app/views/admins/_smtp_integration.html.erb	Updated SMTP authentication dropdown to include :none as an option alongside existing options.
docs/installation/mailing.md	Updated documentation to reflect the addition of none as an option for the authentication parameter.

Assessment against linked issues

Objective	Addressed	Explanation
Allow SMTP Authentication to be nil (#2172)	✅

Possibly related PRs

• Fix an incorrect setting name (SMTP authentication) #2175: This PR addresses changes to the authentication parameter in SMTP configuration, which is directly related to the modifications made in the main PR regarding how the authentication parameter is processed in the params_to_settings method.
• Edited documentation and removed SMTP configs from env #2186: This PR updates the documentation for SMTP configuration, including the authentication parameter, which aligns with the changes made in the main PR that also involve handling the authentication parameter.

Suggested labels

Type: Bug, small

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 502e05b and 2af13bd.

Files selected for processing (3)

• app/controllers/smtp_config_controller.rb (1 hunks)
• app/views/admins/_smtp_integration.html.erb (1 hunks)
• docs/installation/mailing.md (1 hunks)

Additional comments not posted (5)

app/controllers/smtp_config_controller.rb (3)

87-87: LGTM!

The change to conditionally set the authentication setting to nil when the authentication parameter is 'none' enables support for SMTP servers that do not require authentication. This aligns with the PR objective.

---

88-88: LGTM!

The change to conditionally set the user_name setting to nil when the username parameter is an empty string enables support for SMTP servers that do not require a username. This aligns with the PR objective.

---

89-89: LGTM!

The change to conditionally set the password setting to nil when the password parameter is an empty string enables support for SMTP servers that do not require a password. This aligns with the PR objective.

docs/installation/mailing.md (1)

64-64: LGTM!

The addition of 'none' as an option for the authentication parameter aligns with the PR objectives of allowing SMTP authentication to be nil. This change enhances the flexibility of the SMTP configuration by accommodating scenarios where authentication is not required. The comment accurately lists all the available options for the authentication parameter.

app/views/admins/_smtp_integration.html.erb (1)

57-57: LGTM!

The addition of the :none option for SMTP server authentication aligns with the PR objective to allow nil authentication. The selected value logic remains correct and consistent.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.