"Voytek Eymont" <[EMAIL PROTECTED]> writes:
> On Mon, August 4, 2008 4:09 pm, Daniel Pittman wrote:
>> "Voytek Eymont" <[EMAIL PROTECTED]> writes:
>
>>> (i.e., who misconfigured their server ?)
>
>> You did.
>
>> You are sending out email that there is absolutely *NO* way for the
>> intended recipient -- or their server -- to notify you about the success or
>> failure of delivery.
>>
>> If you send out email from an email address ensure that the envelope can
>> receive email; either arrange for the envelope address to be something
>> other than "apache@" or arrange for "apache@" to forward somewhere
>> sensible.
>
>> Also, why are you generating outbound email that it is impossible for
>> the recipient to respond meaningfully to?
>
>
> well, that's actually not correct, the emails have a valid and correct 'from'
> (copied from headers)
> "From: Reservations <[EMAIL PROTECTED]>"
> and, mail client's 'reply' replies the above valid address
It should also include a "Sender" header of "[EMAIL PROTECTED]", by the
RFC, indicating the mailbox that sent the email on the behalf of the
indicated sender.
Further, the issue is that the recipient cannot meaningfully respond to
the *sender* of the messages, only to some other address. The sender,
attached to the envelope, is "apache@", and has nothing significant to
do with the content of the From header in the body.
It is perfectly legitimate for the recipient to act on the SMTP envelope
details, and RFC mandated that your scenario permits them to do so by
way of the Sender header...[1]
> also, these are 'forms' that were actually filled in by the recipient,
> it's simply their conformation on what they filled in
*shrug* So, send it from an appropriate email address.
> it's the "Return-Path: <[EMAIL PROTECTED]> that has 'invalid' address
Return-Path, Sender, and the SMTP envelope. You should fix *all* of
those to be deliverable for responses.
Regards,
Daniel
Footnotes:
[1] Technically, only as a SHOULD, also known as "unless you have an insanely
good reason to do otherwise, which you don't." See RFC2822, 3.6.2
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
