[vchkpw] vpopmail MD5 vs squid MD5
I have an RH9 with qmail 1.03, vpopmail 5.3.30, qmailadmin 1.0.29,
openldap 2.0.27, squid 2.5STABLE3-0 and LDAP Browser/Editor 2.8.2
I've managed to connect both vpopmail and squid to openldap. Both can
authenticate the users okay. The problem raises when I tried to
authenticate vpopmail's user into squid.
When I browse the userlist using LDAP Browser, I find that vpopmail saves
the password in MD5 39Bytes long,
{MD5}$1$qvNMfgHF$/ZsHAjbAHPLALu/MRIj8d., while LDAP Browser saves the
password in MD5 29Bytes long, {MD5}lueSGJZetyySpUndWjMBEg==. Squid can
read the 29Bytes long one, not the 39Bytes long one. Thus vpopmail users
can't authenticate themselves in squid.
Does anybody know how can I synch those two different MD5 password
length?
Thanks,
toblo
[vchkpw] qmail queue
Hi list,
I notice that i have a huge queue.
/service/qmail-send: up (pid 1520) 2907232 seconds
/service/qmail-send/log: up (pid 1524) 2907232 seconds
/service/qmail-smtpd: up (pid 1519) 2907232 seconds
/service/qmail-smtpd/log: up (pid 1526) 2907231 seconds
messages in queue: 560
messages in queue but not yet preprocessed: 0
Going through the queue, i notice that almost all of the mails in the the
queue are junk mails sent out to invalid mailboxes.
I had checked the /var/log/qmail/current
@40003ff925b10cd28244 delivery 194018: deferral:
Sorry,_no_mailbox_here_by_that_name._vpopmail_(#5.1.1)/maildrop:_error_writi
ng_to_mailbox./maildrop:_signal_0x19/
@40003ff925b10cd2a56c status: local 5/10 remote 0/20
@40003ff925bb0ce070ac delivery 194019: deferral:
Sorry,_no_mailbox_here_by_that_name._vpopmail_(#5.1.1)/maildrop:_signal_0x19
/
@40003ff925bb0ce097bc status: local 4/10 remote 0/20
@40003ff925c01c45349c delivery 194020: deferral:
Sorry,_no_mailbox_here_by_that_name._vpopmail_(#5.1.1)/maildrop:_error_writi
ng_to_mailbox./maildrop:_signal_0x19/
@40003ff925c01c455bac status: local 3/10 remote 0/20
@40003ff925c216fa2de4 delivery 194021: deferral:
Sorry,_no_mailbox_here_by_that_name._vpopmail_(#5.1.1)/maildrop:_error_writi
ng_to_mailbox./maildrop:_signal_0x19/
I realised that it is the maildrop which is having the problem.
I have | preline maildrop ./.mailfilter in .qmail-default and in
.mailfilter i have
VPOP=| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
VHOME=`/home/vpopmail/bin/vuserinfo -d [EMAIL PROTECTED]
if ( $SIZE 262144 )
{
exception {
xfilter /usr/bin/spamc -f -u [EMAIL PROTECTED]
}
}
if (/^X-Spam-Flag: *YES/)
{
exception {
include $VHOME/Maildir/.mailfilter
}
exception {
to /home/vpopmail/domains/nchost.net/abuse/Maildir
}
}
else
{
exception {
include $VHOME/Maildir/.mailfilter
}
exception {
to $VPOP
exit
}
}
Can anyone tell me where my mailfilter had gone wrong and how do i clear out
the queue?
I am running qmail 1.03, vpopmail 5.3.20, spamassassin 2.55, and maildrop
1.5.3
Re: [vchkpw] Vpopmail 5.4.0-rc1 released
- Original Message - From: Tom Collins [EMAIL PROTECTED] To: vpopmail list [EMAIL PROTECTED] Sent: Sunday, January 04, 2004 3:50 AM Subject: Re: [vchkpw] Vpopmail 5.4.0-rc1 released On Jan 3, 2004, at 8:53 AM, Dean Henrichsmeyer wrote: On Fri, 2004-01-02 at 00:18, Tom Collins wrote: http://vpopmail.sf.net/ I anticipate that this release will become final/stable in the coming week. There might be a few more documentation additions/changes, but otherwise it should be solid and complete. Someone mentioned something about putting in a patch so that cram-md5 auth would work with vchkpw. I can't remember who it was but does anyone know if this has been done? Shoot. It hasn't been done. I'm visiting family for the holidays, and haven't been able to spend much time working on vpopmail. I wanted to get a release candidate out, but I forgot that that patch was in my queue. Someone (Bowe?) wrote (in a SourceForge tracker item) that it might be incompatible with one of the smtp auth patches for qmail. I know for a fact that I can't use CRAM-MD5 from Apple Mail to my server, so I don't doubt that there's a need for a patch. Yes CRAM-MD5 is typically used with SMTP-AUTH. The problem is that one of the most common qmail SMTP-AUTH patches ( http://members.elysium.pl/brush/qmail-smtpd-auth/ ) has got a bug that breaks CRAM-MD5. Here is the commend I made ( in vpopmail bug tracker 862598 ) : Looking through the changelog, I can see that CRAM-MD5 : SMTP-AUTH was added by Bill Shipp during 5.3.6, and that he : wrote the code to work with the SMTP-AUTH patch from : http://members.elysium.pl/brush/qmail-smtpd-auth/ : However according to this page : : http://www.fehcom.de/qmail/smtpauth.html, that particular : SMTP-AUTH implementatoin breaks the checkpassword : interface... But since it is the most common patch, it if we fix : the vchkpw code to make it compliant, I assume then it will : break this patch If anyone out there can test CRAM-MD5 auth, please try applying this patch to rc1 and reporting back whether it fixes the problem. Also, please report the source of your SMTP AUTH patch if known. http://www.fehcom.de/qmail/smtpauth.html Michael.
