Thanks for the reply, that was along the lines of what I was looking for, my
main concern is that to the public (and relay testers) that I will look like
an open relay, since I do answer for anything and then do the localpart
lookup?
Just throwing out suggestions, I appreciate that small snippet, I will start
to play with this. Thanks
you wrote:
would it suffice to do an address rewrite?
\N^(.*)@(.*)$\N $1@??? STt
that'll write any address to localpart@???
you could sub the $1@??? with something like
$1@${if eq{$2}{lsearch;/path/to/localdomains/file}{prupref.com} fail }
that is HIDEOUSLY wrong in syntax, just there to illustrate a point --
if the submitted domain is in the localdomains file, replace it with
prupref.com -- otherwise fail the whole damn thing and it'll get
rejected
On Wednesday, July 16, 2003, at 10:24 AM, _Chris McKeever_ wrote:
> exim 4.2
> rh7.3
>
> I am using exim for the MTA and a web-email interface (@mail). What I
> would
> liketo do, in the simplest manner possible, is to have a catchall
> router
> that takes any domain other than the main one (prupref.com), removes
> the
> local_user and appends that to the prupref.com domain.
>
> This way, we can have someone@??? --> someone@???
>
> I have a couple concerns,
>
> - would this to relay-checkers look like an open relay?
>
> - is this just a bad idea?
>
> - does any one have a short perl/cgi script for updating/maintaing a
> database file that exim could then reference in local domains?
>
>
> The reason I thought of this, is that I rarely know about the new email
> domains, and if I can tag it into the web interface we use for account
> creation (ie make the db for exim at same time), or just do a
> catchall, that
> would be ideal.
>
> I appreciate your suggestions.
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users
> Exim details at http://www.exim.org/ ##
>
