[Pkg-exim4-users] rewrite rules

Ross Boylan ross at biostat.ucsf.edu
Tue Jan 3 21:14:04 UTC 2006

On Sun, 2005-12-18 at 19:16 +0100, Marc Haber wrote:
> On Fri, Oct 07, 2005 at 12:01:06PM -0700, Ross Boylan wrote:
> > This produced these rewrites on the smarthost transport:
> >   headers_rewrite = *@+local_domains $1 at DCreadhost frs : *@iron.psg.net
> > $1 at DCreadhost frs
> >   return_path = ${if
> > match_domain{$sender_address_domain}{+local_domains}{${sender_address_local_part}@DCreadhost}{${if match_domain{$sender_address_domain}{iron.psg.net}{${sender_address_local_part}@DCreadhost}fail}}}
> > 
> > Which is good, but I really want to get all the headers, including cc or
> > bcc. > Otherwise, when someone hits reply all there may be trouble.  I'm
> > not claiming this is universally desirable behavior, but it seems right
> > for me.
> I think that we shouldn't go too far with rewriting. What we _need_
> to do is take care that the message goes out with a correct sender
> (mostly to take care about bounces being sent to the correct
> recipient), but I don't think that we should interfere with message
> recipients as well.
> The "trouble" would be a bounce, as if our local user had written a
> differently broken address into Cc:.
The trouble I was thinking of is that some people won't get the reply.

> Rewriting Bcc is not an option anyway since Bcc gets removed anyway
> before the message is sent.
exim does have an option to rewrite the bcc fields.  bcc does seem less
important, since nobody should see the bcc field, so they can't be
misled by it.

> > Oh... maybe dc_mailname_in_oh true = mailname appears in other headers;
> > if false they get rewritten too?
> Please explain what you mean, I do not understand.
I was guessing at what cd_mailname_in_oh does: that it controls whether
the mailname appears in other headers.  I further guessed that if it
were false the rewriting might be more extensive.  The second guess is
not too plausible, given the first.

More generally, I was wondering if there are some Debian supplied
buttons to tweak that control which mail headers get rewritten.

> > What's the best way to achieve this effect?  I can't do it with standard
> > rewrites, because before transport my addresses look like
> > foo at iron.psg.net.  I'm not wed to that scheme, but it seemed safer than
> > rewriting everything immediately to foo at biostat.ucsf.edu, which would
> > essentially make it as if my machine were masquerading as a different
> > one.
> > 
> > Also, I'm not sure why the rewrite rules with iron.psg.net are present;
> > I would expect that to be one of the local_domains.
> Please elaborate. I am missing much of your context here.

Some of this we discussed in December's "order of file concatenation"
thread.  However, this thread focuses on the Debian configuration
settings as a possible way to solve the same problem.

The general problem is that my system is now in a domain that doesn't
exist in the public internet (psg.net).  External mail needs to go to
the publicly known biostat.ucsf.edu domain.

So I, and potentially other users on this machine, and potentially other
addresses in this private domain, need to be rewritten for stuff that
goes out to the general internet.

I've cobbled together something that works, but I've done that mostly
behind the back of the debian configuration settings.  I was wondering
if there was a way to achieve the same effect with those settings.

For those whose memories don't extend back to my original post in
October (!), here is my configuration:


# temporarily (?) allow use of unqualified iron


More information about the Pkg-exim4-users mailing list