On Thu, Jan 29, 2009 at 1:17 AM, Victor Duchovni <
victor.ducho...@morganstanley.com> wrote:

> On Thu, Jan 29, 2009 at 12:48:14AM -0500, Dave wrote:
>
> > > Ignoring regexp table syntax problems for the moment, this is a very
> > > degenerate regexp table, the input is completely ignored, and a fixed
> > > output is produced. Postfix has a *much* simpler table type for this
> case,
> > > listed in http://www.postfix.org/DATABASE_README.html#types.
> > >
> > >        smtp_generic_maps = <maptype>:<mapname>
> > >
> > > with the output of the map in question completely independent of
> > > the input.
> >
> > Yes, that is great for my purposes. Perfect! (I am already using
> > smtp_generic_maps.)
> >
> > My  current definition in main.cf is the typical one:
> >
> > smtp_generic_maps = hash:/etc/postfix/generic
> >
> > The question is what goes into the file generic? I asked before if I
> could
> > use something like this:
> > <wildcard>   m...@example.com
>
> No, not what goes in the file, but what maptype to use. The "hash"
> map type can not produce a fixed output for all possible inputs.
>
> > I understood the answer was no, and that regex was the alternative. I
> prefer
> > your suggestion. So how do I accomplish this task using generic?
>
> No not "using generic", rather using a table that returns a fixed output
> regardless of the input. The list of supported tables is still in the
> same place, and looking through it top to bottom will quickly expose
> the right table type for the job.
>

OK, let me guess... is it a static table? (I am guessing and I suppose I'll
have to spend an hour testing by trial and error to find out because you
choose not to give me a direct answer.)

What's with you guys on this list who have the answers yet are just handing
out clues one by one and making me guess about the answer over the course of
several email exchanges?  Fortunately, there are some guys on this list that
don't engage in those psychological games and I have greatly benefited from
their help and I do appreciate it!

Reply via email to