Why we need to configure mail server on Omada SDN controller before adding cloud user and email log
OC200 , Omada Software Controller , Omada SDN
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
For Omada SDN controller, if you want to add cloud user, email log, and reset password by email, you need to configure the mail server at first.
How to configure mail server?
The following is the configuration interface for mail server settings. You need to fill in the SMTP server address, SMTP service port. According to the requirement of your mailbox, you may need to enable SSL and authentication, fill in the username and password of your mailbox.
Let’s take Gmail as an example to show the configuration.
SMTP: smtp.gmail.com
Port: 465
SSL: Checked
Authentication: Checked
Username: Your Gmail address ( Here we use tplinksmb.fae@gmai.com as an example)
Password: Gmail APP password
Sender Address: Your Gmail address
Note: To set the mail server successfully, we need to make sure the third-part mail server already enables SMTP service and allows us to log in. Take Gmail for example:
- Gmail enables SMTP service by default but cannot directly log in. We need to set APP password for Gmail then use this password on the Omada controller to log in. About how to set APP password for Gmail, you can refer to https://support.google.com/accounts/answer/185833?hl=en
- Gmail may restrict the location of the application accessing of the Gmail account. If the Omada Controller locates in another Country or geographical location which is far from your routine location where you live and access Gmail daily, you may need to open the browser on the PC in the Omada Controller site and login into Gmail. It makes Gmail understand that the Omada Controller/OC200/OC300 and its IP Address belongs to you and it will allow you to send emails through your application.
Different mailboxes may have different ways to support third-party access. You need to configure this function based on your mailbox.
You can send a test email to one of your other mailboxes. If you set the mail server successfully, you will receive a “succeeded” message just like the above. Otherwise, you will receive a failed message.
The below are the functions that need to send the email. We need to configure mail server at first if we want to use these functions.
1.Cloud user
For Omada SDN controller, after adding cloud user, the mail server of controller will send an invitation email containing an inviting link to the TP-LINK ID email. Cloud user will be added successfully after clicking the inviting link. So we need to set up mail server before adding cloud user. Otherwise, we will fail to send an inviting email.
If you already added cloud user without setting the mail server, you can re-invite the cloud users in the account list after completing the settings of mail server.
2. Email log
If you want to email the system log to your mailbox, you need to configure the mail server as well. And please follow the following steps complete the settings.
1 ) Enable Mail Server in Controller Settings.
2 ) Enable Alert Emails in Site Settings.
3 ) Enable Alert Emails in Admin Settings.
4 ) Enable Alert Emails in Logs Settings.
3. Forget password
If you forgot your password and need to reset the password, you can fill in your mailbox and receive an email to reset the password. So you need to configure the mail server at first as well.
Looking for More
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or