You are right.
The problem was easily solved by using the real dns name in the resolv.conf
file instead of the gateway address. (I used the gateway address earlier,
since that worked with the other router, but not with this one)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PR
It just don't work.
try searching for 'dbmail' no results.
--
Paul Stevens [EMAIL PROTECTED]
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands__
I'll pass it on.
Ilja
Paul J Stevens wrote:
It just don't work.
try searching for 'dbmail' no results.
On Thu, 13 May 2004 15:32:07 -0400
Will Berry <[EMAIL PROTECTED]> wrote:
> Feargal Reilly wrote:
>
> >... it's then up to the end-user as to how they use it ...
> >
>
> Since the exact format and treatment of a 'gecos' field would be defined
> by the application, I think it's best to use the cl
Feargal Reilly wrote:
I had a look last night and could not find a formal definition of it.
Common usage however indicated that most flavours of unix treat it the same. It
is a comma seperated list which takes the following order:
Full name, Office Location/Room Number, Office/Work Phone Number
Will,
I know that on PostgreSQL it will only waste one bit per row if there's
a
null in a field. I assume that MySQL does something similar. It doesn't
seem like it would that big a deal (unless MySQL is even worse than people
say).
Thanks,
Peter Darley
-Original Message-
From:
Isn't this issue moot as soon as dbmail gets proper ldap support. GECOS
field eat your heart out.
fwiw, ldap support will have my vote as top required feature as soon as
2.1 is out.
Jacques Beaudoin wrote:
Hi all
Some time i wish i could have some fields in dbmail
where i could input users
