Tickets :: [#1833] From: field

6.0.0-beta1

8/28/25

Summary	From: field
Queue	Vacation
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners
Requester	carl (at) blackside (dot) org
Created	04/20/2005 (7435 days ago)
Due
Updated	07/25/2006 (6974 days ago)
Assigned
Resolved	07/25/2006 (6974 days ago)
Milestone
Patch	No

07/25/2006 05:13:36 PM	Jan Schneider	Comment #10 State ⇒ Resolved	Reply to this comment
Updated patch sent privately has been committed.

07/05/2006 10:44:01 PM	ch (at) hernmarck (dot) ch	Comment #9	Reply to this comment
Well - of course that would be fine. I didn't have a deeper look in the possibilities and dont' know the horde framework very well...(in short: the default "From" was a quick 'n'dirty hack I just looked up in "imp/compose.php" - but not to bad as it seems :-) I have more ideas/wishes with vacation - but one after another... /Christian

07/05/2006 11:11:13 AM	Jan Schneider	Comment #8 State ⇒ Feedback	Reply to this comment
Maybe it makes more sense to provide a drop down list with the user's identity instead? But I can be convinced otherwise. You already retrieve the select list from the identity object, but don't use it anywhere.

07/04/2006 02:51:50 PM	ch (at) hernmarck (dot) ch	Comment #7 New Attachment: vacation-h3-3.0_bug1833.patch	Reply to this comment
Hello my patch for this problem/enhancement. Can someone please have a closer look at it. It works for me (ftp based vacation with .forward). Especially the setting of the default "from": I took the default identity - but this might fail (I don't know...). Hope to get some feedback...

06/09/2006 01:08:31 PM	ch (at) hernmarck (dot) ch	Comment #6	Reply to this comment
I would like to vote for this enhancement... A second input field (copy from "subject") should do it. Maybe configurable: Allow/Disallow "From" in vacation... Christian

03/13/2006 05:27:02 PM	Jan Schneider	Priority ⇒ 1. Low

04/22/2005 07:40:28 AM	Jan Schneider	Comment #5 State ⇒ Accepted	Reply to this comment
This should be implemented as a hook then.

04/21/2005 06:24:52 PM	Eric Rostetter	Comment #4	Reply to this comment
The posters problem is he has virtual hosts, so he has e.g. usera@domain1.com, userb@domain2.com, but his vacation responses are being sent out as usera@host.domain.com, userb@host.domain.com, etc. I suggested this was a mail configuration (MTA) issue, or at best a vacation+MTA issue. But I'm not opposed to a work-around in the module, if it is a disabled-by-default configuration setting to set the From: address. It would make the life of people with virtual hosts easier, so they don't have to have as robust a virtual host configuration.

04/21/2005 08:52:23 AM	Matt Selsky	Comment #3	Reply to this comment
Our vacation program on Solaris sets an initial ~/.vacation.msg that looks like this: From: selsky (via the vacation program) Subject: away from my mail I will not be reading my mail for a while. Your mail regarding "$SUBJECT" will be read when I return.

04/21/2005 08:41:29 AM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
I don't know much about the different vacation implementations, but the doesn't make much sense to me. Shouldn't the From: address always be the one that was the original recipient? And shouldn't a correct vacation implementation do that automatically?

04/20/2005 06:09:14 PM	carl (at) blackside (dot) org	Comment #1 Priority ⇒ 2. Medium Type ⇒ Enhancement Summary ⇒ From: field Queue ⇒ Vacation State ⇒ New	Reply to this comment
Some people need to configure the From: field for their Vacation auto reply. As it is today there is only Subject and message that are put in .vacation.msg From my perspective it would be pretty smart to have the From: field as an configurable option, and when enabled, the user gets a scrollbar with their IMP identities that sets the From: address. This is almost a must for those who have HORDE/IMP in an virtualhosting enviroment.