[cid:image.png@4fc4b689cf5dcb3b1acc2eb.4fc4b689c] Hi,
Thanks for reaching out about your proof of insurance. It looks like we weren’t able to accept the document because it was too blurry, or we couldn’t access the attachment. Please resend a clear, crisp insurance document so we can confirm that you’ve met your lease insurance requirement. Make sure that the document is not password-protected so we can open it on our end. You can send us a copy of your policy by submitting it to https://resident.assurant.com/poi using the Resident and Client ID listed in the email subject line. If your carrier is green, they can use the email address we are writing you from to send it to us directly. You can also give us a call using the toll-free number below, Monday through Friday, 8 a.m-8 p.m. EST. Assurant Insurance Service Center On behalf of Greystar Phone 1.800.249.1104 Email greys...@assurant.com Need a faster response? Chat with us 8AM – 5PM Monday – Friday at https://resident.assurant.com/poi/confirmation. You will need the three letter Client ID and resident ID listed in the subject line above. You can also self-service your Assurant policy by visiting www.MyAssurantPolicy.com<http://www.MyAssurantPolicy.com>. ------------------- Original Message ------------------- From: David Hart <daveh...@gmail.com>; Received: Wed May 24 2023 14:22:16 GMT-0400 (Eastern Daylight Time) To: questions@lists.ntp.org; Subject: Re: [questions] Fwd: Windows port pool IPv6 misbehavior On Wed, 24 May 2023 at 02:01, Jakob Bohm <jb-use...@wisemo.com.invalid> wrote: For more rapid testing, could you describe the particular failing getaddrinfo() behavior and perhaps provide a sample command line C program that tests it in isolation instead of forcing each tester to run through a long ntpd run (usually hours of test time plus difficult log interpretation versus a quick run that outputs relevant results to stdout even with a different NTP daemon running). Actually it doesn't take hours, just seconds. You just need to see if using only "pool2.pool.ntp.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__2.pool.ntp.org&d=DwMFaQ&c=59WElTcIEwbBjXQe6gMr9RyqhrzJYRWAhv5h0b8rPQw&r=SFS-Xi521pAy4mTX_qIfD3V2MhNyuNL40eu8gHG8Lq8&m=ySav1sbezdLzYzTIAvHwqF0bdUOTfKWlxmRK8lBD76z9w_QVOCcBgAmHzW5YpaJX&s=98wHPRNzNA6i0bJ9dasbW5XTtZOxu26sMTzPEMhQJJg&e=>" you see only IPv4 pool servers or both IPv4 and IPv6 servers in the "ntpq -p" billboard right after starting ntpd on a Windows system with a global IPv6 address. Nonetheless, a standalone test program is easier to set up and doesn't require messing with your existing ntpd, so I wrote one. getaddrinfo-test optionally takes a hostname and service to look up, defaulting to2.pool.ntp.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__2.pool.ntp.org&d=DwMFaQ&c=59WElTcIEwbBjXQe6gMr9RyqhrzJYRWAhv5h0b8rPQw&r=SFS-Xi521pAy4mTX_qIfD3V2MhNyuNL40eu8gHG8Lq8&m=ySav1sbezdLzYzTIAvHwqF0bdUOTfKWlxmRK8lBD76z9w_QVOCcBgAmHzW5YpaJX&s=98wHPRNzNA6i0bJ9dasbW5XTtZOxu26sMTzPEMhQJJg&e=> and ntp. You can download the source and a ready-to-run 32-bit .exe from: https://people.nwtime.org/hart/getaddrinfo-test.zip<https://urldefense.proofpoint.com/v2/url?u=https-3A__people.nwtime.org_hart_getaddrinfo-2Dtest.zip&d=DwMFaQ&c=59WElTcIEwbBjXQe6gMr9RyqhrzJYRWAhv5h0b8rPQw&r=SFS-Xi521pAy4mTX_qIfD3V2MhNyuNL40eu8gHG8Lq8&m=ySav1sbezdLzYzTIAvHwqF0bdUOTfKWlxmRK8lBD76z9w_QVOCcBgAmHzW5YpaJX&s=fwRkT9S43ANQOQog1gt2FP4xAzqyyPqIyuTGed0RreU&e=> Here's what the output looks like on my Windows 11 22H2 system without IPv6 connectivity: Using hostname 2.pool.ntp.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__2.pool.ntp.org&d=DwMFaQ&c=59WElTcIEwbBjXQe6gMr9RyqhrzJYRWAhv5h0b8rPQw&r=SFS-Xi521pAy4mTX_qIfD3V2MhNyuNL40eu8gHG8Lq8&m=ySav1sbezdLzYzTIAvHwqF0bdUOTfKWlxmRK8lBD76z9w_QVOCcBgAmHzW5YpaJX&s=98wHPRNzNA6i0bJ9dasbW5XTtZOxu26sMTzPEMhQJJg&e=>. service ntp AF_UNSPEC: 128.82.68.1 216.84.68.1 240.84.68.1 160.83.68.1 AF_INET: 56.82.68.1 48.84.68.1 80.82.68.1 104.82.68.1 AF_INET6: getaddrinfo error: The requested name is valid, but no data of the requested type was found. I'd appreciate testing on systems with both IPv4 and IPv6 internet access with as many different versions of Windows as possible. You'll reproduce what I saw if there are IPv6 addresses under AF_INET6 but not under AF_UNSPEC. Incidentally, you can help me convince Microsoft this should be investigated by upvoting the Feedback Hub issue I opened. I presume this link will work only from a Windows 10 or 11 machine: https://aka.ms/AAkyamq<https://urldefense.proofpoint.com/v2/url?u=https-3A__aka.ms_AAkyamq&d=DwMFaQ&c=59WElTcIEwbBjXQe6gMr9RyqhrzJYRWAhv5h0b8rPQw&r=SFS-Xi521pAy4mTX_qIfD3V2MhNyuNL40eu8gHG8Lq8&m=ySav1sbezdLzYzTIAvHwqF0bdUOTfKWlxmRK8lBD76z9w_QVOCcBgAmHzW5YpaJX&s=8O25GIVYJm9otvynr3HKpouvg8qZTvj5b3QoQq_iPUA&e=> Cheers, Dave Hart ********************************************************************** This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you.
