Send mail to user alias: model res.users does not accept incoming emails

[Marcel van der Boom (HS-Development BV)]

alias domain: sub.example.com

users are created with aliases <email address hidden>

System is setup with a catchall IMAP box.
We have the system working for tasks/project issues/leads so I'm fairly confident the setup is sane.

When a mail message is sent to <email address hidden> The following happens:

1. mail is properly routed to the imap mailbox
2. openerp cronjob tries to retrieve it.
3. Server log contains error:
"
2013-09-06 08:40:08,316 17524 ERROR hsd openerp.addons.fetchmail.fetchmail: Failed to fetch mail from imap server Catch All openobject address.
Traceback (most recent call last):
  File "/var/openobject-server/hsd-7.0/addons/fetchmail/fetchmail.py", line 205, in fetch_mail
    context=context)
  File "/var/openobject-server/hsd-7.0/addons/mail/mail_thread.py", line 662, in message_process
    (msg['message_id'], model)
AssertionError: Undeliverable mail with Message-Id <email address hidden>, model res.users does not accept incoming emails
"

Code revistions used (7.0 branches):
server : 5061
web : 4023
addons : 9406

[Marcel van der Boom (HS-Development BV) (mrb)]

Looking at the code, it seems that res.users is just missing an implementation of the message_new method? The message_update method is implemented, but message_new seems to be missing.

[Marcel van der Boom (HS-Development BV) (mrb)]

Oh, and in the Saas version, it works fine.

[Marcel van der Boom (HS-Development BV) (mrb)]

http://bazaar.launchpad.net/~openerp/openobject-addons/7.0/revision/8060 seems relevant

[Marcel van der Boom (HS-Development BV) (mrb)]

This turns out to be a mixed bag of things, partly due to data corruption and partly because I think there is a bug in the 'special' security evalution of mail.message in mail_message.py method check_access_rule.

After correcting the data corruption the error turns into an 'operation cannot be completed due to security restrictions', but only for one address.

In short, I think it's working in 99% of the cases now, except for one specific 'From' address which leads to the security error.

Marking as invalid as I can't provide the proper information for that 1%