Skip to content

Conversation

@yankinmax
Copy link
Contributor

No description provided.

@yankinmax yankinmax mentioned this pull request Aug 4, 2025
4 tasks
@yankinmax
Copy link
Contributor Author

@gurneyalex can you look? It seems good

def _server_env_fields(self):
base_fields = super()._server_env_fields
office365_fields = {
"smtp_authentication": {},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should merge and forward port this instead, IMO:

The smtp_authentication field is not specific to office365.


Is there no other field needed to be set through the environment, for outlook?
Like the microsoft_outlook_access_token or microsoft_outlook_refresh_token ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure @ivantodorovich
This module is a specific one. It provides a description of the parameters required for the outlook.
If we go with forward port we will need to update the description on mail_environment.
Maybe it's not obvious for everyone in the community.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I'm sure of is that the smtp_authentication field is defined in the base mail module, and re-used by microsoft_outlook and google_gmail (and possibly others) -- so making it configurable through environment belongs to mail_environment, not here.

However, I think you need to make other fields configurable through env, that are truly specific to microsoft_outlook, like the ones I suggested above. But to know this you need to test and see if you can fully configure an email server with outlook credentials by playing solely with the environment

@yankinmax
Copy link
Contributor Author

@github-actions
Copy link

github-actions bot commented Dec 7, 2025

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Dec 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants