Consolidating two replies here.
On Thursday 19 January 2006 20:09, Stephen Gran wrote:
> local_part_suffix != local_part_prefix, but both exist.
I believe local_part_prefix is what I mainly need. This plus the example
shown in 46.7 should give me enough information to build a suitable redirect
router. I missed this earlier because I didn't click on the [2] link after
local_part:suffix link in the Exim html docs.
> Hence the local_part_{pre,suf}fix_optional bit. The address will just
> match back to whatever is before the -, so tom-foo will be tom, but so
> will tom.
Cool. I believe this answers my question.
Thank you very, very much, Stephen.
On Thursday 19 January 2006 20:53, Bill Hacker wrote:
> Not pushing SQL as the answer, there has to be a 'lighter' alternative,
> but seems to me that what you want in PostgreSQL-speak is:
>
> where <the DB field name> like 'local_part_prefix%' or <the DB field
> name> = 'local_part'
>
> - 'coz what is important will be seen either as the local_part or the
> local_part_prefix. The suffix is either missing or 'don't care'.
This is cool and it also shows the same commonality -- here again
local_part_prefix is needed before the lookup. With this piece solved, the
ldap lookup can also be done, using a lookup for
mailLocalAddress=$local_part_prefix* which can be used to make a match.
> Now the above sample is bass-ackwards even for PG, and neither properly
> escaped nor correct lsearch/exim sytax, but the concept, I think, is to
> find *either* an exact match *or* a partial match with anything
> following it.
That's fine -- I wasn't looking for an exact solution spelled out. I was
stuck at a particular point and wanted the right solution and knew I needed
help.
Tony, Giuliano, John, Stephan, Bill -- thanks to all of you for your help
and your time.
- Chris
--
Chris Knadle
Chris.Knadle@???
