by Flash_Gordon » Sat Jul 11, 2009 3:52 am
As mentionned by the logs you posted, it seems that
www.google.com needs an HTTPS connection to mail.google.com for login purposes...
I don't remember how precise rules can get, but I'd give a try to this one:
- Code: Select all
Site mail.google.com
Accept from SELF www.google.com/accounts/ServiceLogin
Deny
If ABE's engine accepts this, no other
www.google.com request will be accepted, only ServiceLogin. If ABE's engine is even more precise, maybe you can add a couple paramaters that you know never change from one Gmail notification to the other, service=mail for instance.
The most precise rule would be using
https://www.google.com/accounts/Service ... y%3Dl&bsv=[snip]&ss=1&scc=1<mpl=googlemail or whatever works last before it breaks.
As mentionned by the logs you posted, it seems that http://www.google.com needs an HTTPS connection to mail.google.com for login purposes...
I don't remember how precise rules can get, but I'd give a try to this one:
[code]Site mail.google.com
Accept from SELF www.google.com/accounts/ServiceLogin
Deny[/code]
If ABE's engine accepts this, no other http://www.google.com request will be accepted, only ServiceLogin. If ABE's engine is even more precise, maybe you can add a couple paramaters that you know never change from one Gmail notification to the other, service=mail for instance.
The most precise rule would be using https://www.google.com/accounts/ServiceLogin?service=mail&passive=true&rm=false&continue=https%3A%2F%2Fmail.google.com%2Fmail%2F%3Fui%26ui%3Dhtml%26zy%3Dl&bsv=[snip]&ss=1&scc=1<mpl=googlemail or whatever works last before it breaks.