Re: [exim] Is it posible to copy the original rcpt to to a m…

Góra strony
Delete this message
Reply to this message
Autor: B. Tkatch
Data:  
Dla: exim-users
Temat: Re: [exim] Is it posible to copy the original rcpt to to a message header?
Thanx for the comments.

Oliver, i used what you posted in the original response, and did a
test. I sent an email from another account (this one at hushmail)
and i logged in to my localhost on port 25. In both cases the
Received: header (as opposed to to and cc) lines only included the
address resolved to send me the email. It seems to be good there.

I am now looking into part 2, as mentioned before. To get the
address before it was modified. Specifically, i have an rewrite
rule:

\N^.*@([^.]+)\.example\.com\N    $1@???   T


That is, it used the subdomain as the user, and drops the actual
address sent to. For example, if an email is sent to exim-
users@??? it is rewritten to
subdomain@???. In this case, Envelope to will record
subdomain@???, but Recieved includes "for <exim-
users@???>;"

The question is, can i put that original email address--the one in
the Received header--into the headers on its own line under
something like X-Orig-RCPT_TO.

B.

On Fri, 03 Oct 2008 08:51:32 -0400 Oliver von Bueren
<maillist@???> wrote:
>As a start, Ian, please don't send replay to private address, just
>to
>list. Thanks.
>
>Ian Eiloart wrote:
>> Please don't do this. It will put all the recipients into the
>header,
>> including Bcc recipients.
>>
>I know perfectly well what the RFC tells about BCC. But this
>option does
>not what you think it does. Please read carefully what the
>envelope_to_add does, from the docs:
>---
>If this option is true, an Envelope-to: header is added to the
>message.
>This gives the original
>address(es) in the incoming envelope that caused this delivery to
>happen. More than one address may
>be present if the transport is configured to handle several
>addresses at
>once, or if more than one
>original address was redirected to the same final address. As this
>is
>not a standard header, Exim has a
>configuration option (envelope_to_remove) which requests its
>removal
>from incoming messages, so
>that delivered messages can safely be resent to other recipients.
>---
>This means, it does only include the address(es) in the envelope-
>to
>which cause the delivery to the final destination mailbox. You
>don't get
>any other addresses in that header.
>Key part of this paragraph is "caused this delivery to happen".
>The user
>should always be allowed to see what the RCPT TO was, which caused
>the
>message getting into HIS mailbox. That doesn't show him where it
>went as
>well.
>
>And by the way, these options are in the default configuration for
>
>local_delivery and address_file transports and IMHO are perfectly
>safe
>if used correctly, as in the example configuration.
>
>What B. Tkatch tries to do of course might be different and expose
>BCCs
>if done wrong.
>
>Oliver
>
>
>--
>## List details at http://lists.exim.org/mailman/listinfo/exim-
>users
>## Exim details at http://www.exim.org/
>## Please use the Wiki with this list - http://wiki.exim.org/


--
Click to find deals on GPS Systems, don't get lost.
http://tagline.hushmail.com/fc/Ioyw6h4eWUDpdc8dGR759xjKAEDSqhKTeGnXwGXrmYKEiR6I0mEURf/