Now that this new service is active in the Internet there will be people that want to block it. I understand the need for this kind of feature but corporations will very much want to stop their employees using this service whilst using corporate networks. The WWDC video suggested that there would be ways to block the use but there is nothing linked to the video about how to do this. Can anyone provide instructions or pointers to documentation on this?

Is there / will there be a way to include in the Http response from the Webserver something like "This server is not available with private relay"? Some of my servers checks the source ip and only allowed ip's are served.

When tested with iOS 15 beta 1, If I configure proxy or vpn profile on the device, I have noticed that on the proxy or vpn server there is no information about UserAgent for any http/https requests originated from the device. It is set to "-". Is this a defect?

We have registered the full email addresses on the developer portal and they have green ticks next to them. We are using SendInBlue as an email service, and we are using our own domain+dedicated_ip. With all SPF and DKIM configurations also done and verified. Problem is that 50% of the time - emails are not getting delivered to apple-relay-email-ids (the email ids which look like @private.appleid.com). So, sometimes works, sometimes doesn't without any error or info. How can we debug of fix this?