Mailing List Archive: how do I keep the sender header from being rewritten?

how do I keep the sender header from being rewritten?

Jun 21, 2002, 7:25 PM

Post #1 of 3 (448 views)

Hi,

I'm using TMDA in conjunction with Exim and it creates an auto-reply
that is handed off to port 25 of the localhost for delivery. It is
configured to use a specified bounce_envelope_sender variable to avoid
infinite loops of confirmation requests <-> bounces.

What's happening though is Exim is superceeding the preference of the
envelope sender (even though it's running as a trusted user with the
"untrusted_set_sender = true" configuration variable) and rewriting the
return-path with the confirmation address; which is a bad thing.

2002-06-21 21:10:05 17LaLl-0005YC-00 return-path spambounce@caffe.net
rewritten as tj-confirm-1024711805.21122.d7edc4@caffe.net using Reply-To

I need to turn that function off. I haven't found exactly where to do
that.

How to I preserve the envelope sender as I have specified and not have
Exim rewrite it? (This is 3.3x btw.)

Thanks!
Todd

Re: how do I keep the sender header from being rewritten? [ In reply to ]

djc at microwave

Jun 22, 2002, 10:52 AM

Post #2 of 3 (434 views)

Permalink

On Fri, 21 Jun 2002, Todd Jagger wrote:

> Hi,
>
> I'm using TMDA in conjunction with Exim and it creates an auto-reply
> that is handed off to port 25 of the localhost for delivery. It is
> configured to use a specified bounce_envelope_sender variable to avoid
> infinite loops of confirmation requests <-> bounces.
>
> What's happening though is Exim is superceeding the preference of the
> envelope sender (even though it's running as a trusted user with the
> "untrusted_set_sender = true" configuration variable) and rewriting the
> return-path with the confirmation address; which is a bad thing.
>
> 2002-06-21 21:10:05 17LaLl-0005YC-00 return-path spambounce@caffe.net
> rewritten as tj-confirm-1024711805.21122.d7edc4@caffe.net using Reply-To
>
> I need to turn that function off. I haven't found exactly where to do
> that.

Address rewriting is something that has to be specifically enable. There
is no 'default' address rewriting that is done. If your exim is
rewriiting its becuase someone has specifically configured your exim to
do that. If you are the only person that has worked on it, then you need
to take a closer look at the rewrite rules you have setup and determine
how you want them to work (or not, as the acase may be). If someone else
helped you, then they need to help you. If you have cut and pasted
config lines into your exim config without understanding them, then go
back and understand them.

>
> How to I preserve the envelope sender as I have specified and not have
> Exim rewrite it? (This is 3.3x btw.)
>
> Thanks!
> Todd
>
>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
>

--

Re: how do I keep the sender header from being rewritten? [ In reply to ]

tj.lists at overland

Jun 22, 2002, 1:11 PM

Post #3 of 3 (443 views)

Permalink

Dave C. wrote:

>
> Address rewriting is something that has to be specifically enable. There
> is no 'default' address rewriting that is done. If your exim is
> rewriiting its becuase someone has specifically configured your exim to
> do that. If you are the only person that has worked on it, then you need
> to take a closer look at the rewrite rules you have setup and determine
> how you want them to work (or not, as the acase may be). If someone else
> helped you, then they need to help you. If you have cut and pasted
> config lines into your exim config without understanding them, then go
> back and understand them.
>

Hi,

There are no rewrite rules in my configuration file. I don't claim to
be an expert in Exim but I have been using it since 2.04 and believe I
have a decent grasp of the configuration options.

Anyway, I figured it out. The $local_part for the bounce address has to
actually exist as a system user or Exim will rewrite the return-path
using the reply-to address. Anyone who's using Exim in conjunction with
TMDA can check the tmda-users list for more details.

Thanks,
Todd