RE: [vchkpw] LDAP setup howto
I have got a quick vpopamil / mysql guide at http://www.pipeline.com.au/staff/mbowe/isp/vpopmail-mysql.htm Also I have got detailed qmail / vpopmail / mysql / qmailadmin / courierimap / squirrelmail guide at http://www.pipeline.com.au/staff/mbowe/isp/webmail-server.htm No ldap though, sorry. Michael > -Original Message- > From: Remo Mattei [mailto:[EMAIL PROTECTED]] > Sent: Friday, 6 December 2002 5:15 PM > To: [EMAIL PROTECTED] > Subject: [vchkpw] LDAP setup howto > > > Hi guys, does anyone have an howto on how to setup > vpopmail + mysql + > ldap + qmailadmin? > Thanks > > Ciao, > Remo Mattei > > >
[vchkpw] LDAP setup howto
Hi guys, does anyone have an howto on how to setup vpopmail + mysql + ldap + qmailadmin? Thanks Ciao, Remo Mattei
Re: [vchkpw] vpasswd file issues??
Yeah, recompiles without clear passwords. That extra field in the password file for clear text passwords doesn't exist in your password files. Just compile without clear text passwords and it should fix it. On Thursday, December 5, 2002, at 11:41 AM, Chris Wilson wrote: Hello, Recently i migrated from freebsd to linux (for those of you who saw the last post :)) and I upgraded vpopmail/qmailadmin as well... vpopmail from 4.9.9 to 5.2.1 qmailadmin from 0.38 to 1.0.6 I noticed, in qmailadmin it is no longer listing my accounts (under the "pop accounts" section). as well, the vpasswd file format seems to be a little different (including cleartext passwords now??). when I change the password for the account, it seems to list that account. is there something that needs to be done during the upgrade process so that my domain acconuts can be managed in the newer versions of vpopmail/qmailadmin? Thanks! Chris Wilson
Re: [vchkpw] Maildrop
Fernando Costa de Almeida wrote: Im trying to add mail filtering feature to my existent vpopmail setup: 1) vpopmail-5.2 2) sqwebmail-3.3.3 3) maildrop-1.5.0 4) qmailadmin-1.0.4 5) OpenLdap 2.0.27 But I always get this error when sending email: delivery 43: deferral: /usr/local/bin/maildrop:_Unable_to_open_mailbox./ Remember mailboxes under vpopmail are owned by the vpopmail user. Maybe you need to make the maildrop owner and/or group correspond with the vpopmail binaries' owner. Maybe setuid? -- Aj. Systems Administrator / Developer
Re: [vchkpw] Re: SMTP-AUTH, yet again...
Hi Matt: At 1:06 PM -0500 12/5/02, Matt Simerson wrote: Kit, you're reinventing the wheel! Thanks for getting in touch, but the attempt below is actually qmail with just the SMTP-AUTH patch. I figure if I can't get 1 patch working, my chances for the rest are pretty low. :} Yes, there are significant problems with simply merging together a bunch of the qmail patches. It took me quite some time to get all the patches I wanted to play nicely together. Now that it's done, feel free to use it: http://matt.simerson.net/computing/mail/toaster/. Pay particular attention to the "Install Qmail (with a few hacks)" section. IIRC, your stuff looked good when I was first setting this stuff up but I thought it was overkill for what I was doing. I'm doing more now, so maybe it's time to reevaluate that sentiment. Bill Shupp also has similar patches that I've also heard work well but are linux oriented where mine focuses on the FreeBSD platform. It wouldn't take too much effort to use my setup on Open/NetBSD but those are down the list for me, after making it work on Darwin. (Mac OS X) :) Cool. I'll look at it when I have a chance (waay too much going on right now!) & let you know if I uncover any OpenBSD-specific issues. Thanks, -Kit Matt On Thursday, December 5, 2002, at 12:23 AM, Kit Halsted wrote: Thanks for the pointers, everybody... At 11:22 PM -0500 12/3/02, Kit Halsted wrote: <...> Tried 0.31 tonight, no luck. Maybe my other patches are interfering? I'll try it at home as the only patch & see how that goes. 2.) Try to run qmail-smtpd as root. Just for testing, but this avoids "access denied" to vpasswd.cdb and therefore excludes one possible culprit. Also no luck. Urgh. Just tried again on my home box, which starts qmail/vpopmail from rc.local instead daemontools. (OpenBSD 3.1, virgin qmail 1.03 + elysium.pl 0.31 auth patch only, vpopmail 5.2.1... D'oh!, okay, vpopmail 5.3.9 now.) I'm back to square one now with relay by IP only, but it sure did fail interestingly for a while. Below is what I was trying to do, I've since reverted back to a working setup so I can send & receive. - From rc.local: /usr/local/bin/tcpserver -u 1001 -g 1000 -x /home/vpopmail/etc/tcp.smtp.cdb 0 25 \ /var/qmail/bin/qmail-smtpd yabox.kithalsted.com /home/vpopmail/bin/vchkpw /usr/b in/true \ 2>&1 | /var/qmail/bin/splogger smtpd 3 & <...> /usr/local/bin/tcpserver -u 1001 -g 1000 -H -R 0 110 \ /var/qmail/bin/qmail-popup yabox.kithalsted.com \ /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir & (Linewraps courtesy of less, the files are wrapped correctly.) - yabox# ls -al /var/qmail/bin/qmail-smtpd -rwxr-xr-x 1 vpopmail vchkpw 40960 Dec 4 20:54 /var/qmail/bin/qmail-smtpd yabox# ls -al /home/vpopmail/etc/tcp.smtp.cdb -rwxr-xr-x 1 vpopmail vchkpw 4359 Dec 4 22:09 /home/vpopmail/etc/tcp.smtp.cdb - Log entries corresponding to failed send/check from Eudora on my TiBook: yabox# tail /var/log/maillog Dec 4 23:36:51 yabox qmail: 1039063011.757314 end msg 889600 Dec 4 23:41:18 yabox qmail: 1039063278.163871 status: local 0/10 remote 0/20 Dec 4 23:41:18 yabox qmail: 1039063278.270637 new msg 889600 Dec 4 23:41:18 yabox qmail: 1039063278.270823 info msg 889600: bytes 230 from <[EMAIL PROTECTED]> qp 24677 uid 0 Dec 4 23:41:18 yabox qmail: 1039063278.328081 end msg 889600 Dec 4 23:41:36 yabox vpopmail[5686]: vchkpw-smtp: password fail [EMAIL PROTECTED]:208.36.84.242 Dec 4 23:41:36 yabox vpopmail[32015]: vchkpw-pop3: setgid 1001 failed errno 1 [EMAIL PROTECTED]:208.36.84.242 Dec 4 23:41:37 yabox vpopmail[26305]: vchkpw-pop3: setgid 1001 failed errno 1 [EMAIL PROTECTED]:208.36.84.242 Dec 4 23:41:56 yabox vpopmail[30076]: vchkpw-pop3: setgid 1001 failed errno 1 [EMAIL PROTECTED]:208.36.84.242 Dec 4 23:41:56 yabox vpopmail[18542]: vchkpw-pop3: setgid 1001 failed errno 1 [EMAIL PROTECTED]:208.36.84.242 - (Yes, uid 1001 is vpopmail & gid 1000 is vchkpw.) -Kit -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin "...qui desiderat pacem, praeparet bellum" (...if you would have peace, be prepared for war) -Flavius Vegetius Renatus -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin "...qui desiderat pacem, praeparet bellum" (...if you would have peace, be prepared for war) -Flavius Vegetius Renatus
[vchkpw] vpasswd file issues??
Hello, Recently i migrated from freebsd to linux (for those of you who saw the last post :)) and I upgraded vpopmail/qmailadmin as well... vpopmail from 4.9.9 to 5.2.1 qmailadmin from 0.38 to 1.0.6 I noticed, in qmailadmin it is no longer listing my accounts (under the "pop accounts" section). as well, the vpasswd file format seems to be a little different (including cleartext passwords now??). when I change the password for the account, it seems to list that account. is there something that needs to be done during the upgrade process so that my domain acconuts can be managed in the newer versions of vpopmail/qmailadmin? Thanks! Chris Wilson
Re: [vchkpw] Re: SMTP-AUTH, yet again...
Kit, you're reinventing the wheel! Yes, there are significant problems with simply merging together a bunch of the qmail patches. It took me quite some time to get all the patches I wanted to play nicely together. Now that it's done, feel free to use it: http://matt.simerson.net/computing/mail/toaster/. Pay particular attention to the "Install Qmail (with a few hacks)" section. Bill Shupp also has similar patches that I've also heard work well but are linux oriented where mine focuses on the FreeBSD platform. It wouldn't take too much effort to use my setup on Open/NetBSD but those are down the list for me, after making it work on Darwin. (Mac OS X) :) Matt On Thursday, December 5, 2002, at 12:23 AM, Kit Halsted wrote: Thanks for the pointers, everybody... At 11:22 PM -0500 12/3/02, Kit Halsted wrote: <...> Tried 0.31 tonight, no luck. Maybe my other patches are interfering? I'll try it at home as the only patch & see how that goes. 2.) Try to run qmail-smtpd as root. Just for testing, but this avoids "access denied" to vpasswd.cdb and therefore excludes one possible culprit. Also no luck. Urgh. Just tried again on my home box, which starts qmail/vpopmail from rc.local instead daemontools. (OpenBSD 3.1, virgin qmail 1.03 + elysium.pl 0.31 auth patch only, vpopmail 5.2.1... D'oh!, okay, vpopmail 5.3.9 now.) I'm back to square one now with relay by IP only, but it sure did fail interestingly for a while. Below is what I was trying to do, I've since reverted back to a working setup so I can send & receive. - From rc.local: /usr/local/bin/tcpserver -u 1001 -g 1000 -x /home/vpopmail/etc/tcp.smtp.cdb 0 25 \ /var/qmail/bin/qmail-smtpd yabox.kithalsted.com /home/vpopmail/bin/vchkpw /usr/b in/true \ 2>&1 | /var/qmail/bin/splogger smtpd 3 & <...> /usr/local/bin/tcpserver -u 1001 -g 1000 -H -R 0 110 \ /var/qmail/bin/qmail-popup yabox.kithalsted.com \ /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir & (Linewraps courtesy of less, the files are wrapped correctly.) - yabox# ls -al /var/qmail/bin/qmail-smtpd -rwxr-xr-x 1 vpopmail vchkpw 40960 Dec 4 20:54 /var/qmail/bin/qmail-smtpd yabox# ls -al /home/vpopmail/etc/tcp.smtp.cdb -rwxr-xr-x 1 vpopmail vchkpw 4359 Dec 4 22:09 /home/vpopmail/etc/tcp.smtp.cdb - Log entries corresponding to failed send/check from Eudora on my TiBook: yabox# tail /var/log/maillog Dec 4 23:36:51 yabox qmail: 1039063011.757314 end msg 889600 Dec 4 23:41:18 yabox qmail: 1039063278.163871 status: local 0/10 remote 0/20 Dec 4 23:41:18 yabox qmail: 1039063278.270637 new msg 889600 Dec 4 23:41:18 yabox qmail: 1039063278.270823 info msg 889600: bytes 230 from <[EMAIL PROTECTED]> qp 24677 uid 0 Dec 4 23:41:18 yabox qmail: 1039063278.328081 end msg 889600 Dec 4 23:41:36 yabox vpopmail[5686]: vchkpw-smtp: password fail [EMAIL PROTECTED]:208.36.84.242 Dec 4 23:41:36 yabox vpopmail[32015]: vchkpw-pop3: setgid 1001 failed errno 1 [EMAIL PROTECTED]:208.36.84.242 Dec 4 23:41:37 yabox vpopmail[26305]: vchkpw-pop3: setgid 1001 failed errno 1 [EMAIL PROTECTED]:208.36.84.242 Dec 4 23:41:56 yabox vpopmail[30076]: vchkpw-pop3: setgid 1001 failed errno 1 [EMAIL PROTECTED]:208.36.84.242 Dec 4 23:41:56 yabox vpopmail[18542]: vchkpw-pop3: setgid 1001 failed errno 1 [EMAIL PROTECTED]:208.36.84.242 - (Yes, uid 1001 is vpopmail & gid 1000 is vchkpw.) -Kit -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin "...qui desiderat pacem, praeparet bellum" (...if you would have peace, be prepared for war) -Flavius Vegetius Renatus
Re: [vchkpw] Hard disk replacement
On Thu, Dec 05, 2002 at 10:07:41AM -0600, Nick Lomonte wrote: > What I am planning on doing is stopping qmail, mounting the new drive, > and doing the following: > > cd /home > cp -a * /newdrive > > Does anyone see a problem with this? Is there something I'm overlooking > that would cause this to not work? Some versions of cp don't properly chown ownership on symlinks. Some versions of cp only do utime and chmod updates after entire subdir hierarchies are finished copying. Most versions of cp will leave partially copied files around if interrupted by ctrl-c. If you have gigs of data and millions of files, cp may take too long to run for your allotted window. If you can be assured that cp will run to completion in a relatively short period of time, you should be okay... but if any of the above concerns are real to you, then I'd suggest using rsync. rsync typically cannot easily handled millions of files (it does a full scan before doing any work, building a list in memory), therefore you may need to rsync domain by domain or even mailbox by mailbox for domains with thousands of mailboxes. This is usually easily managed with a list of your email boxes and little scripting. rsync has the advantage that you can spend 8 hours doing the initial copy, but then "sync" up the source and destination in minutes, thus allowing a short migration window, and you can know beforehand that your new disk has the data on it (and your inode counts and block sizes were chosen wisely). I've migrated 14gig of data off of NT and onto unix with only about 2 minutes of downtime using this method. -- Ted Deppner http://www.psyber.com/~ted/
[vchkpw] Maildrop
Hi,
Im trying to add mail filtering feature to my existent vpopmail setup:
1) vpopmail-5.2
2) sqwebmail-3.3.3
3) maildrop-1.5.0
4) qmailadmin-1.0.4
5) OpenLdap 2.0.27
But I always get this error when sending email:
delivery 43: deferral: /usr/local/bin/maildrop:_Unable_to_open_mailbox./
_
$ cat /usr/local/share/sqwebmail/maildirfilterconfig
MAILDIRFILTER=.mailfilter
MAILDIR=./Maildir
_
_
$ cat /var/vpopmail/domains/teste.com.br/.qmail-default
| /usr/local/bin/maildrop ./teste/Maildir/.mailfilter
| /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox
_
_
$ cat /var/vpopmail/domains/teste.com.br/teste/Maildir/.mailfilter
#MFMAILDROP=2
#
# DO NOT EDIT THIS FILE. This is an automatically generated filter.
MAILDIRQUOTA="1048576S"
FROM='[EMAIL PROTECTED]'
import SENDER
if ($SENDER eq "")
{
SENDER=$FROM
}
##Op:contains
##Header:
##Value:teste
##Folder:*Erro Teste
##From:
##PlainString
##Body
##Name:Teste
if ((/teste/:b))
{
echo "Erro Teste"
EXITCODE=77
exit
}
to "./Maildir/."
_
_
$ cat /etc/maildroprc
DEFAULT=./teste/Maildir
_
Ive tried a lot of options in the DEFAULT_DEF in the maildrop configure,
etc, etc etc.. but always got the error above..
Can anyone please help me?
Best Regards
___
ALMEIDA, Fernando Costa de
BSD USER BSD050945
ICQ 72293951
[vchkpw] Hard disk replacement
We're about to have to replace the HD in our mail server that contains the /home partition, which is where vpopmail resides. What I am planning on doing is stopping qmail, mounting the new drive, and doing the following: cd /home cp -a * /newdrive and then removing the old drive and remounting the new one as /home. Does anyone see a problem with this? Is there something I'm overlooking that would cause this to not work? Thanks -- Nick Lomonte Network Engineer Eonet [EMAIL PROTECTED] 409.833.1700
Re: [vchkpw] /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
No need to restart qmail. Just send the message to a box that doesn't exist and it should bounce back to you. Qmail checks for dot-qmail files before every message delivery. On Thursday, December 5, 2002, at 03:45 AM, Joeffrey Betita wrote: hi ppl all want is to bounce some email. on the instruction no. 3 on the FAQ of vpopmail. what should i do next. do i have to restart qmail to test it. how should i test it. sorry for a newbie question. /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.426 / Virus Database: 239 - Release Date: 12/2/2002
[vchkpw] /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
hi ppl all want is to bounce some email. on the instruction no. 3 on the FAQ of vpopmail. what should i do next. do i have to restart qmail to test it. how should i test it. sorry for a newbie question. /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.426 / Virus Database: 239 - Release Date: 12/2/2002
