Cyrus + Sieve

Gottschalk, David dgottsc at emory.edu
Tue May 26 10:03:15 EDT 2009


The Return-Path must be my problem them.

Right now, any emails that come into dgottsc at miriam have a return path of that.

So your saying the Return-Path should be the sender of the email, not the recipient? Correct?

David Gottschalk
UTS Email team
david.gottschalk at emory.edu


-----Original Message-----
From: info-cyrus-bounces+dgottsc=emory.edu at lists.andrew.cmu.edu [mailto:info-cyrus-bounces+dgottsc=emory.edu at lists.andrew.cmu.edu] On Behalf Of Adam Tauno Williams
Sent: Tuesday, May 26, 2009 9:58 AM
To: info-cyrus at lists.andrew.cmu.edu
Subject: RE: Cyrus + Sieve

On Tue, 2009-05-26 at 08:52 -0400, Gottschalk, David wrote:
> Do you mean the From: header line?

No, the "From:" line is, as always, utterly meaningless.

> I have multiple "Received:" headers since the message had to transverse multiple
> servers to get to the Cyrus server.

Which is normal.  But they will show how the message actually got
processed;  most importantly who the message was addresses to by the
first server to process it.  I've seen people header/masquerade
rewritting rules do some weird stuff.

> What is the "Return-Path: <dgottsc at servername>" signify? I'm wondering if that
>  is the problem.

The Return-Path: specifies the reply address for any autp responders
(RFC3834).  It shouldn't matter for diagnosing your problem unless
something is rewriting the Return-Path on inbound messages [which would
be very wrong, and in your MTA, not in Cyrus].

--
OpenGroupware developer: awilliam at whitemice.org
<http://whitemiceconsulting.blogspot.com/>
OpenGroupare & Cyrus IMAPd documenation @
<http://docs.opengroupware.org/Members/whitemice/wmogag/file_view>

----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information.  If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).


More information about the Info-cyrus mailing list