Hi there!

On 16 Mar 00, at 0:43, Michael Wieczorek wrote
    about "Re: Using Macros for header (%RETUR":

> AVK> ...and Stefan is right (as always;-)) here: you should *not* set the 
>return-path 
> AVK> yourself, on the user side you should limit yourself to altering the Reply-To: 
> AVK> header... because return-path: is subject to be set/changed/altered by the 
> AVK> SMTP server...
> 
> But the "Return-Path:" is setting by *TB* to the "Reply-To:"-address
> *not* by the server. 

Nope;-) Here's what goes to the server in my own case (just an example):

---8<---------
Date: Thu, 16 Mar 2000 03:06:57 +0300
From: "Alexander V. Kiselev" <[EMAIL PROTECTED]>
X-Mailer: The Bat! (v1.41) Personal
Reply-To: "Alexander V. Kiselev" <[EMAIL PROTECTED]>
Organization: Home Sweet Home
X-Priority: 3 (Normal)
Message-ID: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: test
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

test
-----8<------

Note the _absence_ of the return-path: field. The latter field is added by the 
"transport system that deliveres message to the recipient", not by the 
originator (in this case, me, or, better to say, TB;-))

> If I right to understand the RFC-822 (see below), the RFC means that the
> "Return-Path" is used to identify the _originator_. That means for me: the
> _send-address_ not the reply-address. 

The transport system determines, what should Return-Path: be, based on what 
the SMTP server receives in the SMTP envelope. That is, _if_ it gets the 
following:

MAIL FROM <[EMAIL PROTECTED]>

,it will set the Return-Path: as follows:

Return-Path: [EMAIL PROTECTED]

or, maybe,

Return-Path: mail.ru!akiselev

which has the same meaning.

And so it is in your case: the message I'm replying to has:

X-Return-Path: [EMAIL PROTECTED]

This field has been added by the MDaemon at dutaint.com.

> Explanation to above: [EMAIL PROTECTED] is my send address, [EMAIL PROTECTED]
> is my reply-address. But the header generated by TB looks like
> 
> Return-Path: <[EMAIL PROTECTED]>

This has been added elsewhere, probably;-) TB shouldn't have added this 
header, IMHO.

> Date: Tue, 14 Mar 2000 21:09:46 +0100
> From: Michael Wieczorek <[EMAIL PROTECTED]>
> X-Mailer: The Bat! (v1.41) Personal
> Reply-To: [EMAIL PROTECTED]

Which implies that the people who will answer you will use *this* address, 
which is exactly what you want to achieve, isn't it?

The RFC822 information that you supplied below says nothing more on the 
point;-)

> RFC-822
> [..]
> 4.3.1.  RETURN-PATH
> 
>                This field  is  added  by  the  final  transport  system  that
>                delivers  the message to its recipient.  The field is intended
>                to contain definitive information about the address and  route
>                back to the message's originator.
> 
>                Note:  The "Reply-To" field is added  by  the  originator  and
>                       serves  to  direct  replies,  whereas the "Return-Path"
>                       field is used to identify a path back to  the  origina-
>                       tor.
> 
>                While the syntax  indicates  that  a  route  specification  is
>                optional,  every attempt should be made to provide that infor-
>                mation in this field.
> [..]
> 4.4.3.  REPLY-TO / RESENT-REPLY-TO
> [..]
>                Note:  The "Return-Path" field is added by the mail  transport
>                       service,  at the time of final deliver.  It is intended
>                       to identify a path back to the orginator  of  the  mes-
>                       sage.   The  "Reply-To"  field  is added by the message
>                       originator and is intended to direct replies.
> 
> 
> So I think it is a bug by TB, is'nt it?

I don't think so;-) See above.

-- 
SY, Alex
(St.Petersburg, Russia)
http://mph.phys.spbu.ru/~akiselev
--- 
Thought for the day:
  Don't take life too seriously; you won't get out of it alive.

--- 
PGP public keys on keyservers:
0xA2194BF9 (RSA);   0x214135A2 (DH/DSS)
fingerprints:
F222 4AEF EC9F 5FA6  7515 910A 2429 9CB1 (RSA)
A677 81C9 48CF 16D1 B589  9D33 E7D5 675F 2141 35A2 (DH/DSS) 
--- 

-- 
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
   <mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
   <mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------

You are subscribed as : archive@jab.org

Reply via email to