HI!
For as long i remember the email notification have been working really nice and accurate. But recently I do not receive email anymore? That may be due to a part of our setup but as we are trying to solve and investigate the issue
we realize that the email get send by the slave itseft… trying to connect to the SMTP server…
We are a school and we can’t allow anonymous smtp to be sent from all CPU in the laps and classrooms.
Is there a way to limit the slaves sending email using smtp? Let say My dedicated CPU in the server room and restrict the workstation in the lab?
Any trick or idea of what should i do?
Millions Thanks
jacquesD
Hi,
A similar request was made some time ago for all emails to be sent only from the Pulse machine, which would also work for you here. I’ll try and bump the feature request up the list order 
Just a thought, you mentioned that ‘anonymous smtp’ is not allowed. How about enabling SMTP authentication via monitor > super-user (so it’s restricted to you) and then your smtp server will only work if the correct authentication is sent by Deadline and then all your machines can be allowed to ‘see’ your smtp server.
Cheers,
Mike
hi Mike
In our super freak school environment. The service and port are block on all workstation …
If we unlock the service and port to allow deadline to use smtP via repository save setting and credential.
that will also means that all workstation are able to send smtp request using some command line … Isn’t it?
That where the need of sending only from a few selected machine of the pulse machine only…
Easier to manage in a freak environment!
;D
Hi,
Yes, command-line would become available, outside of Deadline as well. However, my point was, that even with command line access outside of Deadline, if a user doesn’t have the username and/or the password, any smtp request will be rejected by the smtp server. I know many enterprise users (outside of Deadline as well) who use this approach to secure smtp access. However, I understand each facility has it’s own restrictions. The previous feature request I mentioned has now been updated on our wish-list.
Regards,
Mike