I'm sorry, I think I mispoke. I was actually thinking of SMTP
server-to-server communication, which preserves headers; I'm not sure
clietns would do that. As a matter of fact, I have a suspicion they
don't. I'd try it anyway, just in case.
However, the problem you have is not having control over the client;
this is crucial. If you have no control over the client, you cannot
guarantee that a response or reply will contain any of the information
you originally included in your message--headers or content.
dZ.
On Oct 20, 2008, at 05:41, DZ-Jay wrote:
>
> On Oct 19, 2008, at 08:09, zayin wrote:
>> The person receiving the alarm will just need to reply to the email.
>
> If you include an X-Header when you send the message, the client will
> probably include it when replying, this is standard behaviour in most
> clients.
>
>> So, it appears I might need to embed a unique string in the body of
>> the
>> message and use that to determine the responder.
>
> Use an X-Header. Perform some tests: send a message with a new
> X-Header and reply from your mail client and see if it's there. This
> may be more reliable than including something in the body, which may be
> sanitized, truncated, or modified by the client or any proxy in
> between.
>
> dZ.
> --
> DZ-Jay [TeamICS]
> http://www.overbyte.be/eng/overbyte/teamics.html
>
> --
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
>
>
--
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
