FEATURE: Improve group email settings UI (#13083)
This overhauls the user interface for the group email settings management, aiming to make it a lot easier to test the settings entered and confirm they are correct before proceeding. We do this by forcing the user to test the settings before they can be saved to the database. It also includes some quality of life improvements around setting up IMAP and SMTP for our first supported provider, GMail. This PR does not remove the old group email config, that will come in a subsequent PR. This is related to https://meta.discourse.org/t/imap-support-for-group-inboxes/160588 so read that if you would like more backstory.
### UI
Both site settings of `enable_imap` and `enable_smtp` must be true to test this. You must enable SMTP first to enable IMAP.
You can prefill the SMTP settings with GMail configuration. To proceed with saving these settings you must test them, which is handled by the EmailSettingsValidator.
If there is an issue with the configuration or credentials a meaningful error message should be shown.
IMAP settings must also be validated when IMAP is enabled, before saving.
When saving IMAP, we fetch the mailboxes for that account and populate them. This mailbox must be selected and saved for IMAP to work (the feature acts as though it is disabled until the mailbox is selected and saved):
### Database & Backend
This adds several columns to the Groups table. The purpose of this change is to make it much more explicit that SMTP/IMAP is enabled for a group, rather than relying on settings not being null. Also included is an UPDATE query to backfill these columns. These columns are automatically filled when updating the group.
For GMail, we now filter the mailboxes returned. This is so users cannot use a mailbox like Sent or Trash for syncing, which would generally be disastrous.
There is a new group endpoint for testing email settings. This may be useful in the future for other places in our UI, at which point it can be extracted to a more generic endpoint or module to be included.
2021-05-27 19:28:18 -04:00
|
|
|
# frozen_string_literal: true
|
|
|
|
|
|
|
|
require "net/imap"
|
|
|
|
require "net/smtp"
|
|
|
|
require "net/pop"
|
|
|
|
|
|
|
|
class EmailSettingsExceptionHandler
|
|
|
|
EXPECTED_EXCEPTIONS = [
|
|
|
|
Net::POPAuthenticationError,
|
|
|
|
Net::IMAP::NoResponseError,
|
|
|
|
Net::IMAP::Error,
|
|
|
|
Net::SMTPAuthenticationError,
|
|
|
|
Net::SMTPServerBusy,
|
|
|
|
Net::SMTPSyntaxError,
|
|
|
|
Net::SMTPFatalError,
|
|
|
|
Net::SMTPUnknownError,
|
|
|
|
Net::OpenTimeout,
|
|
|
|
Net::ReadTimeout,
|
|
|
|
SocketError,
|
|
|
|
Errno::ECONNREFUSED,
|
|
|
|
]
|
|
|
|
|
|
|
|
class GenericProvider
|
|
|
|
def initialize(exception)
|
|
|
|
@exception = exception
|
|
|
|
end
|
|
|
|
|
|
|
|
def message
|
|
|
|
case @exception
|
|
|
|
when Net::POPAuthenticationError
|
|
|
|
net_pop_authentication_error
|
|
|
|
when Net::IMAP::NoResponseError
|
|
|
|
net_imap_no_response_error
|
|
|
|
when Net::IMAP::Error
|
|
|
|
net_imap_unhandled_error
|
|
|
|
when Net::SMTPAuthenticationError
|
|
|
|
net_smtp_authentication_error
|
|
|
|
when Net::SMTPServerBusy
|
|
|
|
net_smtp_server_busy
|
|
|
|
when Net::SMTPSyntaxError, Net::SMTPFatalError, Net::SMTPUnknownError
|
|
|
|
net_smtp_unhandled_error
|
|
|
|
when SocketError, Errno::ECONNREFUSED
|
|
|
|
socket_connection_error
|
|
|
|
when Net::OpenTimeout, Net::ReadTimeout
|
|
|
|
net_timeout_error
|
|
|
|
else
|
|
|
|
unhandled_error
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
private
|
|
|
|
|
|
|
|
def net_pop_authentication_error
|
|
|
|
I18n.t("email_settings.pop3_authentication_error")
|
|
|
|
end
|
|
|
|
|
|
|
|
def net_imap_no_response_error
|
|
|
|
# Most of IMAP's errors are lumped under the NoResponseError, including invalid
|
|
|
|
# credentials errors, because it is raised when a "NO" response is
|
|
|
|
# raised from the IMAP server https://datatracker.ietf.org/doc/html/rfc3501#section-7.1.2
|
|
|
|
#
|
|
|
|
# Generally, it should be fairly safe to just return the error message as is.
|
|
|
|
if @exception.message.match(/Invalid credentials/)
|
|
|
|
I18n.t("email_settings.imap_authentication_error")
|
|
|
|
else
|
|
|
|
I18n.t(
|
|
|
|
"email_settings.imap_no_response_error",
|
|
|
|
message: @exception.message.gsub(" (Failure)", ""),
|
|
|
|
)
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
def net_imap_unhandled_error
|
|
|
|
I18n.t("email_settings.imap_unhandled_error", message: @exception.message)
|
|
|
|
end
|
|
|
|
|
|
|
|
def net_smtp_authentication_error
|
2024-07-15 19:14:17 -04:00
|
|
|
# Generally SMTP authentication errors are due to invalid credentials,
|
|
|
|
# and most common mail servers provide more detailed error messages,
|
|
|
|
# so it should be safe to return the error message as is.
|
|
|
|
#
|
|
|
|
# Example: Office 365 returns:
|
|
|
|
#
|
|
|
|
# 535 5.7.139 Authentication unsuccessful, user is locked by your organization's security defaults policy. Contact your administrator.
|
|
|
|
#
|
|
|
|
# Example: Gmail returns:
|
|
|
|
#
|
|
|
|
# Application-specific password required. Learn more at https://support.google.com/accounts/answer/185833
|
|
|
|
I18n.t("email_settings.smtp_authentication_error", message: @exception.message)
|
FEATURE: Improve group email settings UI (#13083)
This overhauls the user interface for the group email settings management, aiming to make it a lot easier to test the settings entered and confirm they are correct before proceeding. We do this by forcing the user to test the settings before they can be saved to the database. It also includes some quality of life improvements around setting up IMAP and SMTP for our first supported provider, GMail. This PR does not remove the old group email config, that will come in a subsequent PR. This is related to https://meta.discourse.org/t/imap-support-for-group-inboxes/160588 so read that if you would like more backstory.
### UI
Both site settings of `enable_imap` and `enable_smtp` must be true to test this. You must enable SMTP first to enable IMAP.
You can prefill the SMTP settings with GMail configuration. To proceed with saving these settings you must test them, which is handled by the EmailSettingsValidator.
If there is an issue with the configuration or credentials a meaningful error message should be shown.
IMAP settings must also be validated when IMAP is enabled, before saving.
When saving IMAP, we fetch the mailboxes for that account and populate them. This mailbox must be selected and saved for IMAP to work (the feature acts as though it is disabled until the mailbox is selected and saved):
### Database & Backend
This adds several columns to the Groups table. The purpose of this change is to make it much more explicit that SMTP/IMAP is enabled for a group, rather than relying on settings not being null. Also included is an UPDATE query to backfill these columns. These columns are automatically filled when updating the group.
For GMail, we now filter the mailboxes returned. This is so users cannot use a mailbox like Sent or Trash for syncing, which would generally be disastrous.
There is a new group endpoint for testing email settings. This may be useful in the future for other places in our UI, at which point it can be extracted to a more generic endpoint or module to be included.
2021-05-27 19:28:18 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
def net_smtp_server_busy
|
|
|
|
I18n.t("email_settings.smtp_server_busy_error")
|
|
|
|
end
|
|
|
|
|
|
|
|
def net_smtp_unhandled_error
|
|
|
|
I18n.t("email_settings.smtp_unhandled_error", message: @exception.message)
|
|
|
|
end
|
|
|
|
|
|
|
|
def socket_connection_error
|
|
|
|
I18n.t("email_settings.connection_error")
|
|
|
|
end
|
|
|
|
|
|
|
|
def net_timeout_error
|
|
|
|
I18n.t("email_settings.timeout_error")
|
|
|
|
end
|
|
|
|
|
|
|
|
def unhandled_error
|
|
|
|
I18n.t("email_settings.unhandled_error", message: @exception.message)
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
|
|
|
def self.friendly_exception_message(exception, host)
|
2024-07-15 19:14:17 -04:00
|
|
|
EmailSettingsExceptionHandler::GenericProvider.new(exception).message
|
FEATURE: Improve group email settings UI (#13083)
This overhauls the user interface for the group email settings management, aiming to make it a lot easier to test the settings entered and confirm they are correct before proceeding. We do this by forcing the user to test the settings before they can be saved to the database. It also includes some quality of life improvements around setting up IMAP and SMTP for our first supported provider, GMail. This PR does not remove the old group email config, that will come in a subsequent PR. This is related to https://meta.discourse.org/t/imap-support-for-group-inboxes/160588 so read that if you would like more backstory.
### UI
Both site settings of `enable_imap` and `enable_smtp` must be true to test this. You must enable SMTP first to enable IMAP.
You can prefill the SMTP settings with GMail configuration. To proceed with saving these settings you must test them, which is handled by the EmailSettingsValidator.
If there is an issue with the configuration or credentials a meaningful error message should be shown.
IMAP settings must also be validated when IMAP is enabled, before saving.
When saving IMAP, we fetch the mailboxes for that account and populate them. This mailbox must be selected and saved for IMAP to work (the feature acts as though it is disabled until the mailbox is selected and saved):
### Database & Backend
This adds several columns to the Groups table. The purpose of this change is to make it much more explicit that SMTP/IMAP is enabled for a group, rather than relying on settings not being null. Also included is an UPDATE query to backfill these columns. These columns are automatically filled when updating the group.
For GMail, we now filter the mailboxes returned. This is so users cannot use a mailbox like Sent or Trash for syncing, which would generally be disastrous.
There is a new group endpoint for testing email settings. This may be useful in the future for other places in our UI, at which point it can be extracted to a more generic endpoint or module to be included.
2021-05-27 19:28:18 -04:00
|
|
|
end
|
|
|
|
end
|