RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread R. Scott Perry
>- The final SMTP server will PRESERVE the ENVELOPE FROM to the >- RETURN PATH header, so that any bounces AFTER completion of >- the SMTP process still know where to send bounces to. > >As I read RFC2821 7.2, second paragraph, a mail system should NOT do >exactly this. RFC2821 7.2 second paragr

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Terrence Koeman
- -Original Message- - From: [EMAIL PROTECTED] - [mailto:[EMAIL PROTECTED]] On Behalf Of Andy Schmidt - Sent: Friday, February 15, 2002 18:52 - To: [EMAIL PROTECTED] - Subject: RE: [Declude.JunkMail] Return-Path - proper use? - - - >> Im curious how this would be achieved w

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Andy Schmidt
>> Im curious how this would be achieved without setting the return-path: header previously: "It is possible for the mailbox in the return path to be different from the actual sender's mailbox, for example, if error responses are to be delivered to a special error handling mailbox rather than to

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Andy Schmidt
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1123.html >> If there is a delivery failure after acceptance of a message, the receiver-SMTP MUST formulate and mail a notification message. This notification MUST be sent using a null ("<>") reverse path in the envelope; see Section 3.6 of RFC-821.

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread R. Scott Perry
> >> Allthough I don't see how the last server should acquire the address for >the return-path: << > >Well - it seems to me as if the last server has responsibility to report >back to the relaying server that it was contacted from? The Return-Path: header *must* take the address from the "MAIL

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Terrence Koeman
Terrence Koeman Technical Director/Administrator MediaMonks B.V. (www.mediamonks.nl) Please quote all replies in correspondence. - -Original Message- - From: [EMAIL PROTECTED] - [mailto:[EMAIL PROTECTED]] On Behalf Of Andy Schmidt - Sent: Friday, February 15, 2002 18:30 - To: [EMAIL PROTEC

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Andy Schmidt
RFC 1123 (http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1123.html) "IMPLEMENTATION: The MAIL FROM: information may be passed as a parameter or in a Return-Path: line inserted at the beginning of the message." >> Allthough I don't see how the last server should acquire the address for the return-p

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Terrence Koeman
- - From: [EMAIL PROTECTED] - - - [mailto:[EMAIL PROTECTED]] On Behalf Of - - Andy Schmidt - - - Sent: Friday, February 15, 2002 17:44 - - - To: [EMAIL PROTECTED] - - - Subject: RE: [Declude.JunkMail] Return-Path - proper use? - - - - - - - - - >> afaik is the Return-Path: header used to det

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Terrence Koeman
ence. - -Original Message- - From: [EMAIL PROTECTED] - [mailto:[EMAIL PROTECTED]] On Behalf Of - Terrence Koeman - Sent: Friday, February 15, 2002 17:52 - To: [EMAIL PROTECTED] - Subject: RE: [Declude.JunkMail] Return-Path - proper use? - - - Well, most servers do not handle Return-Path: correctly,

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Terrence Koeman
r/Administrator MediaMonks B.V. (www.mediamonks.nl) Please quote all replies in correspondence. - -Original Message- - From: [EMAIL PROTECTED] - [mailto:[EMAIL PROTECTED]] On Behalf Of Andy Schmidt - Sent: Friday, February 15, 2002 17:44 - To: [EMAIL PROTECTED] - Subject: RE: [Declude.JunkMa

RE: [Declude.JunkMail] Return-Path - proper use?

2002-02-15 Thread Andy Schmidt
>> afaik is the Return-Path: header used to determine where to return the mail in case it bounces and other postmaster messages. It can very well be some other address than the address where it was sent from. Like the reply-to: header. << Uhhh - so this header should (and possibly could) have be