5.1.1

We're unable to send email to private relay address.The server we're sending from is also the MTA, the domain is verified (with a checkmark) in and we're using (correctly configured) DKIM, DMARC (set to reject unauthenticated mail), and SPF (set to reject mail that doesn't match), but we're still getting this error:550 5.1.1 Relay not allowed for <xxxxx@privaterelay.appleid.comWhat could be wrong?Our SPF record looks like this:v=spf1 a mx ip4:... ip4:... ip6:.../64 ip6:.../64 include:servers.mcsv.net include:_spf.google.com -all(again, the email is actually sent from the server matching 'a', not mailchimp or google)I'm also able to verify that all the headers look right: Return-Path, From, and the smtp from all match both the verified domain and I've added it as an individual email address, Authentication-Results says dkim=pass, spf=pass, and dmarc=pass (p=REJECT sp=REJECT dis=NONE), the d value in the DKIM signature matches the domain, in short, everything seems to be set up properly.

Hello, I have a subscription based app that has been rejected for 2.3.2 Performance: Accurate Metadata 3.1.2 Business: Payments - Subscriptions 5.1.1 Legal: Privacy - Data Collection and Storage I have added additional information to all of these areas, added links to the relevant privacy and usage pages. I am not sure why it keeps being rejected. I am missing some information but cannot see what is needed. Is there an example of the required information for a subscription based app for the localisation information. Currently the app needs a user account to access some of the features and the subscription provides access to that. A user with no account can access the free features without a login. Any pointers would be really appreciated

Hi, I am having a hard time understanding what I did wrong here. My app as a Login screen to authenticate the user, after which they are given to subscribe to either a monthly plan or a yearly plan(auto-renewed). After countless rejection, I guess I am failing to understand. This the message I received from the review team: Hello, Thank you for your question. Regarding guideline 5.1.1, Please note that although App Review Guideline 3.1.2 requires an app to make subscription content available to all the supported devices owned by a single user, it is not appropriate to force user registration to meet this requirement; such user registration must be optional.. Upon further review, additionally we found that your submission does not comply with the following guidelines: Guideline 2.3.2 - Performance - Accurate Metadata We noticed your free download app requires users to subscribe prior to accessing content or features, but this requirement is not clearly specified in your app description. Specifically,

App Rejected stating Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We found in our review that your app does not meet all of our requirements for apps that offer highly regulated services or handle sensitive user data. Specifically: The account that submits the app must be enrolled in the Apple Developer Program as an organization, and not as an individual. The guideline 5.1.1(ix) requirements give App Store users confidence that apps operating in highly regulated fields or that require sensitive user information are qualified to provide these services and will responsibly manage their data. Next Steps To resolve this issue, it would be appropriate to take the following steps: Your app must be submitted through an Apple Developer Program account enrolled as an organization. You may either enroll in a new Apple Developer Program account as an organization, or request that your individual account be converted to an organization account by contacting Apple Developer Support.

We received an email from the Apple Developer Relations Team entitled New iOS 18 security changes may affect your account. regarding accounts that share the same team name across multiple Apple developer accounts. The email includes instructions to contact Apple, but the email address provided in the email bounces back 550 5.1.1 unknown or illegal alias. I tried again a day later, with the same result. Who should we contact instead?

The app does not meet all requirements for apps that offer highly regulated services or handle sensitive user data. Specifically: The account that submits the app must be enrolled in the Apple Developer Program as an organization, and not as an individual. The guideline 5.1.1(ix) requirements give users confidence that apps operating in highly regulated fields or that require sensitive user information are qualified to provide these services and will responsibly manage their data. Next Steps To resolve this issue, it would be appropriate to take the following steps: The app must be submitted through an Apple Developer Program account enrolled as an organization. You may either enroll in a new Apple Developer Program account as an organization, or request that your individual account be converted to an organization account by contacting Apple Developer Support. Please note that you cannot resolve this issue with documentation showing permission to publish this app on behalf of the content owner or ins

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requires users to register or log in to access features that are not account based. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. For example, an e-commerce app should let users browse store offerings and other features that are not account based before being asked to register, or a restaurant app should allow users to explore the menu before placing an order. Registration must then only be required for account-specific features, such as saving items for future reference or placing an order. Next Steps To resolve this issue, please revise your app to let users freely access your app’s features that are not account based. Resources Watch a video from App Review with tips for doing more for users with less data. See guideline 5.1.1(v) - Account Sign-In to learn more about our requirements for apps

Hi,We are using Sign in with Apple to onboard users to our system. We need to send instructions to the user using the email provided at signup. We use Mandrill in the backend to send emails. I have configured the sender email in Individual Email Addresses under Certificates, Identifiers & Profiles in developer account (& it shows a green check mark). The emails sent to private relay addresses (e.g. xxxxxprm23@privaterelay.appleid.com) bounces.I have verified another email using gmail & it works fine.Am I missing some settings?-------------Bounce message from Mandrill-----------------------------------Received: from mail178-28.suw51.mandrillapp.com (unknown [198.2.178.28])by relay-3.us-west-2.relay-prod (Postfix) with ESMTPS id C5BCA20EF5for <bounce-md_31096458.5d52843d.v1-61f4bb207bb443e7a3d9e4482eb7beb3@mandrillapp.com>; Tue, 13 Aug 2019 09:34:54 +0000 (UTC)Date: Tue, 13 Aug 2019 09:34:54 +0000From: postmaster@mail178-28.suw51.mandrillapp.comSubject: Delivery reportTo: bounce-md_31096458.5d

Hello, My team and I are trying to publish an app (It's our first time doing this). The app allows users to purchase self-guided tours using in-app purchases. Users can browse, find tours and see a preview of a tour without registration. However we require registration for the in-app purchase as this is linked to a user account. This is because there is a possibility that someone has bought a tour on an android device and is coming here plus this is the only way that we can enable the users to recover their account if they lose their device so it seems like a logical thing to do right? We only require an email ID and password and not a lot of info for registering. We have tried to explain this multiple times but this is the response we get: Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requires users to register with personal information to purchase in-app purchase products that are not account based. Apps cannot require user registration prior to allowing a