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

Do not set short absence message for system autoresponder #9219

Closed
ChristophWurst opened this issue Jan 8, 2024 · 3 comments · Fixed by #9228
Closed

Do not set short absence message for system autoresponder #9219

ChristophWurst opened this issue Jan 8, 2024 · 3 comments · Fixed by #9228
Assignees

Comments

@ChristophWurst
Copy link
Member

Steps to reproduce

  1. Configure an absence
  2. Go absent
  3. Receive an email

Expected behavior

Sender receives an automated message with "Re: xxx".

Actual behavior

Sender receives an automated message with my user status.

Mail app version

3.5

Mailserver or service

No response

Operating system

No response

PHP engine version

None

Web server

None

Database

None

Additional info

Discussed in #8925 (comment)

@ChristophWurst
Copy link
Member Author

Once fixed let's also reflect this in the user docs nextcloud/documentation#11408.

@st3iny
Copy link
Member

st3iny commented Jan 8, 2024

The default subject is defined as follows:

   Users can specify the Subject of the reply with the ":subject"
   parameter.  If the :subject parameter is not supplied, then the
   subject is generated as follows: The subject is set to the characters
   "Auto: " followed by the original subject.  An appropriate fixed
   Subject, such as "Automated reply", SHOULD be used in the event that
   :subject isn't specified and the original message doesn't contain a
   Subject field.

E.g. Auto: Subject blah blah

Ref https://www.rfc-editor.org/rfc/rfc5230.html#section-5.3

@ChristophWurst
Copy link
Member Author

Then let's use this default subject 👍

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

Successfully merging a pull request may close this issue.

2 participants