I've been working in some modifications on the experimental imap dal adapter after an issue with field types
https://groups.google.com/d/msg/web2py-developers/Jux_FikBQM4/r_3sDQABmGkJ The next dal.py patch will have some relevant changes to the IMAP dal interface so I thought it would be better to first have some user feedback before I change anything: - The content and attachment fields would be no longer available. Users have to implement their custom app code to fetch each part inspecting the complete message structure (i.e. by instantiating a stdlib Message class object with the contents from the "email" RFC822 field with dal text type). This is for simpler and faster dal code. - Because of the previous change, message insertions would support passing a raw text email structure or a Message object (with attachments) as email field and also overwriting header fields with method arguments (to, sender, subject, ...). This way adding a simple text body requires creating a Message object but gives the user complete control over the message payload. - No more message id fields (dal ids will map to service uid values). Message sequence numbers would be no longer used as record reference. It means the imap provider is required to support uids. This simplifies the adapter logic and ensures email-to-record syncronization. -- 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.
