The password reset email *was* sent as evidenced by our email log:
Code:
Jun 24 22:33:40 toastmastersclubs sendmail[13772]: w5OMXdfe013769: to=<mtelder1@live.com>, ctladdr=<server@toastmastersclubs.org> (501/502), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=121401, relay=live-com.olc.protection.outlook.com. [104.47.2.33], dsn=2.0.0, stat=Sent (<201806242233.w5OMXdfe013769@toastmastersclubs.org> [InternalId=12305081332141, Hostname=DB5EU....eop-EUR01.prod.protection.outlook.com] 8773 bytes in 0.206, 41.578 KB/sec Queued mail for delivery)
Jun 24 22:34:07 toastmastersclubs sendmail[14019]: w5OMY6TZ014016: to=<mtelder1@live.com>, ctladdr=<server@toastmastersclubs.org> (501/502), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=121401, relay=live-com.olc.protection.outlook.com. [104.47.33.33], dsn=2.0.0, stat=Sent (<201806242234.w5OMY6TZ014016@toastmastersclubs.org> [InternalId=10539849774334, Hostname=BN3NA....eop-nam01.prod.protection.outlook.com] 8729 bytes in 0.240, 35.404 KB/sec Queued mail for delivery)
Jun 27 05:00:31 toastmastersclubs sendmail[4354]: w5R50TFs004336: to=<mtelder1@live.com>, ctladdr=<server@toastmastersclubs.org> (501/502), delay=00:00:01, xdelay=00:00:00, mailer=esmtp, pri=438323, relay=live-com.olc.protection.outlook.com. [104.47.46.33], dsn=2.0.0, stat=Sent (<201806270500.w5R50TFs004336@toastmastersclubs.org> [InternalId=12322261172831, Hostname=BN3NA...-NAM04.prod.protection.outlook.com] 329481 bytes in 0.146, 2189.117 KB/sec Queued mail for delivery)
Jun 28 08:50:39 toastmastersclubs sendmail[16528]: w5S8oajv016525: to=<mtelder1@live.com>, ctladdr=<server@toastmastersclubs.org> (501/502), delay=00:00:03, xdelay=00:00:03, mailer=esmtp, pri=121401, relay=live-com.olc.protection.outlook.com. [104.47.8.33], dsn=2.0.0, stat=Sent (<201806280850.w5S8oajv016525@toastmastersclubs.org> [InternalId=17300128330830, Hostname=AM5EU....eop-EUR03.prod.protection.outlook.com] 8591 bytes in 0.149, 56.034 KB/sec Queued mail for delivery)
Jun 28 08:51:15 toastmastersclubs sendmail[16664]: w5S8pEMp016661: to=<mtelder1@live.com>, ctladdr=<server@toastmastersclubs.org> (501/502), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=121401, relay=live-com.olc.protection.outlook.com. [104.47.42.33], dsn=2.0.0, stat=Sent (<201806280851.w5S8pEMp016661@toastmastersclubs.org> [InternalId=10544144754261, Hostname=BY2NA....eop-NAM03.prod.protection.outlook.com] 8777 bytes in 0.132, 64.775 KB/sec Queued mail for delivery)
Jun 28 09:52:22 toastmastersclubs sendmail[30231]: w5S9qJeR030211: to=<mtelder1@live.com>, ctladdr=<server@toastmastersclubs.org> (501/502), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=137115, relay=live-com.olc.protection.outlook.com. [104.47.0.33], dsn=2.0.0, stat=Sent (<201806280952.w5S9qJeR030211@toastmastersclubs.org> [InternalId=12210592090698, Hostname=HE1EU...op-EUR01.prod.protection.outlook.com] 24477 bytes in 0.211, 113.207 KB/sec Queued mail for delivery)
Jun 29 01:18:36 toastmastersclubs sendmail[7244]: w5T1IXeS007223: to=<mtelder1@live.com>, ctladdr=<server@toastmastersclubs.org> (501/502), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=145708, relay=live-com.olc.protection.outlook.com. [104.47.8.33], dsn=2.0.0, stat=Sent (<201806290118.w5T1IXeS007223@toastmastersclubs.org> [InternalId=16286515999092, Hostname=AM5EU...op-EUR03.prod.protection.outlook.com] 33045 bytes in 0.191, 168.202 KB/sec Queued mail for delivery)
However given the wording of the log entries ("Queued mail for delivery") it is possible that the emails are being held as possible spam by your member's email system. There is nothing we can do to resolve his lack of receipt for him as the system appears to be functioning as intended and delivering the email to his email provider.
However, he may be able to make a change to his email settings to designate the system as a "safe sender" (white list the system). Please take a look a the following for some suggestions on how to do that. As live.com is a Microsoft email address that shares characteristics with hotmail.com and outlook.com, your member should review the suggestions relevant to those here:
[url]
support.toastmastersclubs.org/doc/item/e...embers-receive-email
[/url]
Once he has designated the system as a safe sender, have him request the password email again.
