25 Mar
2013
25 Mar
'13
10:33 p.m.
I think I've corrected my regex gaff... forgot to match the rest of
the uname before the domain...
(^[a,A].*)(a)domain.com: a.mail.domain.com should do the trick I think.
Josh C
On Mon, Mar 25, 2013 at 5:23 PM, Josh Coombs <jcoombs(a)gwi.net> wrote:
I've got an existing Perdition proxy that I need
to clone, and layer
on some more complexity to.
The existing setup uses a simple regex setup to farm incoming
connections to different servers based on username.
Conf:
map_library /usr/local/lib/libperditiondb_posix_regex.so.0
inetd_mode
popmap.re
^[0-9]: num.mail.domain.com
^[a,A]: a.mail.domain.com
^[b,B]: b.mail.domain.com
etc, etc
Users login with just a username, no domain info is present in their
login. The mailservers they're directed to don't expect domain info
in the login.
What I've been asked to do on the new server is to require users to
login as user(a)domain.com and I have to bolt in support for a couple
dedicated subdomains.
My current conf:
map_library /usr/local/lib/libperditiondb_posix_regex.so.0
S remote_login
popmap.re:
(^[0-9])(a)domain.com: num.mail.domain.com
(^[a,A])(a)domain.com: a.mail.domain.com
(^[b,B])(a)domain.com: b.mail.domain.com
...
(.*)(a)subdomain1.domain.com: subdomain1.domain.com
(.*)(a)subdomain2.domain.com: subdomain2.domain.com
The subdomain entries work. The massaged load distribution regexs
from the original setup fail noting that perdition couldn't determine
a proper outbound server. Anyone have suggestions for a cleaner regex
to try?
Josh C