Yep, I was just about to reply that I had gotten the routing piece of it to work with a custom routes.py file. So now the request gets sent to a controller (mail.py) in my app. First step done.
The question now, which I guess is a mix of Python/GAE/web2py, is how to take the request object (that now has all sorts of web2py stuff in it) and crack it open with Google's InboundMailHandler class. In the GAE world, you subclass IMH and override the receive() function, which passes you a nice message object to work with. If I can figure out how to get one of those GAE message objects in this new controller I'd be golden. -Mike On Apr 14, 9:42 am, Anthony <[email protected]> wrote: > On Thursday, April 14, 2011 6:30:55 AM UTC-4, Mike Giles wrote: > > > That doesn't seem to work. First, I believe web2py will be looking > > for an application named _ah to handle the request (versus a controler > > named _ah in myapp). > > You can use web2py's URL rewrite functionality to map /_ah/ to a controller > instead of an app:http://web2py.com/book/default/chapter/04#URL-Rewrite > > Anthony
