[qmailtoaster] re: vpopmail
Is there a script to reset all the permissions in the /home/vpopmail/domains directory? --
[qmailtoaster] Re: vpopmail
On 05/24/2012 10:44 AM, Cecil Yother, Jr. wrote: Is there a script to reset all the permissions in the /home/vpopmail/domains directory? -- Not that I'm aware of. I've thought on occasion that it'd be nice to have a utility script sort of like queue_repair.py that would go through all of the QMT related directories and check/fix the permissions and ownerships. Anyone care to take a stab at it? I'd be glad to add such a thing to the QTP package. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail
On 05/24/2012 07:37 PM, Bharath Chari wrote: On Friday 25 May 2012 07:47 AM, Bharath Chari wrote: On Friday 25 May 2012 04:51 AM, Eric Shubert wrote: On 05/24/2012 10:44 AM, Cecil Yother, Jr. wrote: Is there a script to reset all the permissions in the /home/vpopmail/domains directory? -- Not that I'm aware of. I've thought on occasion that it'd be nice to have a utility script sort of like queue_repair.py that would go through all of the QMT related directories and check/fix the permissions and ownerships. Anyone care to take a stab at it? I'd be glad to add such a thing to the QTP package. Isn't "chown -R vpopmail:vchkpw * /home/vpopmail/domains" sufficient? Sorry "chown -R vpopmail:vchkpw /home/vpopmail/domains" That's easy enough for ownership, but permission bits are a little trickier. Need to differentiate between directories and files. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail
On 05/24/2012 10:01 PM, xaf wrote:
|--> Eric Shubert, le 25/05/2012 04:58, a dit :
On 05/24/2012 07:37 PM, Bharath Chari wrote:
On Friday 25 May 2012 07:47 AM, Bharath Chari wrote:
On Friday 25 May 2012 04:51 AM, Eric Shubert wrote:
On 05/24/2012 10:44 AM, Cecil Yother, Jr. wrote:
Is there a script to reset all the permissions in the
/home/vpopmail/domains directory?
--
Not that I'm aware of.
I've thought on occasion that it'd be nice to have a utility script
sort of like queue_repair.py that would go through all of the QMT
related directories and check/fix the permissions and ownerships.
Anyone care to take a stab at it? I'd be glad to add such a thing to
the QTP package.
Isn't "chown -R vpopmail:vchkpw * /home/vpopmail/domains" sufficient?
Sorry "chown -R vpopmail:vchkpw /home/vpopmail/domains"
That's easy enough for ownership, but permission bits are a little
trickier. Need to differentiate between directories and files.
cd /home/vpopmail/domains
find . -type d -exec chmod 700 {} \;
find . -type f -exec chmod 600 {} \;
find . -type f -name "courierimap*" -exec chmod 644 {} \;
chown -R vpopmail:vchkpw .
do the job
xaf
-
Nice. If you're running dovecot, also:
find . -type f -name "dovecot-uidvalidity.*" -exec chmod 444 {} \;
Would someone care to add this to the wiki? Maybe in the FAQ section if
there's not a more appropriate place.
--
-Eric 'shubes'
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail defaultdomain
On 05/03/2013 07:58 AM, cj yother wrote: On 05/02/2013 10:22 PM, Myers, Jon W wrote: this is probably yet another thing for the vpopmail list, but I'm not on that list yet... I've setup /home/vpopmail/etc/defaultdomain to contain my main domain name. Users can SOMETIMES login with just their username (tested from android phones, and squirrelmail). But the results (without changing any settings, usernames, or passwords) are inconsistent. Has anyone else run into this problem? I know I can get a plugin for squirrelmail (vlogin) that helps with this, but its not going to help the email app thats pre-installed on android phones. Of course this worked fine on my old vpopmail 5.0 server, but is now sporadic on the new vpopmail 5.4.33 powered qmail toaster. - To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com Isn't authentication handled by courier? -- Not directly. Courier (and dovecot) hand the actual authentication off to vpopmail, as does qmail-smtpd for submissions. Courier no longer supports vpopmail, which is one reason (of several) that QMT is going to be using dovecot in the future. My answer to Jon's question is, I don't know. There, I said it. I had used QMT for a couple years before I even knew there was such a thing as defaultdomain for logins. I just got used to using the whole email address, although it did feel a little goofy at first. I still haven't found a client app which tries or gets that right for the account name. :( -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail defaultdomain
On 05/03/2013 10:14 AM, Cecil Yother, Jr. wrote: On 05/03/2013 10:11 AM, Eric Shubert wrote: On 05/03/2013 07:58 AM, cj yother wrote: On 05/02/2013 10:22 PM, Myers, Jon W wrote: this is probably yet another thing for the vpopmail list, but I'm not on that list yet... I've setup /home/vpopmail/etc/defaultdomain to contain my main domain name. Users can SOMETIMES login with just their username (tested from android phones, and squirrelmail). But the results (without changing any settings, usernames, or passwords) are inconsistent. Has anyone else run into this problem? I know I can get a plugin for squirrelmail (vlogin) that helps with this, but its not going to help the email app thats pre-installed on android phones. Of course this worked fine on my old vpopmail 5.0 server, but is now sporadic on the new vpopmail 5.4.33 powered qmail toaster. - To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com Isn't authentication handled by courier? -- Not directly. Courier (and dovecot) hand the actual authentication off to vpopmail, as does qmail-smtpd for submissions. Courier no longer supports vpopmail, which is one reason (of several) that QMT is going to be using dovecot in the future. My answer to Jon's question is, I don't know. There, I said it. I had used QMT for a couple years before I even knew there was such a thing as defaultdomain for logins. I just got used to using the whole email address, although it did feel a little goofy at first. I still haven't found a client app which tries or gets that right for the account name. :( OK, so I guess the question is does it only use FQDN or does it have some relationship with the IP? They use localhost (127.0.0.1). -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail defaultdomain
On 05/08/2013 04:11 PM, Jon Myers wrote: At 01:57 PM 5/3/2013, you wrote: On 05/03/2013 10:14 AM, Cecil Yother, Jr. wrote: On 05/03/2013 10:11 AM, Eric Shubert wrote: On 05/03/2013 07:58 AM, cj yother wrote: On 05/02/2013 10:22 PM, Myers, Jon W wrote: this is probably yet another thing for the vpopmail list, but I'm not on that list yet... I've setup /home/vpopmail/etc/defaultdomain to contain my main domain name. Users can SOMETIMES login with just their username (tested from android phones, and squirrelmail). But the results (without changing any settings, usernames, or passwords) are inconsistent. Has anyone else run into this problem? I know I can get a plugin for squirrelmail (vlogin) that helps with this, but its not going to help the email app thats pre-installed on android phones. Of course this worked fine on my old vpopmail 5.0 server, but is now sporadic on the new vpopmail 5.4.33 powered qmail toaster. - To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com Isn't authentication handled by courier? -- Not directly. Courier (and dovecot) hand the actual authentication off to vpopmail, as does qmail-smtpd for submissions. Courier no longer supports vpopmail, which is one reason (of several) that QMT is going to be using dovecot in the future. My answer to Jon's question is, I don't know. There, I said it. I had used QMT for a couple years before I even knew there was such a thing as defaultdomain for logins. I just got used to using the whole email address, although it did feel a little goofy at first. I still haven't found a client app which tries or gets that right for the account name. :( OK, so I guess the question is does it only use FQDN or does it have some relationship with the IP? They use localhost (127.0.0.1). -- -Eric 'shubes' This is still a random issue. I'm thinking of just whacking on the source for imap, looking for where it reads in the username from the socket within the imap protocol, and insert a default domain if it doesn't contain an @ sign. As an alternative, should I switch to Dovecot, or is that just another can of worms? vpopmail SHOULD be appending the domain, but isnt. So maybe I should whack on that sourcecode? I just figured it'd be easier to find in the first program thats reading from the raw socket, rather than trying to intercept the handoff to vpopmail. Or maybe look for something in the vpopmail code that randomly checks the defaultdomain file, and make it always check it... as if it were THAT silly. =) we HAD two mail servers, one for our main site, and another for all the domains we hosted. Well, we rolled the main domain into the existing (newest) server. So we have active email accounts that are 20 years old, and lots of people still sticking to just typing in their usernames. Telling them all to change is tricky, as well as getting their pref files converted in squirrelmail, but thats a script I'm working on now anyway. - I would definitely convert to dovecot asap. That's rather painless, and might solve the problem for you. Refer to the wiki page for this. Dovecot is much more efficient than courier, and it's more robust. It can handle Maildirs in the 10s of GBs without breaking a sweat. QMT will be dropping courier soon in favor of dovecot, as courier no longer supports vpopmail. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail db
sima lorena wrote: Hello In the vpopmail db i have on dir_control table an entry that calls "*dom_89*" that i didnt do it Can i delete this entry? - I don't know if that would be safe or not. The vpopmail db is a bit convoluted imho. I would ask this on the vpopmail users list. -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail
On Friday 25 May 2012 04:51 AM, Eric Shubert wrote: On 05/24/2012 10:44 AM, Cecil Yother, Jr. wrote: Is there a script to reset all the permissions in the /home/vpopmail/domains directory? -- Not that I'm aware of. I've thought on occasion that it'd be nice to have a utility script sort of like queue_repair.py that would go through all of the QMT related directories and check/fix the permissions and ownerships. Anyone care to take a stab at it? I'd be glad to add such a thing to the QTP package. Isn't "chown -R vpopmail:vchkpw * /home/vpopmail/domains" sufficient? Bharath - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail
On Friday 25 May 2012 07:47 AM, Bharath Chari wrote: On Friday 25 May 2012 04:51 AM, Eric Shubert wrote: On 05/24/2012 10:44 AM, Cecil Yother, Jr. wrote: Is there a script to reset all the permissions in the /home/vpopmail/domains directory? -- Not that I'm aware of. I've thought on occasion that it'd be nice to have a utility script sort of like queue_repair.py that would go through all of the QMT related directories and check/fix the permissions and ownerships. Anyone care to take a stab at it? I'd be glad to add such a thing to the QTP package. Isn't "chown -R vpopmail:vchkpw * /home/vpopmail/domains" sufficient? Sorry "chown -R vpopmail:vchkpw /home/vpopmail/domains" Bharath - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail
|--> Eric Shubert, le 25/05/2012 04:58, a dit :
> On 05/24/2012 07:37 PM, Bharath Chari wrote:
>> On Friday 25 May 2012 07:47 AM, Bharath Chari wrote:
>>> On Friday 25 May 2012 04:51 AM, Eric Shubert wrote:
On 05/24/2012 10:44 AM, Cecil Yother, Jr. wrote:
> Is there a script to reset all the permissions in the
> /home/vpopmail/domains directory?
> --
Not that I'm aware of.
I've thought on occasion that it'd be nice to have a utility script
sort of like queue_repair.py that would go through all of the QMT
related directories and check/fix the permissions and ownerships.
Anyone care to take a stab at it? I'd be glad to add such a thing to
the QTP package.
>>> Isn't "chown -R vpopmail:vchkpw * /home/vpopmail/domains" sufficient?
>>
>> Sorry "chown -R vpopmail:vchkpw /home/vpopmail/domains"
>>
>>
>
> That's easy enough for ownership, but permission bits are a little
> trickier. Need to differentiate between directories and files.
>
cd /home/vpopmail/domains
find . -type d -exec chmod 700 {} \;
find . -type f -exec chmod 600 {} \;
find . -type f -name "courierimap*" -exec chmod 644 {} \;
chown -R vpopmail:vchkpw .
do the job
xaf
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail
On 05/24/2012 07:58 PM, Eric Shubert wrote: On 05/24/2012 07:37 PM, Bharath Chari wrote: On Friday 25 May 2012 07:47 AM, Bharath Chari wrote: On Friday 25 May 2012 04:51 AM, Eric Shubert wrote: On 05/24/2012 10:44 AM, Cecil Yother, Jr. wrote: Is there a script to reset all the permissions in the /home/vpopmail/domains directory? -- Not that I'm aware of. I've thought on occasion that it'd be nice to have a utility script sort of like queue_repair.py that would go through all of the QMT related directories and check/fix the permissions and ownerships. Anyone care to take a stab at it? I'd be glad to add such a thing to the QTP package. Isn't "chown -R vpopmail:vchkpw * /home/vpopmail/domains" sufficient? Sorry "chown -R vpopmail:vchkpw /home/vpopmail/domains" That's easy enough for ownership, but permission bits are a little trickier. Need to differentiate between directories and files. Precisely and this is what I need. --
[qmailtoaster] Re: Vpopmail build error
No answers??2006/2/27, aledr <[EMAIL PROTECTED]>: Hi!I'm getting this error when trying to build the latest vpopmail from site on my Fedora 4:mv: cannot stat `/var/tmp/vpopmail-toaster-5.4.10-root/home/vpopmail/etc/vpopmail.mysql': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.97391 (%install)RPM build errors: Bad exit status from /var/tmp/rpm-tmp.97391 (%install)What can I do?Regards... -- [ ]'sAledr"OpenSource Solutions for SmallBusiness Problems" -- [ ]'sAledr"OpenSource Solutions for SmallBusiness Problems"
Re: [qmailtoaster] Re: vpopmail defaultdomain
On 05/03/2013 10:11 AM, Eric Shubert wrote: On 05/03/2013 07:58 AM, cj yother wrote: On 05/02/2013 10:22 PM, Myers, Jon W wrote: this is probably yet another thing for the vpopmail list, but I'm not on that list yet... I've setup /home/vpopmail/etc/defaultdomain to contain my main domain name. Users can SOMETIMES login with just their username (tested from android phones, and squirrelmail). But the results (without changing any settings, usernames, or passwords) are inconsistent. Has anyone else run into this problem? I know I can get a plugin for squirrelmail (vlogin) that helps with this, but its not going to help the email app thats pre-installed on android phones. Of course this worked fine on my old vpopmail 5.0 server, but is now sporadic on the new vpopmail 5.4.33 powered qmail toaster. - To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com Isn't authentication handled by courier? -- Not directly. Courier (and dovecot) hand the actual authentication off to vpopmail, as does qmail-smtpd for submissions. Courier no longer supports vpopmail, which is one reason (of several) that QMT is going to be using dovecot in the future. My answer to Jon's question is, I don't know. There, I said it. I had used QMT for a couple years before I even knew there was such a thing as defaultdomain for logins. I just got used to using the whole email address, although it did feel a little goofy at first. I still haven't found a client app which tries or gets that right for the account name. :( OK, so I guess the question is does it only use FQDN or does it have some relationship with the IP? -- - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail defaultdomain
At 01:57 PM 5/3/2013, you wrote: On 05/03/2013 10:14 AM, Cecil Yother, Jr. wrote: On 05/03/2013 10:11 AM, Eric Shubert wrote: On 05/03/2013 07:58 AM, cj yother wrote: On 05/02/2013 10:22 PM, Myers, Jon W wrote: this is probably yet another thing for the vpopmail list, but I'm not on that list yet... I've setup /home/vpopmail/etc/defaultdomain to contain my main domain name. Users can SOMETIMES login with just their username (tested from android phones, and squirrelmail). But the results (without changing any settings, usernames, or passwords) are inconsistent. Has anyone else run into this problem? I know I can get a plugin for squirrelmail (vlogin) that helps with this, but its not going to help the email app thats pre-installed on android phones. Of course this worked fine on my old vpopmail 5.0 server, but is now sporadic on the new vpopmail 5.4.33 powered qmail toaster. - To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com Isn't authentication handled by courier? -- Not directly. Courier (and dovecot) hand the actual authentication off to vpopmail, as does qmail-smtpd for submissions. Courier no longer supports vpopmail, which is one reason (of several) that QMT is going to be using dovecot in the future. My answer to Jon's question is, I don't know. There, I said it. I had used QMT for a couple years before I even knew there was such a thing as defaultdomain for logins. I just got used to using the whole email address, although it did feel a little goofy at first. I still haven't found a client app which tries or gets that right for the account name. :( OK, so I guess the question is does it only use FQDN or does it have some relationship with the IP? They use localhost (127.0.0.1). -- -Eric 'shubes' This is still a random issue. I'm thinking of just whacking on the source for imap, looking for where it reads in the username from the socket within the imap protocol, and insert a default domain if it doesn't contain an @ sign. As an alternative, should I switch to Dovecot, or is that just another can of worms? vpopmail SHOULD be appending the domain, but isnt. So maybe I should whack on that sourcecode? I just figured it'd be easier to find in the first program thats reading from the raw socket, rather than trying to intercept the handoff to vpopmail. Or maybe look for something in the vpopmail code that randomly checks the defaultdomain file, and make it always check it... as if it were THAT silly. =) we HAD two mail servers, one for our main site, and another for all the domains we hosted. Well, we rolled the main domain into the existing (newest) server. So we have active email accounts that are 20 years old, and lots of people still sticking to just typing in their usernames. Telling them all to change is tricky, as well as getting their pref files converted in squirrelmail, but thats a script I'm working on now anyway. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail to old
Aleksander Podsiadły wrote: Actual 5.4.17 version of vpopmail in QMT is released 12-Jul-06, current version is 5.5.0. I tried to compile Dovecot 2.0rc3 and found problem. QMT vpopmail is to old. :( IMO this package should bu upgraded. And it will be upgraded, eventually. vpopmail 5.5.0 is pretty new, and a substantial upgrade from 5.4.x. Would you like to help out getting 5.5 going with QMT? If so, please bring it up on the devel list. -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail to old
Aleksander Podsiadły wrote: Dnia 2010-07-27, wto o godzinie 09:32 -0700, Eric Shubert pisze: And it will be upgraded, eventually. vpopmail 5.5.0 is pretty new, and a substantial upgrade from 5.4.x. Would you like to help out getting 5.5 going with QMT? If so, please bring it up on the devel list. Eric, I have to check am I good enough. ;) Ha! I've no doubt you can handle it. :) -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail to old
I'm thrilled to see Aleksander and Lucian working this out.
Can we take this to the devel list? ;)
Lucian Cristian wrote:
about that real install I was talking when I spoken about backend
cleanup, if the files are not found in the mentioned place, vpopmail
will complain that no backend is installed, of course there may be a
workaround like qmail fake install..
Regards
Lucian
On 28.07.2010 17:38, Aleksander Podsiadły wrote:
Dnia 2010-07-28, śro o godzinie 12:44 +0300, Lucian Cristian pisze:
+mkdir -p %{buildroot}%{mylibdir}
+mkdir -p %{buildroot}%{vdir}/etc/vpopmail
+make DESTDIR=%{buildroot} install
+make install
+
+rm -f %{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
+ln -s %{mylibdir}/vmysql.so
%{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
Oh thanks. :)
IMO vmysql.so is installed in %{vdir}/lib so should be:
mkdir -p %{buildroot}%{vdir}/lib
and
ln -s %{vdir}/lib/vmysql.so
%{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
and in section %files something like:
%attr(0755,vpopmail,vchkpw) %dir %{vdir}/lib
%attr(0751,vpopmail,vchkpw) %{vdir}/lib/*.so
You shouldn't use configure option "prefix". Using this option implicate
in this version non standard vpopmail directories.
One "make install" line in your patch is danger. It causes installation
of files in real directories, not in buildroot directory!
I attached my patch, not all tested!
-
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
--
-Eric 'shubes'
-
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail field problem
On 10/15/2010 02:56 AM, Digital Instruments wrote: Greetings list, I have recompiled vpopmail without the damn pw_clear_passwd. I've used the standard script cnt5064-install-script.sh and modify it like so: if [ $PROCEED = "y" ]; then rpmbuild --rebuild --with $DISTRO --with disable-clear-passwd $VPOP rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/vpopmail-toaster*.rpm fi the result seems not good: Preparing... ### [100%] package vpopmail-toaster-5.4.17-1.3.7.x86_64 is already installed file /home/vpopmail/bin/clearopensmtp from install of vpopmail-toaster-5.4.17-1.3.7.x86_64 conflicts with file from package vpopmail-toaster-5.4.17-1.3.7.x86_64 (many other lines like that) 1:vpopmail-toaster ### [ 50%] I've also try another method: rpm -Uhv vpopmail-toaster*.src.rpm edited the vpopmail-toaster.spec (usually in /usr/src/redhat/SPECS/), change line 729 from "--enable-clear-passwd" to "--disable-clear-passwd" with a text editor. rpmbuild -bs vpopmail-toaster.spec that time it went to 100% 1:vpopmail-toaster ### [ 100%] but unfortunately it doesn't work. If i try to drop the pw_clear_passwd field from the vpopmail database i can't login with any account. If i try to create a new account ... error (if the field is drop) or it write the password in clear if the field isn't drop. Anyone can help me, please? Thanks!! A. - The first method (--with) does not work. The spec file needs to recognize these options, which it doesn't. The second method (editing the .spec file) is correct. After building the rpm from source though, you need to install the binary rpm that was produced by the rpmbuild run: # rpm -Uvh --replacepkgs vpopmail-toaster.*.rpm Be sure you're in the directory where you built the binary rpm when you do this. -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail field problem
Right. Packages which are dependent on vpopmail-toaster are: qmail-toaster qmailadmin-toaster courier-authlib-toaster courier-imap-toaster and these should be rebuilt and reinstalled. qtp-newmodel can do this easily for you. Removing clear text passwords has other implications as well. IIRC, some authentication methods require this. While I'm no proponent of storing passwords in clear text (it wouldn't bother me if the stock toaster removed them), I expect that removing them will take some doing. -- -Eric 'shubes' On 10/15/2010 11:20 AM, Martin Waschbuesch wrote: Several packages depend on vpopmail and recompiling it may require you to recompile the other packages, too? E.g. qmailadmin - don't know about others. Also, I do not know how vqadmin and qcontrol work. If they use the shell commands vpopmail contains then all should be well, but if they access the database directly, they might depend on the structure of that database. Don't know if that helps, but it might be a starting point for debugging. Martin - Original Message - From: "Eric Shubert" To: Sent: Friday, October 15, 2010 4:48 PM Subject: [qmailtoaster] Re: vpopmail field problem On 10/15/2010 02:56 AM, Digital Instruments wrote: Greetings list, I have recompiled vpopmail without the damn pw_clear_passwd. I've used the standard script cnt5064-install-script.sh and modify it like so: if [ $PROCEED = "y" ]; then rpmbuild --rebuild --with $DISTRO --with disable-clear-passwd $VPOP rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/vpopmail-toaster*.rpm fi the result seems not good: Preparing... ### [100%] package vpopmail-toaster-5.4.17-1.3.7.x86_64 is already installed file /home/vpopmail/bin/clearopensmtp from install of vpopmail-toaster-5.4.17-1.3.7.x86_64 conflicts with file from package vpopmail-toaster-5.4.17-1.3.7.x86_64 (many other lines like that) 1:vpopmail-toaster ### [ 50%] I've also try another method: rpm -Uhv vpopmail-toaster*.src.rpm edited the vpopmail-toaster.spec (usually in /usr/src/redhat/SPECS/), change line 729 from "--enable-clear-passwd" to "--disable-clear-passwd" with a text editor. rpmbuild -bs vpopmail-toaster.spec that time it went to 100% 1:vpopmail-toaster ### [ 100%] but unfortunately it doesn't work. If i try to drop the pw_clear_passwd field from the vpopmail database i can't login with any account. If i try to create a new account ... error (if the field is drop) or it write the password in clear if the field isn't drop. Anyone can help me, please? Thanks!! A. - The first method (--with) does not work. The spec file needs to recognize these options, which it doesn't. The second method (editing the .spec file) is correct. After building the rpm from source though, you need to install the binary rpm that was produced by the rpmbuild run: # rpm -Uvh --replacepkgs vpopmail-toaster.*.rpm Be sure you're in the directory where you built the binary rpm when you do this. -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail field problem
You'll need to: .) modify the .spec to your needs .) create the source rpm (.srpm) package from the spec (rpmbuild -bs) .) put the .srpm package in /usr/src/qtp-upgrade/SRPMS/ .) run qtp-newmodel and select the package for rebuild. qtp-newmodel will automatically rebuild whatever's necessary, and install everything. On 10/18/2010 12:12 AM, Digital Instruments wrote: Nice! So ... I need to recompile vpopmail package with the right option then move it somewhere qtp-newmodel needs and finally re-install all those packages with it? Question: Am I gonna lose any configuration? Such as domains, e-mails and everything related to? -- Cheers, Alberto. Il 15/10/2010 21.12, Eric Shubert ha scritto: Right. Packages which are dependent on vpopmail-toaster are: qmail-toaster qmailadmin-toaster courier-authlib-toaster courier-imap-toaster and these should be rebuilt and reinstalled. qtp-newmodel can do this easily for you. Removing clear text passwords has other implications as well. IIRC, some authentication methods require this. While I'm no proponent of storing passwords in clear text (it wouldn't bother me if the stock toaster removed them), I expect that removing them will take some doing. Nessun virus nel messaggio in arrivo. Controllato da AVG -www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3198 - Data di rilascio: 10/15/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3203 - Data di rilascio: 10/17/10 20:33:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail field problem
It appears to be ok. If you changed the documentation in the spec file appropriately, you can run # rpm -qi vpopmail-toaster to see which options are in effect. Note, this comes from a separate part of the spec file, and you need to modify this to reflect any changes you made to the config command in the spec. -- -Eric 'shubes' On 10/18/2010 12:29 AM, Digital Instruments wrote: How do I know if was sucessfull? The only think I've got from the command was that: [r...@ser SRPMS]# rpm -Uvh --replacepkgs vpopmail-toaster-5.4.17-1.3.7.src.rpm 1:vpopmail-toaster ### [100%] It has been replace correctly? Il 15/10/2010 21.12, Eric Shubert ha scritto: Right. Packages which are dependent on vpopmail-toaster are: qmail-toaster qmailadmin-toaster courier-authlib-toaster courier-imap-toaster and these should be rebuilt and reinstalled. qtp-newmodel can do this easily for you. Removing clear text passwords has other implications as well. IIRC, some authentication methods require this. While I'm no proponent of storing passwords in clear text (it wouldn't bother me if the stock toaster removed them), I expect that removing them will take some doing. Nessun virus nel messaggio in arrivo. Controllato da AVG -www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3198 - Data di rilascio: 10/15/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3203 - Data di rilascio: 10/17/10 20:33:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail field problem
qtp-newmodel will use whatever's in /usr/src/qtp-upgrade/SRPMS (unless you've changed the default location). If it doesn't find the source rpm there, it will download it from the web site. Just be sure that you use the latest vpopmail-toaster package, and keep the same version numbers in your spec file. -- -Eric 'shubes' On 10/18/2010 08:22 AM, Digital Instruments wrote: Oh :O thanks Eric. Btw are you sure qtp-newmodel will use my srpm package of vpopmail and will not rebuilt his own? thanks A. Il 18/10/2010 16.41, Eric Shubert ha scritto: You'll need to: .) modify the .spec to your needs .) create the source rpm (.srpm) package from the spec (rpmbuild -bs) .) put the .srpm package in /usr/src/qtp-upgrade/SRPMS/ .) run qtp-newmodel and select the package for rebuild. qtp-newmodel will automatically rebuild whatever's necessary, and install everything. On 10/18/2010 12:12 AM, Digital Instruments wrote: Nice! So ... I need to recompile vpopmail package with the right option then move it somewhere qtp-newmodel needs and finally re-install all those packages with it? Question: Am I gonna lose any configuration? Such as domains, e-mails and everything related to? -- Cheers, Alberto. Il 15/10/2010 21.12, Eric Shubert ha scritto: Right. Packages which are dependent on vpopmail-toaster are: qmail-toaster qmailadmin-toaster courier-authlib-toaster courier-imap-toaster and these should be rebuilt and reinstalled. qtp-newmodel can do this easily for you. Removing clear text passwords has other implications as well. IIRC, some authentication methods require this. While I'm no proponent of storing passwords in clear text (it wouldn't bother me if the stock toaster removed them), I expect that removing them will take some doing. Nessun virus nel messaggio in arrivo. Controllato da AVG -www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3198 - Data di rilascio: 10/15/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3203 - Data di rilascio: 10/17/10 20:33:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! Nessun virus nel messaggio in arrivo. Controllato da AVG -www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3204 - Data di rilascio: 10/18/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3204 - Data di rilascio: 10/18/10 08:34:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail field problem
On 10/19/2010 12:40 AM, Digital Instruments wrote: Should I change vpopmail-toaster.spec file like that: line 584 /clear passwd = ON --enable-clear-passwd/ TO /clear passwd = OFF --disable-clear-passwd/ line 654 /--enable-clear-passwd/ TO /--disable-clear-passwd/ Thanks Cheers A. I'm not familiar with vpopmail's configure commmand off the top of my head. A little googling though appears to indicate that --enable-clear-passwd=n would be the correct syntax. I don't see "disable" being used anywhere. http://www.inter7.com/vpopmail/install.txt http://www.inter7.com/vpopmail/FAQ.txt -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail to old
Dnia 2010-07-27, wto o godzinie 09:32 -0700, Eric Shubert pisze: > And it will be upgraded, eventually. vpopmail 5.5.0 is pretty new, and > a > substantial upgrade from 5.4.x. Would you like to help out getting > 5.5 > going with QMT? If so, please bring it up on the devel list. Eric, I have to check am I good enough. ;) -- Pozdrawiam / Regards, Aleksander Podsiadły mail: a...@westside.kielce.pl jid: a...@jabber.westside.kielce.pl ICQ: 201121279 gg: 9150578 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail to old
here is a patch for vpopmail 5.5.0 spec based on 4.5.17 build (it
needs backend cleanup if you only want to compile it on other system)
--- vpopmail-toaster.spec.old 2009-06-12 05:38:38.0 +0300
+++ vpopmail-toaster.spec 2010-07-28 12:41:55.0 +0300
@@ -1,7 +1,7 @@
%definename vpopmail
-%definepversion 5.4.17
+%definepversion 5.5.0
%definebversion 1.3
-%definerpmrelease 7
+%definerpmrelease 1
# INSTRUCTIONS!!! <- READ THEM!!!
#
@@ -568,7 +568,7 @@
It handles 10 to 10 million users, and over 500K domains.
- vpopmail 5.4.17
+ vpopmail 5.5.0
Current settings
---
@@ -686,10 +686,11 @@
# Run configure to create makefile
#
+
./configure --prefix=%{vdir} \
- --enable-vpopuser=vpopmail \
- --enable-vpopgroup=vchkpw \
- --enable-libdir=%{mylibdir} \
+ --with-vpopuser=vpopmail \
+ --with-vpopgroup=vchkpw \
+ --libdir=%{mylibdir} \
--disable-roaming-users \
--enable-tcprules-prog=/usr/bin/tcprules \
--enable-tcpserver-file=/etc/tcprules.d/tcp.smtp \
@@ -698,15 +699,20 @@
--disable-users-big-dir \
--enable-qmail-ext \
--disable-ip-alias-domains \
- --enable-auth-module=mysql \
--disable-passwd \
--enable-logging=v \
- --enable-log-name=vpopmail \
- --disable-mysql-limits \
- --enable-valias \
- --disable-many-domains
+ --enable-log-name=vpopmail
+make
+echo mysql..
+cd backends/mysql
+./configure --enable-libdir=%{mylibdir} \
+ --disable-many-domains \
+ --enable-valias \
+ --enable-auth-logging \
+ --disable-mysql-limits
make
+
# Delete gcc temp file
#
[ -f %{_tmppath}/%{name}-%{pversion}-gcc ] && rm -f
%{_tmppath}/%{name}-%{pversion}-gcc
@@ -715,24 +721,39 @@
#
%install
#
+cd backends/mysql
+mkdir -p %{buildroot}%{mylibdir}
+mkdir -p %{buildroot}%{vdir}/etc/vpopmail
+make DESTDIR=%{buildroot} install
+make install
+
+rm -f %{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
+ln -s %{mylibdir}/vmysql.so
%{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
+cd ../..
make DESTDIR=%{buildroot} install-strip
# Set defaults for vpopmail mysql
#
-mv %{buildroot}%{vdir}/etc/vpopmail.mysql
%{buildroot}%{vdir}/etc/vpopmail.mysql.dist
-echo "localhost|0|vpopmail|SsEeCcRrEeTt|vpopmail" >
%{buildroot}%{vdir}/etc/vpopmail.mysql
+
+mv %{buildroot}%{vdir}/etc/vpopmail/vpopmail.mysql
%{buildroot}%{vdir}/etc/vpopmail/vpopmail.mysql.dist
+echo "localhost|0|vpopmail|SsEeCcRrEeTt|vpopmail" >
%{buildroot}%{vdir}/etc/vpopmail/vpopmail.mysql
# Install domain quota messages
#
+mkdir -p %{buildroot}%{vdir}/domains/
for i in overquota.msg quotawarn.msg; do
- install $i %{buildroot}%{vdir}/domains
+ install $i %{buildroot}%{vdir}/domains/
done
mv %{buildroot}%{vdir}/domains/overquota.msg
%{buildroot}%{vdir}/domains/.overquota.msg
mv %{buildroot}%{vdir}/domains/quotawarn.msg
%{buildroot}%{vdir}/domains/.quotawarn.msg
+mkdir -p %{buildroot}%{vdir}/doc/
+cp -a doc/doc_html %{buildroot}%{vdir}/doc/
+cp -a doc/man_html %{buildroot}%{vdir}/doc/
+
#
%pre
@@ -783,20 +804,22 @@
%attr(0755,vpopmail,vchkpw) %dir %{vdir}/bin
%attr(0755,vpopmail,vchkpw) %dir %{vdir}/etc
%attr(0755,vpopmail,vchkpw) %dir %{vdir}/include
-%attr(0755,vpopmail,vchkpw) %dir %{vdir}/lib
+#%attr(0755,vpopmail,vchkpw) %dir %{vdir}/lib
%attr(0700,vpopmail,vchkpw) %dir %{vdir}/domains
%attr(0751,vpopmail,vchkpw) %{vdir}/bin/*
%attr(0644,vpopmail,vchkpw) %{vdir}/domains/.quotawarn.msg
%attr(0644,vpopmail,vchkpw) %{vdir}/domains/.overquota.msg
-%attr(0644,vpopmail,vchkpw) %{vdir}/etc/inc_deps
-%attr(0644,vpopmail,vchkpw) %{vdir}/etc/lib_deps
-%attr(0644,vpopmail,vchkpw) %config(noreplace) %{vdir}/etc/vlimits.default
-%attr(0644,vpopmail,vchkpw) %config(noreplace) %{vdir}/etc/vpopmail.mysql
-%attr(0644,vpopmail,vchkpw) %{vdir}/etc/vpopmail.mysql.dist
-%attr(0444,vpopmail,vchkpw) %{vdir}/include/*
-%attr(0600,vpopmail,vchkpw) %{vdir}/lib/*
-
+%attr(0644,vpopmail,vchkpw) %{vdir}/etc/vpopmail/inc_deps
+%attr(0644,vpopmail,vchkpw) %{vdir}/etc/vpopmail/lib_deps
+%attr(0644,vpopmail,vchkpw) %{vdir}/etc/vpopmail/vpopmail.authmodule
+%attr(0644,vpopmail,vchkpw) %config(noreplace)
%{vdir}/etc/vpopmail/vlimits.default
+%attr(06
Re: [qmailtoaster] Re: vpopmail to old
On 07/28/2010 05:44 AM, Lucian Cristian wrote: here is a patch for vpopmail 5.5.0 spec based on 4.5.17 build (it needs backend cleanup if you only want to compile it on other system) Thanks Lucian - I have not gotten to vpopmail yet on v2, but this will save me time, as well as help out those who want to upgrade to the newer version. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail to old
Dnia 2010-07-28, śro o godzinie 12:44 +0300, Lucian Cristian pisze:
> +mkdir -p %{buildroot}%{mylibdir}
> +mkdir -p %{buildroot}%{vdir}/etc/vpopmail
> +make DESTDIR=%{buildroot} install
> +make install
> +
> +rm -f %{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
> +ln -s %{mylibdir}/vmysql.so
> %{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
Oh thanks. :)
IMO vmysql.so is installed in %{vdir}/lib so should be:
mkdir -p %{buildroot}%{vdir}/lib
and
ln -s %{vdir}/lib/vmysql.so
%{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
and in section %files something like:
%attr(0755,vpopmail,vchkpw) %dir %{vdir}/lib
%attr(0751,vpopmail,vchkpw) %{vdir}/lib/*.so
You shouldn't use configure option "prefix". Using this option implicate
in this version non standard vpopmail directories.
One "make install" line in your patch is danger. It causes installation
of files in real directories, not in buildroot directory!
I attached my patch, not all tested!
--
Pozdrawiam / Regards,
Aleksander Podsiadły
mail: a...@westside.kielce.pl
jid: a...@jabber.westside.kielce.pl
ICQ: 201121279
gg: 9150578
--- vpopmail-toaster.spec.old 2009-06-12 04:38:00.0 +0200
+++ vpopmail-toaster.spec 2010-07-28 16:35:27.0 +0200
@@ -1,7 +1,7 @@
%define name vpopmail
-%define pversion 5.4.17
+%define pversion 5.5.0
%define bversion 1.3
-%define rpmrelease 7
+%define rpmrelease 1
# INSTRUCTIONS!!! <- READ THEM!!!
#
@@ -568,11 +568,15 @@
It handles 10 to 10 million users, and over 500K domains.
- vpopmail 5.4.17
+ vpopmail 5.5.0
Current settings
---
-vpopmail directory = /home/vpopmail
+ 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
uid = 89
gid = 89
roaming users = OFF --disable-roaming-users (default)
@@ -585,19 +589,12 @@
user dir hashing = OFF --disable-users-big-dir
address extensions = ON --enable-qmail-ext
ip alias = OFF --disable-ip-alias-domains (default)
- auth module = mysql --enable-auth-module=mysql
- mysql replication = OFF --disable-mysql-replication (default)
- sql logging = OFF --disable-sql-logging (default)
- mysql limits = OFF --disable-mysql-limits (default)
- MySQL valias = ON --enable-valias
- auth inc = -I/usr/include/mysql
- auth lib = -L/usr/lib64/mysql -lmysqlclient -lz -lm
+ onchange script = OFF --disable-onchange-script (default)
+ domain quotas = ON --enable-domainquotas (default)
system passwords = OFF --disable-passwd (default)
-pop syslog = log success and errors including passwords
- --enable-logging=v
- auth logging = ON --enable-auth-logging (default)
-one domain per SQL table = --disable-many-domains
-
+pop syslog = log success and errors including passwords --enable-logging=v
+ spamassassin = OFF --disable-spamassassin (default)
+ maildrop = OFF --disable-maildrop (default)
#
@@ -686,10 +683,8 @@
# Run configure to create makefile
#
-./configure --prefix=%{vdir} \
- --enable-vpopuser=vpopmail \
- --enable-vpopgroup=vchkpw \
- --enable-libdir=%{mylibdir} \
+./configure --with-vpopuser=vpopmail \
+ --with-vpopgroup=vchkpw \
--disable-roaming-users \
--enable-tcprules-prog=/usr/bin/tcprules \
--enable-tcpserver-file=/etc/tcprules.d/tcp.smtp \
@@ -698,13 +693,17 @@
--disable-users-big-dir \
--enable-qmail-ext \
--disable-ip-alias-domains \
- --enable-auth-module=mysql \
--disable-passwd \
--enable-logging=v \
- --enable-log-name=vpopmail \
- --disable-mysql-limits \
- --enable-valias \
- --disable-many-domains
+ --enable-log-name=vpopmail
+make
+echo mysql..
+cd backends/mysql
+./configure --enable-libdir=%{mylibdir} \
+ --disable-many-domains \
+ --enable-valias \
+ --enable-auth-logging \
+ --disable-mysql-limits
make
# Delete gcc temp file
@@ -715,24 +714,38 @@
#
%install
#
+cd backends/mysql
+mkdir -p %{buildroot}%{vdir}/lib
+mkdir -p %{buildroot}%{vdir}/etc
+make DESTDIR=%{buildroot} install
+
+rm -f %{buildroot}%{vdir}/etc/vpopmail.authmodule
+ln -s %{vdir}/lib/vmysql.so %{buildroot}%{vdir}/etc/vpopmail.authmodule
+cd ../..
make DESTDIR=%{buildroot} install-strip
# Set defaults for vpopmail mysql
#
+
mv %{buildroot}%{vdir}/etc/vpopmail.mysql %{buildroot}%{vdir}/etc/vpopmail.mysql.dis
Re: [qmailtoaster] Re: vpopmail to old
Dnia 2010-07-28, śro o godzinie 16:38 +0200, Aleksander Podsiadły pisze:
> ln -s %{vdir}/lib/vmysql.so
> %{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
Should be without "vpopmail/" like in my patch.
--
Pozdrawiam / Regards,
Aleksander Podsiadły
mail: a...@westside.kielce.pl
jid: a...@jabber.westside.kielce.pl
ICQ: 201121279
gg: 9150578
-
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail to old
about that real install I was talking when I spoken about backend
cleanup, if the files are not found in the mentioned place, vpopmail
will complain that no backend is installed, of course there may be a
workaround like qmail fake install..
Regards
Lucian
On 28.07.2010 17:38, Aleksander Podsiadły wrote:
Dnia 2010-07-28, śro o godzinie 12:44 +0300, Lucian Cristian pisze:
+mkdir -p %{buildroot}%{mylibdir}
+mkdir -p %{buildroot}%{vdir}/etc/vpopmail
+make DESTDIR=%{buildroot} install
+make install
+
+rm -f %{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
+ln -s %{mylibdir}/vmysql.so
%{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
Oh thanks. :)
IMO vmysql.so is installed in %{vdir}/lib so should be:
mkdir -p %{buildroot}%{vdir}/lib
and
ln -s %{vdir}/lib/vmysql.so
%{buildroot}%{vdir}/etc/vpopmail/vpopmail.authmodule
and in section %files something like:
%attr(0755,vpopmail,vchkpw) %dir %{vdir}/lib
%attr(0751,vpopmail,vchkpw) %{vdir}/lib/*.so
You shouldn't use configure option "prefix". Using this option implicate
in this version non standard vpopmail directories.
One "make install" line in your patch is danger. It causes installation
of files in real directories, not in buildroot directory!
I attached my patch, not all tested!
-
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail to old
Dnia 2010-07-28, śro o godzinie 10:28 -0700, Eric Shubert pisze: > I'm thrilled to see Aleksander and Lucian working this out. > Can we take this to the devel list? ;) Yes, you can. -- Pozdrawiam / Regards, Aleksander Podsiadły mail: a...@westside.kielce.pl jid: a...@jabber.westside.kielce.pl ICQ: 201121279 gg: 9150578 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail field problem
Several packages depend on vpopmail and recompiling it may require you to recompile the other packages, too? E.g. qmailadmin - don't know about others. Also, I do not know how vqadmin and qcontrol work. If they use the shell commands vpopmail contains then all should be well, but if they access the database directly, they might depend on the structure of that database. Don't know if that helps, but it might be a starting point for debugging. Martin - Original Message - From: "Eric Shubert" To: Sent: Friday, October 15, 2010 4:48 PM Subject: [qmailtoaster] Re: vpopmail field problem On 10/15/2010 02:56 AM, Digital Instruments wrote: Greetings list, I have recompiled vpopmail without the damn pw_clear_passwd. I've used the standard script cnt5064-install-script.sh and modify it like so: if [ $PROCEED = "y" ]; then rpmbuild --rebuild --with $DISTRO --with disable-clear-passwd $VPOP rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/vpopmail-toaster*.rpm fi the result seems not good: Preparing... ### [100%] package vpopmail-toaster-5.4.17-1.3.7.x86_64 is already installed file /home/vpopmail/bin/clearopensmtp from install of vpopmail-toaster-5.4.17-1.3.7.x86_64 conflicts with file from package vpopmail-toaster-5.4.17-1.3.7.x86_64 (many other lines like that) 1:vpopmail-toaster ### [ 50%] I've also try another method: rpm -Uhv vpopmail-toaster*.src.rpm edited the vpopmail-toaster.spec (usually in /usr/src/redhat/SPECS/), change line 729 from "--enable-clear-passwd" to "--disable-clear-passwd" with a text editor. rpmbuild -bs vpopmail-toaster.spec that time it went to 100% 1:vpopmail-toaster ### [ 100%] but unfortunately it doesn't work. If i try to drop the pw_clear_passwd field from the vpopmail database i can't login with any account. If i try to create a new account ... error (if the field is drop) or it write the password in clear if the field isn't drop. Anyone can help me, please? Thanks!! A. - The first method (--with) does not work. The spec file needs to recognize these options, which it doesn't. The second method (editing the .spec file) is correct. After building the rpm from source though, you need to install the binary rpm that was produced by the rpmbuild run: # rpm -Uvh --replacepkgs vpopmail-toaster.*.rpm Be sure you're in the directory where you built the binary rpm when you do this. -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail field problem
Nice! So ... I need to recompile vpopmail package with the right option then move it somewhere qtp-newmodel needs and finally re-install all those packages with it? Question: Am I gonna lose any configuration? Such as domains, e-mails and everything related to? -- Cheers, Alberto. Il 15/10/2010 21.12, Eric Shubert ha scritto: Right. Packages which are dependent on vpopmail-toaster are: qmail-toaster qmailadmin-toaster courier-authlib-toaster courier-imap-toaster and these should be rebuilt and reinstalled. qtp-newmodel can do this easily for you. Removing clear text passwords has other implications as well. IIRC, some authentication methods require this. While I'm no proponent of storing passwords in clear text (it wouldn't bother me if the stock toaster removed them), I expect that removing them will take some doing. Nessun virus nel messaggio in arrivo. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3198 - Data di rilascio: 10/15/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3203 - Data di rilascio: 10/17/10 20:33:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail field problem
How do I know if was sucessfull? The only think I've got from the command was that: [r...@ser SRPMS]# rpm -Uvh --replacepkgs vpopmail-toaster-5.4.17-1.3.7.src.rpm 1:vpopmail-toaster ### [100%] It has been replace correctly? Il 15/10/2010 21.12, Eric Shubert ha scritto: Right. Packages which are dependent on vpopmail-toaster are: qmail-toaster qmailadmin-toaster courier-authlib-toaster courier-imap-toaster and these should be rebuilt and reinstalled. qtp-newmodel can do this easily for you. Removing clear text passwords has other implications as well. IIRC, some authentication methods require this. While I'm no proponent of storing passwords in clear text (it wouldn't bother me if the stock toaster removed them), I expect that removing them will take some doing. Nessun virus nel messaggio in arrivo. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3198 - Data di rilascio: 10/15/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3203 - Data di rilascio: 10/17/10 20:33:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail field problem
Oh :O thanks Eric. Btw are you sure qtp-newmodel will use my srpm package of vpopmail and will not rebuilt his own? thanks A. Il 18/10/2010 16.41, Eric Shubert ha scritto: You'll need to: .) modify the .spec to your needs .) create the source rpm (.srpm) package from the spec (rpmbuild -bs) .) put the .srpm package in /usr/src/qtp-upgrade/SRPMS/ .) run qtp-newmodel and select the package for rebuild. qtp-newmodel will automatically rebuild whatever's necessary, and install everything. On 10/18/2010 12:12 AM, Digital Instruments wrote: Nice! So ... I need to recompile vpopmail package with the right option then move it somewhere qtp-newmodel needs and finally re-install all those packages with it? Question: Am I gonna lose any configuration? Such as domains, e-mails and everything related to? -- Cheers, Alberto. Il 15/10/2010 21.12, Eric Shubert ha scritto: Right. Packages which are dependent on vpopmail-toaster are: qmail-toaster qmailadmin-toaster courier-authlib-toaster courier-imap-toaster and these should be rebuilt and reinstalled. qtp-newmodel can do this easily for you. Removing clear text passwords has other implications as well. IIRC, some authentication methods require this. While I'm no proponent of storing passwords in clear text (it wouldn't bother me if the stock toaster removed them), I expect that removing them will take some doing. Nessun virus nel messaggio in arrivo. Controllato da AVG -www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3198 - Data di rilascio: 10/15/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3203 - Data di rilascio: 10/17/10 20:33:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! Nessun virus nel messaggio in arrivo. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3204 - Data di rilascio: 10/18/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3204 - Data di rilascio: 10/18/10 08:34:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail field problem
Should I change vpopmail-toaster.spec file like that: line 584 /clear passwd = ON --enable-clear-passwd/ TO /clear passwd = OFF --disable-clear-passwd/ line 654 /--enable-clear-passwd/ TO /--disable-clear-passwd/ Thanks Cheers A. Il 18/10/2010 17.33, Eric Shubert ha scritto: qtp-newmodel will use whatever's in /usr/src/qtp-upgrade/SRPMS (unless you've changed the default location). If it doesn't find the source rpm there, it will download it from the web site. Just be sure that you use the latest vpopmail-toaster package, and keep the same version numbers in your spec file. Nessun virus nel messaggio in arrivo. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3204 - Data di rilascio: 10/18/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3205 - Data di rilascio: 10/18/10 20:34:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail field problem
It works with --disable-clear-passwd everything solved the field has gone. Thanks to everyone helped me. :) Now I have another question: How does it work SSL/TLS with qmailtoaster? Cheers, A. Il 19/10/2010 16.36, Eric Shubert ha scritto: On 10/19/2010 12:40 AM, Digital Instruments wrote: Should I change vpopmail-toaster.spec file like that: line 584 /clear passwd = ON --enable-clear-passwd/ TO /clear passwd = OFF --disable-clear-passwd/ line 654 /--enable-clear-passwd/ TO /--disable-clear-passwd/ Thanks Cheers A. I'm not familiar with vpopmail's configure commmand off the top of my head. A little googling though appears to indicate that --enable-clear-passwd=n would be the correct syntax. I don't see "disable" being used anywhere. http://www.inter7.com/vpopmail/install.txt http://www.inter7.com/vpopmail/FAQ.txt Nessun virus nel messaggio in arrivo. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3206 - Data di rilascio: 10/19/10 08:34:00 Nessun virus nel messaggio in uscita. Controllato da AVG - www.avg.com Versione: 9.0.862 / Database dei virus: 271.1.1/3206 - Data di rilascio: 10/19/10 08:34:00 - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail system quota for domain
On 10/19/2010 04:34 AM, Igor Smitran wrote: Since vpopmail domain quota is not working properly i decided to RTFM and found something interesting: If you want to implement a quota for a whole domain, you have 2 options. You can either put the domain under a unique system id and implement system quotas, or (as of 5.3.18) you can use a non-system domain quota. To implement the former, just use 'vadddomain -u ' and set the system quota for that user. I decided to give it a try and here is the result: 1. useradd test.com -d /home/vpopmail -s /sbin/nologin -M 2. vadddomain -u test.com test.com 3. user is created, given uid 1000 and gid 1000 4. domain is created with owner/group test.com/test.com 5. postmaster homedir is created with owner/group test.com/test.com 6. vdominfo displays correct info sending mail from telnet goes well but mail never delivers, stays in queue. after reading logs i see that directory permissions are stopping mail delivery: delivery 1: deferral: Unable_to_switch_to_/home/vpopmail/domains/test.com:_access_denied._(#4.3.0)/ Has anyone tried to do this? What would be the right way to do this and have system quotas work correctly? - I think you would need to utilize *nix group permission capabilities to make this work. The vpopmail user would need to be able to access/update all of the directories in the /home/vpopmail/domains branch. Either that, or if you have only one domain, put the system quota on the vpopmail user. It'd be simple enough to add test.com to the vchkpw group and turn on group permissions under the /home/vpopmail/domains branch. You'd also need to be sure that vpopmail creates things under that branch with group bits set on (umask). If you're using IMAP, that complicates things further. Unless you absolutely need to have the capability ASAP, I'd wait for v5.5 of vpopmail, which reportedly has fixed quotas. Quotas also work better in v5.4.32, but I'm not confident that they're fixed entirely in that version. TTBOMK vpopmail 5.5 is due to be included with QMT v2. Or you could try vpopmail v5.5 with the existing QMT. I think your efforts doing so would be more fruitful in the long run than trying to implement system quotas. -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail --disable-many-domains option
On 05/28/2011 08:19 AM, Jake Vickers wrote: On 05/27/2011 12:10 AM, Eric Shubert wrote: On 05/26/2011 07:55 PM, Jake Vickers wrote: > On 05/26/2011 05:41 PM, Eric Shubert wrote: >> >> I would like to see QMT get to a single-table configuration for >> vpopmail/mysql. Is that never going to happen, or perhaps happen >> with 5.5? It might be best to leave vpopmail at 5.4.x with QMTv2.0, >> then upgrade to 5.5 with QMTv2.x, and go to single-table domains at >> that time. Just a thought. >> > > I haven't given it much thought - anyone care to test what the > performance impact is by going to a single table? Is there any? > I know we hijacked this thread, so let's spin off a new one. > - Apologies for the hijack. I just seem to recall this being discussed a bit, some time ago, and concluding (perhaps with no consensus) that having all domains in a single table made more sense. So I'm still curious as to what you think the benefits are. Segregating your data into multiple tables was always the way I learned to obtain performance. The nature of the requests from QMT are probably not those that would require any performance tuning - the only one I've ever run into is the default number of connections. So I'm willing to table that point if there are other mitigating factors. I agree that performance should not be a consideration in this case. If that's the reason why this option was used (or even developed) in the first place, I think it was a poor choice. The amount of data we're talking about is probably all cached anyhow, even with a fairly large number of domains and users. So what are the advantages/benefits you are thinking will be gained from a single table? Various reasons, most of which were identified in previous discussions I linked to in the first post on this thread. If you're looking for a reason why this *must* (or even strongly should) be done, I don't think there is one. The possibility or actuality of its removal is probably the best reason. The strongest reason to me (most irritating aspect anywise) is that it's just bad design. For instance, in an accounting database, I wouldn't expect to see a separate invoice table for each customer. Would you? It sort of boils down to the question of whether a domain name belongs to the realm of the database schema or the realm of the user data. I think the later is most appropriate, even proper. BL, I think removing the option makes the vpopmail database a little less convoluted than it presently is. Not a big deal though. -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail --disable-many-domains option
On 06/07/2011 12:02 AM, Jake Vickers wrote: On 05/29/2011 03:32 AM, Martin Waschbüsch IT-Dienstleistungen wrote: Hi Jake, Am 28.05.2011 um 17:19 schrieb Jake Vickers: So I'm still curious as to what you think the benefits are. Segregating your data into multiple tables was always the way I learned to obtain performance. The nature of the requests from QMT are probably not those that would require any performance tuning - the only one I've ever run into is the default number of connections. So I'm willing to table that point if there are other mitigating factors. So what are the advantages/benefits you are thinking will be gained from a single table? I agree with Eric that it probably will not make much of a difference with regards to performance. However, a lot of applications that might want to have access to the email user database are not all that flexible and do not support having different domains in different tables. E.g. using courier-auth with mysql or SOGo with mysql-backend, etc. There are other examples. For my own use, I have written an accounting backend that also cycles through domains and users, etc. to produce detail-information to be attached to invoices and that, too, is just way easier when having all in one table. Granted, that may be simplistic design on the parts of those programs, but hey, it works and it is way easier to recompile vpopmail to achieve compatibility than patch those programs. Also, whenever there is any database schema change in order for vpopmail to be upgraded, it is much easier to upgrade that one table than to find all the tables that hold domains and path those. Last but not least, mysql (and other databases) have length-limitations for domain names. I always wondered, but never tried, what would happen if I added a domain with a name longer than 'max-table-name-length' to the database? I think the current limit for mysql is 32 chars and domain names can be longer. I have never tried a FQDN longer than 32 chars - RFC 1035 implies (if I'm reading it correctly) of 255 chars: 2.3.4. Size limits Various objects and parameters in the DNS have size limits. They are listed below. Some could be easily changed, others are more fundamental. labels 63 octets or less names 255 octets or less TTL positive values of a signed 32 bit number. UDP messages 512 octets or less 3. DOMAIN NAME SPACE AND RR DEFINITIONS 3.1. Name space definitions Domain names in messages are expressed in terms of a sequence of labels. Each label is represented as a one octet length field followed by that number of octets. Since every domain name ends with the null label of the root, a domain name is terminated by a length byte of zero. The high order two bits of every length octet must be zero, and the remaining six bits of the length field limit the label to 63 octets or less. To simplify implementations, the total length of a domain name (i.e., label octets and label length octets) is restricted to 255 octets or less. Although labels can contain any 8 bit values in octets that make up a label, it is strongly recommended that labels follow the preferred syntax described elsewhere in this memo, which is compatible with existing host naming conventions. Name servers and resolvers must compare labels in a case-insensitive manner (i.e., A=a), assuming ASCII with zero parity. Non-alphabetic codes must match exactly. Should be easy enough to change in 2.x. Thanks for the app examples for the vpopmail DB schema. So the change seems to hinge around opinion and interop with other applications. I went back over the "helper apps" and can't find anywhere in the code where a change may make something currently supplied stop working, so I'll roll the change into the 2.x test and we'll see what shakes loose. - Thanks Jake. This database conversion may be a little tricky to automate entirely. I'm thinking there'd need to be a list of some sort identifying each database table that needs to be converted/consolidated. Might be able to write a query of database tables (metadata) to determine them all. Do we have any MySQL experts here that can assist with such automation? -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail database contains plaintext password
On 09/25/2012 01:24 PM, Peter Peterse wrote:
Hello,
the table {domainname} in the database vpopmail contains a column
pw_clear_passwd.
What is the correct way to remove this column out this database?
I'm alway deploy qmail-toaster by the qtp-newmodel and it works
fantastic, but such security issue stays in the database or is there an
option in qtp-newmodel to remove this feature?
Thanks for your reply.
Peter Peterse
-
No qtp-newmodel option for this. We'll be removing clear passwords from
the database in the stock QMT in a future release. There are a few other
database changes we intend to make at the same time, one of which is to
not have separate domain tables. This release is planned to be right
after the Cos6 compatible release. I'm not committing to any dates, but
this capability feels like year end or so at this point.
These aspects are controlled by the config command for vpopmail. You'll
need to rebuild the package appropriately (by editing the .spec file),
and modify the database yourself. FWIW, this conversion will be
automated when the stock QMT gets it. If you happen to do this before
the stock version, please post the sql commands for the database update
(so I won't have to look them up!).
Thanks Peter.
--
-Eric 'shubes'
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail system quota for domain
On 10/19/2010 4:57 PM, Eric Shubert wrote: I think you would need to utilize *nix group permission capabilities to make this work. The vpopmail user would need to be able to access/update all of the directories in the /home/vpopmail/domains branch. Either that, or if you have only one domain, put the system quota on the vpopmail user. It'd be simple enough to add test.com to the vchkpw group and turn on group permissions under the /home/vpopmail/domains branch. You'd also need to be sure that vpopmail creates things under that branch with group bits set on (umask). If you're using IMAP, that complicates things further. Unless you absolutely need to have the capability ASAP, I'd wait for v5.5 of vpopmail, which reportedly has fixed quotas. Quotas also work better in v5.4.32, but I'm not confident that they're fixed entirely in that version. TTBOMK vpopmail 5.5 is due to be included with QMT v2. Or you could try vpopmail v5.5 with the existing QMT. I think your efforts doing so would be more fruitful in the long run than trying to implement system quotas. That was my conclusion too. I was thinking of ACL for vpopmail user. I will have to set ACL manualy but since i am the administrator that wont be too hard. Also, i will try onchange feature to set ACL during domain creation. Will let you know of the results. I will wait for 5.5 to be stable before switching to it. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail system quota for domain
Il 19/10/2010 21:47, Igor Smitran ha scritto: On 10/19/2010 4:57 PM, Eric Shubert wrote: I think you would need to utilize *nix group permission capabilities to make this work. The vpopmail user would need to be able to access/update all of the directories in the /home/vpopmail/domains branch. Either that, or if you have only one domain, put the system quota on the vpopmail user. It'd be simple enough to add test.com to the vchkpw group and turn on group permissions under the /home/vpopmail/domains branch. You'd also need to be sure that vpopmail creates things under that branch with group bits set on (umask). If you're using IMAP, that complicates things further. Unless you absolutely need to have the capability ASAP, I'd wait for v5.5 of vpopmail, which reportedly has fixed quotas. Quotas also work better in v5.4.32, but I'm not confident that they're fixed entirely in that version. TTBOMK vpopmail 5.5 is due to be included with QMT v2. Or you could try vpopmail v5.5 with the existing QMT. I think your efforts doing so would be more fruitful in the long run than trying to implement system quotas. That was my conclusion too. I was thinking of ACL for vpopmail user. I will have to set ACL manualy but since i am the administrator that wont be too hard. Also, i will try onchange feature to set ACL during domain creation. Will let you know of the results. I will wait for 5.5 to be stable before switching to it. I'm following a different way, with system quotas. When I need a domain quota, I create another user, which has the same user UID of vpopmail user, and different group GID. Then I set quotas for that GID. So, any vpopmail process can deliver to that mailbox, and quotas are computed against different groups. Regards, Tonino -- in...@zioniInterazioni di Antonio Nati http://www.interazioni.it to...@interazioni.it - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail-5.4.33, qmailadmin-1.2.16, vqadmin-2.3.7 upgrades
On 08/05/2012 02:52 PM, Philip Nix Guru wrote: On 08/05/2012 09:55 PM, Eric Shubert wrote: The subject software upgrades for QMT are now available. These long awaited upgrades are seriously overdue, as QMT has been using the same version of vpopmail since I built my first QMT over 6 years ago. I'm happy to say that this brings QMT up to date with all of the upstream software (TTBOMK - someone please notify if something newer is out there), and completes work on v1.4.x until such time as another upstream update becomes available. If I'm lucky, QMT v1.5.0 (CentOS 6.x compatibility) will be available before then. The recommended upgrade procedure is as follows: # yum update qmailtoaster-plus # qtp-newmodel If you're running the QTP version of dovecot: # yum update dovecot If you're running spamdyke (you should be if you're not): # qtp-install-spamdyke # service qmail restart If you choose to do things the hard way (manually), here are some notes off the top of my head. In addition to the 3 vpopmail related packages, the following packages should be rebuilt and reinstalled (qtp-newmodel will do this automatically): qmail-toaster courier-authlib-toaster courier-imap-toaster If you're running a dovecot version that you built yourself, you should rebuild and reinstall this as well after installing vpopmail. There are vpopmail database changes required by vpopmail-5.4.18+. You should run the qtp-convert script which will do them for you (qtp-newmodel does this as well). TTBOMK, all problems with vqadmin have been fixed. If you have a problem with it, let us know and we'll see if it can't be fixed. Likewise with vpopmail and quotas. There might be some database fixing that needs to be done to put things in sync for you, but we can cross those bridges as they come. As always, if you have any problems with this, please post here. Thanks to everyone who's helped along the way with this, especially our own Bharath, and Matt at inter7 (the present vpopmail maintainer). That's great usually I do compile all manually or even mod a bit the spec files but for once I just started the qtp-newmodel was for updating a "normal" not modified qmt Well I guess I ll have to do it manually :) . qtp-build-rpms v0.3.5 qtp-remove-pkgs v0.3.1 REMOVED control-panel-toaster from sandbox (not for real) Building daemontools-toaster-0.76-1.3.6 ... Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... qtp-build-rpms - binary rpm not found for daemontools-toaster-0.76-1.3.6 qtp-build-rpms - Script Error - aborting. Build failed, Exiting. Wrote: /root/src/rpm/RPMS/x86_64/daemontools-toaster-0.76-1.3.6.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + cd daemontools-0.76 + '[' -n /var/tmp/daemontools-toaster-0.76 -a /var/tmp/daemontools-toaster-0.76 '!=' / ']' + rm -rf /var/tmp/daemontools-toaster-0.76 + '[' -d /root/src/rpm/BUILD/daemontools-0.76 ']' + rm -rf /root/src/rpm/BUILD/daemontools-0.76 + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + rm -rf daemontools-0.76 + exit 0 Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... Conclusion Then script is not handling .rpmmacros env variables that's a fault in my opinion Any idea why it put the rpm in /root/src/ instead of /usr/src/? That's appears to me to be the problem. What does # qtp-whatami show? It shouldn't be tough to fix this, even though your setup isn't apparently typical. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail-5.4.33, qmailadmin-1.2.16, vqadmin-2.3.7 upgrades
On 08/06/2012 06:07 AM, Dan McAllister wrote: On 8/6/2012 4:30 AM, Philip wrote: On 8/6/2012 12:10 AM, Eric Shubert wrote: On 08/05/2012 02:52 PM, Philip Nix Guru wrote: On 08/05/2012 09:55 PM, Eric Shubert wrote: The subject software upgrades for QMT are now available. These long awaited upgrades are seriously overdue, as QMT has been using the same version of vpopmail since I built my first QMT over 6 years ago. I'm happy to say that this brings QMT up to date with all of the upstream software (TTBOMK - someone please notify if something newer is out there), and completes work on v1.4.x until such time as another upstream update becomes available. If I'm lucky, QMT v1.5.0 (CentOS 6.x compatibility) will be available before then. The recommended upgrade procedure is as follows: # yum update qmailtoaster-plus # qtp-newmodel If you're running the QTP version of dovecot: # yum update dovecot If you're running spamdyke (you should be if you're not): # qtp-install-spamdyke # service qmail restart If you choose to do things the hard way (manually), here are some notes off the top of my head. In addition to the 3 vpopmail related packages, the following packages should be rebuilt and reinstalled (qtp-newmodel will do this automatically): qmail-toaster courier-authlib-toaster courier-imap-toaster If you're running a dovecot version that you built yourself, you should rebuild and reinstall this as well after installing vpopmail. There are vpopmail database changes required by vpopmail-5.4.18+. You should run the qtp-convert script which will do them for you (qtp-newmodel does this as well). TTBOMK, all problems with vqadmin have been fixed. If you have a problem with it, let us know and we'll see if it can't be fixed. Likewise with vpopmail and quotas. There might be some database fixing that needs to be done to put things in sync for you, but we can cross those bridges as they come. As always, if you have any problems with this, please post here. Thanks to everyone who's helped along the way with this, especially our own Bharath, and Matt at inter7 (the present vpopmail maintainer). That's great usually I do compile all manually or even mod a bit the spec files but for once I just started the qtp-newmodel was for updating a "normal" not modified qmt Well I guess I ll have to do it manually :) . qtp-build-rpms v0.3.5 qtp-remove-pkgs v0.3.1 REMOVED control-panel-toaster from sandbox (not for real) Building daemontools-toaster-0.76-1.3.6 ... Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... qtp-build-rpms - binary rpm not found for daemontools-toaster-0.76-1.3.6 qtp-build-rpms - Script Error - aborting. Build failed, Exiting. Wrote: /root/src/rpm/RPMS/x86_64/daemontools-toaster-0.76-1.3.6.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + cd daemontools-0.76 + '[' -n /var/tmp/daemontools-toaster-0.76 -a /var/tmp/daemontools-toaster-0.76 '!=' / ']' + rm -rf /var/tmp/daemontools-toaster-0.76 + '[' -d /root/src/rpm/BUILD/daemontools-0.76 ']' + rm -rf /root/src/rpm/BUILD/daemontools-0.76 + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + rm -rf daemontools-0.76 + exit 0 Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... Conclusion Then script is not handling .rpmmacros env variables that's a fault in my opinion Any idea why it put the rpm in /root/src/ instead of /usr/src/? That's appears to me to be the problem. What does # qtp-whatami show? It shouldn't be tough to fix this, even though your setup isn't apparently typical. Hey :) sure I know heheh, I am always using .rpmmacros to define where I want my rpms I am building rpms for different projects and I want mine in my homedir not in the usual /usr/src before I validate them for release. It is is a typical way to define by user where to store . But no worry I can disable it when using qtp-newmodel, just passing the infos for those who may get that error Thx for your great work Just an FYI -- that is the DEFAULT behavior of rpmbuild in RHEL/COS 6! The normal build location becomes /root/rpmbuild/* Dan -- That did ring a bell after I sent the reply. Thanks for the confirmation, Dan. I need to modify qtp-whatami for this. Philip, you can change qtp-whatami to set BUILD_DIR to whatever your preference is. Since I have to change qtp-whatami anyhow for COS6, if you post the format of your .rpmmacros (hidden file in /root/ I'm presuming, yes?) I can have qtp-whatami check for this, and set the variable accordingly. Thanks. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail-5.4.33, qmailadmin-1.2.16, vqadmin-2.3.7 upgrades
On 08/06/2012 10:21 AM, Philip Nix Guru wrote: yes .rpmmacros is in the root of the user's dir # cat .rpmmacros %_topdir /root/src/rpm # ls /root/src/rpm/ BUILD RPMS SOURCES SPECS SRPMS Thanks. I'll get this done with the next QTP release. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: vpopmail-5.4.33, qmailadmin-1.2.16, vqadmin-2.3.7 upgrades
On 08/15/2012 08:59 AM, Aleksander Podsiadły wrote: Dnia 2012-08-05, nie o godzinie 12:55 -0700, Eric Shubert pisze: If you're running the QTP version of dovecot: # yum update dovecot I was on the vacation, so I readed it today. :) After update (I'm running Dovecot): service qmail stop rm -rf /var/qmail/supervise/pop3 service qmail start I have touched a /var/qmail/supervise/pop3/down file, so it simply stays down. ;) qmail's pop3 will go away soon enough (when dovecot becomes official). IMHO most of us have dovecot compiled from source, not from binary repository. http://packages.atrpms.net/dist/ That's totally up to you. From what I've seen, most pre-built dovecot packages are not configured for vpopmail. The qtp version is ready for QMT. Making it "official" and seamlessly getting rid of qmail-pop3d and courier packages is yet to be done. I don't think we're too far from it though. Perhaps by the end of the year, but don't hold me to that. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: vpopmail-5.4.33, qmailadmin-1.2.16, vqadmin-2.3.7 upgrades
On 8/6/2012 12:10 AM, Eric Shubert wrote: On 08/05/2012 02:52 PM, Philip Nix Guru wrote: On 08/05/2012 09:55 PM, Eric Shubert wrote: The subject software upgrades for QMT are now available. These long awaited upgrades are seriously overdue, as QMT has been using the same version of vpopmail since I built my first QMT over 6 years ago. I'm happy to say that this brings QMT up to date with all of the upstream software (TTBOMK - someone please notify if something newer is out there), and completes work on v1.4.x until such time as another upstream update becomes available. If I'm lucky, QMT v1.5.0 (CentOS 6.x compatibility) will be available before then. The recommended upgrade procedure is as follows: # yum update qmailtoaster-plus # qtp-newmodel If you're running the QTP version of dovecot: # yum update dovecot If you're running spamdyke (you should be if you're not): # qtp-install-spamdyke # service qmail restart If you choose to do things the hard way (manually), here are some notes off the top of my head. In addition to the 3 vpopmail related packages, the following packages should be rebuilt and reinstalled (qtp-newmodel will do this automatically): qmail-toaster courier-authlib-toaster courier-imap-toaster If you're running a dovecot version that you built yourself, you should rebuild and reinstall this as well after installing vpopmail. There are vpopmail database changes required by vpopmail-5.4.18+. You should run the qtp-convert script which will do them for you (qtp-newmodel does this as well). TTBOMK, all problems with vqadmin have been fixed. If you have a problem with it, let us know and we'll see if it can't be fixed. Likewise with vpopmail and quotas. There might be some database fixing that needs to be done to put things in sync for you, but we can cross those bridges as they come. As always, if you have any problems with this, please post here. Thanks to everyone who's helped along the way with this, especially our own Bharath, and Matt at inter7 (the present vpopmail maintainer). That's great usually I do compile all manually or even mod a bit the spec files but for once I just started the qtp-newmodel was for updating a "normal" not modified qmt Well I guess I ll have to do it manually :) . qtp-build-rpms v0.3.5 qtp-remove-pkgs v0.3.1 REMOVED control-panel-toaster from sandbox (not for real) Building daemontools-toaster-0.76-1.3.6 ... Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... qtp-build-rpms - binary rpm not found for daemontools-toaster-0.76-1.3.6 qtp-build-rpms - Script Error - aborting. Build failed, Exiting. Wrote: /root/src/rpm/RPMS/x86_64/daemontools-toaster-0.76-1.3.6.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + cd daemontools-0.76 + '[' -n /var/tmp/daemontools-toaster-0.76 -a /var/tmp/daemontools-toaster-0.76 '!=' / ']' + rm -rf /var/tmp/daemontools-toaster-0.76 + '[' -d /root/src/rpm/BUILD/daemontools-0.76 ']' + rm -rf /root/src/rpm/BUILD/daemontools-0.76 + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + rm -rf daemontools-0.76 + exit 0 Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... Conclusion Then script is not handling .rpmmacros env variables that's a fault in my opinion Any idea why it put the rpm in /root/src/ instead of /usr/src/? That's appears to me to be the problem. What does # qtp-whatami show? It shouldn't be tough to fix this, even though your setup isn't apparently typical. Hey :) sure I know heheh, I am always using .rpmmacros to define where I want my rpms I am building rpms for different projects and I want mine in my homedir not in the usual /usr/src before I validate them for release. It is is a typical way to define by user where to store . But no worry I can disable it when using qtp-newmodel, just passing the infos for those who may get that error Thx for your great work
Re: [qmailtoaster] Re: vpopmail-5.4.33, qmailadmin-1.2.16, vqadmin-2.3.7 upgrades
On 8/6/2012 4:30 AM, Philip wrote: On 8/6/2012 12:10 AM, Eric Shubert wrote: On 08/05/2012 02:52 PM, Philip Nix Guru wrote: On 08/05/2012 09:55 PM, Eric Shubert wrote: The subject software upgrades for QMT are now available. These long awaited upgrades are seriously overdue, as QMT has been using the same version of vpopmail since I built my first QMT over 6 years ago. I'm happy to say that this brings QMT up to date with all of the upstream software (TTBOMK - someone please notify if something newer is out there), and completes work on v1.4.x until such time as another upstream update becomes available. If I'm lucky, QMT v1.5.0 (CentOS 6.x compatibility) will be available before then. The recommended upgrade procedure is as follows: # yum update qmailtoaster-plus # qtp-newmodel If you're running the QTP version of dovecot: # yum update dovecot If you're running spamdyke (you should be if you're not): # qtp-install-spamdyke # service qmail restart If you choose to do things the hard way (manually), here are some notes off the top of my head. In addition to the 3 vpopmail related packages, the following packages should be rebuilt and reinstalled (qtp-newmodel will do this automatically): qmail-toaster courier-authlib-toaster courier-imap-toaster If you're running a dovecot version that you built yourself, you should rebuild and reinstall this as well after installing vpopmail. There are vpopmail database changes required by vpopmail-5.4.18+. You should run the qtp-convert script which will do them for you (qtp-newmodel does this as well). TTBOMK, all problems with vqadmin have been fixed. If you have a problem with it, let us know and we'll see if it can't be fixed. Likewise with vpopmail and quotas. There might be some database fixing that needs to be done to put things in sync for you, but we can cross those bridges as they come. As always, if you have any problems with this, please post here. Thanks to everyone who's helped along the way with this, especially our own Bharath, and Matt at inter7 (the present vpopmail maintainer). That's great usually I do compile all manually or even mod a bit the spec files but for once I just started the qtp-newmodel was for updating a "normal" not modified qmt Well I guess I ll have to do it manually :) . qtp-build-rpms v0.3.5 qtp-remove-pkgs v0.3.1 REMOVED control-panel-toaster from sandbox (not for real) Building daemontools-toaster-0.76-1.3.6 ... Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... qtp-build-rpms - binary rpm not found for daemontools-toaster-0.76-1.3.6 qtp-build-rpms - Script Error - aborting. Build failed, Exiting. Wrote: /root/src/rpm/RPMS/x86_64/daemontools-toaster-0.76-1.3.6.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + cd daemontools-0.76 + '[' -n /var/tmp/daemontools-toaster-0.76 -a /var/tmp/daemontools-toaster-0.76 '!=' / ']' + rm -rf /var/tmp/daemontools-toaster-0.76 + '[' -d /root/src/rpm/BUILD/daemontools-0.76 ']' + rm -rf /root/src/rpm/BUILD/daemontools-0.76 + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + rm -rf daemontools-0.76 + exit 0 Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... Conclusion Then script is not handling .rpmmacros env variables that's a fault in my opinion Any idea why it put the rpm in /root/src/ instead of /usr/src/? That's appears to me to be the problem. What does # qtp-whatami show? It shouldn't be tough to fix this, even though your setup isn't apparently typical. Hey :) sure I know heheh, I am always using .rpmmacros to define where I want my rpms I am building rpms for different projects and I want mine in my homedir not in the usual /usr/src before I validate them for release. It is is a typical way to define by user where to store . But no worry I can disable it when using qtp-newmodel, just passing the infos for those who may get that error Thx for your great work Just an FYI -- that is the DEFAULT behavior of rpmbuild in RHEL/COS 6! The normal build location becomes /root/rpmbuild/* Dan -- IT4SOHO, LLC PO Box 507 St. Petersburg, FL 33731-0507 CALL TOLL FREE: 877-IT4SOHO We have support plans for QMail!
Re: [qmailtoaster] Re: vpopmail-5.4.33, qmailadmin-1.2.16, vqadmin-2.3.7 upgrades
On 08/06/2012 06:29 PM, Eric Shubert wrote: On 08/06/2012 06:07 AM, Dan McAllister wrote: On 8/6/2012 4:30 AM, Philip wrote: On 8/6/2012 12:10 AM, Eric Shubert wrote: On 08/05/2012 02:52 PM, Philip Nix Guru wrote: On 08/05/2012 09:55 PM, Eric Shubert wrote: The subject software upgrades for QMT are now available. These long awaited upgrades are seriously overdue, as QMT has been using the same version of vpopmail since I built my first QMT over 6 years ago. I'm happy to say that this brings QMT up to date with all of the upstream software (TTBOMK - someone please notify if something newer is out there), and completes work on v1.4.x until such time as another upstream update becomes available. If I'm lucky, QMT v1.5.0 (CentOS 6.x compatibility) will be available before then. The recommended upgrade procedure is as follows: # yum update qmailtoaster-plus # qtp-newmodel If you're running the QTP version of dovecot: # yum update dovecot If you're running spamdyke (you should be if you're not): # qtp-install-spamdyke # service qmail restart If you choose to do things the hard way (manually), here are some notes off the top of my head. In addition to the 3 vpopmail related packages, the following packages should be rebuilt and reinstalled (qtp-newmodel will do this automatically): qmail-toaster courier-authlib-toaster courier-imap-toaster If you're running a dovecot version that you built yourself, you should rebuild and reinstall this as well after installing vpopmail. There are vpopmail database changes required by vpopmail-5.4.18+. You should run the qtp-convert script which will do them for you (qtp-newmodel does this as well). TTBOMK, all problems with vqadmin have been fixed. If you have a problem with it, let us know and we'll see if it can't be fixed. Likewise with vpopmail and quotas. There might be some database fixing that needs to be done to put things in sync for you, but we can cross those bridges as they come. As always, if you have any problems with this, please post here. Thanks to everyone who's helped along the way with this, especially our own Bharath, and Matt at inter7 (the present vpopmail maintainer). That's great usually I do compile all manually or even mod a bit the spec files but for once I just started the qtp-newmodel was for updating a "normal" not modified qmt Well I guess I ll have to do it manually :) . qtp-build-rpms v0.3.5 qtp-remove-pkgs v0.3.1 REMOVED control-panel-toaster from sandbox (not for real) Building daemontools-toaster-0.76-1.3.6 ... Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... qtp-build-rpms - binary rpm not found for daemontools-toaster-0.76-1.3.6 qtp-build-rpms - Script Error - aborting. Build failed, Exiting. Wrote: /root/src/rpm/RPMS/x86_64/daemontools-toaster-0.76-1.3.6.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + cd daemontools-0.76 + '[' -n /var/tmp/daemontools-toaster-0.76 -a /var/tmp/daemontools-toaster-0.76 '!=' / ']' + rm -rf /var/tmp/daemontools-toaster-0.76 + '[' -d /root/src/rpm/BUILD/daemontools-0.76 ']' + rm -rf /root/src/rpm/BUILD/daemontools-0.76 + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.97447 + umask 022 + cd /root/src/rpm/BUILD + rm -rf daemontools-0.76 + exit 0 Installing daemontools-toaster-0.76-1.3.6 in the sandbox ... Conclusion Then script is not handling .rpmmacros env variables that's a fault in my opinion Any idea why it put the rpm in /root/src/ instead of /usr/src/? That's appears to me to be the problem. What does # qtp-whatami show? It shouldn't be tough to fix this, even though your setup isn't apparently typical. Hey :) sure I know heheh, I am always using .rpmmacros to define where I want my rpms I am building rpms for different projects and I want mine in my homedir not in the usual /usr/src before I validate them for release. It is is a typical way to define by user where to store . But no worry I can disable it when using qtp-newmodel, just passing the infos for those who may get that error Thx for your great work Just an FYI -- that is the DEFAULT behavior of rpmbuild in RHEL/COS 6! The normal build location becomes /root/rpmbuild/* Dan -- That did ring a bell after I sent the reply. Thanks for the confirmation, Dan. I need to modify qtp-whatami for this. Philip, you can change qtp-whatami to set BUILD_DIR to whatever your preference is. Since I have to change qtp-whatami anyhow for COS6, if you post the format of your .rpmmacros (hidden file in /root/ I'm presuming, yes?) I can have qtp-whatami check for this, and set the variable accordingly. Thanks. Hello Eric yes .rpmmacros is in the root of the user's dir # cat .rpmmacros %_topdir /root/src/rpm # ls /root/src/rpm/ BUILD RPMS SOURCES SPECS SRPMS
Re: [qmailtoaster] Re: vpopmail-5.4.33, qmailadmin-1.2.16, vqadmin-2.3.7 upgrades
On 8/6/2012 1:21 PM, Philip Nix Guru wrote: Hello Eric yes .rpmmacros is in the root of the user's dir # cat .rpmmacros %_topdir /root/src/rpm # ls /root/src/rpm/ BUILD RPMS SOURCES SPECS SRPMS Just my 2-cents worth... In RHEL/COS 6, the default build is ~/rpmbuild Dan McAllister -- IT4SOHO, LLC PO Box 507 St. Petersburg, FL 33731-0507 CALL TOLL FREE: 877-IT4SOHO We have support plans for QMail!
