CBers 6778 Posted November 30, 2016 Share Posted November 30, 2016 Are you setting the To and From address up with different accounts? I just put same address in in both when testing with my gmail. Even on a new build I get error message (pop-up) on new plugin 3.0.6178.681, I can get the previous version to work though 3.0.6143.20346. With GMAIL yes. I have created a new GMAIL email address and have used that to send to my normal GMAIL email address, but the email bounces back to itself with that you@ error. It seems that using the same To/From GMAIL address, is just a masking the issue, as it's the sending email address that is receiving the email and the error messages, not the recipient email. Link to comment Share on other sites More sharing options...
Happy2Play 8319 Posted November 30, 2016 Share Posted November 30, 2016 Maybe, I can send from Hotmail to gmail, but get that same bounce error trying gmail to hotmail. Link to comment Share on other sites More sharing options...
MSattler 387 Posted November 30, 2016 Share Posted November 30, 2016 With GMAIL yes. I have created a new GMAIL email address and have used that to send to my normal GMAIL email address, but the email bounces back to itself with that you@ error. It seems that using the same To/From GMAIL address, is just a masking the issue, as it's the sending email address that is receiving the email and the error messages, not the recipient email. Even with using the same from and to, I still get the you@.com bounce. Link to comment Share on other sites More sharing options...
Happy2Play 8319 Posted November 30, 2016 Share Posted November 30, 2016 (edited) @@CBers @@MSattler Just tested this if I use port 465 I get the you@ bounce, but using port 587 I don't get any mail. On plugin (.681) Edited November 30, 2016 by Happy2Play Link to comment Share on other sites More sharing options...
Happy2Play 8319 Posted November 30, 2016 Share Posted November 30, 2016 (edited) My testing result from previous and current plugin Single User3.0.6143.20346From and To using same address: gmail notifications worked on ports 465 and 587 Hotmail failed(no emails) on port 465From gmail to hotmail: failed (no emails) on port 465 but port 587 workedFrom hotmail to gmail: failed (no emails) ports 465 but port 587 worked Multiple usersTested one user setup with hotmail and the other with gmailUser A password get deleted when you save user B and vice versas (copied both hashed passwords for next step)Shutdown server and manually entered hashed password for the one that is missing allows both to recieve emails ________________________________________________________________________________________________________ Reset xml file for single user (all gmail)Updated to 3.0.6178.681Clicked Test - error (log) "The handshake failed due to an unexpected packet format."Re-entered passord - same as aboveShutdown server and delete xmlRestarted and entered information in againSame errors (log) "The handshake failed due to an unexpected packet format."Changed from port 587 to 465Test notification received but received email failure also Delivery to the following recipient failed permanently: you@.comTechnical details of permanent failure: Google tried to deliver your message, but it was rejected by the server for the recipient domain gmail.com gmail to hotmailport 465 recieve failure email as above but recieve test notification in gmail not hotmail.port 587 error (log) The handshake failed due to an unexpected packet format. Changed to hotmailport 465 error (log)"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"port 587 error (log)"The handshake failed due to an unexpected packet format." Probably by design but Test Notifications should be independent of the user you select to test. Current emails are attempted to sent to All configured users enabled or not. Edited November 30, 2016 by Happy2Play Link to comment Share on other sites More sharing options...
CBers 6778 Posted November 30, 2016 Share Posted November 30, 2016 Even with using the same from and to, I still get the you@.com bounce. Yes, but no matter what the TO address is, that message is received by the sending email. Looks like a bug using Gmail SMTP. Link to comment Share on other sites More sharing options...
CBers 6778 Posted November 30, 2016 Share Posted November 30, 2016 So @@Happy2Play, there's no real answer then? Have you tried all of the above with the version that you made read-only? Link to comment Share on other sites More sharing options...
Happy2Play 8319 Posted November 30, 2016 Share Posted November 30, 2016 So @@Happy2Play, there's no real answer then? Have you tried all of the above with the version that you made read-only? I haven't tested with the stable version in dev but I can here in a few minutes. Link to comment Share on other sites More sharing options...
CBers 6778 Posted November 30, 2016 Share Posted November 30, 2016 I haven't tested with the stable version in dev but I can here in a few minutes. OK, only if you have time. Thanks. Link to comment Share on other sites More sharing options...
Happy2Play 8319 Posted November 30, 2016 Share Posted November 30, 2016 New plugin 3.0.6178.28512 gmail to hotmail 465 goodgmail to hotmail 587 pop-up error log The handshake failed due to an unexpected packet format. gmail port 465 goodgmail port 587 pop-up error log The handshake failed due to an unexpected packet format. homail port 465 pop-up error log A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond hotmail port 587 pop-up error log The handshake failed due to an unexpected packet format. hotmail to gmail port 465 pop-up error log A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respondhotmail to gmail port 587 pop-up error log The handshake failed due to an unexpected packet format. Link to comment Share on other sites More sharing options...
Luke 37143 Posted November 30, 2016 Share Posted November 30, 2016 At this point I can revert it back to the stock .net smtp mailer, or I can keep the third party one. The stock mailer built into the framework I think is a little out of date and will only work with email domains that are not exactly on the cutting edge. The third party mailer has additional configuration and can probably solve the above, however someone else in the community will have to take on the responsibility of exploring this. Right now I am leaning towards reverting to stock and keeping the plugin around temporarily so that everyone who has it can get an update that will be compatible with their server version. And then I'll probably just pull it until a contributor comes around who is interested in helping to get this perfected. Maybe @@landgazr or @@chef enjoy email notifications? Link to comment Share on other sites More sharing options...
Happy2Play 8319 Posted November 30, 2016 Share Posted November 30, 2016 Overall 3.0.6143.20346 had the most functionality at least from my test, unless this changed with server updates affected this. Only issue was multi-user password issue. @@CBers 3.0.6119.41073 on dev 3.1.6178.26744 doesn't work at all all configurations port 465 pop-up error log Unable to find the specified file. all configurations port 587 pop-up error log Unable to find the specified file. 1 Link to comment Share on other sites More sharing options...
Happy2Play 8319 Posted November 30, 2016 Share Posted November 30, 2016 (edited) Looks like only port 587 in server 3.1.6178.26744 and plugin 3.0.6143.20346 works now. gmail to hotmail 465 Syntax error, command unrecognized. The server response was:gmail to hotmail 587 Good gmail port 465 Syntax error, command unrecognized. The server response was:gmail port 587 Good homail port 465 pop-up error log A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respondhotmail port 587 Good hotmail to gmail port 465 pop-up error log A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respondhotmail to gmail port 587 Good Edited November 30, 2016 by Happy2Play Link to comment Share on other sites More sharing options...
trifleneurotic 44 Posted December 1, 2016 Share Posted December 1, 2016 Although I'm new to Emby, I currently do not use e-mail notifications. However the world doesn't revolve around me (: I'd love to help if I can. Link to comment Share on other sites More sharing options...
Luke 37143 Posted December 1, 2016 Share Posted December 1, 2016 I have just reverted the plugin to use the stock smtp mailer built into the .net framework. I have also moved the source to a standalone repository to make it easier for anyone interested to help out: https://github.com/MediaBrowser/email-notifications Thanks. Link to comment Share on other sites More sharing options...
rjay 21 Posted December 1, 2016 Share Posted December 1, 2016 What happ2play mentioned is exactly what I was experiencing and is now making a bit of sense to me. I setup a second user to notify them of library updates which is when I started noticing all the problems. The password thing mentioned makes complete sense as I would go in Save the password for one user, test and all good then go onto the second user and notice password was missing so resetup again thinking it was working only to find the first user was without password again and no longer receiving emails. thanks Link to comment Share on other sites More sharing options...
CBers 6778 Posted December 1, 2016 Share Posted December 1, 2016 I am now running v3.0.6178.37996 of the plugin and I have reverted my sending email (FROM) to my own email address, sending TO my gmail addres. Test notifications with the plugin on both dev and beta servers were received. I'll wait and see if I get other notifications. Link to comment Share on other sites More sharing options...
Happy2Play 8319 Posted December 1, 2016 Share Posted December 1, 2016 Tested plugin v3.0.6178.37996, everything appears to work only on port 587. Link to comment Share on other sites More sharing options...
Luke 37143 Posted December 1, 2016 Share Posted December 1, 2016 Well done. Link to comment Share on other sites More sharing options...
econ 74 Posted December 1, 2016 Share Posted December 1, 2016 Email notifications using gmail on 587 also working for me. Link to comment Share on other sites More sharing options...
Luke 37143 Posted December 1, 2016 Share Posted December 1, 2016 Thanks for confirming. Link to comment Share on other sites More sharing options...
2Fake 0 Posted January 9, 2018 Share Posted January 9, 2018 My Email notification doesn't work anymore. My settings are: From and To Email Address: My own Gmailadress SMTP Hostname smtp.gmail.com Port 587 both checkboxes are checked SMTP Autentification Username: my own Gmailadress password app password from google. This is the failure i can see in the log file 2018-01-09 11:41:01.964 Error HttpServer: Error processing request *** Error Report *** Version: 3.2.60.1 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -updatepackage emby-server-deb_{version}_armhf.deb Operating system: Unix 4.9.35.7 64-Bit OS: False 64-Bit Process: False User Interactive: True Processor count: 4 Program data path: /var/lib/emby Application directory: /opt/emby-server/system System.Net.Mail.SmtpException: Failure sending mail. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.PartialFrameCallback(AsyncProtocolRequest asyncRequest) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result) at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult) at System.Net.Mail.SmtpConnection.ConnectAndHandshakeAsyncResult.TlsStreamAuthenticateCallback(IAsyncResult result) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Mail.SmtpConnection.ConnectAndHandshakeAsyncResult.End(IAsyncResult result) at System.Net.Mail.SmtpTransport.EndGetConnection(IAsyncResult result) at System.Net.Mail.SmtpClient.ConnectCallback(IAsyncResult result) --- End of inner exception stack trace --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Plugins.SmtpNotifications.Notifier.<SendNotification>d__11.MoveNext() System.Net.Mail.SmtpException at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Plugins.SmtpNotifications.Notifier.<SendNotification>d__11.MoveNext() InnerException: System.Security.Authentication.AuthenticationException System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.PartialFrameCallback(AsyncProtocolRequest asyncRequest) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result) at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult) at System.Net.Mail.SmtpConnection.ConnectAndHandshakeAsyncResult.TlsStreamAuthenticateCallback(IAsyncResult result) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Mail.SmtpConnection.ConnectAndHandshakeAsyncResult.End(IAsyncResult result) at System.Net.Mail.SmtpTransport.EndGetConnection(IAsyncResult result) at System.Net.Mail.SmtpClient.ConnectCallback(IAsyncResult result) at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.PartialFrameCallback(AsyncProtocolRequest asyncRequest) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result) at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult) at System.Net.Mail.SmtpConnection.ConnectAndHandshakeAsyncResult.TlsStreamAuthenticateCallback(IAsyncResult result) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Net.Mail.SmtpConnection.ConnectAndHandshakeAsyncResult.End(IAsyncResult result) at System.Net.Mail.SmtpTransport.EndGetConnection(IAsyncResult result) at System.Net.Mail.SmtpClient.ConnectCallback(IAsyncResult result) It seems that there is a problem with the ssl connection. I can see that app password was never used, so emby never logged in and try to send the email. Hope you can help me. 2Fake Link to comment Share on other sites More sharing options...
Luke 37143 Posted January 9, 2018 Share Posted January 9, 2018 @@2Fake, I don't know, sorry. The .NET Core email API is giving an error about the SSL cert of the remote email server. The only thing I can tell you is that in the past others have had issues using this with gmail and have had to make changes in their google accounts in order to get it to work. 1 Link to comment Share on other sites More sharing options...
CBers 6778 Posted January 9, 2018 Share Posted January 9, 2018 You may need to allow less secure apps to use your account. https://support.google.com/accounts/answer/6010255?hl=en 1 Link to comment Share on other sites More sharing options...
Luke 37143 Posted January 9, 2018 Share Posted January 9, 2018 Thanks @@CBers Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now