Show Advanced KnowledgeHide Advanced Knowledge

User account email for sender-mail (from header)

1 Initial Problem

User emails use a global from address configured in the ILIAS administration. The email from the user account is only used in the reply-to header of user emails. This header is not visible by default in most (if not all mail clients). Users have to add this data as a seperate column for their inbox. Without this information users can easily think that they cannot directly reply to an email since the from header will (most likely) be a noreply@domain address.

In addition we ran into problems with some mail clients not being able to correctly process the reply-to header resulting in users replying to mails from ILIAS to the noreply address even though the reply-to header was set to the user accounts email address.

2 Conceptual Summary

2.1 RFC 2119

2.2 Requirements

The mail administration is updated with the optional setting to decide if the from header for user user emails is set to a fixed address or if the user account email is used. To achieve this we must make some changes to the settings for user mails:

• make the field "Sender E-Mail (From)" optional (currently it is mandatory),
• if the field is left empty ILIAS must use the user accounts email for the from header,
• we need to update the help-block for this field accordingly.

We may also change the behaviour for the Reply-To field so that this field is only filled with the users e-mail if no global address is given.

3 User Interface Modifications

3.1 List of Affected Views

• ILIAS Administration / Communication / Mail / Settings: External

3.2 User Interface Details

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

None.

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

• user email as from header for user generated mails

6 Security

None.

7 Contact

• Author of the Request: Sesterhenn, Fabian [sesterhenn]
  
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• TH Köln

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.