Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[15.0] mail_multicompany default from not being applied #607

Open
iTecan opened this issue Apr 3, 2024 · 2 comments
Open

[15.0] mail_multicompany default from not being applied #607

iTecan opened this issue Apr 3, 2024 · 2 comments
Labels

Comments

@iTecan
Copy link

iTecan commented Apr 3, 2024

Module

mail_multicompany

Describe the bug

After installing the module, when we configure 2 smtp servers and send an email, the default mail from parameter is not being applied, being the email from the user the one applied instead

To Reproduce

Affected versions: 15.0

Steps to reproduce the behavior:

  1. Config 2 outgoing mail servers that have different domains (@domain1 and @domain2), with from filter being applied
  2. In system parameters, config mail.default.from_filter and mail.default.from with one domain (default@domain1)
  3. Config a user with an email (user@domain1)
  4. Send a mail with a user that is from the company that has the mail.default.from (user from domain1)

Expected behavior
The from in the email header and the resume on top should be the one applied in mail.default.from and mail.default.from_filter (default@domain1) instead of the user's email (user@domain1)

Additional context
We tried using the ir_config_parameter_multi_company (after migration) that is from this repo in branch 14.0 that creates and enviroment for the system parameters per company, but is not being applied either

@iTecan iTecan added the bug label Apr 3, 2024
@dg18
Copy link

dg18 commented May 6, 2024

Hello @iTecan,

Do you have any knowledge if this module is having the same issue in 16.0?

@iTecan
Copy link
Author

iTecan commented May 6, 2024

Hello @dg18,

Currently we haven't tested this behavior in version 16 so we can't give futher information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants