> I'm comverting our MTA service from PP to Exim and have managed
> to overcome most of the cultural differences.
>
> There's One thing I haven't quite managed to sort out -
>
> Our MTA is a hub for the entire site, and addresses are re-written
> in the form 'Initial(s).Surname@???' as they pass through
> the MTA. This worked OK in PP and is fine in Exim.
>
> A feature of our PP configuration is that addresses which do not
> exist in the tables cannot EMail out of this site. The most
> useful result of this feature is that badly formed return addresses
> are not let out of the site.
>
> With Exim, I'm not sure how to achieve the same thing - what
> I really want is for Exim to return/dump any EMail which contains
> an originator's address which cannot be rewritten.
>
> Has anyone else done this ?
>
> Any ideas gratefully received - please could you reply directly
> to me as I'm not (yet) a member of this list.
This reply may be too late to be of interest -- I have just returned from
holiday.
I wanted to do the same thing and nobody suggested anything better than
what I came up with myself. I use a pair of rewriting rules (which can be
compressed into one at the cost of much longer strings in the database):
*@*.shef.ac.uk ${lookup{$2}lsearch{/var/spool/exim/tables/rewrite_hosts}\
{$1@$2.rewrite}fail} bcfrF
*@*.rewrite ${lookup{${lc:$1}@$2}dbm{/var/spool/exim/tables/invaliases}\
{$value}{unknown@???}} bcfrF
The first checks to see whether the host is one for which rewriting is
required; if so it maps user@??? to user@???. The
second rule looks up the string user@host to find the
I.Surname@??? form but returning unknown@??? if
the lookup fails. With sender_verify set this address fails as required.
Richard
--
Richard Gilbert
Corporate Information and Computing Services
University of Sheffield, Sheffield, S10 2TN, UK
Phone: +44 114 222 3028 Fax: +44 114 222 3040