Good thinking. If there's no delay using another client (eg TBird) with migrated users (have you tested such?), then you may have found the culprit. :) Let us know.

On 10/15/2010 02:38 AM, Sandeil Tenebro wrote:
Hi Eric,

I was thinking since you said that there are connections with database, I now
remembered that squirrelmail from source instance uses mysql database for its
address book. I think the database and squirrelmail is not configured on the
destination machine.

Will check it and restore the mysql and re-configure squirrelmail's address
book. Hope this solves the issue.


Sandeil




----- Original Message ----
From: Eric Shubert<[email protected]>
To: [email protected]
Sent: Thursday, October 14, 2010 11:35:23 PM
Subject: [qmailtoaster] Re: After backup restoration web based email sending
went slow

I hope that IP is just a typo here. Should be:
nameserver 127.0.0.1
;) (I expect you have it right)

Have you tested submitting with other clients?

You might also try using port 587 to see if that behaves any
differently. Port 587 does not do any rbl checking, and does require
authentication. You can change squirrelmail's configuration as such:
$smtpPort = 587;

The fact that it's fast for new users and slow for migrated users would
seem to indicate that there is a problem with the migrated accounts,
causing vpopmail to be slow with authentication. I think I'd use
phpmyadmin to look for any differences between new and migrated users in
the database.



--
-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: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to