-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Q&A- Tec: Sending invitation by email #28
Comments
This could be a problem with hotmail. In particular, these two errors in the stack traces (from the images posted above) suggest that:
Message failed: 432 4.3.2 Concurrent connections limit exceeded. Visit https://aka.ms/concurrent_sending for more information. [Hostname=SA3PR10MB7600.namprd10.prod.outlook.com"
"[email protected] not allowed to send as [email protected];" |
@jchartrand add the example csv file as well as the credential and email template, so they can replicate the incident. |
@MyriamLara - would you be able to try this with Tec de Monterrey smtp or sendmail smtp instead of hotmail? (Javier emailed with this question too) |
@kayaelle @jchartrand |
@MyriamLara - checking in on the status of sending email because i've heard that it is working now. Could you let us know? Also, would love to hear about the solution you found for gmail so we can provide that for others. Thanks! |
10/17/24: Checking in with Tec to see if this issue has been resolved. |
Hello!
Sometimes, when sending the invitation to the students, the dashboard admin is left “Sending”, and we are left with uncertainty because we do not know if the complete process was really done or not. We have observed the above when we send several invitations, since with 1 or 2, the behavior is stable.
Can you please guide us to know where the detail could be?
Below we share evidence through image 1:
As you can see in image 1, after sending the invitation, it remains “Sending” indefinitely.
With a shipment of approx. 5 students, most of them do not receive the invitation and the console sends the following errors (see images 2 and 3).
Image 2
Image 3
The text was updated successfully, but these errors were encountered: