
Dear Linkgroup Gold bot user,
We would like to keep you informed about Latest changes on Linkedin which affects bot proper work.
As you know we have released Linkgroup Gold 3.4 with new functionality and options, but almost at the same time Linkedin released new version of group messaging server which affects proper work of the bot.
We have some information which we would like to share with you.
We have received several reports that Linkgroup gold 3.4 stops working after sending more than 500 messages per day – it looks like this is because new Linkedin limitations.
How can you identify that your account is limited:
a. open group members list and check address line – if it does not have &sik= parameter like this: http://ift.tt/1E9hJFz – your account is limited.
b. send message to group member manually from regular browser – if it redirects you to inbox – your account is limited.
c. send more than 10 messages to group member manually from regular browser – if start getting errors “You are no longer allowed to message the user” – your account is limited.
As a result of Linkedin update some accounts are currently not able to send messages to group members at all (even on regular browser without the bot).
Also we have one account which can send only 1-2 messages and after that get errors “You are no longer allowed to message the user”.
What should you do?
1. If you work with version 2.6 – continue to work with it until it stops working, then update to 3.4
2. If you are working with 3.4 – try to not send more than 500 messages per day per account until the issue resolved.
3. If you are working with 3.4 and your account become limited:
a. you can wait assuming that the limit is temporary (we do not know that).
b. you can contact Linkedin support and ask them why you can’t send group messages manually from regular browser and asking to remove limitations from account.
4. Version 3.4 will start working as soon as your account will not be limited any more – follow step 2.
We would like to hear from you and get more information to try to find workaround for the issue.
via WordPress http://ift.tt/1FcO9Tm