-
-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Email notification invalid domain #5161
Comments
What’s your domain in the application url under the ombi settings? Like the
general settings?
…On Sat, 17 Aug 2024 at 2:10 AM, Thom0145 ***@***.***> wrote:
Summary
My test email will not send, when I check the logs I get invalid domain
log20240816.txt
<https://github.com/user-attachments/files/16642936/log20240816.txt>
Ombi Version
4.44.1
What platform(s) does this occur on?
Windows
What database are you using?
SQLite (Default)
Relevant log output
System.ArgumentException: The domain is invalid. (Parameter 'domain')
at MimeKit.Utils.MimeUtils.GenerateMessageId(String domain)
at Ombi.Notifications.GenericEmailProvider.SendAdHoc(NotificationMessage model, EmailNotificationSettings settings) in /home/runner/work/Ombi/Ombi/src/Ombi.Notifications/GenericEmailProvider.cs:line 47
at Ombi.Controllers.V1.External.TesterController.Email(EmailNotificationSettings settings) in /home/runner/work/Ombi/Ombi/src/Ombi/Controllers/V1/External/TesterController.cs:line 300
—
Reply to this email directly, view it on GitHub
<#5161>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSVULF6LCVQWDK6KXWKAOTZR2PHVAVCNFSM6AAAAABMU55XOSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3TCMRVGAZDAOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
My test email will not send, when I check the logs I get invalid domain
log20240816.txt
Ombi Version
4.44.1
What platform(s) does this occur on?
Windows
What database are you using?
SQLite (Default)
Relevant log output
The text was updated successfully, but these errors were encountered: