>
> I may be wrong, but what you are fundamentally doing here is routing
> to a remote site using pop3 as a transport. So you should be able to
> accomplish what you require by using a dedicated transport and the
> domainlist router. IMHO you should only be using a director if you are
> worried about the local_part of a name. ie
>
> pop3_transport:
> driver=appendfile;
> user=mail,
> file="/var/spool/vpop/${domain}/mail"
No. This is not all that my director is doing. In my system, a customer
with a virtual mail domain can get mail either from a "virtual" pop
server, or have the mail for users in their domain individually pointed
at other addresses at other domains. Thus the need for access to the
local_name part. This, as I said, results in and alias file that has
some names pointed to other addresses and some pointed to a file path.
I can hide the path behind a web page management system, but I thought
it would be more elegant if the driver could expand the default mail
spool to deliver to from the $domain lookup, as it already has already
done the lookup.
I suppose I could use the prefix driver to route local users found in
the alias file through a pop driver like you suggested, with would then
strip the prefix off the name.
ie in the aliasfile
fred: pop-fred
Artificial Intelligence stands no chance against Natural Stupidity.
GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v
b+++ e* s-/+ n-(?) h++ f+g+ w+++ y*
