Hello there
Would it be possible to restore some administration web UI for this
mailing list, so that I can take care of fixing cases like these, where
customer center addresses are registered as users and we get all sorts
of **** in the list?
Also, I wonder why it's happening. I have been into many mailing lists
and this is the only one where "rogue" list members pop up more or less
regularly...
Ciao
-- bronto
On 24/05/2023 16:13, Greystar wrote:
*Hi, *
Thanks for reaching out.
If it were up to us, we’d solve all your problems, but renter’s
insurance is what we do best. For everything else, we suggest you
contact your leasing professional or property management company.
Feel free send us your questions by responding to this email. 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
<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:* Dave Hart <h...@ntp.org>;
*Received:* Sun May 21 2023 23:50:10 GMT-0400 (Eastern Daylight Time)
*To:* questions@lists.ntp.org;
*Subject:* [questions] Fwd: Windows port pool IPv6 misbehavior
I recently visited a relative who, unlike myself, has IPv6 service
from her ISP. I noticed ntpd on my Windows laptop configured with:
pool 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=xZGKngDdRx9Sg72e86ZEs0fIhjiboUVJ1Jp22FloMFGparyUWVyu-2BsT_xE_Lju&s=PeBMSOWyEk9p9miInS_QllfknNA8tvwDlpxbGYGIWwM&e=>
was not soliciting any IPv6 pool servers. For those unfamiliar, the
2.*.pool.ntp.org
<https://urldefense.proofpoint.com/v2/url?u=http-3A__pool.ntp.org&d=DwMFaQ&c=59WElTcIEwbBjXQe6gMr9RyqhrzJYRWAhv5h0b8rPQw&r=SFS-Xi521pAy4mTX_qIfD3V2MhNyuNL40eu8gHG8Lq8&m=xZGKngDdRx9Sg72e86ZEs0fIhjiboUVJ1Jp22FloMFGparyUWVyu-2BsT_xE_Lju&s=u-T1XHTiDndS1l4rprS4CaG1dXPPBHJ4bzEHbR_gJwE&e=>
names are the only ones which return IPv6 addresses
as well as IPv4.
This appears to be a bug in Windows 11 resolving hostnames to IP
addresses.
I would love to hear from others if they are seeing similar behavior
on Windows ntpd with a similar pool configuration. I'm using Windows
11 22H2 (22621.702) x64. I'm particularly curious to hear from those
using other Windows versions so I can note in my bug report which
versions have broken getaddrinfo().
Incidentally there is a workaround available. You can use something
like the following:
pool pool.ntp.org
<https://urldefense.proofpoint.com/v2/url?u=http-3A__pool.ntp.org&d=DwMFaQ&c=59WElTcIEwbBjXQe6gMr9RyqhrzJYRWAhv5h0b8rPQw&r=SFS-Xi521pAy4mTX_qIfD3V2MhNyuNL40eu8gHG8Lq8&m=xZGKngDdRx9Sg72e86ZEs0fIhjiboUVJ1Jp22FloMFGparyUWVyu-2BsT_xE_Lju&s=u-T1XHTiDndS1l4rprS4CaG1dXPPBHJ4bzEHbR_gJwE&e=>
pool -6 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=xZGKngDdRx9Sg72e86ZEs0fIhjiboUVJ1Jp22FloMFGparyUWVyu-2BsT_xE_Lju&s=PeBMSOWyEk9p9miInS_QllfknNA8tvwDlpxbGYGIWwM&e=>
The first pool prototype association will pick up IPv4 addresses,
while the second one will get IPv6 addresses.
Thanks for your time and assistance.
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.
