[vchkpw] More vpopmail 5.5 notes / experiences
Good morning, Consider a vpopmail 5.5 install using timestamp build 1239053335: - I noticed that domains are now created in /home/vpopmail/var/vpopmail as opposed to /home/vpopmail/domains. Is this intended as a change in 5.5 or is it incorrect, perhaps also part of the FHS patch? Or can i specify the /home/vpopmail/domains somewhere as a confiugre option? It is a bit difficult to test on production servers if we have live data in /home/vpopmail/domains unless we all move the data to a different directory, but that would not be preferable. - vadddomain correctly adds a domain in the database and creates files / directories in the above mentioned parent directory, vdeldomain correctly deletes it from the database (and the files / directories), however it also throws an error message: "Warning: Failed while attempting to delete domain from auth backend". - vlist is new to me, is this automatically packaged in 5.5 now? - vdelivermail (feautre request). At the moment we are running a modified version and have disabled 90% full checks in vdelivermail.c (around line 1139 by simply exiting the function). We do our own quota check, which with the use of the vusaged will become a lot faster. Perhaps you can include an option to disable this automatic mailing? Sincerely, - Wouter van der Schagt !DSPAM:49f6aef132681061776773!
Re: [vchkpw] to specify some mail addresses
Smtp authentication is installed in my system. How can I do that restriction? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bulend Kolay wrote: I use vpopmail-5.4.x on qmail-1.03. I have a customer who has a static ip addres. He wish me to restrict a mail adress which belongs to him to do send and receieve for all ip block except that static ip address. How can I do that ? You cannot. The best way to do what you want is to have an SMTP authentication patch installed on your system. - -- /* Matt BrookingsGnuPG Key D9414F70 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknxvgEACgkQ6QgvSNlBT3AWiwCfY6HRCdYDlrpg0wCKiU8FbURM 7uMAn3qFJRv4vw/ICfWN8TfdWH6G/4h0 =3Q/R -END PGP SIGNATURE- !DSPAM:49f6ed6e32682135319792!
[vchkpw] vpopmail valias wildcard support - every...@domain.com
Hi: In the case where a domain has, say, 100 email accounts, is there an easy way to configure a wildcard alias or mailinglist so that an email can be sent to everyone? Otherwise I can see that in a constantly changing organization it could be a lot of work to keep a mailing list or alias current. vpopbull would not work since the individual domains don't have that access. Thanks Best Regards, Jeff Koch !DSPAM:49f70f5b32681074618554!
Re: [vchkpw] vpopmail valias wildcard support - every...@domain.com
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Koch wrote: > > Hi: > > In the case where a domain has, say, 100 email accounts, is there an > easy way to configure a wildcard alias or mailinglist so that an email > can be sent to everyone? Otherwise I can see that in a constantly > changing organization it could be a lot of work to keep a mailing list > or alias current. > > vpopbull would not work since the individual domains don't have that > access. There's no current way to do this, mostly because there's no easy way to authenticate the sent mail. You wouldn't want a spammer, or an employee who shouldn't be emailing everyone, to email company-wide. You could write an email interface to vpopbull probably. One that requires a password somewhere in the email, and have it passed the message via a dotqmail file. - -- /* Matt BrookingsGnuPG Key D9414F70 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn3HgQACgkQ6QgvSNlBT3CPVgCbBIb5n9MEweccmeWYES+hoYVP KdYAnRX4ZDKclKcOuQNd+215+V+OmVnZ =QNtP -END PGP SIGNATURE-
Re: [vchkpw] More vpopmail 5.5 notes / experiences
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wouter van der Schagt wrote: > Good morning, > > Consider a vpopmail 5.5 install using timestamp build 1239053335: > > - I noticed that domains are now created in /home/vpopmail/var/vpopmail > as opposed to /home/vpopmail/domains. Is this intended as a change in > 5.5 or is it incorrect, perhaps also part of the FHS patch? Or can i > specify the /home/vpopmail/domains somewhere as a confiugre option? It > is a bit difficult to test on production servers if we have live data in > /home/vpopmail/domains unless we all move the data to a different > directory, but that would not be preferable. Are you working with the current SVN branch, or with a tarball from Sourceforge? I'm not certain all changes to the FHS-related code are on Sourceforge. > - vadddomain correctly adds a domain in the database and creates files / > directories in the above mentioned parent directory, vdeldomain > correctly deletes it from the database (and the files / directories), > however it also throws an error message: "Warning: Failed while > attempting to delete domain from auth backend". This is odd. I have not experienced this on any systems I have it installed on. What OS are you doing this on? > - vlist is new to me, is this automatically packaged in 5.5 now? Yes. It's also in the latest 5.4 release. > - vdelivermail (feautre request). At the moment we are running a > modified version and have disabled 90% full checks in vdelivermail.c > (around line 1139 by simply exiting the function). We do our own quota > check, which with the use of the vusaged will become a lot faster. > Perhaps you can include an option to disable this automatic mailing? Disable quota checking and build the vusage daemon separately. You can then use the vusage API, or the client, to perform your own checks. The vusage daemon doesn't care about vpopmail's configurations in regards to quota checking, because it doesn't do quota enforcement. It simply reports usage. - -- /* Matt BrookingsGnuPG Key D9414F70 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn3Hx0ACgkQ6QgvSNlBT3D8IwCcC0i6Vk8JRr7STOI8zGyykiUx iWYAmQGm6kzuO7H0fYahLEFjet4iBu9H =vEmh -END PGP SIGNATURE-
Re: [vchkpw] vpopmail valias wildcard support - every...@domain.com
Jeff Koch wrote: Hi: In the case where a domain has, say, 100 email accounts, is there an easy way to configure a wildcard alias or mailinglist so that an email can be sent to everyone? Otherwise I can see that in a constantly changing organization it could be a lot of work to keep a mailing list or alias current. vpopbull would not work since the individual domains don't have that access. If you use ezmlm-idx with SQL support adding and removing users from a list is easy and a simple webpage can be build in minutes. That was the path we took. Depending on how you add/remove accounts a wrapper around the vpopmail tools can add/remove users from any company maillists too. DAve -- "Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it." John Quincy Adams http://appleseedinfo.org !DSPAM:49f7225b32681242592022!
Re: [vchkpw] vpopmail valias wildcard support - every...@domain.com
Matt Brookings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Koch wrote: Hi: In the case where a domain has, say, 100 email accounts, is there an easy way to configure a wildcard alias or mailinglist so that an email can be sent to everyone? Otherwise I can see that in a constantly changing organization it could be a lot of work to keep a mailing list or alias current. vpopbull would not work since the individual domains don't have that access. There's no current way to do this, mostly because there's no easy way to authenticate the sent mail. You wouldn't want a spammer, or an employee who shouldn't be emailing everyone, to email company-wide. You could write an email interface to vpopbull probably. One that requires a password somewhere in the email, and have it passed the message via a dotqmail file. Perhaps it should be something added to vpopmaild, allowing the postmaster to send to their domain and the administrator to send to all domains. Just an idea. Rick !DSPAM:49f7238932683784218311!
Re: [vchkpw] vpopmail valias wildcard support - every...@domain.com
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rick Macdougall wrote: > Perhaps it should be something added to vpopmaild, allowing the > postmaster to send to their domain and the administrator to send to all > domains. If it's added to vpopmaild, regular users can't use it. I think it makes sense to be able to configure it so a regular user of the system can email their company without having to learn to log into vpopmaild. Maybe vpopbull should be modified to have an argument that indicates it's being passed a message via a dotqmail file, and in this mode, it will look for a password in the email (to be stripped out of course). I'll look into this. I'll probably have it link EPS and only enable this feature if EPS is found on the system. - -- /* Matt BrookingsGnuPG Key D9414F70 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn3JicACgkQ6QgvSNlBT3A/QgCdFSsLjI36yFD+z8/GSQL6Pnin 7AgAnjAZK/g3Qut9Roiv8X9s9D077mH5 =D/Pu -END PGP SIGNATURE-
Re: [vchkpw] More vpopmail 5.5 notes / experiences
Are you working with the current SVN branch, or with a tarball from Sourceforge? I'm not certain all changes to the FHS-related code are on Sourceforge. I was using the tarball, am now testing with SVN revision 891. Further testing reveals that a default ./configure returns: domains directory = /home/vpopmail/domains conf directory = /home/vpopmail/etc bin directory = /home/vpopmail/bin lib directory = /home/vpopmail/lib include directory = /home/vpopmail/include As expected, however adding "--prefix=/home/vpopmail" messes this up and makes it (im guessing unintentionally) domains directory = /home/vpopmail/var/vpopmail conf directory = /home/vpopmail/etc/vpopmail bin directory = /home/vpopmail/bin lib directory = /home/vpopmail/lib include directory = /home/vpopmail/include/vpopmail I think herein lies the source of both the strange location of vusaged.conf and the odd /domains directory. I realize the prefix i added was the default, but still. As for the error message from the SQL backend: I'm still getting that: "Warning: Failed while attempting to delete domain from auth backend". running on Debian 5 - squeeze (testing). with MySQL Server version: 5.0.51a-24 (Debian) Sincerely, - Wouter van der Schagt !DSPAM:49f74fdb32681216471239!
Re: [vchkpw] More vpopmail 5.5 notes / experiences
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wouter van der Schagt wrote: >> Are you working with the current SVN branch, or with a tarball from >> Sourceforge? I'm not certain all changes to the FHS-related code are >> on Sourceforge. > > I was using the tarball, am now testing with SVN revision 891. Further > testing reveals that a default ./configure returns: > > domains directory = /home/vpopmail/domains >conf directory = /home/vpopmail/etc > bin directory = /home/vpopmail/bin > lib directory = /home/vpopmail/lib > include directory = /home/vpopmail/include > > As expected, however adding "--prefix=/home/vpopmail" messes this up and > makes it (im guessing unintentionally) > > domains directory = /home/vpopmail/var/vpopmail >conf directory = /home/vpopmail/etc/vpopmail > bin directory = /home/vpopmail/bin > lib directory = /home/vpopmail/lib > include directory = /home/vpopmail/include/vpopmail > > I think herein lies the source of both the strange location of > vusaged.conf and the odd /domains directory. I realize the prefix i > added was the default, but still. Yeah. That's an issue that I'm still struggling with. vpopmail has always used /home, and *not* been FHS compliant. Therefore, when you set a prefix, it has to assume FHS compliance, which means a prefix would be like /var, and so it has to tack on /vpopmail. That's why when you set the prefix to /home/vpopmail, it starts tacking on /var/vpopmail and /etc/vpopmail. If you're *not* going to use the FHS compliance, don't set a prefix. It will use whatever the vpopmail user's home directory is. > As for the error message from the SQL backend: I'm still getting that: > > "Warning: Failed while attempting to delete domain from auth backend". > > running on Debian 5 - squeeze (testing). with MySQL Server version: > 5.0.51a-24 (Debian) I know it's unlikely you can let me, but on the off chance, is there any chance you could get me remote access to this system so I could debug the situation? Because of the sheer amount of changes made in regards to authentication backends, the amount of possible issues that could cause this is pretty steep. If not, can you please verify that it's using the correct etc directory (ie: it's looking at the correct vpopmail.mysql file), and that the vpopmail.mysql file is accurate? Also, please give me the output of: nm ~vpopmail/etc/vpopmail.authmodule ldd ~vpopmail/etc/vpopmail.authmodule Thanks. - -- /* Matt BrookingsGnuPG Key D9414F70 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn3VEUACgkQ6QgvSNlBT3CBOgCbBBwLCyXZ1c9pn9iNYD3Y98nX DhEAnRznfRmcuDEBDbtU5p1As6tMyVFg =l4dB -END PGP SIGNATURE-
Re: [vchkpw] More vpopmail 5.5 notes / experiences
Regarding the FHS patch. Noted...i will ommit the prefix setting for now or consider to create a symbolic link for the time being. --- This machine is not accessible to the outside world, it is an internal mailserver. But I think i may have found more useful information: I performed a strace on the command vdeldomain and found: write(4, "1\0\0\0\3delete from lastauth where d"..., 53) = 53 read(4, "0\0\0\1\377z\4#42S02Table 'vpopmail.last"..., 16384) = 52 write(2, "Warning: Failed while attempting "..., 68Warning: Failed while attempting to delete domain from auth backend ) = 68 Manual investigation showed that there is no table "lastauth" in the vpopmail database. Should this have been created on install ? or is this created when somebody logs in? The error doesn't appear to be fatal, but it is ugly. --- I can test the setup on Ubuntu and FreeBSD as well if you like? Are you interested in testing results on other platforms or has it already been tested? Sincerely, - Wouter van der Schagt !DSPAM:49f75ae232682117489581!
Re: [vchkpw] More vpopmail 5.5 notes / experiences
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wouter van der Schagt wrote: > Regarding the FHS patch. Noted...i will ommit the prefix setting for now > or consider to create a symbolic link for the time being. I'll probably end up adding a test to see if the prefix matches the vpopmail user's home directory. > Manual investigation showed that there is no table "lastauth" in the > vpopmail database. Should this have been created on install ? or is this > created when somebody logs in? The error doesn't appear to be fatal, but > it is ugly. I see how this is happening. I'll add a fix to SVN soon. > I can test the setup on Ubuntu and FreeBSD as well if you like? Are you > interested in testing results on other platforms or has it already been > tested? Any platforms you want to test on would be appreciated. Specifically, I want to test the vusage daemon and the backend module code to make sure it's fully portable across Unix-based systems. - -- /* Matt BrookingsGnuPG Key D9414F70 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn3XfkACgkQ6QgvSNlBT3BbLQCZAWJwncOAIJVbELHtIFPPSGV1 SvEAoIX80uc4ccmClOvRzQhHfyT6IZYX =yjqp -END PGP SIGNATURE-
Re: [vchkpw] vpopmail valias wildcard support - every...@domain.com
Rick Macdougall wrote: Matt Brookings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Koch wrote: Hi: In the case where a domain has, say, 100 email accounts, is there an easy way to configure a wildcard alias or mailinglist so that an email can be sent to everyone? Otherwise I can see that in a constantly changing organization it could be a lot of work to keep a mailing list or alias current. vpopbull would not work since the individual domains don't have that access. There's no current way to do this, mostly because there's no easy way to authenticate the sent mail. You wouldn't want a spammer, or an employee who shouldn't be emailing everyone, to email company-wide. You could write an email interface to vpopbull probably. One that requires a password somewhere in the email, and have it passed the message via a dotqmail file. Perhaps it should be something added to vpopmaild, allowing the postmaster to send to their domain and the administrator to send to all domains. I would suggest using onchange to update either a mailing list or .qmail file in the domain directory when the user list changes. See README.onchange. Rick !DSPAM:49f7ce1932681070413337!