RIght now we are using GMail accounts for sending those automatic updates, but 2 days ago they stopped working and password change is enforced (not done yet). As for GMail error message, this password change is required due to suspicious activity on those accounts. We need to get other accounts (maybe from a different provider), which will allow us to send those notifications without marking those as suspicious activity.
wojciech.kapcia@tigase.net commented 6 years ago
%andrzej.wojcik - wouldn't those accounts start working (for TTS-NG tests) once:
password is changed;
iot1 notifications are not sent through it.
They were working just fine and I'm not sure how easy it would be to find alternative to gmail (though gmail with it's security measures can be a bit of PITA…)
Andrzej Wójcik (Tigase) commented 6 years ago
We can try to move IoT1 Cloud notifications to SES and leave those 2 accounts (with updated passwords) for TTS-NG and check if all is ok.
Artur Hefczyc commented 6 years ago
Wojciech Kapcia wrote:
%andrzej.wojcik - wouldn't those accounts start working (for TTS-NG tests) once:
password is changed;
iot1 notifications are not sent through it.
They were working just fine and I'm not sure how easy it would be to find alternative to gmail (though gmail with it's security measures can be a bit of PITA…)
I am against using gmail for this. (both TTS and IoT). GMail accounts are not for such things. We have the SES service which is designed for sending notifications, let's use it instead.
Andrzej Wójcik (Tigase) commented 6 years ago
Yes, but for testing TTS-NG, we need to receive messages as well. Is SES capable of that?
Artur Hefczyc commented 6 years ago
Andrzej Wójcik wrote:
Yes, but for testing TTS-NG, we need to receive messages as well. Is SES capable of that?
What do you mean: "we need to receive messages as well"?
Andrzej Wójcik (Tigase) commented 6 years ago
During TTS-NG tests, Tigase is sending notifications and TTS-NG must check email account if it received those notifications or not.
Artur Hefczyc commented 6 years ago
SES is for sending emails only.
I am still not entirely convinced that gmail is the right tool for the task, but we can use it as a temp solution.
wojciech.kapcia@tigase.net commented 6 years ago
Andrzej Wójcik wrote:
We can try to move IoT1 Cloud notifications to SES and leave those 2 accounts (with updated passwords) for TTS-NG and check if all is ok.
Could you update those?
Andrzej Wójcik (Tigase) commented 6 years ago
Look like it is working properly now. Closing issue.
RIght now we are using GMail accounts for sending those automatic updates, but 2 days ago they stopped working and password change is enforced (not done yet). As for GMail error message, this password change is required due to suspicious activity on those accounts. We need to get other accounts (maybe from a different provider), which will allow us to send those notifications without marking those as suspicious activity.