Re: [vchkpw] vpopmail + mysql + sqwebmail

2002-12-23 Thread Kurt Bigler
on 12/22/02 9:07 PM, Hugo Escobar [EMAIL PROTECTED] wrote:

 On Mon, 2002-12-23 at 00:17, Kurt Bigler wrote:
 on 12/22/02 5:37 PM, Hugo Escobar [EMAIL PROTECTED] wrote:
 
 
 Hi list:
 
 Sorry if this is off-topic but the sqwebmail ml-manager seems to be
 discarding message postings.
 
 This is what I have so far:
 
 Vpopmail+mysql working fine.
 
 $ telnet mymailserver 110
 
 always works for all the virtualdomains.
 
 
 When it comes to the SqWebMail part, everything compiles, installs, etc.
 but when I try to log in I get the following message:
 
 Internal error (module sqconfig.c, line 63) - contact system
 administrator
 
 I don't have the same version of sqwebmail as you, but it looks like this
 might be a problem opening the sqconfig file (whatever that is) for writing.
 The error is likely to be a failure at this point in the C code:
 
 f=fopen(p, w);
 if (!f) enomem();
 
 enomem is a macro that generates the error message you see with the file
 name and line number.  fopen is what is failing.
 
 So if you can figure out that that configuration file might be, I suppose it
 might be a permission problem with that file, the directory containing it,
 or the user/group that one of the sqwebmail applications is running under.
 
 Sorry can't look into this more right now - hoping that might give you a
 clue.
 
 
 Yes, indeed
 
 that file is one of the files that store session information related
 to the user. The name of the file is sqwebmail-ip and this is supposed
 to be created in the directory
 
 ~vpopmail/domains/virtualdomain/username/Maildir.
 
 The problem is that when the function gets called, the first parameter
 should be ~vpopmail/domains/virtualdomain/username/Maildir, but
 the function only receives ., in other words, sqwebmail is trying to
 create the file at the root directory.

You mean the code is running cd'd to / so that . is /  ?

Conceivably some code is trying to generate a pathname and uses . instead
when it gives up due to some error.

Did you try running as root temporarily just to see if that helps?

Unjustifiable hunch:  maybe a chdir is failing.  Maybe . is fine when the
current directory is set right.

 So I guess I should dig deeper
 into the source code.
 
 
 Configuration information:
 
 vpopmail-5.2.1
 mysql  Ver 11.15 Distrib 3.23.41, for redhat-linux-gnu (i386)
 sqwebmail-3.4.0.20021212
 
 relevant line in the /usr/local/share/sqwebmail/authdaemonrc:
 authmodulelist=authcustom authvchkpw
 
 authdaemond is running.
 
 Any ideas?
 
 Hugo
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 





[vchkpw] vpopmail + mysql + sqwebmail

2002-12-22 Thread Hugo Escobar

Hi list:

Sorry if this is off-topic but the sqwebmail ml-manager seems to be
discarding message postings.

This is what I have so far:

Vpopmail+mysql working fine.

$ telnet mymailserver 110

always works for all the virtualdomains.


When it comes to the SqWebMail part, everything compiles, installs, etc.
but when I try to log in I get the following message:

Internal error (module sqconfig.c, line 63) - contact system
administrator

Configuration information:

vpopmail-5.2.1
mysql  Ver 11.15 Distrib 3.23.41, for redhat-linux-gnu (i386)
sqwebmail-3.4.0.20021212

relevant line in the /usr/local/share/sqwebmail/authdaemonrc:
authmodulelist=authcustom authvchkpw

authdaemond is running.

Any ideas?

Hugo













Re: [vchkpw] vpopmail + mysql + sqwebmail

2002-12-22 Thread Hugo Escobar
On Mon, 2002-12-23 at 00:17, Kurt Bigler wrote:
 on 12/22/02 5:37 PM, Hugo Escobar [EMAIL PROTECTED] wrote:
 
  
  Hi list:
  
  Sorry if this is off-topic but the sqwebmail ml-manager seems to be
  discarding message postings.
  
  This is what I have so far:
  
  Vpopmail+mysql working fine.
  
  $ telnet mymailserver 110
  
  always works for all the virtualdomains.
  
  
  When it comes to the SqWebMail part, everything compiles, installs, etc.
  but when I try to log in I get the following message:
  
  Internal error (module sqconfig.c, line 63) - contact system
  administrator
 
 I don't have the same version of sqwebmail as you, but it looks like this
 might be a problem opening the sqconfig file (whatever that is) for writing.
 The error is likely to be a failure at this point in the C code:
 
 f=fopen(p, w);
 if (!f) enomem();
 
 enomem is a macro that generates the error message you see with the file
 name and line number.  fopen is what is failing.
 
 So if you can figure out that that configuration file might be, I suppose it
 might be a permission problem with that file, the directory containing it,
 or the user/group that one of the sqwebmail applications is running under.
 
 Sorry can't look into this more right now - hoping that might give you a
 clue.
 

Yes, indeed

that file is one of the files that store session information related
to the user. The name of the file is sqwebmail-ip and this is supposed
to be created in the directory

~vpopmail/domains/virtualdomain/username/Maildir.

The problem is that when the function gets called, the first parameter
should be ~vpopmail/domains/virtualdomain/username/Maildir, but
the function only receives ., in other words, sqwebmail is trying to
create the file at the root directory. So I guess I should dig deeper
into the source code.

  
  Configuration information:
  
  vpopmail-5.2.1
  mysql  Ver 11.15 Distrib 3.23.41, for redhat-linux-gnu (i386)
  sqwebmail-3.4.0.20021212
  
  relevant line in the /usr/local/share/sqwebmail/authdaemonrc:
  authmodulelist=authcustom authvchkpw
  
  authdaemond is running.
  
  Any ideas?
  
  Hugo
  
  
  
  
  
  
  
  
  
  
  
 
 
 






Re: [vchkpw] vpopmail + mysql + sqwebmail

2002-12-22 Thread Rick Widmer


on 12/22/02 5:37 PM, Hugo Escobar [EMAIL PROTECTED] wrote:

 authdaemond is running.

 Any ideas?


One thing comes to mind...

I did not look at your specific problem, but in everything I've seen when 
using sqwebmail with vpopmail says you should NOT use authdaemon.  I've 
seen numerous problems from people who are doing it, and always the 
solution is to re-compile sqwebmail with:

   --with-authvchkpw --without-authdaemon

Kill off the troublesome daemon, and use vchkpw authentication only.

Rick