[vchkpw] digascii and auth fail

2003-10-13 Thread ParkerArts Admin
Anyone...

I'm using an qmail-smtp auth patch (auth-jms1.3.patch) and  
vpopmail-5.3.28.
I can pop3 authorize just fine. but a test of smtp auth produces the  
following:

--
[EMAIL PROTECTED]:etc # telnet 127.0.0.1 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 mydomain.com ESMTP
auth login
334 VXNlcm5hbWU6
my base64 user account on the form [EMAIL PROTECTED]
334 UGFzc3dvcmQ6
my base64 passwd
vchkpw: smtp auth
digascii: 9c816a55b58cd6a6c0bd7f746939008c, response: 235 ok, go ahead  
(#2.0.0)

502 unimplemented (#5.5.1)
quit
221 mydomain.com
Connection closed by foreign host.
 

The server is OSX. Apparently the digascii text causes my email client  
to assume failure on the os even though success is indicated. The SMTP  
log states success. A grep of digascii shows it is in the vchkpw.c  
file.
Any ideas or pointers on how to deal with this?

Interestingly I have another installation with the same patch and  
vpopmail version on FreeBSD that produces this correct output  
(abbreviated):

my base64 passwd
vchkpw: smtp auth
235 ok, go ahead (#2.0.0)

However if I cause an auth failure on the same server it produces  
digascii text while failing:
...
vchkpw: smtp auth
digascii: 3a459a2f3843b4d2d670bc93a2bd2956, response: 535 authorization  
failed (#5.7.0)
...

TIA
-jason
Jason Parker




Re: [vchkpw] digascii and auth fail

2003-10-13 Thread Tom Collins
On Monday, October 13, 2003, at 08:00  PM, ParkerArts Admin wrote:
Anyone...

I'm using an qmail-smtp auth patch (auth-jms1.3.patch) and  
vpopmail-5.3.28.
I can pop3 authorize just fine. but a test of smtp auth produces the  
following:

--
[EMAIL PROTECTED]:etc # telnet 127.0.0.1 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 mydomain.com ESMTP
auth login
334 VXNlcm5hbWU6
my base64 user account on the form [EMAIL PROTECTED]
334 UGFzc3dvcmQ6
my base64 passwd
vchkpw: smtp auth
digascii: 9c816a55b58cd6a6c0bd7f746939008c, response: 235 ok, go ahead  
(#2.0.0)

502 unimplemented (#5.5.1)
quit
221 mydomain.com
Connection closed by foreign host.
--- 
-
The current CVS version (to be released as 5.3.29) does not dump the  
vchkpw: smtp auth and digascii... lines to the SMTP session, which  
should take care of the problem.  The CVS version also does a better  
job of figuring out that it's a SMTP session when running on a  
non-standard port.

You can either pull the latest vchkpw from the CVS repository on  
SourceForge, or just comment out those two printfs in the source and  
rebuild vchkpw.

Give it a shot, and let us all know how it turns out.

--
Tom Collins  -  [EMAIL PROTECTED]
Note: The Tom Logic offices will be closed October 23 to November 18.
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



Re: [vchkpw] digascii and auth fail

2003-10-13 Thread ParkerArts Admin
Thanks Tom.

Commenting out the printf (only one) seems to have done the trick.

I'm still at a loss why on the other installation there was not the  
digascii text unless an actual auth fail occured...

Anyway, thanks again...
-jason
On Monday, October 13, 2003, at 10:41 PM, Tom Collins wrote:

On Monday, October 13, 2003, at 08:00  PM, ParkerArts Admin wrote:
Anyone...

I'm using an qmail-smtp auth patch (auth-jms1.3.patch) and  
vpopmail-5.3.28.
I can pop3 authorize just fine. but a test of smtp auth produces the  
following:

--
[EMAIL PROTECTED]:etc # telnet 127.0.0.1 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 mydomain.com ESMTP
auth login
334 VXNlcm5hbWU6
my base64 user account on the form [EMAIL PROTECTED]
334 UGFzc3dvcmQ6
my base64 passwd
vchkpw: smtp auth
digascii: 9c816a55b58cd6a6c0bd7f746939008c, response: 235 ok, go  
ahead (#2.0.0)

502 unimplemented (#5.5.1)
quit
221 mydomain.com
Connection closed by foreign host.
-- 
--
The current CVS version (to be released as 5.3.29) does not dump the  
vchkpw: smtp auth and digascii... lines to the SMTP session, which  
should take care of the problem.  The CVS version also does a better  
job of figuring out that it's a SMTP session when running on a  
non-standard port.

You can either pull the latest vchkpw from the CVS repository on  
SourceForge, or just comment out those two printfs in the source and  
rebuild vchkpw.

Give it a shot, and let us all know how it turns out.

--
Tom Collins  -  [EMAIL PROTECTED]
Note: The Tom Logic offices will be closed October 23 to November 18.
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail:  
http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/