[trunk][7.0] fetchmail writes fetchmail_server_id to mail.mail, but shouldn't it be mail.message?

[Holger Brunn (Therp)]

Please correct me if I'm wrong, but shouldn't lines 266ff in http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/view/head:/fetchmail/fetchmail.py#L266 be about mail.message? I can't think of a way how an email fetched by fetchmail could end up as a mail.mail.

Working on a fetchmail related module, I found it would be very helpful to have exactly that on mail.message.

If you confirm this one, I'll be more than happy to provide appropriate merge requests.

[Stefan Rijnhart (Opener) (stefan-opener)]

After a quick glance through the code it seems to me you are perfectly right. I for one would welcome a proposal for this.

[Niels Huylebroeck (red15)]

mail.mail has a mail.message embedded (encapsulated / as a child)

_inherits = {'mail.message': 'mail_message_id'}

http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/view/head:/mail/mail_mail.py#L42

This makes me consider that if you create a mail.message an optional mail.mail can be made as a parent and this would serve to store more details about the actual mail message (instead of just the content) and how it got delivered or should be sent.

This would server to keep the mail.message agnostic of the source, allowing users to enter messages without having to have one model that needs more columns to store all the possible meta data associated with real SMTP/IMAP/POP3 protocols.