[sork] Re: Vacation From?

[Carl Boberg]

Hi,

Thanks for your response :-)

My mailserver is unfortunately hosting several domains and all responses 
from vacation are from user at firtshost.firstdomain.com when they ought to 
be from second/third/fourth -host/domain.com

Changing the mailserver to exclude hostname would most likely just 
reduce my problem to responses from user at second/third/fourth -domain.com
to allways be user at firstdomain.com (am I making sense?)

Im using sendmail/dovecot btw.
I will try and see if I can conjure up some sendmail magic ;-)

But I would still gladly see it as an configurable option :-)

Maybe I have a sort of lazy setup of my virtualhosting but everything 
else works great for me :-)
I tried to hack my way past this but realised soon that it would take 
too much effort for me since im not familiar with the code....

On a side note, about hindering users from forging the From:
They can already do that in IMP by using different identities where they 
easily can set their From: address and such(yes it can be disabled but 
still).
And if I would like to fake my from address it probably wouldnt be by 
using auto respons function from vacation...
And also; Is there any colaboration between horde modules to take care 
of theese kind of securityconcerns?

/ Cheers
Carl

Eric Rostetter wrote:
> Quoting Carl Boberg <carl at blackside.org>:
> 
> 
>>In regular vacation.msg are you not supposed to put a From: field at the
>>top?
> 
> 
> You can, or not, depending on your needs/desires/policies/etc.  It is
> optional.
> 
> 
>>When my vacation sends a reply it is always with user at host.domain.com
>>and not with user at domain.com as I would like since the From: field is
>>not present.
> 
> 
> This is something you would better fix in your mail server software,
> so it translates *@host.domain.com to *@domain.com internally.  It really
> isn't something the user should be expected to know/do, IMHO.
>  
> 
>>It would be great if one could specify the From: field just as one can
>>specify the Subject: filed today.
> 
> 
> It could be done as a configurable option, without any real problem.  It isn't
> done for several reasons:
> 
> 1) I didn't want to give my users an easy way to forge the From: address
>    and spoof emails.
> 2) Specifying the From: may not be enough (may also need Reply-To: and so on).
> 3) Figured people would fill in bogus addresses, make typos, etc. that would
>    make the e-mail get filtered, be non-replyable, be bounced, etc.
> 
> However, if there was demand/desire, we could code this up as an option
> that was disabled by default, and could be enabled for those who like
> to live more dangerously.
>