But to play games with terminology, when I'm putting the address in
the "to:" line, I'm not steaming open the envelope. I'm attaching a
mailing label to the outside -- you're looking at the envelope too
literally here with VERP. all I'm doing is choosing to use a more
correct (or perhaps specific is a less loaded word) address on that
mailing label I paste on the envelope.the header *is* part of the
envelope, even if it's not 'envelope' in the terminology of SMTP.
If you really want to get literal about it, what I'm doing is what my
bank does with my bank statement -- print the address on the
statement, and use an envelope with a window instead of printing it
on the envelope itself....
Heh, heh, nice analogy. But I think I can use it to my benefit
instead of yours. :-)
I would make the case that the bank statement analogy is better matched
with personalizing the actual content as opposed to the headers. The
physical envelope itself is generic, as should the headers be in an
elist message. The window itself represents the name of the elist, with
what's visible on the inside representing the SMTP envelope information.
The actual name and address information on the inside represents the
salutation of the actual content of the email message.
I think the real problem here is that Internet email (SMTP/RFC822)
overloads the "headers" in a "message". I had intimated before that at
least one thing X.400 really did do better was to make an absolute
separation of such things. Without this I don't see any easy
resolutions.
Recently I modified my "goodbye" messages sent to people who
unsubscribe, so that they say that we're sorry to see them go, and
adds a mailto: link if they want to send us feedback on why they're
leaving.
Good idea! I've already added this to my service.
Thanks,
Jim
--
James M. Galvin <[EMAIL PROTECTED]>
------------------------------------------------------------------------
Public mailing lists hosted free at <http://www.elistx.com>
