Re: [vchkpw] SMTP Auth problem for non vpopmail users

2005-05-16 Thread Ken Jones
On Monday 16 May 2005 4:10 pm, Rainer Duffner wrote:
> Ken Jones wrote:
> > On Monday 16 May 2005 3:52 pm, Nick Gilbert wrote:
> >>Hi,
> >>
> >>I have IMAP authentication working for vpopmail and standard linux
> >>users, but I have a problem with SMTP authentication.
> >>
> >>I need SMTP authentication to work for standard linux users (I'm not
> >>worried about vpop users at all for SMTP-AUTH). I have built my box
> >>using the instructions on Shupp.org (Bill Schupp).  I understand that
> >>Bill's toaster incorporates a Qmail AUTH patch but when I try to login
> >>it doesn't work:
> >>
> >>Escape character is '^]'.
> >>220 blue.x-rm.com ESMTP
> >>ehlo localhost
> >>250-blue.x-rm.com
> >>250-STARTTLS
> >>250-PIPELINING
> >>250-8BITMIME
> >>250-SIZE 0
> >>250 AUTH LOGIN PLAIN CRAM-MD5
> >>auth login
> >>334 VXNlcm5hbWU6
> >>bmljaw==
> >>334 UGFzc3dvcmQ6
> >>
> >>535 authentication failed (#5.7.1)
> >>
> >>I also have this line in /var/log/maillog
> >>
> >>May 16 20:56:23 blue vpopmail[22654]: vchkpw-smtp: vpopmail user not
> >>found nick@:127.0.0.1
> >>
> >>..which implies that perhaps it's only looking for vpopmail users rather
> >>than /etc/passwd users.
> >>
> >>I would like it to work for /etc/passwd users only, or both vpopmail AND
> >>/etc/passwd users - whichever is easier.
> >>
> >>Can someone please give me some pointers on how I can fix this problem
> >>so that normal shell account users can authenticate.
> >
> > I think smtp auth requires a clear text password for CRAM-MD5
> > authentication to work. If so, /etc/passwd users won't be able to use
> > smtp authentication.
>
> Wasn't the other problem that qmail-smtpd needed to be run as root?

Possibly. It would need permission to access the passwd information.




Re: [vchkpw] SMTP Auth problem for non vpopmail users

2005-05-16 Thread Rainer Duffner
Ken Jones wrote:
On Monday 16 May 2005 3:52 pm, Nick Gilbert wrote:
Hi,
I have IMAP authentication working for vpopmail and standard linux
users, but I have a problem with SMTP authentication.
I need SMTP authentication to work for standard linux users (I'm not
worried about vpop users at all for SMTP-AUTH). I have built my box
using the instructions on Shupp.org (Bill Schupp).  I understand that
Bill's toaster incorporates a Qmail AUTH patch but when I try to login
it doesn't work:
Escape character is '^]'.
220 blue.x-rm.com ESMTP
ehlo localhost
250-blue.x-rm.com
250-STARTTLS
250-PIPELINING
250-8BITMIME
250-SIZE 0
250 AUTH LOGIN PLAIN CRAM-MD5
auth login
334 VXNlcm5hbWU6
bmljaw==
334 UGFzc3dvcmQ6

535 authentication failed (#5.7.1)
I also have this line in /var/log/maillog
May 16 20:56:23 blue vpopmail[22654]: vchkpw-smtp: vpopmail user not
found nick@:127.0.0.1
..which implies that perhaps it's only looking for vpopmail users rather
than /etc/passwd users.
I would like it to work for /etc/passwd users only, or both vpopmail AND
/etc/passwd users - whichever is easier.
Can someone please give me some pointers on how I can fix this problem
so that normal shell account users can authenticate.

I think smtp auth requires a clear text password for CRAM-MD5 authentication 
to work. If so, /etc/passwd users won't be able to use smtp authentication.
Wasn't the other problem that qmail-smtpd needed to be run as root?

Rainer
--
===
~ Rainer Duffner - [EMAIL PROTECTED] ~
~Unix - Linux - BSD - OpenSource - Security   ~
~  http://www.ultra-secure.de/~rainer/pubkey.pgp  ~
===


Re: [vchkpw] SMTP Auth problem for non vpopmail users

2005-05-16 Thread Ken Jones
On Monday 16 May 2005 3:52 pm, Nick Gilbert wrote:
> Hi,
>
> I have IMAP authentication working for vpopmail and standard linux
> users, but I have a problem with SMTP authentication.
>
> I need SMTP authentication to work for standard linux users (I'm not
> worried about vpop users at all for SMTP-AUTH). I have built my box
> using the instructions on Shupp.org (Bill Schupp).  I understand that
> Bill's toaster incorporates a Qmail AUTH patch but when I try to login
> it doesn't work:
>
> Escape character is '^]'.
> 220 blue.x-rm.com ESMTP
> ehlo localhost
> 250-blue.x-rm.com
> 250-STARTTLS
> 250-PIPELINING
> 250-8BITMIME
> 250-SIZE 0
> 250 AUTH LOGIN PLAIN CRAM-MD5
> auth login
> 334 VXNlcm5hbWU6
> bmljaw==
> 334 UGFzc3dvcmQ6
> 
> 535 authentication failed (#5.7.1)
>
> I also have this line in /var/log/maillog
>
> May 16 20:56:23 blue vpopmail[22654]: vchkpw-smtp: vpopmail user not
> found nick@:127.0.0.1
>
> ..which implies that perhaps it's only looking for vpopmail users rather
> than /etc/passwd users.
>
> I would like it to work for /etc/passwd users only, or both vpopmail AND
> /etc/passwd users - whichever is easier.
>
> Can someone please give me some pointers on how I can fix this problem
> so that normal shell account users can authenticate.

I think smtp auth requires a clear text password for CRAM-MD5 authentication 
to work. If so, /etc/passwd users won't be able to use smtp authentication.

Ken Jones


[vchkpw] SMTP Auth problem for non vpopmail users

2005-05-16 Thread Nick Gilbert
Hi,
I have IMAP authentication working for vpopmail and standard linux 
users, but I have a problem with SMTP authentication.

I need SMTP authentication to work for standard linux users (I'm not 
worried about vpop users at all for SMTP-AUTH). I have built my box 
using the instructions on Shupp.org (Bill Schupp).  I understand that 
Bill's toaster incorporates a Qmail AUTH patch but when I try to login 
it doesn't work:

Escape character is '^]'.
220 blue.x-rm.com ESMTP
ehlo localhost
250-blue.x-rm.com
250-STARTTLS
250-PIPELINING
250-8BITMIME
250-SIZE 0
250 AUTH LOGIN PLAIN CRAM-MD5
auth login
334 VXNlcm5hbWU6
bmljaw==
334 UGFzc3dvcmQ6

535 authentication failed (#5.7.1)
I also have this line in /var/log/maillog
May 16 20:56:23 blue vpopmail[22654]: vchkpw-smtp: vpopmail user not 
found nick@:127.0.0.1

..which implies that perhaps it's only looking for vpopmail users rather 
than /etc/passwd users.

I would like it to work for /etc/passwd users only, or both vpopmail AND 
/etc/passwd users - whichever is easier.

Can someone please give me some pointers on how I can fix this problem 
so that normal shell account users can authenticate.

Thanks,
Nick...