Email Integration

The following pertains to Yarkon Server only. Yarkon Cloud is fully integrated with an email service provided by Yarkon, and does not require any additional work by the end customer.

Access to an email server or service is required to communicate new passwords to end-users, and to allow them to self-serve their accounts (reset password etc.). Email is used to securely and confidentially communicate the newly auto-generated, temporary passwords to the users.

You would need to provide access to an SMTP (Email) end-point that Yarkon Admin Console would then be able to use to send outbound email. The SES service is a good choice, but any other email service you use for your business should work just as well.


Yarkon will work with any standard SMTP server. Make sure to follow the instructions recommended by your provider. You can always use the Validate button to verify that Yarkon can communicate with the SMTP server, or the Send Test Email button to send an email from Yarkon to an address of your choosing to ensure it all works.

In the image below you can see the Yarkon Admin Console set up to use a 1and1 SMTP server, a popular choice.

Yarkon Admin Console using SMTP


AWS SES is supported. Follow this document from Amazon on how to obtain your credentials. Using Yarkon Admin Console, choose the Administration option from the sidebar, then select the Mail tab. Choose SES for the service type, this will automatically use the correct port and TLS settings. The SMTP endpoints (hosts) for SES are listed here; use the appropriate endpoint for the Server Name. Use the aforementioned SMTP credentials for the Username and Password. The Send From field must be a verified email address you can send from. Use the Display Name field to add a user friendly name.

Note that the sender email must be approved by AWS SES before it can be used to send outbound email.

In the image below you can see the Yarkon Admin Console set up to use an AWS SES endpoint.

Yarkon Admin Console using AWS SES


You can use Gmail as your SMTP server, but you should not. Even though Gmail is the fastest way to get started with sending emails, it is by no means a preferable solution. Gmail expects the user to be an actual user and not a robot/application, so it runs heuristics for every login attempt and blocks anything that looks suspicious. Being that this is a business product, having access to an Email server is expected and required. Use the same Email server you use for your other automated emails.