Mopar1973Man

It would be nice if someone from the staff could comment on this and say if there will be a solution to this or not...

I'd rather have a true fix instead of a band-aid that might fail...

I'm just coming back to reply showing support for the need of this to be researched and solution provided for us. I know I'm losing income over this and would like to see a fix to this in the near future.

Absolutely correct. Adsense produces way more profit than Viglink does. To me, Viglink is a joke. I know it would help my income a ton load if I could get Google Adsense logged into my site.

This is where I came from. I got sick and tired of fighting with Hotmail and Gmail over 550 error mostly stating that no longer going to send email to any account permanently. Now with the error codes present you need to clean up your email problem and contact the email provider and go there hoops and loops to resolve your 550 error code. Sorry to say after two times around I lost my first IP address to Hotmail permanently this stopped me from sending email completely for a time. Now when I got fired up with @stoo2000 Mail Bouncer I was set up still on SparkPost which was easy to setup and worked instantly. The first pass I wiped out a ton load of email accounts. Now after the 4.3.x update we got forced to move to SendGrdi which was more of a PITA to handle and setup IMHO. Now once its set up I'm still sending newsletters out monthly to capture that rogue email addresses that are floating on the website. No longer have to filter out user into groups to ditch the older accounts and prevent sending email to the dead account. Still, in all your 550 codes have to be fixed first. Then you can get to use the Mail Bouncer. Again I doubt Mail Bouncer will work with a standard email server because of the lack of API connection.

That's all I'm doing exactly. The newsletter is the trigger to send email to the entire email list. Now if it bounces or marked as spam then the account is set to Validation.

I'm actually doing that for exact reason. I had many older account long gone. Then have an old post being revived and now emailing these account with bounced emails or marked as spam because they are no longer part of the website. So instead of hunting down the emails I send out as newsletter once a month and let the Mail Bouncer filter out the email. Now I've got a clean email database and no longer have to worry about spam or bounce issues. I don't think this plugin can work on its own because of the lack of information from the normal email server and no API connection.

Never mind... I got it handled but thank you for the heads up.

I've ran into an email where a member clicked spam and the account did not update. What do you need for information to handle bugs?

Response... So we are basically without the ability to have Google Adsense Bots login to IPS software.

Thank you I passed it along on the ticket I've got going to see if we can get an answer to this puzzle.

auth = Username given for Google Adsense password = password given for Google Adsense NOTICE: This will pass the information along to the login boxes but still at this point for me it will NOT actually login. I've got a support ticket going currently to attempt to figure out why.

Like I said it passes the login info. Now how do you get it to login in? Here what I found on the Google side. https://productforums.google.com/forum/#!topic/adsense/uzT7CuJBjnE

I'll give that a shot and see what happens. ---TINKERING in the Admin CP --- It passes the login information now. Hopefully Google knows enough to hit the login button.

No. Still trying to figure this out.

Can someone post a fresh copy of the parameters that Google Bots need to login to the forum? Login URL = https://mopar1973man.com/login/ auth_key = 880ea6a14ea49e853634fbdc5015a024 ips_password = (Account password) ips_username = (Google Bot Username) rememberMe = 1 Are these correct?

It would be nice to be able to understand the error codes and what is causing them more in depth. It might reduce the amount of support tickets you guys (IPS staff) have to handle if the trouble shooting side of the software was laid out better. Some of the codes are pretty easy but other take a bit of digging to figure out because the description doesn't tell enough sometimes.

Upgrade...

Same 404 page either way... Admin or guest.

I'm running Member Map 3.1.1.1 and when you click on the link for the Member Map it returns a 404 page error. Something I'm missing?

My question is how do we resolve this properly meeting Adsense requirements? If we have semi-public area in other words behind a login area but still designed for the public? As far as what I got set up the login is not working there is never been a IP recorded other than my own for my Adsense login.

Same here no luck either with this same settings.