Date: Mon, 25 Feb 2002 16:11:23 -0800
   From: Ian Macdonald <[EMAIL PROTECTED]>
[...]
   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]>
[...]
   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]?

When Cyrus puts the return-path into the message, it qualifies it
with the value of 'servername' (defaulting to gethostname()).  It
doesn't pass that qualification to the Sieve subsystem.

Thus Sieve attempts to send a message to cyrus@unspecified-domain
which your MTA is qualifying as [EMAIL PROTECTED]

Hmm, sounds like a FAQ entry about double Return-Paths and unqualified
envelopes is in order here.  Can anyone give me a Q/A for doc/faq.html?

thanks,
Larry

Reply via email to