Bug 37593 - Use user's mail address as sender address
Use user's mail address as sender address
Status: CLOSED FIXED
Product: UCS@school
Classification: Unclassified
Component: UMC - Helpdesk
UCS@school 4.0
Other Linux
: P5 enhancement (vote)
: UCS@school 4.0 R2
Assigned To: Florian Best
Alexander Kramer
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-01-22 16:32 CET by Sönke Schwardt-Krummrich
Modified: 2015-05-11 19:24 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2015-01-22 16:32:46 CET
Currently the helpdesk module uses the hardcoded sender address 
"ucsschool-helpdesk@$FQDN" and writes the username into the mail body. 

Customers requested that the helpdesk module should use the user's mail primary address as sender address if available, to avoid the manual lookup of mail addresses by the helpdesk staff.
Comment 1 Florian Best univentionstaff 2015-04-17 13:23:58 CEST
If exists, the mailPrimaryAddress is now used as From field so that the helpdesk/staff can directly answer to the mail.

Package: ucs-school-umc-helpdesk
Fix: svn r59786
Comment 2 Alexander Kramer univentionstaff 2015-04-22 13:02:58 CEST
OK - debian / changelog
OK - xml /changelog
OK - If exists, the mailPrimaryAddress is now used as From field so that the helpdesk/staff can directly answer to the mail.
OK - otherwise - "ucsschool-helpdesk@$FQDN"
Comment 3 Florian Best univentionstaff 2015-05-11 19:24:54 CEST
UCS@school 4.0 R2 v1 has been released:
http://docs.univention.de/release-notes-ucsschool-4.0R2v1-de.html

If this error occurs again, please use "Clone This Bug".