> > > - Does this mean that *message.content* will not work in the future? > > This is because the current adapter uses an invalid field type for attachment and content fields that can raise errors when used with other core features. In order to keep those fields, they should have custom field types (experimental), since none of the built-in types is suitable for them.
> > - Also, does it mean than the users will have to write their own > message content extraction by traversing the MIME Multipart? > > Yes, unless the above issue is solved. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
