Re: [qmailtoaster] QMT migration problems

2006-04-28 Thread Jake Vickers 




Supriyo Banerjee wrote:

  
  
  
  
  Hi list,
   
  While trying to migrate
users from my old Qmailtoaster server
(containing around 10 domains) which was running on Redhat Liinux 9.0,
to a new
server running Centos 4.3, and the latest Qmail Toaster packages, I
have run
into some problems as described below:
   
  I used Jake’s backup
script to take the backup from
my old server, on which the UID:GID of vpopmail
was 7797:7797. Then I did a manual install of QMT on my new server
which was successful.
Then I transferred the ‘curlfile’
containing the backup of the old server
to the new server’s root
directory. Then from the home directory of my user account, as ‘root’
user, I executed the restore script (again from Jake’s site). I must
mention here that in Jake’s restore script, I had enabled the line that
converted the old aliases to the new format.
   
  I must also mention
here that the mysql root
password in my old server and the new server are not same. I guess
there is no
harm as such!? Likewise, initially, the vpopmail
da
  The
‘/var/log/qmail/imap4/current’ log showed:
   
  2006-04-28
15:01:38.022432500 tcpserver: status: 1/40
  2006-04-28
15:01:38.022644500 tcpserver: pid 6567 from 127.0.0.1
  2006-04-28
15:01:38.022670500 tcpserver: ok 6567 mail2.jdvu.ac.in:127.0.0.1:143
:127.0.0.1::32833
  2006-04-28
15:01:38.023586500 DEBUG: Connection, ip=[127.0.0.1]
  2006-04-28
15:01:38.037758500 chdir
"/home/vpopmail/domains/systems.jdvu.ac.in/supriyo": Permission
denied
  2006-04-28
15:01:38.038321500 tcpserver: end 6567 status 256
  2006-04-28
15:01:38.038323500 tcpserver: status: 0/40
   
  Doing a ‘ls –al’ in
‘/home/vpopmail/domains/systems.jdvu.ac.in’
directory shows the following:
   
   
drwx--  
7 vpopmail vchkpw 4096 Apr 28 13:20 .
  drwx--  40
vpopmail
vchkpw 4096 Apr 28 14:22 ..
   
drwx--  
3 vpopmail vchkpw 4096 Apr 25 17:44 postmaster
   
drwx--  
3 vpopmail vchkpw 4096 Apr 25 17:43 supriyo
   
  It may be of interest
that when I added a new domain and
new user to my new QMT server, I was able to use/access both QMAILADMIN
and
webmail for the new domain/user without any problem.
  

Those permissions look right. When
you create a domain, are there any differences with permissions between
the two? Since you changed the vpopmail database password, did you also
change the user?

Re: [qmailtoaster] QMT migration problems

2006-04-28 Thread Supriyo Banerjee 




Hi Jake...

Here is the details of the file/directory
permissions for the new domain  I created and which is working properly:

drwx--   4 vpopmail vchkpw 4096 Apr 28 14:23 .
drwx--  40 vpopmail vchkpw 4096 Apr 28 14:22 ..
drwx--   3 vpopmail vchkpw 4096 Apr 28 14:22 postmaster
-rw---   1 vpopmail vchkpw  111 Apr 28 14:22 .qmailadmin-limits
-rw---   1 vpopmail vchkpw   55 Apr 28 14:22 .qmail-default
drwx--   3 vpopmail vchkpw 4096 Apr 28 15:07 sb

When I said that I changed the vpopmail
database password, I actually meant the one which is set using the
command: 

   echo "GRANT ALL
PRIVILEGES ON vpopmail.* TO [EMAIL PROTECTED] IDENTIFIED BY
'SsEeCcRrEeTt'" | mysql -u root –p 

and then the same password is added  to the 
'/home/vpopmail/etc/vpopmail.mysql' file. 

Initially while setting up QMT on the new server I had set some new
password for this and then later on when I reset the password adding
the same one that I had in my old server.

Regards,
Supriyo

Jake Vickers wrote:

  
Supriyo Banerjee wrote:
  




Hi list,
 
While trying to migrate
users from my old Qmailtoaster server
(containing around 10 domains) which was running on Redhat Liinux 9.0,
to a new
server running Centos 4.3, and the latest Qmail Toaster packages, I
have run
into some problems as described below:
 
I used Jake’s backup
script to take the backup from
my old server, on which the UID:GID of vpopmail
was 7797:7797. Then I did a manual install of QMT on my new server
which was successful.
Then I transferred the ‘curlfile’
containing the backup of the old server
to the new server’s root
directory. Then from the home directory of my user account, as ‘root’
user, I executed the restore script (again from Jake’s site). I must
mention here that in Jake’s restore script, I had enabled the line that
converted the old aliases to the new format.
 
I must also mention
here that the mysql root
password in my old server and the new server are not same. I guess
there is no
harm as such!? Likewise, initially, the vpopmail
da
The
‘/var/log/qmail/imap4/current’ log showed:
 
2006-04-28
15:01:38.022432500 tcpserver: status: 1/40
2006-04-28
15:01:38.022644500 tcpserver: pid 6567 from 127.0.0.1
2006-04-28
15:01:38.022670500 tcpserver: ok 6567 mail2.jdvu.ac.in:127.0.0.1:143
:127.0.0.1::32833
2006-04-28
15:01:38.023586500 DEBUG: Connection, ip=[127.0.0.1]
2006-04-28
15:01:38.037758500 chdir
"/home/vpopmail/domains/systems.jdvu.ac.in/supriyo": Permission
denied
2006-04-28
15:01:38.038321500 tcpserver: end 6567 status 256
2006-04-28
15:01:38.038323500 tcpserver: status: 0/40
 
Doing a ‘ls –al’ in
‘/home/vpopmail/domains/systems.jdvu.ac.in’
directory shows the following:
 
 
drwx--  
7 vpopmail vchkpw 4096 Apr 28 13:20 .
drwx--  40
vpopmail
vchkpw 4096 Apr 28 14:22 ..
 
drwx--  
3 vpopmail vchkpw 4096 Apr 25 17:44 postmaster
 
drwx--  
3 vpopmail vchkpw 4096 Apr 25 17:43 supriyo
 
It may be of interest
that when I added a new domain and
new user to my new QMT server, I was able to use/access both QMAILADMIN
and
webmail for the new domain/user without any problem.

  
  Those permissions look right.
When
you create a domain, are there any differences with permissions between
the two? Since you changed the vpopmail database password, did you also
change the user?

Re: [qmailtoaster] QMT migration problems

2006-04-28 Thread Jake Vickers 




Supriyo Banerjee wrote:

  
  
  Hi Jake...
  
  Here is the details of the file/directory
permissions for the new domain  I created and which is working properly:
  
drwx--   4 vpopmail vchkpw 4096 Apr 28 14:23 .
drwx--  40 vpopmail vchkpw 4096 Apr 28 14:22 ..
drwx--   3 vpopmail vchkpw 4096 Apr 28 14:22 postmaster
-rw---   1 vpopmail vchkpw  111 Apr 28 14:22 .qmailadmin-limits
-rw---   1 vpopmail vchkpw   55 Apr 28 14:22 .qmail-default
drwx--   3 vpopmail vchkpw 4096 Apr 28 15:07 sb
  
  When I said that I changed the vpopmail
database password, I actually meant the one which is set using the
command: 
  
   echo "GRANT ALL
PRIVILEGES ON vpopmail.* TO [EMAIL PROTECTED] IDENTIFIED BY
'SsEeCcRrEeTt'" | mysql -u root –p 
  
and then the same password is added  to the 
'/home/vpopmail/etc/vpopmail.mysql' file. 
  
Initially while setting up QMT on the new server I had set some new
password for this and then later on when I reset the password adding
the same one that I had in my old server.
  
  
Just for safety's sake, try stopping qmail, then
running the qmail-newu command, as well as the queue-repair python
script.
I'm still a little unclear. Is your new machine using the old password
(SsEeCcRrEeTt), or did you run the commands and change it? I understand
the old machine was using a different password.

Re: [qmailtoaster] QMT migration problems

2006-04-28 Thread Shai 

On 4/28/06, Supriyo Banerjee <[EMAIL PROTECTED]> wrote:


Hi list,

While trying to migrate users from my old Qmailtoaster server (containing
around 10 domains) which was running on Redhat Liinux 9.0, to a new server
running Centos 4.3, and the latest Qmail Toaster packages, I have run into
some problems as described below:

I used Jake's backup script to take the backup from my old server, on which
the UID:GID of vpopmail was 7797:7797. Then I did a manual install of QMT on
my new server which was successful. Then I transferred the 'curlfile'
containing the backup of the old server to the new server's root directory.
Then from the home directory of my user account, as 'root' user, I executed
the restore script (again from Jake's site). I must mention here that in
Jake's restore script, I had enabled the line that converted the old aliases
to the new format.

I must also mention here that the mysql root password in my old server and
the new server are not same. I guess there is no harm as such!? Likewise,
initially, the vpopmail database passwords, in both my servers were also
dissimilar, but later on I changed that in my new server to the same
password as in the old one.

When the restoration was complete, I logged on to VQADMIN and I could see
all the domains and the users within, with their respective password (in
plain text) were being displayed correctly. However, when I tried using
QMAILADMIN, I was not able to login to any of the domains using any of the
accounts – either user account or the postmaster account. It just displayed
"Invalid Login" even after I successfully changed the passwords from the
terminal (using the executables in '/home/vpopmail/bin').

I was also unable to log in to any of the e-mail accounts using POP3 (mail
clients) or IMAP (Webmail). The error I received while trying to login to
webmail was:

ERROR: Connection dropped by IMAP server.

The '/var/log/qmail/imap4/current' log showed:

2006-04-28 15:01:38.022432500 tcpserver: status: 1/40
2006-04-28 15:01:38.022644500 tcpserver: pid 6567 from 127.0.0.1
2006-04-28 15:01:38.022670500 tcpserver: ok 6567
mail2.jdvu.ac.in:127.0.0.1:143 :127.0.0.1::32833
2006-04-28 15:01:38.023586500 DEBUG: Connection, ip=[127.0.0.1]
2006-04-28 15:01:38.037758500 chdir
"/home/vpopmail/domains/systems.jdvu.ac.in/supriyo":
Permission denied
2006-04-28 15:01:38.038321500 tcpserver: end 6567 status 256
2006-04-28 15:01:38.038323500 tcpserver: status: 0/40

Doing a 'ls –al' in
'/home/vpopmail/domains/systems.jdvu.ac.in' directory shows
the following:

drwx--   7 vpopmail vchkpw 4096 Apr 28 13:20 .
drwx--  40 vpopmail vchkpw 4096 Apr 28 14:22 ..
drwx--   3 vpopmail vchkpw 4096 Apr 25 17:44 postmaster
drwx--   3 vpopmail vchkpw 4096 Apr 25 17:43 supriyo

It may be of interest that when I added a new domain and new user to my new
QMT server, I was able to use/access both QMAILADMIN and webmail for the new
domain/user without any problem.

I will be looking forward to your help in resolving these issues. Thanking
you in anticipation….

Supriyo Banerjee


Hi,

I'm not a guru.. but try this:

1. run this command a few times over and over (3 or 4 times):
   $ chown -R vpopmail:vchkpw /home/vpopmail/domains/
2. the this one:
   $ /var/qmail/bin/qmail-newu
3. delete your browser's cookies. they may hold invalid info from your
own domain and thus making login failures.

See if that above helped.

Shai

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] QMT migration problems

2006-04-28 Thread Supriyo Banerjee 




Hi Jake...

I followed your instructions, but they yielded the same results. Then I
had an idea and I modified the '/var/qmail/users/assign' file.  I
stopped Qmail, then manually changed the  UID:GID  numbers for one of
the domains mentioned there, from 7797:7797 to  89:89, saved the file,
then I executed the 'qmail-newu' command followed by the queue-repair
python script you mentioned. After that I restarted Qmail and voilà!!! I was able to login to webmail as well as
Qmailadmin for that domain just like that!

Now... does this mean there was something I missed earlier during the
backup process or while restoring? What do you think went wrong for me?
Should I follow the same procedure for the rest of the domains or is
there any other procedure?

Coming to your second question... while setting up QMT on the new
server I had set the mysql password to a new value (say ... 'xyz1234'),
while the existing mysql password in my old server was something else
(say... 'abcd6789'). Later on, after I found the problems (which I had explained in my
earlier e-mail) after I had restored the backup from the old server to
the new one, I thought may be the mysql password on both the machines
should be same. So then I run the command to change the mysql password
in the new machine to the same value as was there in the old server
(abcd6789).

I hope I have been able to define the problems clearly this time. :)

Regards,
Supriyo Banerjee    

Jake Vickers wrote:

  
  Just for safety's sake, try stopping qmail, then
running the qmail-newu command, as well as the queue-repair python
script.
I'm still a little unclear. Is your new machine using the old password
(SsEeCcRrEeTt), or did you run the commands and change it? I understand
the old machine was using a different password.

[Fwd: Re: [qmailtoaster] QMT migration problems]

2006-05-01 Thread Supriyo Banerjee 




Hi there...

I guess my earlier message was missed, hence forwarding that again.

Just wanted to be sure whether I should modify the
/var/qmail/users/assign file and replace all the 7797:7797 by 89:89, or
is there is some other way out. I wonder if anything went wrong in my
backup/restore procedure!

thanks!
Supriyo Banerjee

 Original Message 



Hi Jake...

I followed your instructions, but they yielded the same results. Then I
had an idea and I modified the '/var/qmail/users/assign' file.  I
stopped Qmail, then manually changed the  UID:GID  numbers for one of
the domains mentioned there, from 7797:7797 to  89:89, saved the file,
then I executed the 'qmail-newu' command followed by the queue-repair
python script you mentioned. After that I restarted Qmail and voilà!!! I was able to login to webmail as well as
Qmailadmin for that domain just like that!

Now... does this mean there was something I missed earlier during the
backup process or while restoring? What do you think went wrong for me?
Should I follow the same procedure for the rest of the domains or is
there any other procedure?

Coming to your second question... while setting up QMT on the new
server I had set the mysql password to a new value (say ... 'xyz1234'),
while the existing mysql password in my old server was something else
(say... 'abcd6789'). Later on, after I found the problems (which I had explained in my
earlier e-mail) after I had restored the backup from the old server to
the new one, I thought may be the mysql password on both the machines
should be same. So then I run the command to change the mysql password
in the new machine to the same value as was there in the old server
(abcd6789).

I hope I have been able to define the problems clearly this time. :)

Regards,
Supriyo Banerjee    

Jake Vickers wrote:

  
  Just for safety's sake, try stopping qmail, then
running the qmail-newu command, as well as the queue-repair python
script.
I'm still a little unclear. Is your new machine using the old password
(SsEeCcRrEeTt), or did you run the commands and change it? I understand
the old machine was using a different password.

Re: [Fwd: Re: [qmailtoaster] QMT migration problems]

2006-05-01 Thread Erik Espinoza 

Yes, change the uid:gid in /var/qmail/users/assign, and run
/var/qmail/bin/qmail-newu

This will re-generate the /var/qmail/users/cdb

Thanks,
Erik

On 5/1/06, Supriyo Banerjee <[EMAIL PROTECTED]> wrote:

 Hi there...

 I guess my earlier message was missed, hence forwarding that again.

 Just wanted to be sure whether I should modify the /var/qmail/users/assign
file and replace all the 7797:7797 by 89:89, or is there is some other way
out. I wonder if anything went wrong in my backup/restore procedure!

 thanks!
 Supriyo Banerjee


  Original Message 

 Hi Jake...

 I followed your instructions, but they yielded the same results. Then I had
an idea and I modified the '/var/qmail/users/assign' file.  I stopped Qmail,
then manually changed the  UID:GID  numbers for one of the domains mentioned
there, from 7797:7797 to  89:89, saved the file, then I executed the
'qmail-newu' command followed by the queue-repair python script you
mentioned. After that I restarted Qmail and voilà!!! I was able to login
to webmail as well as Qmailadmin for that domain just like that!

 Now... does this mean there was something I missed earlier during the
backup process or while restoring? What do you think went wrong for me?
Should I follow the same procedure for the rest of the domains or is there
any other procedure?

 Coming to your second question... while setting up QMT on the new server I
had set the mysql password to a new value (say ... 'xyz1234'), while the
existing mysql password in my old server was something else (say...
'abcd6789'). Later on, after I found the problems (which I had explained in
my earlier e-mail) after I had restored the backup from the old server to
the new one, I thought may be the mysql password on both the machines should
be same. So then I run the command to change the mysql password in the new
machine to the same value as was there in the old server (abcd6789).

 I hope I have been able to define the problems clearly this time. :)

 Regards,
 Supriyo Banerjee

 Jake Vickers wrote:
 Just for safety's sake, try stopping qmail, then running the qmail-newu
command, as well as the queue-repair python script.
 I'm still a little unclear. Is your new machine using the old password
(SsEeCcRrEeTt), or did you run the commands and change it? I understand the
old machine was using a different password.



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]