I have this set up as I did in version 6, the email test in the SMTP settings works fine, everything is filled out in notifications tab but I am not getting any emails…
Email notification is enabled for your user account?
docs.thinkboxsoftware.com/produc … r-settings
Are the emails hitting your SPAM / JUNK folder?
You receive the “test” email ok, but you don’t get any of the ‘global’ email notifications as defined here?
docs.thinkboxsoftware.com/produc … ifications
yes
No
correct
ok. After configuring the various fields with one or more email addresses and committing the change by pressing “OK” button, you waited at least 10 mins for the settings to be propagated throughout the Deadline system?
Emails for “job completed” for example, are sent out randomly from a Deadline Slave. Do all your slaves have routable access to your SMTP server and can successfully send an email compared to the machine that you actually performed the “send test email” on?
If your defining multiple email addresses in the same field, you are using a “comma” to separate them correctly?
If none of the above explains it, can you enable verbose application logging here for at least Slave/Pulse:
docs.thinkboxsoftware.com/produc … on-logging
wait a while for when you know an email should have been sent by, then package up and send us the logs, which should explain why the emails aren’t coming through.
Ah I just saw an error in the pulse log
2015-08-13 15:44:45: Error occurred while trying to send email:
2015-08-13 15:44:45: System.Net.Mail.SmtpException - The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.5.1 Authentication Required. Learn more at
When I look at the smtp settings window, my auth password appears blank… Is that an issue? I didn’t really think about it before
But then I fill it in, send a test email successfully -press okay, then next time the windows is blank again.
I just put the same settings into the secondary tab, and the password remained… So I guess that’s the issue?
I can confirm that worked, I recieved an email from the secondary SMTP (which was the same)
Ah ha! So, for the life of me, I can’t find the related forum post / private support ticket, but this was reported literally last week or something and it’s a UI form bug in the “primary” SMTP server configuration. So, this explains why the “secondary” SMTP server page is playing ball for you. Now, I’m working completely from memory here, but IIRC, the “password” field isn’t saved unless you edit the “username” field. So, as a temp hack workaround, if you enter your “Password” AND then edit the “username” field to something wrong and then back again, so it’s correct and then commit your changes, does the “password” field ‘stick’? This has already been fixed internally and I would have thought it will find it’s way into v7.2 beta 5 build when released to the beta group, which is open for beta if you so wish?
Or just configure the secondary as you have!
I did your work around, and that works indeed!
I am on the beta but don’t tend to use it. I should…