On Mon 25 Feb 2002 at 16:14:33 -0500, you wrote:
> What's the "Return-Path" header indicate?
Hmm, I seem to have two.
The Cyrus server is currently not in production, so the current
sequence of events for delivery is as follows:
- MX host (sendmail) accepts message from the Internet
- MX host (sendmail) forwards message to internal mail relay (sendmail)
- mail relay (sendmail) hands off message to another machine
(sendmail) for local delivery via procmail
- user's ~/.procmailrc forwards a copy of e-mail to new mail server (Cyrus)
- new mail server (Cyrus) delivers locally over LMTP
The top few lines of a message sent from outside the company to my
account inside look like this:
Return-Path: <[EMAIL PROTECTED]>
Received: from lovelace.corp.google.com ([unix socket])
by lovelace.corp.google.com (Cyrus v2.1.2) with LMTP; Mon, 25 Feb 2002
+16:00:45 -0800
X-Sieve: CMU Sieve 2.0
Return-Path: <[EMAIL PROTECTED]>
As you can see, lovelace is the new machine running Cyrus. The second
Return-Path header is picked up when procmail is run on the previous
hop, so it's the top Return-Path header that applies when the message
is being delivered to Cyrus.
Even though the return path is wrong, it's still fully qualified, so
why doesn't Cyrus try to send the vacation reponse to
[EMAIL PROTECTED] instead of
[EMAIL PROTECTED]?
> If Return-Path isn't right, vacation won't work either, since the
> vacation message will attempt to go to the Return-Path.
Right, but even that doesn't appear to be what happens.
Thanks for your help so far.
Ian
--
Ian Macdonald | God made the integers; all else is the work
System Administrator | of Man. -- Kronecker
Google, Inc. |
[EMAIL PROTECTED] |
650.330.0100 x1265 |
