RE: [qmailtoaster] Big problems after old-to-new qmt migrate
This exact same thing happened to me. The fix for me was to run /var/qmail/bin/qmail-newu. This did the trick for me. Although for me mail to the main domain worked, just not to virtual domains. Took me about 4 hours searching through the man pages at http://www.qmail.org/man/ EVERYONE HERE SHOULD HAVE A GOOD MIND NUMBING TOUR! Would make Jake's job a lot easier. :) Anyway that's my two cents. NAME qmail-newu - prepare address assignments for qmail-lspawn SYNOPSIS qmail-newu DESCRIPTION qmail-newu reads the assignments in /var/qmail/users/assign and writes them into /var/qmail/users/cdb in a binary format suited for quick access by qmail-lspawn. If there is a problem with users/assign, qmail-newu complains and leaves users/cdb alone. qmail-newu ensures that users/cdb is updated atomically, so qmail-lspawn never has to wait for qmail-newu to finish. However, qmail-newu makes no attempt to protect against two simultaneous updates of users/cdb. The binary users/cdb format is portable across machines. -Original Message- From: Patrick Ring [mailto:pr...@pringtech.net] Sent: Sunday, May 03, 2009 4:27 PM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] Big problems after old-to-new qmt migrate Is there a definitive way to tell what version the old server is? Thank you. -Original Message- From: Jake Vickers [mailto:j...@qmailtoaster.com] Sent: 2009-05-03 15:05 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Big problems after old-to-new qmt migrate Patrick Ring wrote: > Should it be able to restore a backup done from a very old version on > to a fresh loaded version? > > Depends on how old the old version is. If you look in the restore script you'll see there's some commands commented out. These were needed when I went from an old version to a newer one. The error you said you got about not being able to read a user's dir sounds like permission problems. Check to make sure 89:89 is free in your /etc/passwd, since vpopmail will want to use those UID/GIDs. If your older version did NOT user 89:89, you'll see the qmail-newu command in the resore script (commented out) as this will be needed to change the UID for vpopmail. This is mostly guessing though, without seeing the exact errors/logs. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database: 270.12.16/2094 - Release Date: 05/03/09 16:51:00 - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Big problems after old-to-new qmt migrate
Jake Vickers wrote: Patrick Ring wrote: I haven't seen any errors yet. Until the machinery became unstable, and we decided to update (finally), it had been working perfectly since we built the load over 4 years ago, so I've rather forgotten where to look for the logs that have any errors. I'm going to try to copy the queue files (to the old server) and run the utility shortly (now that I've put the old one back online successfully). On the new server, show us the /var/log/qmail/smtp/current and /var/log/qmail/send/current log files (or at least parts of them). This will help us begin to understand what may be wrong with the new installation. Since you have QTP installed, you can # qmlog smtp # qmlog send to view the logs in 'less'. You can copy and paste from there. :) -- -Eric 'shubes' - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Big problems after old-to-new qmt migrate
Patrick Ring wrote: I haven't seen any errors yet. Until the machinery became unstable, and we decided to update (finally), it had been working perfectly since we built the load over 4 years ago, so I've rather forgotten where to look for the logs that have any errors. I'm going to try to copy the queue files (to the old server) and run the utility shortly (now that I've put the old one back online successfully). On the new server, show us the /var/log/qmail/smtp/current and /var/log/qmail/send/current log files (or at least parts of them). This will help us begin to understand what may be wrong with the new installation. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
RE: [qmailtoaster] Big problems after old-to-new qmt migrate
I haven't seen any errors yet. Until the machinery became unstable, and we decided to update (finally), it had been working perfectly since we built the load over 4 years ago, so I've rather forgotten where to look for the logs that have any errors. I'm going to try to copy the queue files (to the old server) and run the utility shortly (now that I've put the old one back online successfully). Thank you, Patrick Ring -Original Message- From: Jake Vickers [mailto:j...@qmailtoaster.com] Sent: 2009-05-03 18:49 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Big problems after old-to-new qmt migrate Patrick Ring wrote: > While I'm in the process of 'rolling-back' to my old qmail server, I > have 461 items in the mail queue of what was to be the new > qmailtoaster server. Is there an easy way of routing those to the old > server directly? > ...thus far I added all of my domains to the smtproutes with pointers > to one of the IP's of the old qmt server. > Was this the correct thing to do? (I don't want to lose anything that > made it into the new queue). > > After I've transferred the queued items, I'll be rolling back the > snapshot of the new qmt server to just before I started this mess so I > can try again. > > You may be able to copy the queue items over and use one of the queue-repair tools (try queue-repair.py) to fix the inodes and it may deliver them. What error is it giving you when it tries to send the messages? We need to see some log clips - it may be a simple fix. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Big problems after old-to-new qmt migrate
Patrick Ring wrote: While I'm in the process of 'rolling-back' to my old qmail server, I have 461 items in the mail queue of what was to be the new qmailtoaster server. Is there an easy way of routing those to the old server directly? ...thus far I added all of my domains to the smtproutes with pointers to one of the IP's of the old qmt server. Was this the correct thing to do? (I don't want to lose anything that made it into the new queue). After I've transferred the queued items, I'll be rolling back the snapshot of the new qmt server to just before I started this mess so I can try again. You may be able to copy the queue items over and use one of the queue-repair tools (try queue-repair.py) to fix the inodes and it may deliver them. What error is it giving you when it tries to send the messages? We need to see some log clips - it may be a simple fix. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Big problems after old-to-new qmt migrate
Patrick Ring wrote: Is there a definitive way to tell what version the old server is? Thank you. rpm -qa | grep toaster | sort That will show you the versions of the Toaster packages you have installed. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
RE: [qmailtoaster] Big problems after old-to-new qmt migrate
While I'm in the process of 'rolling-back' to my old qmail server, I have 461 items in the mail queue of what was to be the new qmailtoaster server. Is there an easy way of routing those to the old server directly? ...thus far I added all of my domains to the smtproutes with pointers to one of the IP's of the old qmt server. Was this the correct thing to do? (I don't want to lose anything that made it into the new queue). After I've transferred the queued items, I'll be rolling back the snapshot of the new qmt server to just before I started this mess so I can try again. Thank you, Patrick Ring. -Original Message- From: Jake Vickers [mailto:j...@qmailtoaster.com] Sent: 2009-05-03 15:05 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Big problems after old-to-new qmt migrate Patrick Ring wrote: > Should it be able to restore a backup done from a very old version on > to a fresh loaded version? > > Depends on how old the old version is. If you look in the restore script you'll see there's some commands commented out. These were needed when I went from an old version to a newer one. The error you said you got about not being able to read a user's dir sounds like permission problems. Check to make sure 89:89 is free in your /etc/passwd, since vpopmail will want to use those UID/GIDs. If your older version did NOT user 89:89, you'll see the qmail-newu command in the resore script (commented out) as this will be needed to change the UID for vpopmail. This is mostly guessing though, without seeing the exact errors/logs. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
RE: [qmailtoaster] Big problems after old-to-new qmt migrate
Is there a definitive way to tell what version the old server is? Thank you. -Original Message- From: Jake Vickers [mailto:j...@qmailtoaster.com] Sent: 2009-05-03 15:05 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Big problems after old-to-new qmt migrate Patrick Ring wrote: > Should it be able to restore a backup done from a very old version on > to a fresh loaded version? > > Depends on how old the old version is. If you look in the restore script you'll see there's some commands commented out. These were needed when I went from an old version to a newer one. The error you said you got about not being able to read a user's dir sounds like permission problems. Check to make sure 89:89 is free in your /etc/passwd, since vpopmail will want to use those UID/GIDs. If your older version did NOT user 89:89, you'll see the qmail-newu command in the resore script (commented out) as this will be needed to change the UID for vpopmail. This is mostly guessing though, without seeing the exact errors/logs. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Big problems after old-to-new qmt migrate
Patrick Ring wrote: Should it be able to restore a backup done from a very old version on to a fresh loaded version? Depends on how old the old version is. If you look in the restore script you'll see there's some commands commented out. These were needed when I went from an old version to a newer one. The error you said you got about not being able to read a user's dir sounds like permission problems. Check to make sure 89:89 is free in your /etc/passwd, since vpopmail will want to use those UID/GIDs. If your older version did NOT user 89:89, you'll see the qmail-newu command in the resore script (commented out) as this will be needed to change the UID for vpopmail. This is mostly guessing though, without seeing the exact errors/logs. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Big problems after old-to-new qmt migrate
I believe so (yes), as long as the database schema hasn't changed. Can you tell which version is "very old"? Patrick Ring wrote: Should it be able to restore a backup done from a very old version on to a fresh loaded version? I have a snapshot from just after qtp being loaded and before migration attempts. Good. After I transfer the queue to the old server (so I can get mail online again for a short while), I'll roll back to that snapshot and take a screen cap or two when I try that again. Sounds good. Thank you. NP -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: 2009-05-03 14:31 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Big problems after old-to-new qmt migrate Patrick Ring wrote: The problem with qtp-newmodel was on the old server (VERY out of date ... QmailToaster from early 2005 (I don't know which version), and CentOS 4.2 [yum] upgraded to 4.7) was that it kept errorring out on building packages for clamav. When I told it to skip that (later attempt), it then wanted to install the kernel-smp-devel. So, after it fails again, I tried to do a basic 'yum install kernel-smp-devel' and get "Nothing to do". I went to DaagWieers and made sure my repos were up to date and tried again... "Nothing to do". By then I was just wanting to get a migration done (to the new, more stable equipment), so I started a backup in order to follow through with a restore (even though the versions are years apart). Backup seemed to work fine on the old server (CentOS 4.7 w/ QMT ~2005), but when I went to restore it to the new load of CentOS 5.2 and the latest QMT (loaded last month...recent qtp-newmodel), it got caught in a loop looking for something that it though didn't exist. It'd be nice you could reproduce this error (on a clean COS5 toaster) so we could fix whatever the problem is. qtp-restore doesn't have any issues that we're (I'm) aware of. After it showing this error repeatedly (didn't write it down) for :30, I killed it, restored a snapshot, and tried a manual migration. Thank you, Patrick Ring -- -Eric 'shubes' -- -Eric 'shubes' - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
RE: Re: [qmailtoaster] Big problems after old-to-new qmt migrate
Should it be able to restore a backup done from a very old version on to a fresh loaded version? I have a snapshot from just after qtp being loaded and before migration attempts. After I transfer the queue to the old server (so I can get mail online again for a short while), I'll roll back to that snapshot and take a screen cap or two when I try that again. Thank you. -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: 2009-05-03 14:31 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Big problems after old-to-new qmt migrate Patrick Ring wrote: > The problem with qtp-newmodel was on the old server (VERY out of date > ... QmailToaster from early 2005 (I don't know which version), and > CentOS 4.2 [yum] upgraded to 4.7) was that it kept errorring out on > building packages for clamav. When I told it to skip that (later > attempt), it then wanted to install the kernel-smp-devel. So, after > it fails again, I tried to do a basic 'yum install kernel-smp-devel' > and get "Nothing to do". I went to DaagWieers and made sure my repos > were up to date and tried again... "Nothing to do". By then I was > just wanting to get a migration done (to the new, more stable > equipment), so I started a backup in order to follow through with a > restore (even though the versions are years apart). > > Backup seemed to work fine on the old server (CentOS 4.7 w/ QMT > ~2005), but when I went to restore it to the new load of CentOS 5.2 > and the latest QMT (loaded last month...recent qtp-newmodel), it got > caught in a loop looking for something that it though didn't exist. It'd be nice you could reproduce this error (on a clean COS5 toaster) so we could fix whatever the problem is. qtp-restore doesn't have any issues that we're (I'm) aware of. > After it > showing this error repeatedly (didn't write it down) for :30, I killed > it, restored a snapshot, and tried a manual migration. > > Thank you, > Patrick Ring > -- -Eric 'shubes' - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Big problems after old-to-new qmt migrate
Patrick Ring wrote: The problem with qtp-newmodel was on the old server (VERY out of date ... QmailToaster from early 2005 (I don't know which version), and CentOS 4.2 [yum] upgraded to 4.7) was that it kept errorring out on building packages for clamav. When I told it to skip that (later attempt), it then wanted to install the kernel-smp-devel. So, after it fails again, I tried to do a basic 'yum install kernel-smp-devel' and get "Nothing to do". I went to DaagWieers and made sure my repos were up to date and tried again... "Nothing to do". By then I was just wanting to get a migration done (to the new, more stable equipment), so I started a backup in order to follow through with a restore (even though the versions are years apart). Backup seemed to work fine on the old server (CentOS 4.7 w/ QMT ~2005), but when I went to restore it to the new load of CentOS 5.2 and the latest QMT (loaded last month...recent qtp-newmodel), it got caught in a loop looking for something that it though didn't exist. It'd be nice you could reproduce this error (on a clean COS5 toaster) so we could fix whatever the problem is. qtp-restore doesn't have any issues that we're (I'm) aware of. After it showing this error repeatedly (didn't write it down) for :30, I killed it, restored a snapshot, and tried a manual migration. Thank you, Patrick Ring -- -Eric 'shubes' - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
RE: Re: [qmailtoaster] Big problems after old-to-new qmt migrate
The problem with qtp-newmodel was on the old server (VERY out of date ... QmailToaster from early 2005 (I don't know which version), and CentOS 4.2 [yum] upgraded to 4.7) was that it kept errorring out on building packages for clamav. When I told it to skip that (later attempt), it then wanted to install the kernel-smp-devel. So, after it fails again, I tried to do a basic 'yum install kernel-smp-devel' and get "Nothing to do". I went to DaagWieers and made sure my repos were up to date and tried again... "Nothing to do". By then I was just wanting to get a migration done (to the new, more stable equipment), so I started a backup in order to follow through with a restore (even though the versions are years apart). Backup seemed to work fine on the old server (CentOS 4.7 w/ QMT ~2005), but when I went to restore it to the new load of CentOS 5.2 and the latest QMT (loaded last month...recent qtp-newmodel), it got caught in a loop looking for something that it though didn't exist. After it showing this error repeatedly (didn't write it down) for :30, I killed it, restored a snapshot, and tried a manual migration. Thank you, Patrick Ring -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: 2009-05-03 13:38 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Big problems after old-to-new qmt migrate Patrick Ring wrote: > I've had a qmail toaster running problem-free (in a VMWare server) > since early 2005. However, since the older machine it has been on was > having recent problems I decided it would be good to migrate to a new > server (with a new qmailtoaster and OS). > > So, I loaded up a new CentOS 5.3 server on a ESXi host (mostly what I > run now), and successfully installed the latest Qmail-Toaster along > with Qmail-Toaster-Plus. > > I read that it is possible to copy over the configs/mysql/data from > old to new, and should have no problems, If you hadn't upgraded the old toaster at all, I doubt that this would work. Certainly not the safest way to go. > but I also read it was best to upgrade (qtp-newmodel) before doing so. It's always a good idea to run the latest release. > After pulling my hair out with several unsuccessful qtp-newmodel > attempts, What were the problems? qtp-newmodel is pretty solid, and has run many times on COS5.3, on virtual machines (VMware Server, but not ESXi that I know of, although that should be transparent). In addition, since you had built a fresh toaster, there should have been nothing for qtp-newmodel to do. > I decided to extract and copy over the following to the new > server: > /var/lib/squirrelmail/prefs/ > /usr/share/squirrelmail/plugins/ > /var/qmail/control/ > /usr/share/toaster/include/admin.pass > /usr/share/toaster/include/admin.htpasswd > /home/vpopmail/ (all dirs/subdirs) > Mysqldump of vpopmail > /var/qmail/users/assign > /var/qmail/users/cdb I would definitely not try to piecemeal a migration. qtp-backup and qtp-restore make migration pretty trivial. > I figured out that I needed to mod a couple of permissions and the "cdb" > file turned out to be important too, then I could easily log into the > admin-toaster web interface, and I could read mail via IMAP and/or > squirrelmail. Currently POP3 is not authenticating, but the bigger > problem is that mail seems to be stacking up in the queue and not > going to the respective inboxes. > > I've found that I also cannot "Read user mail" in the Webmin Qmail > interface (something I have been able to do as a diagnostic before). > It gives "You are not allowed to read email for any users on this system." > > I'm not really sure what to look at next. Help would be greatly > appreciated. I'd start over, and use qtp-backup and qtp-restore to migrate the data over. That's the only way you'll know you have a stock (and stable) toaster. > Thank you, > Patrick Ring > -- -Eric 'shubes' - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qma
Re: [qmailtoaster] Big problems after old-to-new qmt migrate
Patrick Ring wrote: I've had a qmail toaster running problem-free (in a VMWare server) since early 2005. However, since the older machine it has been on was having recent problems I decided it would be good to migrate to a new server (with a new qmailtoaster and OS). So, I loaded up a new CentOS 5.3 server on a ESXi host (mostly what I run now), and successfully installed the latest Qmail-Toaster along with Qmail-Toaster-Plus. I read that it is possible to copy over the configs/mysql/data from old to new, and should have no problems, If you hadn't upgraded the old toaster at all, I doubt that this would work. Certainly not the safest way to go. but I also read it was best to upgrade (qtp-newmodel) before doing so. It's always a good idea to run the latest release. After pulling my hair out with several unsuccessful qtp-newmodel attempts, What were the problems? qtp-newmodel is pretty solid, and has run many times on COS5.3, on virtual machines (VMware Server, but not ESXi that I know of, although that should be transparent). In addition, since you had built a fresh toaster, there should have been nothing for qtp-newmodel to do. I decided to extract and copy over the following to the new server: /var/lib/squirrelmail/prefs/ /usr/share/squirrelmail/plugins/ /var/qmail/control/ /usr/share/toaster/include/admin.pass /usr/share/toaster/include/admin.htpasswd /home/vpopmail/ (all dirs/subdirs) Mysqldump of vpopmail /var/qmail/users/assign /var/qmail/users/cdb I would definitely not try to piecemeal a migration. qtp-backup and qtp-restore make migration pretty trivial. I figured out that I needed to mod a couple of permissions and the "cdb" file turned out to be important too, then I could easily log into the admin-toaster web interface, and I could read mail via IMAP and/or squirrelmail. Currently POP3 is not authenticating, but the bigger problem is that mail seems to be stacking up in the queue and not going to the respective inboxes. I've found that I also cannot "Read user mail" in the Webmin Qmail interface (something I have been able to do as a diagnostic before). It gives "You are not allowed to read email for any users on this system." I'm not really sure what to look at next. Help would be greatly appreciated. I'd start over, and use qtp-backup and qtp-restore to migrate the data over. That's the only way you'll know you have a stock (and stable) toaster. Thank you, Patrick Ring -- -Eric 'shubes' - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
[qmailtoaster] Big problems after old-to-new qmt migrate
I've had a qmail toaster running problem-free (in a VMWare server) since early 2005. However, since the older machine it has been on was having recent problems I decided it would be good to migrate to a new server (with a new qmailtoaster and OS). So, I loaded up a new CentOS 5.3 server on a ESXi host (mostly what I run now), and successfully installed the latest Qmail-Toaster along with Qmail-Toaster-Plus. I read that it is possible to copy over the configs/mysql/data from old to new, and should have no problems, but I also read it was best to upgrade (qtp-newmodel) before doing so. After pulling my hair out with several unsuccessful qtp-newmodel attempts, I decided to extract and copy over the following to the new server: /var/lib/squirrelmail/prefs/ /usr/share/squirrelmail/plugins/ /var/qmail/control/ /usr/share/toaster/include/admin.pass /usr/share/toaster/include/admin.htpasswd /home/vpopmail/ (all dirs/subdirs) Mysqldump of vpopmail /var/qmail/users/assign /var/qmail/users/cdb I figured out that I needed to mod a couple of permissions and the "cdb" file turned out to be important too, then I could easily log into the admin-toaster web interface, and I could read mail via IMAP and/or squirrelmail. Currently POP3 is not authenticating, but the bigger problem is that mail seems to be stacking up in the queue and not going to the respective inboxes. I've found that I also cannot "Read user mail" in the Webmin Qmail interface (something I have been able to do as a diagnostic before). It gives "You are not allowed to read email for any users on this system." I'm not really sure what to look at next. Help would be greatly appreciated. Thank you, Patrick Ring - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
[qmailtoaster] New subscription - testing
Please disregard this, I'm simply testing to see if I've subscribed correctly. Thank you. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] migrating to spamdyke
DAVID wrote: I have the ip-in-rdns-cc-reject turned on and for the most part it is stopping 90% or better of my spam. I still have a few that are getting thru. Is it because the rdns cc code is not set in the abusive domain or is it because they are configured to imitate the us cc? TM Dave reject-ip-in-cc-rdns: Reject connections from servers with rDNS names* that contain their IP address and end in a two-character country code. * " In essence, this option is the same as using ip-in-rdns-keyword-blacklist-entry for every two-letter country code (e.g. .us). This option is not very useful for large servers or servers outside the United States. *As ICANN begins allowing arbitrary top-level domains, two-letter domains will no longer be a reliable way of detecting non-US servers. *" http://www.spamdyke.org/documentation/README.html#RDNS More important is DNS RBLs ( DNS Realtime Blackhole Lists) , check-dnsrbl= in spamdyke.conf. Constantin
