Merge lp://staging/~therp-nl/therp-addons/6.1-fetchmail_invoice into lp://staging/~therp-nl/therp-addons/6.1

you don't handle message_append. actually, you should do something for all message_*, otherwise you risk 'lost' mails attached silently somewhere

Hi Holger,

thank you for your response.

Looks like message_* methods are provided by mail.thread, which are available now that I use

   _inherit = ['account.invoice', 'mail.thread']

instead of

   _inherit = 'account.invoice'
   _inherits = {'mail.thread': 'mail_thread_id'}

If I do not need additional functionality, then I can rely on these existing methods, right?

I doubt that you want to have that functionality. My mail-client has a button 'edit as new' which lets me send a sent message again. This one won't do anything concerning invoices by now because it just will be attached to the invoice created by my first mail (it will have the same message id).

So if the desired behavior is 'whatever the circumstance, create an invoice if there is a new mail', you need to inhibit matching old mails to new ones, viz override message_append and call message_new there. The same with message_update.

Hi Holger,

the meaning of two messages with the same message-id from the same host is that they are to be treated as one and the same (virtually unchanged) message (see [1]). So in that case, I would not want to create that same invoice twice.

For the record, my client's 'Edit as new' button generates a copy of the message with a new message-id.

Best regards,
Stefan.

[1] http://tools.ietf.org/html/rfc2822#section-3.6.4

Valid point => approve