OK, looks like I found the problem.  There was a
problem during the table creation process that I
overlooked.  Postgres chokes on the # comment
character.  It will accept C type comments /* */ and
also -- type comments.  But it has trouble parsing #. 
As a result, it never inserted the all important 
 [EMAIL PROTECTED]@__ userid and that's why
I was getting the error.

Ilja, I am running Postgres 7.3 in case you want to
make a note in bug track.  And the file is
create_tables.pgsql.  Error is at the bottom of the
file with the line that reads:
# Create the user for the delivery chain:

just right before the INSERT statement.

--- David <[EMAIL PROTECTED]> wrote:
> Curtis, thanks for the reply.  I've tried that and
> am
> still getting the error.  I actually have 2 aliases.
> 
> So my dbmail-adduser looks like this:
> 
> dbmail-adduser a [EMAIL PROTECTED] <password> 0 0
> [EMAIL PROTECTED] @somedomain.tld
> 
> Do you have any other suggestion on fixing the
> problem?  I'm using clientid of 0 by the way.  Does
> that matter?
> 
> Thanks again,
> David
> 
> 
> ----- Original Message ----- 
> From: "Curtis Maurand" <[EMAIL PROTECTED]>
> To: <dbmail@dbmail.org>
> Sent: Wednesday, February 18, 2004 10:08 AM
> Subject: Re: [Dbmail] dbmail unable to find
> recipient
> dbmail + postfix
> 
> 
> > 
> > I found that if you create a user, there needs to
> be
> at least one alias 
> > (which doesn't seem to be covered in the docs
> (what
> few of them there 
> > are.)).  So if your create an account
> [EMAIL PROTECTED] then there 
> > needs to be an alias of [EMAIL PROTECTED] as
> well.  Then the command 
> > becomes
> > 
> > dbmail-adduser a [EMAIL PROTECTED]
> <password>
> <clientid> \
> > <maxmailboxsize> [EMAIL PROTECTED]
> > 
> > Curtis
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail SpamGuard - Read only the mail you want.
> http://antispam.yahoo.com/tools
> 


__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools

Reply via email to