[vchkpw] Vpopmail 5.4.3 released
http://vpopmail.sf.net/ This release contains a few minor bugfixes. We have started the 5.5.0 development series for large scale changes (rewriting the db modules, adding SpamAssassin support, making libvpopmail a shared library, etc.) Tom Collins - Add missing link libs (m, nsl, socket) on Solaris installs. - Fix vsetuserquota() to write properly formatted quota to maildirsize file. - Update vdominfo to ignore non-domains in users/assign. - Update vconvert and dotqmail2valias to ignore non-domains in users/assign.
[vchkpw] Vpopmail 5.5.0 released
http://vpopmail.sf.net/ This is the start of the new development series, and will include significant changes from the 5.4 series. Many people got comfortable using development releases on production servers during the 5.3 series. We don't recommend doing that with this series as the releases won't be thoroughly tested. This first release focuses on security-related improvements to the SQL auth modules. There are also some fixes to Postgres in an attempt to add stability and get it caught up with MySQL. The new qnprintf() command escapes strings used in queries to avoid possible SQL exploits to the vpopmail codebase. Once tested, we will backport this code to the 5.4 series. ChangeLog: Tom Collins - Consolidate table creation code in vmysql.c and vpgsql.c. - Increase SQL_BUF_SIZE from 600 to 2048 for Oracle, Postgres and Sybase. - Add qnprintf() to vpopmail.c for escaping strings in SQL queries. - Use qnprintf() when building queries in vmysql.c, vpgsql.c, voracle.pc, and vsybase.c. - Multiple fixes to vpgsql.c related to freeing PGresults and attempting to access NULL PGresults when reporting errors.
RE: [vchkpw] Using qmail-smtp-auth with vchkpw
Kit Halsted wrote: > At 3:36 PM + 3/10/04, Roger Lipscombe wrote: >> Now, I've fixed it by making vchkpw setuid/setgid, as follows: >> >> My question: is this the right thing to do? > > I don't think so. > >> Is there a better way to do this? > > AFAIK, you must run qmail-smtpd as the vpopmail user, see below for > what works for me. I've changed it to do this, and it works fine now. Thanks! Regards, Roger.
[vchkpw] qmail install script 1.3.7-rc5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, A new version of my installing's script for qmail are released (1.3.7-rc5). More bugfix are cleaned :) All feedback are welcome please ... http://www.linuxpourtous.com/download/qmail/releases/ install_qmail-1.3.7-rc5.tar.gz http://www.linuxpourtous.com/download/qmail/CHANGELOG http://www.linuxpourtous.com/download/qmail/README Changelog since 1.3.7-rc4 * Versions of softwares sources updated * Change qqtools's installation to Mail Toaster's installation * Added MySQL's values in debian and suse .values files * Added suse90 value for $DISTRIB * Minor changes in ezmlm's installation * Minor changes in ucspi's installation * Minor changes in maildrop's installation Thanks to marcello : http://www.linuxpourtous.com/forum/ viewtopic.php?t=21&highlight= Regards - -- Franck http://www.linuxpourtous.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAUErM1zwfep5k9qERAgiWAKCzRn6/zTn3HMLkiku5Tr1uFcFrKACeKied 8osIK9LqeFudOPgE18Dnq9Q= =B14x -END PGP SIGNATURE-
[vchkpw] SMTP AUTH vpopmail mysql qmail
Hi all. I have installed a box with qmail, vpopmail, courier imap and mysql. Things run smoothly except I don't know how to get the SMTP AUTH to work. I want the auth-check to be done from the mysql db I use with vpopmail. I assume this has been discussed before on the list and I hope someone may be able to guide me in the right direction. Regards Stefan G
Re: [vchkpw] vuserinfo quotas delay
Alex Borges wrote: I have a vpopmail+qmail Vpopmail has been upgraded to 5.2.1 and well... i send a large email to an account and it gets there fine...BUT vuserinfo does not report the usage increase correctly i assume some quota file is corrupt or something... What can i do to fix this? A lot of issues were fixed in 5.2.2 or, even in 5.4.3 (Which is the new stable, 5.5.0 is the new development.). You could try those. If anything, just go to the users Maildir, and delete the quota file, and recreate it with vusermod, or whatever that one tool is called (I am at school, sorry). X-Istence
Re: [vchkpw] Vpopmail 5.4.3 released
Hi folks! Am Do, 2004-03-11 um 09.05 schrieb Tom Collins: > http://vpopmail.sf.net/ > > This release contains a few minor bugfixes. We have > started the 5.5.0 development series for large scale > changes (rewriting the db modules, adding SpamAssassin > support, making libvpopmail a shared library, etc.) Will I get problems with any kind of DBs if I upgrade from 5.4.2 to 5.4.3? I think I must update qmailadmin after the new 5.4.3, too. Is it right? Viele Gruesse, Peter. -- [EMAIL PROTECTED], gpg -key http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x690A1AC2
Re: [vchkpw] Vpopmail 5.4.3 released
On Mar 11, 2004, at 1:42 PM, [EMAIL PROTECTED] wrote: Will I get problems with any kind of DBs if I upgrade from 5.4.2 to 5.4.3? You shouldn't, as there weren't any changes to that code. I think I must update qmailadmin after the new 5.4.3, too. Is it right? Correct. -- Tom Collins - [EMAIL PROTECTED] 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.4.3 released
Thank you very much, for that fast answer and your time. Am Do, 2004-03-11 um 21.56 schrieb Tom Collins: > On Mar 11, 2004, at 1:42 PM, [EMAIL PROTECTED] wrote: > > Will I get problems with any kind of DBs if I upgrade from > > 5.4.2 to 5.4.3? > > You shouldn't, as there weren't any changes to that code. > > > I think I must update qmailadmin after the new 5.4.3, too. > > Is it right? > > Correct. > > -- > Tom Collins - [EMAIL PROTECTED] > QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ > Info on the Sniffter hand-held Network Tester: http://sniffter.com/ -- [EMAIL PROTECTED], gpg -key http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x690A1AC2
[vchkpw] Vpopmail shared library patch
I've uploaded a patch to the sourceforge project which applies to 5.4.(2|3) and 5.5.0 which adds a configure option --enable-shared-library and its corollary --disable-shared-library. The default is for this to be on, and it causes a libvpopmail.so to be built and linked against for the vpopmail binaries. For the vpopmail binaries this isn't such a big deal, but for anything linking against vpopmail which doesn't force static linking this can save a lot of work down the road. I saw in Tom's plans for 5.5.x that he wants this included down the road. I've done some testing with no glitches so far and am planning on putting it in my production environment (about 80K accounts) in the future, so I have some confidence in this, but in the end this is still beta at best. Its all makefile modifications, so it should be quite safe. The only caveat is that right now you must run autoconf then aclocal then automake. Please let me know if people have issues with it, however I'm not the worlds greatest autoconf/automake person, so its very possible I won't be able to help. Hope folks enjoy it, Nick Harring Webley Systems
Re: [vchkpw] Vpopmail shared library patch
On Mar 11, 2004, at 3:06 PM, Nick Harring wrote: I've uploaded a patch to the sourceforge project which applies to 5.4.(2|3) and 5.5.0 which adds a configure option --enable-shared-library and its corollary --disable-shared-library. The default is for this to be on, and it causes a libvpopmail.so to be built and linked against for the vpopmail binaries. For the vpopmail binaries this isn't such a big deal, but for anything linking against vpopmail which doesn't force static linking this can save a lot of work down the road. I saw in Tom's plans for 5.5.x that he wants this included down the road. I've done some testing with no glitches so far and am planning on putting it in my production environment (about 80K accounts) in the future, so I have some confidence in this, but in the end this is still beta at best. Its all makefile modifications, so it should be quite safe. The only caveat is that right now you must run autoconf then aclocal then automake. Please let me know if people have issues with it, however I'm not the worlds greatest autoconf/automake person, so its very possible I won't be able to help. I have done some work with Nick's original patch, and plan to roll it into 5.5.1. I wanted to release 5.5.0 without the patch, and have the 5.5.1 release focused solely on the shared library patch. This should make it easy to back out of certain features further down the road. I'm not sure that there's a need to disable the shared library option -- I'd like to always build it. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] Vpopmail shared library patch
On Thursday 11 March 2004 4:22 pm, Tom Collins wrote: > On Mar 11, 2004, at 3:06 PM, Nick Harring wrote: > > I've uploaded a patch to the sourceforge project which applies to > > 5.4.(2|3) and 5.5.0 which adds a configure option > > --enable-shared-library and its corollary --disable-shared-library. The > > default is for this to be on, and it causes a libvpopmail.so to be > > built > > and linked against for the vpopmail binaries. For the vpopmail binaries > > this isn't such a big deal, but for anything linking against vpopmail > > which doesn't force static linking this can save a lot of work down the > > road. > > I saw in Tom's plans for 5.5.x that he wants this included down the > > road. I've done some testing with no glitches so far and am planning on > > putting it in my production environment (about 80K accounts) in the > > future, so I have some confidence in this, but in the end this is still > > beta at best. Its all makefile modifications, so it should be quite > > safe. > > > > The only caveat is that right now you must run autoconf then aclocal > > then automake. > > Please let me know if people have issues with it, however I'm not the > > worlds greatest autoconf/automake person, so its very possible I won't > > be able to help. > > I have done some work with Nick's original patch, and plan to roll it > into 5.5.1. I wanted to release 5.5.0 without the patch, and have the > 5.5.1 release focused solely on the shared library patch. This should > make it easy to back out of certain features further down the road. > > I'm not sure that there's a need to disable the shared library option > -- I'd like to always build it. I'd like to be able to disable shared libraries. I like not having run time linking each time vchkpw and vdelivermail are run. I'd rather link once at compile time. Makes it just-a-bit-more efficent. The only thing it would save me is recompiling vpopmail dependent libraries on an update, and that's not a big deal for me. Ken Jones
Re: [vchkpw] Vpopmail shared library patch
On Thu, 11 Mar 2004, Ken Jones wrote: > On Thursday 11 March 2004 4:22 pm, Tom Collins wrote: [snip] > > I'm not sure that there's a need to disable the shared library option > > -- I'd like to always build it. > > I'd like to be able to disable shared libraries. > I like not having run time linking each time vchkpw and vdelivermail > are run. I'd rather link once at compile time. Makes it just-a-bit-more > efficent. The only thing it would save me is recompiling vpopmail dependent > libraries on an update, and that's not a big deal for me. I see where Mr. Jones is coming from and I agree. However, I also see where having a shared library could be better. (See, for instance, the recurring theme on this list of "I just recompiled vpopmail and now qmail doesn't work/users can't authenticate through courier-imap/other stuff is broken now.") Perhaps, for a 'best of both worlds' (or 'horrible compromise') idea, maybe we should have configure switches so that we can build static vchkpw and vdelivermail binaries (since these are the two most run programs under vpopmail as far as I can see) and yet still build the shared library for linking with other binaries, including vadddomain, qmailadmin, courier's authvchkpw module, etc. I think that any performance hit we might take by making vadddomain and the other binaries link against the shared library would be tolerable. Sincerely, Chris Ess System Administrator / CDTT (Certified Duct Tape Technician)
[vchkpw] hello question about vpopmail + spamassassin
Hello guys is there a way to delete specific mail that have been identified by spamassassin as spam. I do not want them to go on my mail box. Thanks, REMO
Re: [vchkpw] hello question about vpopmail + spamassassin
Good question! Does it? I have been just setting up a rule for the messages that have been marked as SPAM to go in to a "Spam Folder" or for them to be deleted. "Spam Folder" is a better option in case of false positives. TroyB MtIda On Thu, 2004-03-11 at 14:57, Remo Mattei wrote: > Hello guys is there a way to delete specific mail that have been identified > by spamassassin as spam. I do not want them to go on my mail box. Thanks, > > REMO > > >
Re: [vchkpw] hello question about vpopmail + spamassassin
On Thursday 11 March 2004 4:57 pm, Remo Mattei wrote: > Hello guys is there a way to delete specific mail that have been > identified by spamassassin as spam. I do not want them to go on my mail > box. Thanks, I've got code to merge into the 5.5 version that does it. It's based on the freebsd patch but uses the X-Spam-Flag: YES header instead of the X-Spam-Level: header, since different users could have different spam level settings. Ken Jones
RE: [vchkpw] hello question about vpopmail + spamassassin
Well yes but my server gets poll from a exchange server which I am not sure if it does have SPAM folder I use my SPAM folder since I get mail directly from the main server Thanks, again, REMO -Original Message- From: Troy Bouchard [mailto:[EMAIL PROTECTED] Sent: Thursday, March 11, 2004 4:02 PM To: [EMAIL PROTECTED] Subject: Re: [vchkpw] hello question about vpopmail + spamassassin Good question! Does it? I have been just setting up a rule for the messages that have been marked as SPAM to go in to a "Spam Folder" or for them to be deleted. "Spam Folder" is a better option in case of false positives. TroyB MtIda On Thu, 2004-03-11 at 14:57, Remo Mattei wrote: > Hello guys is there a way to delete specific mail that have been identified > by spamassassin as spam. I do not want them to go on my mail box. Thanks, > > REMO > > >
[vchkpw] Error: dir too long
Hi, I am running an email server that is running qmail and vpopmail 5.4.0 ... its running on a FreeBSD 4.9 server. Everything has been going fine for me until today. I was attempting to add a new domain to my server and I got this message: Error: dir too long The command that I entered to attempt to create this domain is this: /usr/local/vpopmail/bin/vadddomain -i 65534 -g 65534 -d /client/vs/theminnesotabuilding.com/ theminnesotabuilding.com The problem appears to be a character limit in the length of the directory that I can use with the -d option... So, my question is this: Does anyone know of a fix for this? Is there a patch that I need to get? Or is there some workaround that I can do? Or am I just SOL? Any information/advice would be greatly appreciated. Thanks, Jason Haselbauer Soundconcept.net [EMAIL PROTECTED]
Re: [vchkpw] Vpopmail shared library patch
On Thu, 2004-03-11 at 16:48, Chris Ess wrote: > On Thu, 11 Mar 2004, Ken Jones wrote: > > On Thursday 11 March 2004 4:22 pm, Tom Collins wrote: > > [snip] > > > > I'm not sure that there's a need to disable the shared library option > > > -- I'd like to always build it. > > > > I'd like to be able to disable shared libraries. > > I like not having run time linking each time vchkpw and vdelivermail > > are run. I'd rather link once at compile time. Makes it just-a-bit-more > > efficent. The only thing it would save me is recompiling vpopmail dependent > > libraries on an update, and that's not a big deal for me. > > I see where Mr. Jones is coming from and I agree. However, I also see > where having a shared library could be better. (See, for instance, the > recurring theme on this list of "I just recompiled vpopmail and now > qmail doesn't work/users can't authenticate through courier-imap/other > stuff is broken now.") > [snip] Disabling should definitely remain an option since I've both done all the work, and the bulk of the work was done by autoconf by automagically supporting --disable-foo for every --enable-foo with a case statement and some ifs. The next issue is the bugaboo of performance. Rather than shooting from the hip, I decided to do some minimal benchmarking. This is all on a pentiumIII 750Mhz with 128M of physical memory and an IDE hard disk (7200 rpm). That all said, zero swapping was done during any of the testing as this is an idle test server. I was trying to do what I could to eliminate outside influences. The vpopmail binary tested was vdelivermail, as everyone I think would agree its the most frequently executed binary on a busy system. The test run was a loop of 10K vdelivermails to the same account by doing: export EXT=nick export HOME=qa.webley time for((i=0;i<1;i++)); do echo test | \ /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox; done I tested four different binaries: Everything static (including libc) [EMAIL PROTECTED] root]# ldd /var/vpopmail/bin/vdelivermail not a dynamic executable real4m59.377s user0m47.580s sys 1m13.210s Everything dynamic (using the exact patch on sf.net) real4m5.353s user1m12.150s sys 1m18.490s Out of the box vpopmail 5.4.2 (what I run in production) with dynamic libmysqlclient [EMAIL PROTECTED] root]# ldd /var/vpopmail/bin/vdelivermail libmysqlclient.so.10 => /usr/lib/mysql/libmysqlclient.so.10 libz.so.1 => /usr/lib/libz.so.1 libcrypt.so.1 => /lib/libcrypt.so.1 libc.so.6 => /lib/libc.so.6 libnsl.so.1 => /lib/libnsl.so.1 libm.so.6 => /lib/libm.so.6 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 real5m27.626s user1m6.210s sys 1m17.560s Out of the box vpopmail 5.4.2 with static libmysqlclient (done by moving the .so files out of /usr/lib/mysql so ld couldn't find them) [EMAIL PROTECTED] vpopmail-5.4.2]# ldd /var/vpopmail/bin/vdelivermail libz.so.1 => /usr/lib/libz.so.1 libcrypt.so.1 => /lib/libcrypt.so.1 libc.so.6 => /lib/libc.so.6 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 real4m59.499s user0m55.380s sys 1m15.480s Now the relocation is going to hit against user space time, rather than system. The real time is obviously limited by IO, which is something to bear in mind later. Obviously the fastest was with everything static, however it only beat out a "normal" installation by 8 seconds over 10K iterations. Close behind is a dynamic libmysqlclient 11 seconds back, and then 1 more second is lost to dynamic libvpopmail. I'm planning on doing more runs, and seeing if I can introduce some factors that'd more closely simulate a "production" environment, but obviously the cost of runtime linking is pretty small percentage wise, and the bulk of it is in libc (unsurprisingly). Another possible place to pickup performance but retain dynamic benefits is with glibc3.2 and prelinking, though the jury appears to be out in a big way based on benchmarks all over the web. Ultimately though, looking at these results (which i consider fairly average, since the contents of the message was a mere four characters), 75% of time is spent doing IO of one sort or another. We're worrying about optimizing the remaining 25% by a margin of what, 30 seconds over 10K iterations, or 0.003 seconds. My entire production cluster does roughly 500K deliveries, so I'd save 1500 seconds of cpu time. On boxes with idle times above 80% on average. Contrast this with an upgrade time of vpopmail/qmail/courier/my proprietary stuff of roughly 2 hours for each new version of vpopmail. I lose 0 productivity for that 1500 seconds of "lost" cpu time. I lose 2 hours of productivity having to upgrade all of these components on all of these servers. Obviously everyone will need to make their own choices, and I wholeheartedly support supporting --disable-shared-library, however I think its a waste of peoples time to use it. Cheers, Nick Harring
Re: [vchkpw] hello question about vpopmail + spamassassin
Hi Remo!
Am Do, 2004-03-11 um 23.57 schrieb Remo Mattei:
> Hello guys is there a way to delete specific mail that have been identified
> by spamassassin as spam. I do not want them to go on my mail box. Thanks,
>
> REMO
>
Is this want you want?:
vi /etc/mailfiler
import EXT
import HOST
VHOME=`/home/vpopmail/bin/vuserinfo -d [EMAIL PROTECTED]
if (/^X-Spam-Status: *Yes/)
{
exception {
to "/dev/null/"
}
}
else
{
exception {
to "$VHOME/Maildir/"
}
}
You can enable maildrop somewhere in qmailadmin I think.
I read a little bit about the configfile from SA.
Viele Gruesse,
Peter.
--
[EMAIL PROTECTED], gpg -key
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x690A1AC2
