Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail

2006-05-08 Thread Tomas Kuliavas
>>>> Message: 2 >>>> Date: Mon, 8 May 2006 16:30:44 +0300 (EEST) >>>> Subject: Re: [SM-USERS] Possible DNS problem being shown by >>>> Squirrelmail >>>> From: "Tomas Kuliavas" <[EMAIL PROTECTED]> >>>> T

Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail

2006-05-08 Thread Geoff Soper
Tomas Kuliavas wrote: [EMAIL PROTECTED] wrote: Message: 2 Date: Mon, 8 May 2006 16:30:44 +0300 (EEST) Subject: Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail From: "Tomas Kuliavas" <[EMAIL PROTECTED]> To: squirrelmail-users@lists

Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail

2006-05-08 Thread Tomas Kuliavas
> [EMAIL PROTECTED] wrote: >> Message: 2 >> Date: Mon, 8 May 2006 16:30:44 +0300 (EEST) >> Subject: Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail >> From: "Tomas Kuliavas" <[EMAIL PROTECTED]> >> To: squirrelmail-users@lists.

Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail

2006-05-08 Thread Geoff Soper
[EMAIL PROTECTED] wrote: Message: 2 Date: Mon, 8 May 2006 16:30:44 +0300 (EEST) Subject: Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail From: "Tomas Kuliavas" <[EMAIL PROTECTED]> To: squirrelmail-users@lists.sourceforge.net I've recently inst

Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail

2006-05-08 Thread Geoff Soper
[EMAIL PROTECTED] wrote: Message: 2 Date: Mon, 8 May 2006 16:30:44 +0300 (EEST) Subject: Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail From: "Tomas Kuliavas" <[EMAIL PROTECTED]> To: squirrelmail-users@lists.sourceforge.net I've recently inst

Re: [SM-USERS] Possible DNS problem being shown by Squirrelmail

2006-05-08 Thread Tomas Kuliavas
> I've recently installed Squirrelmail on two virtualised (running Plesk & > Virtuozzo) supposedly identical web servers running FC3. My problem is > that on one server there was a delay of 5-10 seconds in displaying any > pane in Squirrelmail. This same server was initially unable to resolve > any