Re: database access

From: Kelley Lingerfelt (no email)
Date: Mon Dec 01 2003 - 16:59:42 EST


This would be a correct assumption about DB's I think, someone verify this:

That any query of a db(aka MySQL or Postgres) is looking for rows to be returned,
no matter what the result, it is only concerned if the query returned any
results, if it returns an empty result set, as in nothing matched the query then
it would be considered to return false, otherwise if the query returns records,
it would be an OK or true return value.

Kelley

Kyle Dent wrote:

> On Mon, 1 Dec 2003 wrote:
>
> > I've got a question about using a database for the access table.
> >
> > The intention is to, by default, REJECT or DEFER email while using a
> > database for keeping a list of 'OK' addresses.
> >
> > Is the answer this simple:
> >
> > smtpd_helo_restrictions = postgresql:/etc/postfix/sql_access.cf... reject
> > smtpd_sender_restrictions = postgresql:/etc/postfix/sql_access.cf... reject
> >
> > and to put the 'OK' addresses into the database?
>
> Only if the question is 'How do I create an open relay?' :-) You
> cannot allow relaying based on any client-supplied info (other
> than IP address). Look into SASL authentication or one of the
> before-POP solutions. See http://www.postfix.org/docs.html.
>
> > Also, I didn't see many examples on the use of postgresql...
> > Any suggestions on how best to use postgres for the database?
>
> Works the same as MySQL if those examples help.
>
> Kyle








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD