[vchkpw] Force passwords change
Hi, I want to implement an way to force my vpopmail users change them passwords before the first time that they use it and in each 90 days. Does have a way to I manage this? Thanks for all, Adalberto.
[vchkpw] qMail + vPopMail working together better
This message is being sent to the vpopmail mailing list and the qmail mailing list I have been using qmail and vpopmail for a while now, but i am seeing some major things that should be addressed, to make the two work together better. The first being that if a user does not exist for a domain that vpopmail has, that it should drop the message immediately SMTPD level, and not send a email message, as this can cause a lot of trouble. Consider the following: Someone is sending you 100 messages an hour to a local domain that vpopmail handles, and it does not eexist. It will put the message in the queue, get vdelivermail to parse it, and then vdelivermail will create a bounce message and tell the sender that the account does not exist. The problem with this is though, that we have is that all those 100's of messages are messages with viruses. Now what we have is us bouncing back an email to an address that might not even exist, if it does exists its kinda bad for the person getting it as they will get 1000's of bounce messages, but if it does not exist, and is a qmail server as well, or Windows or whatever, it will sometimes also generate a bounce email instead of just a SMTP error code. Thus what happens now, is that we also get all the bounce messages back that the user does not exist. To the postmaster account. Making more unnecessary data transfer over the net. (Every bit counts). What i think qmail should include, is a way to have an program (Thus we do not want it hard coded, to keep it modular) to check if a users account exist, so that way you can run a program for the stock qmail to check if the unix user exists, and vpopmail can include code so that we can check the domains structure for the domain and user, and if the program exits with an error code, we drop the email at smtpd lever, thus not generating bounce messages, as the users local mail server will do that, saying that they gave up cause it did not work out. Another thing that would greatly be good to the qmail community and vpopmail, is support for auth. I know there are auth patches out there, but if it were included in the default release, it could include better support for it. Like with the qmail-pop3d its possible to choose what application to run to check the users email and account, on the stock this is check password, on the vpopmail install, this would be vchkpw. Now the current problem is that qmail AUTH patches are available freely, but they limit you if you use it with vchkpw, as you have to run qmail-smtpd and qmail-pop3d as root, to be able to authenticate with the services, or you have a problem, and you can not login. What i suggest is that somehow we make it work together, either under the same uid, and gid, or some other way. I can currently not think of any other good ways. That way we can run qmail-smtpd more secure, as i personally do not like having stuff running as root. Another feature i would like to see included with the stock qmail, but which is not really a major problem. Is qmail-imapd =). It would be great to have something like it, that works just like qmail-pop3d, and is just as fast, safe and modular. Thats all folks. J-W
[vchkpw] Re: qMail + vPopMail working together better
Eero Volotinen wrote: What i think qmail should include, is a way to have an program (Thus we do not want it hard coded, to keep it modular) to check if a users account exist, so that way you can run a program for the stock qmail to check if the unix user exists, and vpopmail can include code so that we There is vchkusr patch that works that way. -- Eero -- this message passed virusscanner at host jlug.fi -- But the problem is, would it work correctly with the qMail auth patch many are using? Is there also one available so that we can check unix users, something like checkpassword but then rahter checkuser? X-Istence
[vchkpw] Vpopmail 5.3.29 released
http://vpopmail.sf.net/ More bug fixes as we move toward a stable 5.4 release. This version includes changes to the configure and build process, so please post bug reports to the bug tracker on SourceForge if you encounter any problems with configure/build. ChangeLog: Michael Bowe - Fix formatting error in tcp.smtp.tmp.pid filename (was being created as tcp.smtptmp.pid). Tom Collins - Remove acconfig.h; update configure.in to work without it. - Update 'missing' script with version from automake 1.6. - Send errors to stderr instead of stdout (vpopmail, vchkpw). - Add support for port 587 (submission) to vchkpw. - Increase size of VchkpwLogName in vchkpw.c to eliminate a buffer overflow. - Improve seeding for rand() and random() in vpopmail.c - Add -r (random password) option to vpasswd. - Better detection of connection type in vchkpw.c. [818943] - Remove extraneous calls to mysql_store_result(). [809472] - Minor cleanup of make_user_dir() in vpopmail.c. - Don't prompt for password in `vadduser -e ...`. [822308] - Set quota to default when adding new users. [821995] - vpgsql.c vauth_getpw(): Put in_domain on the stack. [822175] - Fix vget_limits calls. [824067, 824070] - Update example for --enable-tcpserver-file in configure. [824077] - Fix loop checking on Delivered-To header. [826231] Justin Heeseman - Set pw_flags field based on pw_gid and domain limits. [795688] - Use pw_flags instead of pw_gid to check permissions. - Allow K/KB/M/MB modifiers on vmoddomlimits -Q. [821892] -- 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] Vpopmail 5.3.29 released
Tom Collins wrote: http://vpopmail.sf.net/ More bug fixes as we move toward a stable 5.4 release. This version includes changes to the configure and build process, so please post bug reports to the bug tracker on SourceForge if you encounter any problems with configure/build. Seems to be broken for me: # vadddomain test.com bla Error: (vadduser) can't read domain limits # vdominfo test.com domain: test.com uid:509 gid:511 dir:/home/vpopmail/domains/test.com users: 0 # vmoddomlimits -S test.com Failed to vget_limits # vmoddomlimits -S previously-existing-domain.com Failed to vget_limits My config: ./configure --enable-logging=y --enable-ucspi-dir=../ucspi-tcp-0.88 --enable-passwd=y --enable-tcpserver-file=/etc/tcp.smtp --enable-defaultquota=50M --enable-domainquotas=y ...back to 5.3.28. Regards Jochen
Re: [vchkpw] 110 locks up qmail+vpopmail
thanks...I will try this and let you know how it work out Martin David Bristol wrote: When this happens, try running qmailctl stat and ps aux |more . Look for any qmail services that are not running, or any readproctitle service errors. Also, make sure you do not have any other servers/services running on port 110 (qmailctl stop - then - nmap localhost. If anything comes up on 110, qmail will not be able to bind to that port.) I had something similar to this happening on a system for a while, but it was because the pop service kept dying (because of invalid DNS entries as near as I can tell.) On Fri, 2003-10-17 at 22:11, martin wrote: Hi - I got vpopmail up and running with qmail I created my virtual account and was able to send recieve a few emails with the accout...so life is good. However..I added my 2nd v-domain and port 110 seems to have locked up. I even attemept to telnet to 100 while in the machine and it just hange there saying "connecting to 192.168.0.12" with the escape info...and that is it. I rebooted the macine...and as was well for a little bit...then it has happened again. Have I messed something up? thanks, Martin
[vchkpw] Re: s/vdelivermail/maildrop/ (was Re: Vpopmail Problems)
Are there any drawbacks to replacing vdelivermail with maildrop? I need to implement a complete package consisting of: 1) vpopmail + vqadmin + qmailadmin for mailbox/domain administration 2) maildrop for delivery (but I only really need it for filtering) 3) sqwebmail 4) qmail-scanner for virus filtering and spamassassin processing In my tests, long long ago, I ended up patching vpopmail and qmailadmin in a similar fashion as below to just put a call to shell scripts for delivery. The shell scripts used maildrop for the final delivery, and they setup environment variables for quotas. Now, it appears as though a lot of that is unnecessary (thankfully!), and I have yet to actually implement anything, so I'm trying to re-grasp the whole process. Also, are there any plans for implementing the pw_maildir field in vpopmail? I was playing with maildropmysql, and I tried putting "concat(pw_dir,'/Maildir')" for the maildir_field into maildropmysql.config, but I have yet to test it (because I haven't yet replaced vdelivermail). I dream of a future in which vdelivermail contains all the necessary maildrop filtering code.. Tim Hasson wrote (at Thu, Oct 16, 2003 at 10:40:27PM -0700): > The only way I could get around this problem, is replace vdelivermail with > maildrop, for all my domains, and configure it to run in delivery mode to read > the vpopmail users from mysql database. > > I also changed qmail-start command to pipe to the deliverquota program from > courier-imap or courier-maildrop packages (compiled with quota support). This > catches locally delivered messages that could escape the quota because of > qmail-local's lack of maildirquota support (the maildir++ patch by bill shupp > didn't help either). > > change your `qmail-start ./Maildir/` in /var/qmail/rc to: > > qmail-start | /usr/local/bin/deliverquota -w 90 ./Maildir > > > > Now time for maildrop: > > # wget http://aleron.dl.sourceforge.net/sourceforge/courier/courier-imap- > 2.0.0.tar.bz2 > # export HAVE_OPEN_SMTP_RELAY=1 > # export DYNMYSQLLIBS="-L/usr/local/lib/mysql -lmysqlclient" > > ./configure --prefix=/usr/local --exec-prefix=/usr/local \ > --without-authldap --without-authshadow \ > --with-authvchkpw --without-authcram \ > --sysconfdir=/usr/local/etc/courier-imap \ > --datadir=/usr/local/share/courier-imap \ > --libexecdir=/usr/local/libexec/courier-imap \ > --enable-workarounds-for-imap-client-bugs \ > --disable-root-check --without-authdaemon > > sed 's/#undef HAVE_OPEN_SMTP_RELAY/#define HAVE_OPEN_SMTP_RELAY 1/g' \ > authlib/preauthvchkpw.c > preauthvchkpw.c.new > > mv authlib/preauthvchkpw.c authlib/preauthvchkpw.c.orig > > mv authlib/preauthvchkpw.c.new authlib/preauthvchkpw.c > > > cd maildir > make autoresponsequota.h > make mailbot.h > make maildirfilterconfig.h > make maildirsharedrc.h > make quotawarnmsg.h > cd ../authlib > make authchangepwdir.h > make sbindir.h > cd .. > > make install > > /usr/local/etc/maildropmysql.conf > - > > # hostname - host name of your ldap server > hostnamemysql.hostname.com > port3306 > databasevpopmail > dbuser vpopmail > dbpwsecret > dbtable vpopmail > > #not used now > #timeout5 > > # default_uid - default uid (number only) to use incase uidnumber attribute not > # found in users mysql entry > default_uidnumber 500 > > # default_gid - default gid (number only) to use incase gidnumber attribute not > # found in users ldap entry > default_gidnumber 500 > > # MySQL Field definitions > # > # This section allows you to specify the actual attributes you > # use in your Mysql record > # > # The example attribute mapping shown below is also the default > # mapping used by maildrop in the case that any are missing > > # UID_FIELD - MySQL attribute which contains the users name (w or w/o domain) > uid_field pw_email > > # UIDNUMBER_FIELD - MySQL attribute which contains the system uid to deliver > # mail as > uidnumber_field real_uid > > # GIDNUMBER_FIELD - MySQL attribute which contains the system gid to deliver > # mail as > gidnumber_field real_gid > > # MAILDIR_FIELD - MySQL attribute which contains the path to the users > # custom maildir > maildir_field pw_maildir > > # HOMEDIRECTORY_FIELD - MySQL attribute which contains the path to the users > # home directory > homedirectory_field pw_dir > > # QUOTA_FIELD - MySQL attribute which contains the users quota > quota_field pw_shell > > # MYSQL_DEFAULT_STATUS_FIELD - MySQL attribute which could be created in the > # MySQL entry to set whether or not the user is allowed to receive email on > # this box.. > # -- looks unused for now; but must be valid column ! (2001-11- > 03) > mailstatus_fieldpw_st
[vchkpw] SMTP_AUTH Problem
Hi, I have qmail 1.03 and vpopmail with MySQL running on a Gentoo-Box (newest ebuilds). Everything worked fine for a while, but suddenly SMTP_AUTH does not work anymore. vchkpw logs a "vchkpw: login success", but also an "error 2". As I did not find any information about error 2 after two hours of searching I ask you, if you have any hint for me, what "error 2" means. I apreciate any hint and thank you Best regards Jens Ott E-Mail: [EMAIL PROTECTED] GPG-Key: 7E27ACCF
