How many subscribers do I have in AWeber?

Why is my subscriber’s confirmation still pending?

It seems like your account is set up for double opt-in, which means that your subscribers need to confirm their subscription via an email link sent to them. This is a common practice that helps ensure that only real people are subscribing to your list. To get rid of the confirmation pending issue, you can switch your account to single opt-in, which means that subscribers will be automatically subscribed without having to confirm their subscription. You can find this setting in your account settings.

Additionally, you can check if any of your subscribers have entered an incorrect email address, which could be causing the confirmation pending issue.

If this is the case, you can delete those subscribers from your list and ask them to resubscribe with the correct email address.

If your subscribers are not getting approved, it could be due to the purchase approval settings on Google Play. As a parent or family manager, you can choose the purchase approval settings for your family members. You may need to check and modify these settings to ensure that your subscribers can make purchases or download content.

To change purchase approval settings, follow these steps:

1. Open the Google Play app.
2. Tap your profile picture at the top right.
3. Go to Settings > Family > Manage family members.
4. Select the family member’s name.
5. Tap Purchase approvals.
6. Choose the type of purchases that you want to require approval for or select “No approval required” if you want to allow them to make purchases without confirmation.

If you’re using the Family Link app to manage your child’s account, you can follow these steps to change purchase approval settings:

1. Open the Family Link app.
2. Tap your child’s name and go to Content restrictions > Google Play.
3. Under “Purchases & download approvals,” tap Require approval for.
4. Select the type of purchase approval you want to give.

Once you have set the purchase approval settings, you can approve or deny requests for content from Google Play. If you’re the family manager, you will receive an email receipt when a purchase is completed. For paid content, you will be asked to enter your Google Account password to approve the purchase. For content at no charge, you can approve or deny the request through a notification on your phone or by reviewing the request on your child’s device.

If there are pending requests for content, you can find them in the Play Store app or the Family Link app. In the Play Store app, go to Settings > Family > Manage approval requests. In the Family Link app, go to Notifications to view the requests.

It’s also important to note that if you haven’t added a family payment method, your family members may request your approval to make a purchase. You can complete the purchase using any payment method added to your Google Play account.

If none of these solutions resolve the issue, you may need to reach out to Google Play support for further assistance.

If subscribers are not getting approved and you are seeing a “Subscription request already pending” error, there are a few steps you can take to resolve the issue.

Firstly, check if the subscribers have been sent a confirmation email and ask them to confirm their subscription using the link in the email.

If the subscribers are unable to find the confirmation email or are not responding to it, you can try one of the following options:

1. Wait for the request to expire: By default, subscription requests expire after 3 days. If you wait for the request to expire, the subscribers can make a new request to subscribe.

2. Use mailman shell, REST API, or direct interaction with the database to find and manually confirm the subscription request. You can use a shell command like util.confirm('hex_token') to confirm the request. However, this option may not be available if you are using a shared Mailman 3 server.

3. Change the Subscription Policy to “open”: Changing the subscription policy to “open” will allow pending requests to be automatically accepted. This can help clear out the queue of pending subscription requests.

Remember to restart Mailman core after making any changes to apply the changes properly.

It seems that the issue of subscribers not getting approved is due to pending subscription requests. When someone tries to subscribe to a mailing list, they receive a confirmation email that they need to respond to in order to confirm their subscription. If they haven’t responded to this email, their subscription request remains pending.

In this specific case, the user [email protected] mentioned that they have users experiencing an error message stating: “Subscription request already pending.” When they tried to use the Mass Subscribe feature in Postorius (the web interface for Mailman), they also received the same error message.

It was explained by Mark Sapiro that this behavior is expected. Since the list’s subscription policy is set to require user confirmation, the subscription requests will remain pending until the user confirms their subscription by responding to the confirmation email. The current version of Postorius, as of version 1.2.3, does not display subscription requests that are pending user confirmation. It only displays requests that are pending moderator approval. This is to prevent moderators from accidentally approving requests that are waiting for user confirmation.

To resolve this issue, there are a few options:

1. Have the user find the confirmation request email and confirm their subscription.
2. Wait for the request to expire. By default, the expiration time for pending requests is 3 days.
3. Use the Mailman shell, REST API, or interact directly with the database to find the token and confirm it. An example of using the Mailman shell to find and confirm a token is provided in Mark Sapiro’s response.

It was also suggested to temporarily change the subscription policy to “open” to allow pending requests to be accepted and clear the queue. However, this may not be ideal if there are substantial pending requests as it could result in a large influx of subscribers.

In summary, subscribers are not getting approved because their subscription requests are pending user confirmation. They need to respond to the confirmation email or take other steps outlined above to have their subscription request processed.

If your subscribers are not getting approved on Google Play, it could be due to the purchase approval settings that you have configured. As a parent or family manager in a family group, you have the ability to require approval for purchases or downloads made by your family members. This setting only applies to purchases made through Google Play’s billing system.

To change the purchase approval settings, follow these steps:

1. Open the Google Play app.
2. Tap on your profile picture at the top right.
3. Go to Settings > Family > Manage family members.
4. Select the family member whose approval settings you want to change.
5. Tap on Purchase approvals.
6. Choose the type of purchases that you want to require approval for: all content, all purchases using the family payment method, only in-app purchases, or no approval required.

If you’re using the Family Link app to manage your child’s account, the process is slightly different:

1. Open the Family Link app.
2. Tap on your child’s name.
3. Go to Content restrictions > Google Play.
4. Under “Purchases & download approvals,” tap on Require approval for.
5. Select the type of purchase approval you want to give.

Once you have set the purchase approval settings, you can approve or deny requests for content from Google Play. For paid content, you will need to enter your Google Account password on their device to approve the request. For content at no charge, you will either receive a notification on your phone or review the request on your child’s device and enter your Google Account password to approve it.

If you want to view pending requests for content, you can do so in the Play Store app or the Family Link app, depending on the device you’re using.

It’s important to note that if you haven’t added a family payment method, your family members may need your approval to make a purchase. You can complete the purchase with any payment method you have added to your Google Play account.

If you’re still experiencing issues with your subscribers not getting approved, it may be helpful to reach out to Google Play support for further assistance.

When subscribers aren’t getting approved on a Mailman mailing list and receive an error message like “Subscription request already pending,” there are a few things you can do.

First, confirm that the subscribers have received a confirmation email and ask them to complete the confirmation process. Sometimes, users may overlook or misunderstand the need to reply to the confirmation email.

If the confirmation request email has been received and confirmed but the subscribers are still pending approval, you can try the following options:

1. Wait for the request to expire: By default, subscription requests expire after 3 days. If the subscriber doesn’t respond within this period, the request will expire.

2. Use the Mailman shell or REST API: With the Mailman shell or REST API, you can find the token for the pending request and manually confirm it. You can use commands like mailman shell -l your.list.id and util.confirm('hex_token') to accomplish this. However, note that this may require shell access or technical expertise.

3. Temporarily change the subscription policy: You can change the subscription policy for the list to “open” temporarily. This will allow the pending requests to be automatically accepted and clear the queue. However, be cautious with this option as it may allow unwanted subscriptions.

Additionally, it’s worth mentioning that Mailman Postorius, the web interface for Mailman, does not display subscription requests pending user confirmation. It only shows requests waiting for moderator approval. This is a design choice to prevent moderators from approving requests that require user confirmation. A fix to display requests pending user approval has been implemented in version 1.2.4 of Postorius.

If you continue to have issues or need further assistance, you can reach out to the Mailman support team at EMWD or consider using the sample script provided by Mark Sapiro to delete expired pending subscription requests.

There could be a few reasons why your subscribers are not getting approved. One possibility is that your account is set up for double opt-in, meaning that subscribers have to confirm their subscription through an email link. If they are not confirming, their subscription will remain pending. You can switch your account to single opt-in to eliminate the need for confirmation.

Another reason could be that some subscribers may have entered an incorrect email address, which is causing the confirmation pending issue. In this case, you can delete those subscribers from your list and ask them to resubscribe with the correct email address.

Alternatively, if you are experiencing this issue on Google Play, it could be due to the purchase approval settings that you have configured. As a parent or family manager, you can choose the purchase approval settings for your family members. Adjusting these settings may allow your subscribers to make purchases or download content without confirmation.

If none of these solutions resolve the issue, it may be helpful to reach out to Aweber or Google Play support for further assistance.

It seems that the issue of subscribers not getting approved in this case is due to a confirmation request already pending. When users try to subscribe to the list, they receive an error stating that a subscription request is already pending. The error also occurs when trying to mass subscribe them in Postorius. However, these pending requests are not visible in Postorius. The recommended solutions to resolve this issue are:

1. Have the user find the confirmation request email and confirm their subscription.
2. Wait for the request to expire, which is usually set to a default of 3 days.
3. Use the mailman shell, REST API, or direct interaction with the database to find and confirm the token.

The issue with not being able to see the pending requests in Postorius has been acknowledged, and a fix is planned for version 1.2.4. Additionally, the default setting for the expiration of requests is usually 3 days, but it can be changed in the mailman.cfg file under the pending_request_life option. It is also worth noting that changing the subscription policy to “open” will not allow pending requests to be automatically accepted.

If subscribers are not getting approved for a mailing list and you are seeing the error message “Subscription request already pending,” there are a few things you can try to resolve the issue.

First, check if the subscribers have received a confirmation email. In some cases, the subscribers may not have confirmed their subscription by clicking on the confirmation link in the email. Instruct the subscribers to check their email and follow the confirmation process.

If the subscribers have confirmed their subscription but are still not approved, you can try mass subscribing them using the Postorius interface. However, if you encounter the same error message, you may need to take additional steps.

One option is to use the Mailman shell or the REST API to find the pending subscription requests and manually confirm them. In the Mailman shell, you can use the following commands:

<br>mailman shell -l your.list.id<br>util = getUtility(IPendings)<br>requests = list(util.find(mlist=m, pend_type='subscription'))<br>for request in requests:<br> util.confirm(request[0])<br>

Alternatively, you can directly interact with the database to find the token and confirm it. However, this method is not recommended.

It is worth noting that in Postorius versions starting from 1.2.3, subscription requests pending user confirmation are not displayed. This is because it is generally not advisable for moderators to approve requests that are awaiting user confirmation. However, there is ongoing development to provide a separate place to view and manage pending requests.

If you are still experiencing issues, it is recommended to seek assistance from the Mailman support team or consult the appropriate documentation for your specific Mailman version.

When subscribers are not getting approved, it could be because their subscription request is pending confirmation. This issue was discussed in a thread on the Mailman Users mailing list. One user reported receiving an error message stating, “Subscription request already pending,” when trying to subscribe people using the Mass Subscribe feature in Postorius. Another user suggested that this error occurs when a subscriber has not confirmed their subscription request by replying to the confirmation email. In Postorius, pending subscription requests are not displayed, but they can still be found and confirmed using the Mailman shell or other methods.

To confirm a pending subscription request using the Mailman shell, you can follow these steps:

1. Open the Mailman shell for the relevant mailing list.
2. Use the util = getUtility(IPendings) command to set the util variable to the instance of the IPendings utility.
3. Use the list(util.find(mlist=m, pend_type='subscription')) command to find a list of subscription requests pending confirmation.
4. Iterate through the list of pending requests and check if the request is waiting for user confirmation using the data.token_owner attribute.
5. Use the util.confirm(token) command to confirm the subscription request, replacing token with the hexadecimal token for the request.
6. Use the commit() command to save the changes.

Note that in this particular thread, there was also a suggestion to use the util.confirm(token, expunge=True) command, which not only confirms the request but also removes it from the pending list.

It is worth mentioning that the issue discussed in this thread has been addressed in Mailman Postorius version 1.2.4, where pending requests waiting for user confirmation are displayed in Postorius, allowing moderators to see and manage them more easily. Additionally, the default expiration time for pending subscription requests is three days, but it can be adjusted using the pending_request_life setting in the mailman.cfg configuration file.

If your subscribers are not getting approved, it could be due to the purchase approval settings on Google Play. If you are a parent in a family group, you can require family members to get your permission to purchase or download content on Google Play. Purchase approval settings only apply to purchases made through Google Play’s billing system.

To change purchase approval settings, you can follow these steps:

1. Open the Google Play app.
2. Tap your Profile picture at the top right.
3. Tap Settings, then Family, and then Manage family members.
4. Select a family member’s name.
5. Tap Purchase approvals.
6. Select the type of purchases that you want to require approval for.

If you are using the Family Link app, you can follow these steps:

1. Open the Family Link app on your device.
2. Tap your child’s name, then Content restrictions, and then Google Play.
3. Under “Purchases & download approvals,” tap Require approval for.
4. Select the type of purchase approval that you want to give.

If you are a parent in a family group, you can approve or deny requests for content from Google Play. When a purchase is completed through Google Play’s billing system, the family manager gets an email receipt. You can manage approvals for recommended apps separately in the Google Kids Space settings.

If you are the family manager and you didn’t add a family payment method, your family members may request your approval to make a purchase. You can complete the purchase with any payment method you add to your Google Play account, including Google Play gift cards.

It’s important to note that purchase approval settings, including purchase confirmation emails, apply to purchases made through Google Play’s billing system.

Based on the conversation provided, it seems that subscribers are not getting approved because their subscription requests are still pending. The error message “409 Conflict” indicates that the subscription request is already pending. One possible reason is that the users have not yet confirmed their subscription request. In the conversation, it is mentioned that Postorius does not show subscription requests waiting for user confirmation, so it might be helpful to check the confirmation emails sent to the subscribers and ask them to confirm their subscription. Another option is to wait for the requests to expire, which is usually set to 3 days by default. You can also use the Mailman shell or the REST API to find and confirm the pending requests manually. The script delete_orphans_expireds.py mentioned in the conversation can be used to delete pending subscriptions that have expired. Keep in mind that using the script might require modifications to specify a specific list.