RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Michael Bowe wrote: Try something simple like telnet 127.0.0.1 pop3 user [EMAIL PROTECTED] pass password I've tried with courier pop3. observe# telnet 127.0.0.1 110 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. +OK Hello there. USER [EMAIL PROTECTED] +OK Password required. PASS test +OK logged in. LIST +OK POP3 clients that break here, they violate STD53. . QUIT +OK Bye-bye. Connection closed by foreign host I couldn't donwload my emails, in /var/log/maillog I see: Jan 14 10:23:22 observe pop3d: LOGIN, [EMAIL PROTECTED], ip=[:::192.168.0.15] Jan 14 10:23:24 observe pop3d: LOGOUT, [EMAIL PROTECTED], ip=[:::192.168.0.15], top=0, retr=0 192.168.0.15 is my local ip. Is the :: problem that Tom said about clearopensmtp? Thanks Andrea
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Hi, On Wed, 2004-01-14 at 11:24, Andrea Riela wrote: Try something simple like telnet 127.0.0.1 pop3 user [EMAIL PROTECTED] pass password I've tried with courier pop3. observe# telnet 127.0.0.1 110 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. +OK Hello there. USER [EMAIL PROTECTED] +OK Password required. PASS test +OK logged in. LIST +OK POP3 clients that break here, they violate STD53. Is this an error or a warning? It does return +OK and nothing seems wrong about the output? Is there actually any mail waiting? Please double-check. /Anders
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Anders Brander wrote: +OK POP3 clients that break here, they violate STD53. Is this an error or a warning? It does return +OK and nothing seems wrong about the output? Is there actually any mail waiting? Please double-check. I don't know, in my opinion is a bug, I've never seen that with qmail-pop3d, only with courier-imap pop3 and pop3-ssl. There's probably a problem. Another thing: When I try to download the emails through courier-imap pop3, I couldn't, and in my /var/log/maillog I've something like: Jan 14 10:23:07 observe pop3d: Connection, ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGIN, [EMAIL PROTECTED], ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGOUT, [EMAIL PROTECTED], ip=[:::192.168.17.13], top=0, retr=0 Jan 14 10:23:06 observe pop3d: Connection, ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGIN, [EMAIL PROTECTED], ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGOUT, [EMAIL PROTECTED], ip=[:::192.168.17.13], top=0, retr=0 Jan 14 10:23:06 observe pop3d: Connection, ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGIN, [EMAIL PROTECTED], ip=[:::192.168.17.13] Jan 14 10:23:07 observe pop3d: LOGOUT, [EMAIL PROTECTED], ip=[:::192.168.17.13], top=0, retr=0 And so on. What's that? Thanks Andrea
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
On Wed, 2004-01-14 at 10:10, Andrea Riela wrote: Anders Brander wrote: +OK POP3 clients that break here, they violate STD53. I don't know, in my opinion is a bug, I've never seen that with qmail-pop3d, only with courier-imap pop3 and pop3-ssl. There's probably a problem. what exactly is a bug? It states clearly that POP3 clients that break here, they violate STD53 That is courier saying that. It doesn't HAVE to be there, but it can be. Another thing: When I try to download the emails through courier-imap pop3, I couldn't, and in my /var/log/maillog I've something like: Jan 14 10:23:07 observe pop3d: Connection, ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGIN, [EMAIL PROTECTED], ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGOUT, [EMAIL PROTECTED], ip=[:::192.168.17.13], top=0, retr=0 Jan 14 10:23:06 observe pop3d: Connection, ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGIN, [EMAIL PROTECTED], ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGOUT, [EMAIL PROTECTED], ip=[:::192.168.17.13], top=0, retr=0 Jan 14 10:23:06 observe pop3d: Connection, ip=[:::192.168.17.13] Jan 14 10:23:06 observe pop3d: LOGIN, [EMAIL PROTECTED], ip=[:::192.168.17.13] Jan 14 10:23:07 observe pop3d: LOGOUT, [EMAIL PROTECTED], ip=[:::192.168.17.13], top=0, retr=0 they look like successful logins to me. You have an MUA issue, and are blaming courier for it. Try a different MUA. -Jeremy -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! . Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Jeremy Kitchen wrote: It states clearly that POP3 clients that break here, they violate STD53 That is courier saying that. It doesn't HAVE to be there, but it can be. It's a courier bug, for you? Another thing: they look like successful logins to me. You have an MUA issue, and are blaming courier for it. Try a different MUA. Wich MUA, for example? I need a pop3+ssl to connect to vpopmail for roaming through my smtp relay. I've tried with qmail-pop3d with ucspi-ssl, auth is ok, I could download my emails, but the roaming doesn't work. With courier (2.2.1) I've problems to connect to vpopmail, or (now:2.2.2.20040112) I couldn't donwload the emails (I don't know if the roaming works). Courier+relay-ctrl has a bug: an user with password wrong opens the smtp relay. Well, what I've to try? All advices are appreciates to me. Thanks Andrea
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
On Wed, 2004-01-14 at 10:28, Andrea Riela wrote: Jeremy Kitchen wrote: It states clearly that POP3 clients that break here, they violate STD53 That is courier saying that. It doesn't HAVE to be there, but it can be. It's a courier bug, for you? no, I'm asking you, what do you think is the 'bug'. Not asking about code, what is jumping out at you and indicating a bug? I didn't see anything in your report that showed anything that looked like a bug. Another thing: they look like successful logins to me. You have an MUA issue, and are blaming courier for it. Try a different MUA. Wich MUA, for example? whichever one you're having the problem with. I assume you are mailing the list because you are having a problem, am I incorrect? -Jeremy -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! . Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
I assume you are mailing the list because you are having a problem, am I incorrect? No, I'm incorrect. When I've seen +OK POP3 clients that break here, they violate STD53. I've supposed that's a bug, or that's a strange thing, a problem? Well, I couldn't donwload my emails with courier, and I'm checking my system. The :::192.168.17.13 for me is a strange thing too. But, If you say no, I agree with you. Then, where is my problem? Pop3 and pop3-ssl don't completely work. The auth is ok (thanks to Michael Bowe, for the patch), but I couldn't download the emails. Now I try with imap, but I need the pop3 service. Andrea
Re: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
On Jan 14, 2004, at 10:26 AM, Andrea Riela wrote:
The :::192.168.17.13 for me is a strange thing too. But, If you
say
no, I agree with you.
Here's the patch to fix that, currently in CVS, that will be in the
next release (which will probably be out by the end of the week).
Courier might still log that IPv6 address, but the opensmtp file will
have the correct IPv4 address.
Update of /cvsroot/vpopmail/vpopmail
In directory sc8-pr-cvs1:/tmp/cvs-serv13384
Modified Files:
vchkpw.c vpopmail.c
Log Message:
log IPv4 address instead if IPv6 address in lastlog table (and fix bug
in related get_remote_ip() code in vpopmail.c) [876019]
Index: vchkpw.c
===
RCS file: /cvsroot/vpopmail/vpopmail/vchkpw.c,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- vchkpw.c13 Jan 2004 06:09:18 - 1.10
+++ vchkpw.c13 Jan 2004 15:59:42 - 1.11
@@ -105,7 +105,7 @@
{
char *tmpstr;
- if ( (IpAddr = getenv(TCPREMOTEIP)) == NULL) IpAddr=;
+ if ( (IpAddr = get_remote_ip()) == NULL) IpAddr=;
if ( (tmpstr = getenv(TCPLOCALPORT)) == NULL) LocalPort = 110;
else LocalPort = atoi(tmpstr);
Index: vpopmail.c
===
RCS file: /cvsroot/vpopmail/vpopmail/vpopmail.c,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- vpopmail.c 13 Jan 2004 05:24:18 - 1.27
+++ vpopmail.c 13 Jan 2004 15:59:42 - 1.28
@@ -3058,7 +3058,7 @@
char *p;
ipenv = getenv(TCPREMOTEIP);
- if ((ipenv == NULL) || (strlen(ipenv) sizeof(ipaddr))) return
ipenv;
+ if ((ipenv == NULL) || (strlen(ipenv) sizeof(ipbuf))) return ipenv;
strcpy (ipbuf, ipenv);
ipaddr = ipbuf;
--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Andrea Riela wrote: Then, where is my problem? Pop3 and pop3-ssl don't completely work. The auth is ok (thanks to Michael Bowe, for the patch), but I couldn't download the emails. Sorry Jeremy, sorry Peter, I'm stupid. I need a beer :) Here, all works fine with courier-pop3. Now I check the roaming with vpopmail. The courier-pop3s, instead, doesn't work: I couldn't download the emails. After openssl s_client -connect 127.0.0.1:995, and USER (correct or not) and PASS (correct or not), the session is closed. That's normal? Thanks Andrea
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Andrea Riela wrote: 18592 authvchkpw CALL fcntl(0x3,0x3,0) 18592 authvchkpw RET fcntl -1 errno 9 Bad file descriptor Well, I've seen that MrSam has released another 2.2.2 version (20040112). In the changelog there isn't our bug, but MrSam says that This build fixes all reported bugs. I need your feedbacks. Thanks Andrea
RE: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
I should have a patch available soon Well, Michael, now it partially works. I send my test to you: observe# openssl s_client -connect 127.0.0.1:995 CONNECTED(0004) depth=0 /C=US/ST=NY/L=New York/O=Courier Mail Server/OU=Automatically-generated POP3 SSL key/CN=localhost/[EMAIL PROTECTED] cut --- +OK Hello there. USER [EMAIL PROTECTED] +OK Password required. PASS test +OK logged in. LIST +OK POP3 clients that break here, they violate STD53. . QUIT DONE observe# The auth works, I think, but I couldn't donwload my emails through the pop3-ssl service. The 'testit' test already fails! My /tmp/testit file --- pop3 login [EMAIL PROTECTED] test --- observe# /usr/local/courier-imap/libexec/authlib/authvchkpw \ /bin/sh -c 'echo $AUTHENTICATED' 3/tmp/testit AUTHFAILURE observe# ktrace /usr/local/courier-imap/libexec/authlib/authvchkpw \ /bin/sh -c 'echo $AUTHENTICATED' 3/tmp/testit AUTHFAILURE My kdump.out file: -- 20131 ktrace RET ktrace 0 20131 ktrace CALL execve(0xcfbfda27,0xcfbfd9c8,0xcfbfd9e0) 20131 ktrace NAMI /usr/local/courier-imap/libexec/authlib/authvchkpw 20131 authvchkpw EMUL native 20131 authvchkpw RET execve 0 20131 authvchkpw CALL open(0x10e5,0,0) 20131 authvchkpw NAMI /usr/libexec/ld.so 20131 authvchkpw RET open 3 20131 authvchkpw CALL read(0x3,0xcfbfd9a4,0x20) 20131 authvchkpw GIO fd 3 read 32 bytes [EMAIL PROTECTED] \0\0\0\0\0\0\0\0\0\0 \0\0\0\0\0\0\0\0\0\0\0 20131 authvchkpw RET read 32/0x20 20131 authvchkpw CALL mmap(0,0xf000,0x5,0x2,0x3,0,0,0) 20131 authvchkpw RET mmap 1073831936/0x40016000 20131 authvchkpw CALL mmap(0x40023000,0x2000,0x7,0x12,0x3,0,0xd000,0) 20131 authvchkpw RET mmap 1073885184/0x40023000 20131 authvchkpw CALL issetugid 20131 authvchkpw RET issetugid 0 20131 authvchkpw CALL __sysctl(0xcfbfd814,0x2,0x40024a08,0xcfbfd810,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL mmap(0,0x8000,0x3,0x1004,0x,0,0,0) 20131 authvchkpw RET mmap 1073893376/0x40025000 20131 authvchkpw CALL open(0x40017b74,0,0) 20131 authvchkpw NAMI /var/run/ld.so.hints 20131 authvchkpw RET open 4 20131 authvchkpw CALL fstat(0x4,0xcfbfd7bc) 20131 authvchkpw RET fstat 0 20131 authvchkpw CALL mmap(0,0x1bcb,0x1,0x4,0x4,0,0,0) 20131 authvchkpw RET mmap 1073926144/0x4002d000 20131 authvchkpw CALL open(0x4002e26e,0,0) 20131 authvchkpw NAMI /usr/lib/libm.so.1.0 20131 authvchkpw RET open 5 20131 authvchkpw CALL read(0x5,0xcfbfd89c,0x20) 20131 authvchkpw GIO fd 5 read 32 bytes [EMAIL PROTECTED] \0\0\0\0\0\0\0\0\0\0\0 20131 authvchkpw RET read 32/0x20 20131 authvchkpw CALL mmap(0,0x14000,0x5,0x4,0x5,0,0,0) 20131 authvchkpw RET mmap 1073934336/0x4002f000 20131 authvchkpw CALL mprotect(0x40042000,0x1000,0x7) 20131 authvchkpw RET mprotect 0 20131 authvchkpw CALL mmap(0x40043000,0,0x3,0x1014,0x,0,0,0) 20131 authvchkpw RET mmap 1074016256/0x40043000 20131 authvchkpw CALL close(0x5) 20131 authvchkpw RET close 0 20131 authvchkpw CALL open(0x4002e093,0,0) 20131 authvchkpw NAMI /usr/lib/libc.so.29.0 20131 authvchkpw RET open 5 20131 authvchkpw CALL read(0x5,0xcfbfd89c,0x20) 20131 authvchkpw GIO fd 5 read 32 bytes [EMAIL PROTECTED] \0\0\0\0\0\0\0\0\0\0\0 20131 authvchkpw RET read 32/0x20 20131 authvchkpw CALL mmap(0,0xbd6f0,0x5,0x4,0x5,0,0,0) 20131 authvchkpw RET mmap 1074016256/0x40043000 20131 authvchkpw CALL mprotect(0x400c9000,0x9000,0x7) 20131 authvchkpw RET mprotect 0 20131 authvchkpw CALL mmap(0x400d2000,0x2e6f0,0x3,0x1014,0x,0,0,0) 20131 authvchkpw RET mmap 1074601984/0x400d2000 20131 authvchkpw CALL close(0x5) 20131 authvchkpw RET close 0 20131 authvchkpw CALL __sysctl(0xcfbfd7c4,0x2,0x18210,0xcfbfd7c0,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL __sysctl(0xcfbfd7c4,0x2,0x18214,0xcfbfd7c0,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL __sysctl(0xcfbfd7c4,0x2,0x18218,0xcfbfd7c0,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL __sysctl(0xcfbfd7c4,0x2,0x1821c,0xcfbfd7c0,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL __sysctl(0xcfbfd7c4,0x2,0x18220,0xcfbfd7c0,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL __sysctl(0xcfbfd7c4,0x2,0x18224,0xcfbfd7c0,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL __sysctl(0xcfbfd7c4,0x2,0x18228,0xcfbfd7c0,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL __sysctl(0xcfbfd7c4,0x2,0x1822c,0xcfbfd7c0,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL munmap(0x4002d000,0x1bcb) 20131 authvchkpw RET munmap 0 20131 authvchkpw CALL close(0x4) 20131 authvchkpw RET close 0 20131 authvchkpw CALL close(0x3) 20131 authvchkpw RET close 0 20131 authvchkpw CALL __sysctl(0xcfbfd94c,0x2,0x401006e8,0xcfbfd948,0,0) 20131 authvchkpw RET __sysctl 0 20131 authvchkpw CALL readlink(0x4008a5f6,0xcfbfd8a4,0x3f)
Re: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Original Message - From: Andrea Riela [EMAIL PROTECTED] Well, Michael, now it partially works. I send my test to you: observe# openssl s_client -connect 127.0.0.1:995 CONNECTED(0004) depth=0 /C=US/ST=NY/L=New York/O=Courier Mail Server/OU=Automatically-generated POP3 SSL key/CN=localhost/[EMAIL PROTECTED] cut Please try to simplify the testing phase Rather than trying to do the most complex stuff and failing, try doing some more simple stuff 1st and work your way forward until we track down what actually isnt working. For example, Try something simple like telnet 127.0.0.1 pop3 user [EMAIL PROTECTED] pass password If that works ok, then try something like telnet 127.0.0.1 imap 1 LOGIN [EMAIL PROTECTED] password If that works, then try connecting to the server using a mail client like outlook express. Try in POP3 mode and IMAP mode etc etc Work your way forwards to determine exactly what is working and what isnt. But i have this http://www.courier-mta.org/beta/imap/courier-imap-2.2.2.20040112.tar.bz2 plus this ftp://ftp.pipeline.com.au/Uploads/courier-imap-2.2.2-vchkpw.diff.txt working on my production server here, and it seems to go fine I am only using the imap services, not pop3 though... Michael.
[vchkpw] vchkpw and courier 2.2.2 (probably a bug)
Hi folks, I've tryed to connect courier-2.2.2 with authvchkpw to the vpopmail-5.4.0-rc1, and probably I've finded a bug. MrSam has confirmed. I hope my test could help you to define the bug, and to find the solution. The thread in courier-imap ml is this: '[Courier-imap] Re: courier-2.2.2.20040110, vpopmail-5.4.0-rc1 and authentication problem' My test: # cat /tmp/testit pop3 login [EMAIL PROTECTED] test ^D # /usr/local/courier-imap/libexec/authlib/authvchkpw \ /bin/sh -c 'echo $AUTHENTICATED' 3/tmp/testit AUTHFAILURE # My ktrace (like strace): ktrace /usr/local/courier-imap/libexec/authlib/authvchkpw \ /bin/sh -c 'echo $AUTHENTICATED' 3/tmp/testit kdump -f ktrace.out kdump.out 18592 ktrace RET ktrace 0 18592 ktrace CALL execve(0xcfbfdbcf,0xcfbfdb74,0xcfbfdb8c) 18592 ktrace NAMI /usr/local/courier-imap/libexec/authlib/authvchkpw 18592 authvchkpw EMUL native 18592 authvchkpw RET execve 0 18592 authvchkpw CALL open(0x10e5,0,0) 18592 authvchkpw NAMI /usr/libexec/ld.so 18592 authvchkpw RET open 3 18592 authvchkpw CALL read(0x3,0xcfbfd8a4,0x20) 18592 authvchkpw GIO fd 3 read 32 bytes [EMAIL PROTECTED] \0\0\0\0\0\0\0\0\0\0 \0\0\0\0\0\0\0\0\0\0\0 18592 authvchkpw RET read 32/0x20 18592 authvchkpw CALL mmap(0,0xf000,0x5,0x2,0x3,0,0,0) 18592 authvchkpw RET mmap 1073831936/0x40016000 18592 authvchkpw CALL mmap(0x40023000,0x2000,0x7,0x12,0x3,0,0xd000,0) 18592 authvchkpw RET mmap 1073885184/0x40023000 18592 authvchkpw CALL issetugid 18592 authvchkpw RET issetugid 0 18592 authvchkpw CALL __sysctl(0xcfbfd714,0x2,0x40024a08,0xcfbfd710,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL mmap(0,0x8000,0x3,0x1004,0x,0,0,0) 18592 authvchkpw RET mmap 1073893376/0x40025000 18592 authvchkpw CALL open(0x40017b74,0,0) 18592 authvchkpw NAMI /var/run/ld.so.hints 18592 authvchkpw RET open 4 18592 authvchkpw CALL fstat(0x4,0xcfbfd6bc) 18592 authvchkpw RET fstat 0 18592 authvchkpw CALL mmap(0,0x1bcb,0x1,0x4,0x4,0,0,0) 18592 authvchkpw RET mmap 1073926144/0x4002d000 18592 authvchkpw CALL open(0x4002e26e,0,0) 18592 authvchkpw NAMI /usr/lib/libm.so.1.0 18592 authvchkpw RET open 5 18592 authvchkpw CALL read(0x5,0xcfbfd79c,0x20) 18592 authvchkpw GIO fd 5 read 32 bytes [EMAIL PROTECTED] \0\0\0\0\0\0\0\0\0\0\0 18592 authvchkpw RET read 32/0x20 18592 authvchkpw CALL mmap(0,0x14000,0x5,0x4,0x5,0,0,0) 18592 authvchkpw RET mmap 1073934336/0x4002f000 18592 authvchkpw CALL mprotect(0x40042000,0x1000,0x7) 18592 authvchkpw RET mprotect 0 18592 authvchkpw CALL mmap(0x40043000,0,0x3,0x1014,0x,0,0,0) 18592 authvchkpw RET mmap 1074016256/0x40043000 18592 authvchkpw CALL close(0x5) 18592 authvchkpw RET close 0 18592 authvchkpw CALL open(0x4002e093,0,0) 18592 authvchkpw NAMI /usr/lib/libc.so.29.0 18592 authvchkpw RET open 5 18592 authvchkpw CALL read(0x5,0xcfbfd79c,0x20) 18592 authvchkpw GIO fd 5 read 32 bytes [EMAIL PROTECTED] \0\0\0\0\0\0\0\0\0\0\0 18592 authvchkpw RET read 32/0x20 18592 authvchkpw CALL mmap(0,0xbd6f0,0x5,0x4,0x5,0,0,0) 18592 authvchkpw RET mmap 1074016256/0x40043000 18592 authvchkpw CALL mprotect(0x400c9000,0x9000,0x7) 18592 authvchkpw RET mprotect 0 18592 authvchkpw CALL mmap(0x400d2000,0x2e6f0,0x3,0x1014,0x,0,0,0) 18592 authvchkpw RET mmap 1074601984/0x400d2000 18592 authvchkpw CALL close(0x5) 18592 authvchkpw RET close 0 18592 authvchkpw CALL __sysctl(0xcfbfd6c4,0x2,0x18210,0xcfbfd6c0,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL __sysctl(0xcfbfd6c4,0x2,0x18214,0xcfbfd6c0,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL __sysctl(0xcfbfd6c4,0x2,0x18218,0xcfbfd6c0,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL __sysctl(0xcfbfd6c4,0x2,0x1821c,0xcfbfd6c0,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL __sysctl(0xcfbfd6c4,0x2,0x18220,0xcfbfd6c0,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL __sysctl(0xcfbfd6c4,0x2,0x18224,0xcfbfd6c0,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL __sysctl(0xcfbfd6c4,0x2,0x18228,0xcfbfd6c0,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL __sysctl(0xcfbfd6c4,0x2,0x1822c,0xcfbfd6c0,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL munmap(0x4002d000,0x1bcb) 18592 authvchkpw RET munmap 0 18592 authvchkpw CALL close(0x4) 18592 authvchkpw RET close 0 18592 authvchkpw CALL close(0x3) 18592 authvchkpw RET close 0 18592 authvchkpw CALL __sysctl(0xcfbfd84c,0x2,0x401006e8,0xcfbfd848,0,0) 18592 authvchkpw RET __sysctl 0 18592 authvchkpw CALL readlink(0x4008a5f6,0xcfbfd7a4,0x3f) 18592 authvchkpw NAMI /etc/malloc.conf 18592 authvchkpw RET readlink -1 errno 2 No such file or directory 18592 authvchkpw CALL issetugid 18592 authvchkpw RET issetugid 0 18592 authvchkpw CALL mmap(0,0x1000,0x3,0x1002,0x,0,0,0) 18592
Re: [vchkpw] vchkpw and courier 2.2.2 (probably a bug)
- Original Message - From: Andrea Riela [EMAIL PROTECTED] Subject: [vchkpw] vchkpw and courier 2.2.2 (probably a bug) Hi folks, I've tryed to connect courier-2.2.2 with authvchkpw to the vpopmail-5.4.0-rc1, and probably I've finded a bug. MrSam has confirmed. I hope my test could help you to define the bug, and to find the solution. The thread in courier-imap ml is this: '[Courier-imap] Re: courier-2.2.2.20040110, vpopmail-5.4.0-rc1 and authentication problem' I have been doing some testing against that 2.2.2 build, and I have found the bug. I should have a patch available soon Michael.
