-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Andy,

On 13 December 2001 at 16:20:58 [GMT-0500] (which was 21:20 where I
live) Andy Spiegl wrote to TBUDL and made these points:

>> The trouble is, if you received a message then the "To:" line is to
>> you. If you resend it still "To:" you then it does a boomerang.

AS> As far as I know this is incorrect.  If there are "Resent-" headers then
AS> the To: line is ignored.  I just tried it.

RFC822 says:

     4.5.  RECEIVER FIELDS

     4.5.1.  TO / RESENT-TO

        This field contains the identity of the primary recipients  of
        the message.

It says nothing about mutual exclusivity, which means that if both are
present then the "To:" field would be used for routing in addition to
the Resent-To:. Thing is, there's the headers and then there's the
SMTP envelope, which is what specifies the *true* recipient. Using TB,
we don't get control over that - it's just taken from the "To:" field
or even just left to the SMTP server to siphon out of the various
destination address fields and place in the RCPT TO: envelope header.

Mutt clearly provides better control of such things (as does most
software from the *nix world).

>> 1) Using an SMTP remailer to place an envelope around the message
>>    with a different delivery target. (TB is not one of these).
>> 2) MIME forward the entire message as an attachment.

AS> And 3) just put Resent- headers in and refeed it to the smtp
AS> server.

... from a client that allows you to do such a thing. No, TB doesn't
support this.

>> Other than that "Redirect" is as close as you get.

AS> But it changes ALL the header lines. :-((

Well, the To: and the Date: ... nothing else that I can see. Option 2
works good.

- --
Cheers -- .\\arck D. Pearlstone -- List moderator
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
\ BrainStorm - free thinking - www: http://www.brainstormsw.com /
 \ PGP Key ID: 0x929DCDA0  |  www: http://www.silverstones.com /
'
TB! v1.54 Beta/15-14F4B4B2 on Windows NT 5.0.2195
'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)
Comment: GPG Sealed for freshness

iD8DBQE8GTdQOeQkq5KdzaARAi+gAKDc5reTJz8WRIfBVIq+GGaf7yNpOwCeP3qk
yFIZx07S6xS+DpylWWisyy4=
=h0ab
-----END PGP SIGNATURE-----



-- 
________________________________________________________
Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d
FAQ        : http://faq.thebat.dutaint.com 

Reply via email to