[FIX] mass_mailing: do not reset mailing_domain when changing model

Indeed due to onchange being trigerred at creation it breaks trying to
set default_mailing_domain when creating a new mailing through the web
client.

As setting domain and then changing model should not be the primary use
case of mass mailing, people will have to update their domain manually
instead of seeing it reset to a void domain.

0 files changed, 0 insertions, 0 deletions