[vchkpw] Re: aliases
Hello martin, On Wednesday, November 13, 2002 at 5:04:39 AM you wrote: Do you :- 1) Change the username entry to /home/vpopmail/domains/domain/username Never ever. But do you have even _tried_ to read qmail documentation? $ MANPATH=/var/qmail/man man 5 dot-qmail 2) Create new .qmail-root etc. in /home/vpopmail/domains/domain/ If _ALL_ domains this qmail should receive messages for and deliver on the same machine are virtual, and there's _NO_ domain left in /var/qmail/control/locals yes. Especially if domain domain ain't in 'locals' but is setup via vpopmail _AND_ should receive mails directed to user root in this domain. On qmail.org search for the link to big qmail picture. Have a look at them, read the documentation and understand how your mail server works. -- Best regards Peter Palmreuther
[vchkpw] vchkpw mysql
Title: vchkpw mysql hello I am attempting to transfer an old qmail/webmail framework system from an old redhat 6.2 to a SuSE 8.1 system. I have successfully compiled and deployed Qmail smtp on SuSE (using inetd) and disabled the default postfix. Qmail smtp works fine and i dont have any problem with that. I have trasnfered the /home/vpopmail directory to the new system. I also copied the ezmlm binaries from one system to another and made sure that they are found in the proper paths. I installed Mysql and transfered the vpopmail db. i quadrouple checked the account rights in /etc/passwd, /etc/group and mysql. first i tried using the old qmailadmin binaries from the redhat system and faced problems connecting to mysql i installed a separte mysql client on my wks and tried to use the same account to the mysql server and didnt experience any problems but when i tried to use qmailadmin i kept getting vsql_getpw: failed select i recompiled vpopmail to make sure that the propper account credentials are there after compiling i tried ./vadddomain revere.laboratory.kom and got the following error Kilara:/adm/vpopmail-5.2.1 # ./vadddomain revere.laboratory.kom Please enter password for postmaster: enter password again: could not connect to mysql update server Access denied for user: 'vpopmail@localhost' (Using password: YES) with database could not connect to mysql update server Access denied for user: 'vpopmail@localhost' (Using password: YES) vmysql: sql error[c]: MySQL server has gone away vmysql: sql error[b]: MySQL server has gone away vmysql: sql error[3]: MySQL server has gone away vmysql: sql error[c]: MySQL server has gone away vmysql: sql error[c]: MySQL server has gone away vmysql: sql error[b]: MySQL server has gone away vmysql: sql error[3]: MySQL server has gone away vmysql: sql error[2]: MySQL server has gone away Error: Unable to chdir to vpopmail/users directory Kilara:/adm/vpopmail-5.2.1 # can anyone please help me with this?? regards Elie
[vchkpw] qmail-pop3d-maildirquota patch
I finally figured out why the quotas were not being updated when users =downloaded their messages with outlook, eudora, etc. I know I need to =patch qmail with this patch: contrib/qmail-pop3d-maildirquota.patch.What I can't figure out is how to apply this pach. Where it goes, etc.=20Any help will be greatly appreciated.Regards,Mark
RE: [vchkpw] qmail-pop3d-maildirquota patch
Go to where your qmail-1.03 source is.. if it's not anywhere, then uncompress a fresh batch from the tarball. Once you're in the directory where the source code is, copy your qmail-pop3d-maildirquota.patch file into that directory. And assuming you're using GNU patch version 2.5.4+ just go into the source dir and type: patch qmail-pop3d-maildirquota.patch That's it. Then just do a make and if it compiles w/o error do a make setup check and you're set. There are a couple other helpful patches for qmail you might want to take a look at on the qmail.org site, but that's all you really need to do to patch qmail with the pop3d patch. -Clayton -Original Message- From: Mark MacIntyre [mailto:mmacintyre;wwcnet.net] Sent: Thursday, November 14, 2002 7:40 AM To: [EMAIL PROTECTED] Subject: [vchkpw] qmail-pop3d-maildirquota patch I finally figured out why the quotas were not being updated when users = downloaded their messages with outlook, eudora, etc. I know I need to = patch qmail with this patch: contrib/qmail-pop3d-maildirquota.patch. What I can't figure out is how to apply this pach. Where it goes, etc.=20 Any help will be greatly appreciated. Regards, Mark
[vchkpw] Re: aliases
Hi martin, On Thu, 14 Nov 2002 06:27:42 -0800 (PST) martin [EMAIL PROTECTED] wrote: 1) Change the username entry to /home/vpopmail/domains/domain/username Never ever. But do you have even _tried_ to read qmail documentation? Yes, I have it printed out and have been using qmail for 5-years. To be honest: I would have guessed so. The problem is trying to understand how vpopmail is doing things. It does it the qmail way. Have you never ever noticed while reading vpopmail documentation it uses _absolutely identical_ syntax for dor-qmail files? Have you _ever_ understood what qmail uses /var/qmail/users/* for? No? Than you lied and you haven't read qmail documentation. Yes? So what makes you think there's something different in syntax? There _can't_ be a difference in syntax for files like ~vpopmail/domains/yourdomain.com/.qmail-whatever because they _are_ processed by qmail itself, not vpopmail nor any part of it. Execute the following command to educate yourself about qmail, virtual domains and dot-qmail using and handling for VDs (assuming your incarnation of 'man' respects $MANPATH): MANPATH=/var/qmail/man man qmail-users MANPATH=/var/qmail/man man dot-qmail vpopmail is there for _only_ two things: - preventing you from creating a dot-qmail file for _every_ e-mail-address you want to be handled in a virtual domain, by using the .qmail-default mechanism of qmail and having a program behind this file (vdelivermail) that looks up a database (real DB or dot-cdb file) for delivery instructions - providing a password checking tool (vchkpw) that makes use of an own and system independent user database (again: real DB or dot-cdb file) Everything else is the _pure_ qmail way. 'vadddomain' does nothing that can't be achieved by manually editing _qmail_ configuration files. 'vadduser' is only a helping tool to handle the independent user db. 'vpopmail' only let you distribute an e-mail easier to all known users, nothing that can't be done without it (albeit it's quite more comfortable this way :-)). For not being misunderstood: I _do_ appreciate development of vpopmail, the package itself and the easy interface for administer virtual domains; I'm no qmail fetishist who loves it to do everything the manual way. But I really wish people would stop trying to put to much esoteric ideas in the way vpopmail works. It simly makes great use of a equally great basic system. qmail simply is build to be easily extended, and that is what vpopmail does. Extend where necessary / useful; reuse where possible. -- Pit
Re: [vchkpw] using spamassassin....
Do you use Spamassassin in conjunction with any other software or scripts, such as qmail-scanner, etc.? Can I just run Spamassassin on its own? Brendan On Wednesday, November 13, 2002, at 02:09 PM, Rick Macdougall wrote: Hi, We use it in .qmail-default for domains that want it and set the required_hits to 30. Users can then manage required_hits, white list, black list etc via a PHP web page. Regards, Rick - Original Message - From: Brendan McAlpine [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 13, 2002 2:03 PM Subject: [vchkpw] using spamassassin Can anyone point me in the right direction for any resources regarding installing and using spamassassin with qmail? Basically I want to be able to use spamassassin on certain mailboxes and not others on the system, and be able to add the ability to use the filtering as new accounts are added. TIA Brendan
RE: [vchkpw] using spamassassin....
I run spamassassin with qmail-scanner and I LOVE THE COMBO.. Install Spamassassin And configure the local.cf and then install qmail-scanner and it will find it and Call it to check email not procmail config files or anything like that.. I love it! -John -Original Message- From: Brendan McAlpine [mailto:bmcalpine;macconnect.com] Sent: Thursday, November 14, 2002 9:51 AM To: Rick Macdougall Cc: [EMAIL PROTECTED] Subject: Re: [vchkpw] using spamassassin Do you use Spamassassin in conjunction with any other software or scripts, such as qmail-scanner, etc.? Can I just run Spamassassin on its own? Brendan On Wednesday, November 13, 2002, at 02:09 PM, Rick Macdougall wrote: Hi, We use it in .qmail-default for domains that want it and set the required_hits to 30. Users can then manage required_hits, white list, black list etc via a PHP web page. Regards, Rick - Original Message - From: Brendan McAlpine [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 13, 2002 2:03 PM Subject: [vchkpw] using spamassassin Can anyone point me in the right direction for any resources regarding installing and using spamassassin with qmail? Basically I want to be able to use spamassassin on certain mailboxes and not others on the system, and be able to add the ability to use the filtering as new accounts are added. TIA Brendan
Re: [vchkpw] using spamassassin....
Hi, I personally run it right from .qmail-default with no extra settings like qmail-scanner.pl etc. I used to run it from qmail-scanner.pl but the over head was just too much considering I do smtp forwarding for some domains, other domains didn't want it, etc etc. Right now I can configure it for each domain seperately and I remove the overhead of scanning each and every message that comes into our system. As well, running it from qmail-scanner.pl loses the ability to do per user config's. Something our users really wanted. Regards, Rick - Original Message - From: Brendan McAlpine [EMAIL PROTECTED] To: Rick Macdougall [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, November 14, 2002 12:50 PM Subject: Re: [vchkpw] using spamassassin Do you use Spamassassin in conjunction with any other software or scripts, such as qmail-scanner, etc.? Can I just run Spamassassin on its own? Brendan On Wednesday, November 13, 2002, at 02:09 PM, Rick Macdougall wrote: Hi, We use it in .qmail-default for domains that want it and set the required_hits to 30. Users can then manage required_hits, white list, black list etc via a PHP web page. Regards, Rick - Original Message - From: Brendan McAlpine [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 13, 2002 2:03 PM Subject: [vchkpw] using spamassassin Can anyone point me in the right direction for any resources regarding installing and using spamassassin with qmail? Basically I want to be able to use spamassassin on certain mailboxes and not others on the system, and be able to add the ability to use the filtering as new accounts are added. TIA Brendan
Re: [vchkpw] using spamassassin....
I do NOT want to scan each and every message that comes in. I want to set this up on a per user basis. Is it straightforward to have spamassassin scan email for an individual user rather than by domain? Brendan On Thursday, November 14, 2002, at 01:00 PM, Rick Macdougall wrote: Hi, I personally run it right from .qmail-default with no extra settings like qmail-scanner.pl etc. I used to run it from qmail-scanner.pl but the over head was just too much considering I do smtp forwarding for some domains, other domains didn't want it, etc etc. Right now I can configure it for each domain seperately and I remove the overhead of scanning each and every message that comes into our system. As well, running it from qmail-scanner.pl loses the ability to do per user config's. Something our users really wanted. Regards, Rick - Original Message - From: Brendan McAlpine [EMAIL PROTECTED] To: Rick Macdougall [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, November 14, 2002 12:50 PM Subject: Re: [vchkpw] using spamassassin Do you use Spamassassin in conjunction with any other software or scripts, such as qmail-scanner, etc.? Can I just run Spamassassin on its own? Brendan On Wednesday, November 13, 2002, at 02:09 PM, Rick Macdougall wrote: Hi, We use it in .qmail-default for domains that want it and set the required_hits to 30. Users can then manage required_hits, white list, black list etc via a PHP web page. Regards, Rick - Original Message - From: Brendan McAlpine [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 13, 2002 2:03 PM Subject: [vchkpw] using spamassassin Can anyone point me in the right direction for any resources regarding installing and using spamassassin with qmail? Basically I want to be able to use spamassassin on certain mailboxes and not others on the system, and be able to add the ability to use the filtering as new accounts are added. TIA Brendan
Re: [vchkpw] using spamassassin....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Said Rick Macdougall on Thu, Nov 14, 2002 at 01:00:57PM -0500: I personally run it right from .qmail-default with no extra settings like qmail-scanner.pl etc. I used to run it from qmail-scanner.pl but the over head was just too much considering I do smtp forwarding for some domains, other domains didn't want it, etc etc. Right now I can configure it for each domain seperately and I remove the overhead of scanning each and every message that comes into our system. As well, running it from qmail-scanner.pl loses the ability to do per user config's. Something our users really wanted. So you just do something like run 'spamc -C /path/to/conf/file' in the .qmail-default files? And you said that you have a web frontend for it? Care to share any code? ;-) - -- [!] Justin R. Miller [EMAIL PROTECTED] Encrypted email preferred (key 0xC9C40C31) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE90+ko94d6K8nEDDERAqZ1AJ91e1Xo5lxcgcOk9hFqLbaCFhOvjgCgiKjC s0z/jWNhqCz1GTbpl2FiwMg= =XuRH -END PGP SIGNATURE-
Re: [vchkpw] using spamassassin....
Hi Rick: Does this work in conjunction with qmailadmin? I thought qmailadmin overwrote the entries in qmail-default. Best Regards, Jeff Koch -- On Thu, 14 Nov 2002, Rick Macdougall wrote: Hi, I personally run it right from .qmail-default with no extra settings like qmail-scanner.pl etc. I used to run it from qmail-scanner.pl but the over head was just too much considering I do smtp forwarding for some domains, other domains didn't want it, etc etc. Right now I can configure it for each domain seperately and I remove the overhead of scanning each and every message that comes into our system. As well, running it from qmail-scanner.pl loses the ability to do per user config's. Something our users really wanted. Regards, Rick - Original Message - From: Brendan McAlpine [EMAIL PROTECTED] To: Rick Macdougall [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, November 14, 2002 12:50 PM Subject: Re: [vchkpw] using spamassassin Do you use Spamassassin in conjunction with any other software or scripts, such as qmail-scanner, etc.? Can I just run Spamassassin on its own? Brendan On Wednesday, November 13, 2002, at 02:09 PM, Rick Macdougall wrote: Hi, We use it in .qmail-default for domains that want it and set the required_hits to 30. Users can then manage required_hits, white list, black list etc via a PHP web page. Regards, Rick - Original Message - From: Brendan McAlpine [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 13, 2002 2:03 PM Subject: [vchkpw] using spamassassin Can anyone point me in the right direction for any resources regarding installing and using spamassassin with qmail? Basically I want to be able to use spamassassin on certain mailboxes and not others on the system, and be able to add the ability to use the filtering as new accounts are added. TIA Brendan
RE: [vchkpw] using spamassassin....
I would like to see this info as well... I am sure there is allways a better Way to do things so I have to check this out!! -John -Original Message- From: Justin R. Miller [mailto:incanus;codesorcery.net] Sent: Thursday, November 14, 2002 10:19 AM To: [EMAIL PROTECTED] Subject: Re: [vchkpw] using spamassassin -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Said Rick Macdougall on Thu, Nov 14, 2002 at 01:00:57PM -0500: I personally run it right from .qmail-default with no extra settings like qmail-scanner.pl etc. I used to run it from qmail-scanner.pl but the over head was just too much considering I do smtp forwarding for some domains, other domains didn't want it, etc etc. Right now I can configure it for each domain seperately and I remove the overhead of scanning each and every message that comes into our system. As well, running it from qmail-scanner.pl loses the ability to do per user config's. Something our users really wanted. So you just do something like run 'spamc -C /path/to/conf/file' in the .qmail-default files? And you said that you have a web frontend for it? Care to share any code? ;-) - -- [!] Justin R. Miller [EMAIL PROTECTED] Encrypted email preferred (key 0xC9C40C31) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE90+ko94d6K8nEDDERAqZ1AJ91e1Xo5lxcgcOk9hFqLbaCFhOvjgCgiKjC s0z/jWNhqCz1GTbpl2FiwMg= =XuRH -END PGP SIGNATURE-
Re: [vchkpw] using spamassassin....
My my, so many questions :) I'm going to answer them all in one email to reduce the noise on the list. 1 - Not easy to run it on a per user basis but you can by running it in their own .qmail file in their directory. You could do it manually, or hack qmailadmin to add the code itself to the .qmail file. 2 - No, it currently doesn't work in conjunction with qmailadmin. If the administrator of the domain changes the catch-all options it would get over written. I'll look into patching qmail to give the admin the option of adding it or someone else can. I'm kinda busy with other stuff right now, so a patch to qmailadmin is near the bottom of my list. 3 - I use spamc -F -u $EXT$HOST to call spamassassin. That makes spamd look at a MySQL database for user preferences to over ride the default. We currently set required_hits to 30 by default and allow the user to turn on better filtering if the so desire by a web page using phpsa.php. That can be found at http://www.spamassassin.org/devel/ Nothing really tricky to it. For those who wish, my exact syntax in the qmail-default file is | preline /usr/bin/spamc -f -u $EXT$HOST | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox Regards to all, Rick
Re: [vchkpw] Re: aliases
on 11/14/02 9:17 AM, Peter Palmreuther [EMAIL PROTECTED] wrote: [snip] Have you _ever_ understood what qmail uses /var/qmail/users/* for? No? Than you lied and you haven't read qmail documentation. [snip] The information in the rest of your email is very helpful. Incredibly so for me, and I thank you for it. However, do you realize how full of assumptions most explanations (e.g. helpful explanations from people who know things) and documentation are? Full of assumed knowledge and assumed points of view. So often this makes even extensive documentation almost useless for asimilating even the basics - unless you have lots of time on your hands and can study and study and study until the obvious hidden information finally dawns on you. I find that in particular information about the internet and about server software is more buried right in front of us all than any other area I have ever studied. So the bottom line is no one really needs to prove anything about how hard someone else has studied the documentation. Some of us have studied until it hurt. Others reach their threshold of pain much sooner. But let's face it, learning from documentation is often a pain. A little dialog with someone can help almost effortlessly to bring forward the implicit points of view and create seeds for the process of assimilation, so that returning to the doc can then be fruitful. Documentation writers can learn from this. And learn and learn and learn - I believe without limit. Documentation can be much better. It is hard to be without attitude, and to rid oneself of all the hidden assumptions of being involved in a particularly community of discourse. Documentation is ideally written for everybody. That is an impossible task, but it can be approached. I appreciate this list and the help it provides to supplement the inevitable limitations of documentation (limitations that are experienced very differently by different people needing to learn and get work done). I am just lobbying for the cause of relieving us all from any need to even so much as clarify what someone has failed to do in using the documentation. This would leave our helpful information totally uncolored by anything besides help, which I think would be a good step. After all there is no need to defend the documentation. Like everything it was hard work to write it, and tries to meet an impossible goal. It is good to be aware of both all the time. The best of us (and who is that anyway?) will miss the obvious often enough whether writing or reading. Thanks, Kurt Bigler
Re: [vchkpw] Re: aliases
I was having similiar problems with aliases and finally figured out that my problem was that I did not set --enable-qmail-ext=y in my initial compilation. I wasn't clear myself on exactly how aliases worked with qmail/vpopmail (and yes I read the dot-qmail and dot-users man pages -- they are well-written but asking questions to get the big picture is often helpful). Anyway I think based on my maillogs from my original installation then compared to my new installation vpopmail was simply ignoring .qmail-ext files (which makes sense if I didn't enbable it at compile time!) Curious - does anyone have an explanation of why this is disabled by deafult? I would think you would want it enabled by default but perhaps there is a reason I am unaware of. Also - vpopmail has many options that are set at compile time that would be nice to be file-based configurable - thoughts? On my original compilation i d Quoting Kurt Bigler [EMAIL PROTECTED]: on 11/14/02 9:17 AM, Peter Palmreuther [EMAIL PROTECTED] wrote: [snip] Have you _ever_ understood what qmail uses /var/qmail/users/* for? No? Than you lied and you haven't read qmail documentation. [snip] The information in the rest of your email is very helpful. Incredibly so for me, and I thank you for it. However, do you realize how full of assumptions most explanations (e.g. helpful explanations from people who know things) and documentation are? Full of assumed knowledge and assumed points of view. So often this makes even extensive documentation almost useless for asimilating even the basics - unless you have lots of time on your hands and can study and study and study until the obvious hidden information finally dawns on you. I find that in particular information about the internet and about server software is more buried right in front of us all than any other area I have ever studied. So the bottom line is no one really needs to prove anything about how hard someone else has studied the documentation. Some of us have studied until it hurt. Others reach their threshold of pain much sooner. But let's face it, learning from documentation is often a pain. A little dialog with someone can help almost effortlessly to bring forward the implicit points of view and create seeds for the process of assimilation, so that returning to the doc can then be fruitful. Documentation writers can learn from this. And learn and learn and learn - I believe without limit. Documentation can be much better. It is hard to be without attitude, and to rid oneself of all the hidden assumptions of being involved in a particularly community of discourse. Documentation is ideally written for everybody. That is an impossible task, but it can be approached. I appreciate this list and the help it provides to supplement the inevitable limitations of documentation (limitations that are experienced very differently by different people needing to learn and get work done). I am just lobbying for the cause of relieving us all from any need to even so much as clarify what someone has failed to do in using the documentation. This would leave our helpful information totally uncolored by anything besides help, which I think would be a good step. After all there is no need to defend the documentation. Like everything it was hard work to write it, and tries to meet an impossible goal. It is good to be aware of both all the time. The best of us (and who is that anyway?) will miss the obvious often enough whether writing or reading. Thanks, Kurt Bigler
Re: [vchkpw] using spamassassin....
What would be the best syntax to have in the .qmail-default file to just filter the emails for the domain through spamassassin? On Thursday, November 14, 2002, at 01:29 PM, Rick Macdougall wrote: My my, so many questions :) I'm going to answer them all in one email to reduce the noise on the list. 1 - Not easy to run it on a per user basis but you can by running it in their own .qmail file in their directory. You could do it manually, or hack qmailadmin to add the code itself to the .qmail file. 2 - No, it currently doesn't work in conjunction with qmailadmin. If the administrator of the domain changes the catch-all options it would get over written. I'll look into patching qmail to give the admin the option of adding it or someone else can. I'm kinda busy with other stuff right now, so a patch to qmailadmin is near the bottom of my list. 3 - I use spamc -F -u $EXT$HOST to call spamassassin. That makes spamd look at a MySQL database for user preferences to over ride the default. We currently set required_hits to 30 by default and allow the user to turn on better filtering if the so desire by a web page using phpsa.php. That can be found at http://www.spamassassin.org/devel/ Nothing really tricky to it. For those who wish, my exact syntax in the qmail-default file is | preline /usr/bin/spamc -f -u $EXT$HOST | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox Regards to all, Rick
