Skip to content
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

Emails not sending #2636

Closed
damusmf opened this issue Nov 10, 2018 · 21 comments
Closed

Emails not sending #2636

damusmf opened this issue Nov 10, 2018 · 21 comments

Comments

@damusmf
Copy link

damusmf commented Nov 10, 2018

Ombi build Version:

V 3.0.3966

Update Branch:

Develop

Media Sever:

Plex

Media Server Version:

Version 1.13.5.5291

Operating System:

Ubuntu 16.04 - ombi
Server 2012r2 - plex media server

Ombi Applicable Logs (from /logs/ directory or the Admin page):


Problem Description:

Email notifications are no longer working. Noticed when the newsletter stopped sending and no test notifications from email config page are sent. i don't see anything in the logs relate to it. Cleared todays log file and restarted ombi and hit the test button on email and nothing populated. Not sure what else to look for as other services that use my relay are still sending just fine

Reproduction Steps:

Attempt to send any sort of email from ombi. Test or otherwise.

@ghost ghost added the bug / issue label Nov 10, 2018
@tidusjar
Copy link
Member

Logs?

@damusmf
Copy link
Author

damusmf commented Nov 10, 2018

Nothing in the logs. As in to narrow down what was going on I cleared the initial log file. Restarted ombi and tried it again. The test email button doesn't write anything to the log. All i get is the notification popup in the webui that says email was sent successfully.

@tidusjar
Copy link
Member

Please check the stdout

@damusmf
Copy link
Author

damusmf commented Nov 17, 2018

There is nothing. It is like pressing the button doesn't actually do anything except say successful. If i use the gmail smtp relay i can get it to display info, when i use my internal relay that relays through my domain i get nothing at all in logs or stdout

@damusmf
Copy link
Author

damusmf commented Nov 21, 2018

More notes here. I have my internal smtp relay set to route mail through gsuite. As it sits this works for everything else except ombi. It used to work for ombi as well.

Now what I'm noticing is that emails from ombi are not being sent through to other Google accounts. So any Gmail address or my gsuite address dont receive email from ombi. If I send an email from ombi to a non Google address it sends just fine.

Again other services I have (tautulli, unifi controller) can send email using the same relay to Google email addresses just fine.

@damusmf
Copy link
Author

damusmf commented Nov 21, 2018

Turns out I am just not that smart. Emails from ombi going through the relay are getting marked as spam by Google. This is a new thing. Not sure if the email template changed and now Google is flagging it as potential spam. I can create a rule myself to never send it to spam, but for the users I have it is a bit of an inconvenience. Definitely a new thing within the last month. All my users are tied to their Gmail account except one. And none of them are receiving the emails now.

@tidusjar
Copy link
Member

tidusjar commented Nov 21, 2018 via email

@asc6
Copy link

asc6 commented Nov 29, 2018

Not sure how much this helps, but I have the same issue where I send my emails via GSuite and all of the sudden they are getting marked as spam by Google. It’s been about the last month for me as well. Same exact setup as damusmf. Obviously if it’s a google thing, not much you can do tidusjar, but figured I’d provide more information as if there’s two of us having the exact same issue there’s bound to be more.

@Codehhh
Copy link
Contributor

Codehhh commented Nov 30, 2018

I just switched to GSuite and now my Ombi emails are being marked as spam. I can still receive emails from my other services just fine though.
--
Edit: I changed my email inside of Ombi to a regular GMail account and the test email went straight into my inbox.

@tidusjar
Copy link
Member

Not sure if there is anything I can do with this, the way we send and the templates themselves have not changed in a very long time

@gdob
Copy link

gdob commented Feb 16, 2019

I don’t know much about this and I’m using Mailgun, but the headers contain <BG2SZ08UR6U4.GMNJKRNR2JBI2@localhost.localdomain> so that’s probably why mails from SendGrid or Mailgun go straight to Gmail’s Spam folder. When I send email notifications from Tautulli or SSMTP it uses my hostname and I have no problems with delivery.

For instance SSMTP emails have something like this for Message ID: <BG2SZ08UR6U4.GMNJKRNR2JBI2@example.com>.

Maybe the email delivery system needs some tweaking on Ombi.

Edit: What’s funny is this. And it still goes straight to spam.

screen shot 2019-02-16 at 21 20 41

@tidusjar
Copy link
Member

@gdob Good find,

I've pushed an update to develop branch, if you have the ApplicationUrl set in the CustomziationSettings then we will use that for the domain.

@gdob
Copy link

gdob commented Feb 17, 2019

My application URL is set to https://example.com/ombi, so I’m guessing it will use just example.com in the Message ID headers, right?

@tidusjar
Copy link
Member

tidusjar commented Feb 17, 2019 via email

@gdob
Copy link

gdob commented Feb 18, 2019

Weird, after upgrading to v3.0.4248 the message ID header still contains localhost.localdomain.
<MMZNV0UES6U4.3LQVJCZCGL4I@localhost.localdomain> Maybe I have something configured incorrectly? My ApplicationUrl is set to ombi.example.com.

@tidusjar
Copy link
Member

Strange. I'll reopen

@tidusjar tidusjar reopened this Feb 18, 2019
@jamiew0w
Copy link

On 3.0.4256 can confirm this is still happening

Subject: [blah]!
Message-Id: <44MCPXW5V6U4.FMLEXO4W24O32@localhost.localdomain>

That's with the application path set also, is there a hotfix we can apply in the meantime?

@gdob
Copy link

gdob commented Mar 1, 2019 via email

@gdob
Copy link

gdob commented Mar 14, 2019

I’ll just update this issue with a quote from Mailgun’s documentation:

Gmail pays particularly close attention to Message ID and Received headers. Message IDs that are formed incorrectly (without brackets <> and with wrong domain after @) can make Gmail think you are a spammer. The simplest way to create the right Message ID is to not set Message ID at all. Then Mailgun will create a perfect Message ID for you. Also, if you use the HTTP API, Mailgun will deal with all of this for you.

tidusjar added a commit that referenced this issue Mar 14, 2019
@tidusjar
Copy link
Member

This has been fixed in the develop branch! 🎉 🎈

@PixelPerfectJenna
Copy link

PixelPerfectJenna commented Jan 22, 2020

I am having the same issue with the spam, but my email is not being sent under the same domain that Ombi is on. So I can't change the ApplicationUrl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants