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

Out-of-office: Apply user info to auto responder settings (if enabled) #8925

Closed
Tracked by #40397
st3iny opened this issue Oct 4, 2023 · 5 comments · Fixed by #9077
Closed
Tracked by #40397

Out-of-office: Apply user info to auto responder settings (if enabled) #8925

st3iny opened this issue Oct 4, 2023 · 5 comments · Fixed by #9077
Assignees
Labels
2. developing enhancement skill:backend Issues and PRs that require backend development skills skill:frontend Issues and PRs that require JavaScript/Vue/styling development skills

Comments

@st3iny
Copy link
Member

st3iny commented Oct 4, 2023

Is your feature request related to a problem? Please describe.

There will be a global absence form in the personal settings. Those settings should be integrated with our autoresponder.

Tracked in nextcloud/server#40397

Probably requires nextcloud/server#40650 to fetch the actual data

Describe the solution you'd like

Global out-of-office data should be applied to the autoresponder form.

Describe alternatives you've considered

None

Additional context

No response

@st3iny st3iny added enhancement 1. to develop skill:backend Issues and PRs that require backend development skills skill:frontend Issues and PRs that require JavaScript/Vue/styling development skills labels Oct 4, 2023
@st3iny st3iny moved this to 📄 To do (~10 entries) in 💌 📅 👥 Groupware team Oct 4, 2023
@st3iny st3iny self-assigned this Nov 6, 2023
@ChristophWurst
Copy link
Member

Idea for the Mail settings: make the switch ternary:

  1. Auto responder off
  2. Auto responder enabled
  3. Auto responder follows system setting

Default should be on off, I think.

For provisioning we have an option to enable Sieve. There could be a checkbox to enable system autoresponders by default.

@ChristophWurst
Copy link
Member

@jancborchardt @nimishavijay the current implementation sets the short message as subject. The long message becomes the body of the autoreply. E.g. the subject Out sick, body I am currently ….
I'm wondering if we should have a more generic subject instead, like Out of office (translated), instead of the short message. AFAIR the short ooo message was mainly for the status automation.

Our original specs nextcloud/server#40397

Set my Mail app account(s) auto responder to the date range and the absence message at the start of the absence, reset when it ends

… are not very clear about this.

Ref nextcloud/documentation#11408 (comment)

@jancborchardt
Copy link
Member

@ChristophWurst is the main intention of this to have it translated? Because e.g. for mail autoreply, this is not something which can be translated for the sender anyway, right?
But I don’t have strong feelings about the subject being the short message, it would be fine to have a generic subject. It would still be useful for other places where it appears, right?

@ChristophWurst
Copy link
Member

Fair enough. L10n is indeed tricky here. Sometimes the user's own language is fine. Other times you want to internationalize.

But I don’t have strong feelings about the subject being the short message, it would be fine to have a generic subject. It would still be useful for other places where it appears, right?

In my personal use case, I do want other Nextcloud users to see why I'm out, like when I'm sick. Other Nextcloud users are colleagues and people I work with. The autoresponder is on for anyone who knows my email. I don't want my short message (status) sent to them.

We could also just prepend Re: to the original message's subject and avoid the l10n dilemma.

@jancborchardt
Copy link
Member

Ah right, got it. Yes, the status is indeed a bit more private. Then let's go with the generic "Out of office" subject as you suggest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2. developing enhancement skill:backend Issues and PRs that require backend development skills skill:frontend Issues and PRs that require JavaScript/Vue/styling development skills
Projects
Development

Successfully merging a pull request may close this issue.

3 participants