Q10064 – HOWTO: Reset Cache Mode in Outlook

thanks
http://www.lanlogic.net/support/docs/article.aspx?id=10064

You may need to turn off cache mode and turn it back on if your Outlook
client is running slow, or if you are suddenly unable to send or receive
emails. Going through the steps will essentially remove the Outlook
cache from your computer, and then rebuild it. The cache is the local
copies of your emails.

1. Turn Off Cache Mode

1. Open Outlook
2. Tools
3. Email Accounts
4. Select View or change existing e-mail accounts
5. Next
6. With "Microsoft Exchange Server" selected, Click "Change"
7. Uncheck the box for "Use Cached Exchange Mode"
8. Next
9. In the box that pops up, click on OK
10. Click Finish

2. Close Outlook
1. File
2. Exit

3. Delete OST files from hard drive
1. Start
2. Search
3. For Files or folders
4. All files and Folders
5. Expand "More Advanced Options"
6. Check the box next to "Search hidden files and folders"
7. Leave the other options at default
8. In the top box for "All or part of the file name", type in
"*.ost"
9. Look in should be "Local Hard Drives"
10. Click Search
11. It'll find files such as outlook.ost, outlook001.ost, etc.
Select all the files it finds and select delete. This will
delete all the offline emails from your computer, but they
are still on the server so you won't lose anything.

4. Turn On Cache Mode

1. Open Outlook
2. Tools
3. Email Accounts
4. Select View or change existing e-mail accounts
5. Next
6. With "Microsoft Exchange Server" selected, Click "Change"
7. Check the box for "Use Cached Exchange Mode"
8. Next
9. In the box that pops up, click on OK
10. Click Finish

5. Restart Outlook

Once Outlook is restarted, all of your emails will download to your
computer again. It may take awhile, depending on the number of emails
you have. You can watch the progress in the lower right corner of your
Outlook screen… it will show the folders as they update.

Outlook (xp or 2003) slow to open mails

thanks to http://www.brichet.be/?p=139

Try first to launch Outlook in safe mode (Outlook /safe).
If the problem disappear in safe mode, try first disabling add ins and
then try renaming cache files (source : newsgroups)

Locate and rename the Outlook cache files
(frmcache.dat,outcmd.dat,extend.dat) one by one.
————————————————–

1. Quit Outlook.
2. Click Start -> Search -> For Files and folders
3. Click Tools -> Folder Options.
4. Select View tab, select Show hidden files and folders, uncheck Hide
extensions for known file types, and click OK.
5. Click All files and folders.
6. Type "frmcache.dat,outcmd.dat,extend.dat,views.dat" (without the
quotation marks) in the filename box, and then select Local Hard Drives.
7. Click More advanced options, check Search hidden files and
folders, and
click Search.
8. After the search has finished, renames files in .old
NOTE: We may find multiple files for each name. Please rename them all.
9. Restart Outlook.

DRIVER_IRQL_NOT_LESS_OR_EQUAL error

DRIVER_IRQL_NOT_LESS_OR_EQUAL:
chissà a quanti di voi sarà capitato di vedere improvvisamente questa
schermata blu con riportato in cima questa scritta, beh la soluzione è
alquanto semplice, generalmente il problema è causato dalla RAM che è o
difettosa o incompatibile con la scheda madre, oppure sono impostati dei
timings troppo aggressivi per cui bisogna alzarli.

In caso invece vi fossero problemi hardware di altra natura, consiglio
la consultazione delle seguenti pagine Microsoft:

Hardware and Software Third-Party Vendor Contact List, A-K
<http://support.microsoft.com/?kbid=65416>
Hardware and Software Third-Party Vendor Contact List, L-P
<http://support.microsoft.com/?kbid=60781>
Hardware and Software Third-Party Vendor Contact List, Q-Z
<http://support.microsoft.com/?kbid=60782>

In qualche altra circostanza la causa del problema potrebbe dipendere
dal file di paginazione, e visto che non costa nulla, provare questa
procedura:

1. destro mouse su risorse del PC / proprietà /avanzate / impostazioni e
cliccare sul pulsante prestazioni / avanzate / memoria virtuale / cambia
/ qui selezionare nessun file di paging e cliccare su imposta / OK / OK
e riavviare

2. una volta riavviato destro mouse su risorse del PC / proprietà
/avanzate / impostazioni e cliccare sul pulsante prestazioni / avanzate
/ memoria virtuale / e selezionare Dimensioni gestite dal Sistema
cliccare Imposta / Ok / Ok e riavviare.

Se con questa procedura non compare più l'errore
DRIVER_IRQL_NOT_LESS_OR_EQUAL allora siamo stati fortunati, se invece
compare ancora e pure frequentemente, allora meglio focalizzare
l'attenzione sulla RAM.

fonte jsi

[Freebsd] – abilitare il su

su – how to become a super user. avoid using root

If you're like most people new to Unix, you do everything as root. You
shouldn't. I know I don't follow my own advice, but I'm trying to
improve.

Create yourself another account. Use that instead of root. Unless you
really need root. You can always invoke su to become a super user.
That way, you don't have to log out and back in every time you need the
power.

wheel

Only users in the wheel group can run su. The group can be specified
when creating a user via adduser. To add a user manuall, just put the
name of the user at the end of the line in /etc/group. For example:

wheel:*:0:root,marc

This adds the user marc to the wheel group.

su

To become super user, you do this:

bash-2.02$ su
Password:
su-2.02#

At the password prompt, supply the root password.

Note that you might also want to use either the -l or the -m options.
Respectively, these options will simulate a full login or leave the
environment unmodified. see man su
<http://www.freebsd.org/cgi/man.cgi?query=su&apropos=0&sektion=0&manpath=FreeBSD+2.2.8-RELEASE&format=html>
for details.

GPO – Group Policy – Installazione Software – OpenOffice e JRE

GPO – Group Policy – Installazione Software

OpenOffice e JRE

thanks to
http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation

Desktop Software Installation

These instructions describe the steps needed to perform a network
installation of the OpenOffice.org office suite and the
OpenOffice-Enterprise client software using Windows Group Policy.

These instructions are copyright Open Office Technology. They may be
linked to but not copied. Their permanent location is

http://OpenOfficeTechnology.com/OpenOffice-Enterprise/Desktop_Installation

<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation>

* Overview <http://openofficetechnology.com/node/24>
* Package Installation Order <http://openofficetechnology.com/node/30>
* Step 1 – Download Software Packages
<http://openofficetechnology.com/node/25>
* Step 2 – Create Network Installation Images
<http://openofficetechnology.com/node/26>
* Step 3 – Create Installation Group Policy Object
<http://openofficetechnology.com/node/27>
* Step 4 – Set Policy Scope and Link to Domain
<http://openofficetechnology.com/node/28>
* Upgrading OpenOffice-Enterprise
<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation/Upgrading_OpenOffice-Enterprise>
* Upgrading OpenOffice
<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation/Upgrading_OpenOffice>
* Installation Troubleshooting <http://openofficetechnology.com/node/29>

Overview

The three software packages discussed in these instructions are:

1. The OpenOffice.org office suite. Installation of this package on
each client is required.
2. The OpenOffice-Enterprise client software. Provides Group Policy
management for the OpenOffice.org office suite. Installation of
this package on each managed client is required.
3. Sun's Java runtime environment (JRE). Certain functions in the
OpenOffice suite depend on the Java runtime, such as the database
application, mail merge and the document wizards in Writer. (For a
more complete list, see Java and OpenOffice.org
<http://wiki.services.openoffice.org/wiki/Java_and_OpenOffice.org#OpenOffice.org_2.0_Functionality_depending_on_Java>).
If these features are not required, the JRE does not need to be
installed. Full functionality requires the JRE or JDK version
1.4.0_02 or newer, or version 1.4.1_01 or newer. Limited
functionality is available with version 1.3.1 or higher. (Source:

http://www.openoffice.org/dev_docs/source/sys_reqs_20.html)

These instructions describe the installation procedure using the most
recent application versions as of the date these instructions were
written. The OpenOffice suite and Java JRE are not distributed by Open
Office Technology, and the information related to these packages may
change from time to time. If you find any discrepancies in these
instructions, please let us know <http://openofficetechnology.com/contact>.

Package Installation Order

The three packages must be installed in the following order:

1. Optionally, if required, the Java JRE.
2. The OpenOffice.org office suite.
3. The OpenOffice-Enterprise client software.

The installation of one or more of these packages can be combined into a
single Group Policy operation.

These instructions describe the process of installing all three packages
in one operation. If one or more are already installed, simply skip the
corresponding steps. To install one or more of the packages separately,
create separate Group Policy objects these packages.

Step 1 – Download Software Packages

The first step in the installation process is to download the software
packages.

A. Optionally, download the Java JRE *offline* installation package for
Windows. As of the date of these instructions:

* Most recent version of the JRE: Version 6.0
* Installation package file name: jre-6-windows-i586.exe
* Download location: http://java.sun.com/javase/downloads/

(Click to download "Java Runtime Environment (JRE) 6", click to
accept license agreement, then click on "Windows Offline
Installation, Multi-language")
* Other versions: http://java.sun.com/javase/downloads/previous.jsp

B. If OpenOffice is not already installed on the client machines,
download the OpenOffice installer for Windows without the JRE bundled.
As of the date of these instructions:

* Most recent version of the OpenOffice suite: Version 2.1
* Installation package file name: OOo_2.1.0_Win32Intel_install_en-US.exe
* Download location: http://download.openoffice.org/

* Other versions at: http://distribution.openoffice.org/mirrors/

<http://distribution.openoffice.org/mirrors/index.html#mirrors>

C. Download the OpenOffice-Enterprise client software installer. As of
the date of these instructions:

* Most recent version of OpenOffice-Enterprise client software:
Build 450
* Corresponding package file name: ooewin-450.msi
* Download location: http://OpenOfficeTechnology.com/download

<http://openofficetechnology.com/download>

Step 2 – Create Network Installation Images

The next step is to create network installation images for each of the
software packages. This places the installation images on a network file
server that is accessible to the client computers. To complete this
process, you must have write access to this location. The client
computer should have read-only access.

A. Extract the Java JRE msi file:

1. Run the JRE installation executable file, jre-6-windows-i586.exe.
The License Agreement screen will appear. Do not click either
"Decline" or "Accept".
2. The installer executable will have placed a file called
"jre1.6.0.msi" into the directory "C:\Documents and Settings\<your
username>\Application Data\Sun\Java\jre1.6.0". Copy the .msi file
to a network installation point, which is a location on the
network accessible to the client computers, such as
|
\\fileserver\net_install_images\jre-1_6_0\
|
Note 1: Earlier versions of JRE installation executable placed the
.msi file into a subdirectory such as "C:\Documents and
Settings\<your username>\Local Settings\Application
Data\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}", where the name of
the subdirectory depends on the JRE version. The .msi file
corresponding to the JRE version can be located by looking in all
subdirectories with names matching this pattern.
Note 2: Neither the Java installer executable nor the .msi file
support the "/a" administrative installation option.
3. Returning to the License Agreement screen, click "Decline". The
installer will delete the Application Data\Sun\Java directory and
its .msi file, then terminate.

B. Perform an administrative installation of the OpenOffice suite:

1. Run the OpenOffice installer,
OOo_2.1.0_Win32Intel_install_en-US.exe, with no parameters.
2. When prompted, enter a location to unpack the installation files,
such as a subdirectory called Ooo_installer_files in your current
working directory.
3. When the next stage of the installer runs ("Welcome to the
Installation Wizard for OpenOffice.org 2.1"), click "Cancel" and
abort the installation.
4. The OpenOffice installer should have unpacked several executable
and data files into the directory you selected. From the command
prompt, launch the setup file using the following command line:
|
setup /a
|
When prompted, enter a network installation point such as
|
\\fileserver\net_install_images\OpenOffice-2.1\
|
and then click "Install". The installer will create the directory
you specified, if it doesn't already exist, and then unpack the
file "openofficeorg21.msi" along with a handful of subdirectories
into this location.

C. Perform an administrative installation of the OpenOffice-Enterprise
client software:

1. From the command prompt, launch the installer file using the
following command line:
|
msiexec /a ooewin-450.msi
|
When prompted, enter a network installation point such as
|
\\fileserver\net_install_images\ooewin-450\
|
and then click "Next" twice. The installer will copy the .msi file
to this folder and unpack several files and one subdirectory.

Before continuing, ensure that the client computers have read-only
access to the network installation points that you used above.

Step 3 – Create Installation Group Policy Object

This step creates a Group Policy Object or "GPO" that will install the
software packages.

1. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then right-click on
"Group Policy Objects" and select "New". Enter a name such as
"OpenOffice-Enterprise Installation". Your new Group Policy Object
will appear in the tree under "Group Policy Objects". Right-click
on its name and select "Edit…". This will open the Group Policy
Object Editor.
2. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New –> Package…".
3. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
4. Navigate to the network location where you placed the Java JRE
install file "jre1.6.0.msi" and double-click on this file. If you
are not installing Java, skip this step and move down to the first
package you are installing.
5. For the deployment method, select "Assigned". The JRE install file
should appear in the view pane.
6. Right-click on "Software Installation" and select "New –>
Package…" again.
7. Navigate to the network location containing your OpenOffice suite
administrative install, and double-click on the .msi file
"openofficeorg21.msi".
8. Several installation transform files are available here
<http://openofficetechnology.com/OpenOffice_Installation_Transforms>.
If you do not want to use any transforms, select "Assigned" as the
deployment method and click "OK". The install file for OpenOffice
should appear in the view pane. Otherwise, to install OpenOffice
with one or more transforms, download the transform (.mst) files
and add them to the directory that contains the OpenOffice
installation file openofficeorg21.msi. Then for "Deployment
Method" select "Advanced" and click "OK". After a short pause, the
Properties dialog should appear. Under the "Modifications" tab,
add the transform file you wish to apply, then click "OK".
9. Right-click on "Software Installation" and select "New –>
Package…" again.
10. Navigate to the network location containing your
OpenOffice-Enterprise administrative install, and double-click on
the .msi file "ooewin-450.msi". For the deployment method, select
"Assigned". The OpenOffice-Enterprise install file should appear
in the view pane.

IMPORTANT: You must add the .msi files in the indicated order:
Java JRE, then OpenOffice.org suite, then OpenOffice-Enterprise.
The packages will appear in the view pane in alphabetical order,
but they will be installed in the order they were selected. The
indicated installation order is mandatory in order for all three
packages to be installed successfully.

11. To set additional options, double-click on each package name in
the view pane. For example, selecting "Uninstall this application
when it falls out of the scope of management" will cause the
applications to be automatically uninstalled if this group policy
object is deleted or unlinked. (Alternately, the software can be
uninstalled later by right-clicking on each package name and
selecting "All Tasks" -> "Remove…"). Any options selected must
be set for each package individually, so be certain to
double-click on each package name in succession and set the
desired options.
12. When done, double check your selections and close the Group Policy
Object Editor.

Step 4 – Set Policy Scope and Link to Domain

This final step selects the computers on which the software will be
installed. This involves designating a group or list of computers, along
with one or more domains or organizational units. The software will be
installed on a computer if it is both in the group that you designated
/and/ in one of the domains or organizational units you select.

The default is to "assign" the installation to all users which will
ultimately cause the software to be installed on all computers in the
selected domains, including servers and domain controllers. This is
probably not what you want.

A typical configuration will only install this software on desktop
workstations, not on domain controllers. Here are instructions to
accomplish this:

1. Back in the Group Policy Management console, click on the name of
your Group Policy Object (e.g., "OpenOffice-Enterprise
Installation" or whatever name you previously chose). In the pane
on the right, under "Security Filtering" in the "Scope" tab,
select "Authenticated Users" and click on "Remove".
2. Click "Add…", and in the dialog box that appears, under "Enter
the object name to select", type "domain computers" and click OK.
"Domain Computers" refers to all workstations in your domain; it
does not include domain controllers. It may however include
servers, so you should check the members of this group. In the
Group Policy Management view pane, click on the word "Domain
Computers", then click "Properties". In the Properties dialog,
select the "Members" tab. This brings up a list of the computers
in the "Domain Computers" group. If this group includes more
computers than desired, you can "Remove" this group and then
"Add…" computers individually, or you can create a custom group
using Active Directory Users and Computers. You can also select
computers using WMI filters, but this is beyond the scope of this
document.
3. When you are finished selecting computers, click on the name of
your Group Policy Object in the tree view again, and without
releasing the mouse button, drag the pointer to the name of the
domain or organization unit in which to install the software. The
pointer will change shape to a pointer with a "+". Release the
mouse button and click OK to link your Group Policy Object to this
domain. Repeat this process for any additional domains or
organizational units.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the software will be installed the next time the computer is
rebooted. The installation process will take several minutes.

Upgrading OpenOffice-Enterprise

The following instructions describe how to upgrade an existing Group
Policy installation to a new version of the OpenOffice-Enterprise client
software.

1. Download the new release of the OpenOffice-Enterprise client
software, as described in Step C of Download Software Packages
<http://openofficetechnology.com/node/25>.
2. Perform an administrative installation of the new release, as
described in Step C of Create Network Installation Images
<http://openofficetechnology.com/node/26>. CAUTION: Do not
overwrite the previous version; install the new release in a
different directory. Do not delete the previous version until you
are certain all desktops have been upgraded.
3. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then expand the tree
for "Group Policy Objects". Right-click on the Group Policy Object
used to install the previous version of OpenOffice, then select
"Edit…". This will open the Group Policy Object Editor.
4. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New –> Package…".
5. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
6. Navigate to the network location containing the administrative
installation of the new version of the OpenOffice-Enterprise
client software and and double-click on the .msi file
"ooewin-450.msi".
7. Select "Advanced" as the deployment method and click "OK". After a
short pause, the Properties dialog should appear.
8. Under the "Upgrade" tab, click "Add…" and under "Package to
upgrade", select "OpenOffice-Enterprise" and click "OK". The
properties dialog will display the text "Replace
OpenOffice-Enterprise".
9. The option "Uninstall this application when it falls out of the
scope of management" can be set under the "Deployment" tab. This
option will cause the application to be automatically uninstalled
if this group policy object is deleted or unlinked. Alternately,
the application can be uninstalled later by right-clicking on its
package name and selecting "All Tasks" -> "Remove…"
10. When all of the installation properties look correct, click "OK"
to accept the properties, then close the Group Policy Object Editor.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the new version of the OpenOffice-Enterprise client software
will be installed the next time the computer is rebooted. The
installation process will take only a few seconds.

Upgrading OpenOffice

The following instructions describe how to upgrade an existing Group
Policy installation to a new version of the OpenOffice.org office suite.

IMPORTANT: If you are upgrading to the latest v2.1 release of
OpenOffice, you must first upgrade to the latest release of the
OpenOffice-Enterprise client software, ooewin-450.msi. Prior releases of
the OpenOffice-Enterprise client software are not compatible with
OpenOffice v2.1.

1. Download the new release of OpenOffice, as described in Step B of
Download Software Packages <http://openofficetechnology.com/node/25>.
2. Perform an administrative installation of the new release, as
described in Step B of Create Network Installation Images
<http://openofficetechnology.com/node/26>. CAUTION: Do not
overwrite the previous version; install the new release in a
different directory. Do not delete the previous version until you
are certain all desktops have been upgraded.
3. Download the file Check_OOE.mst
<http://openofficetechnology.com/system/files?file=Check_OOE.mst>
and add it to the network installation directory.
4. Download any additional installation transform (.mst) files
<http://openofficetechnology.com/OpenOffice_Installation_Transforms>
you would like to use, and add them to the network installation
directory.
5. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then expand the tree
for "Group Policy Objects". Right-click on the Group Policy Object
used to install the previous version of OpenOffice, then select
"Edit…". This will open the Group Policy Object Editor.
6. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New –> Package…".
7. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
8. Navigate to the network location containing the administrative
installation of the new version of OpenOffice and and double-click
on the .msi file "openofficeorg21.msi".
9. Select "Advanced" as the deployment method and click "OK". After a
short pause, the Properties dialog should appear.
10. Under the "Upgrade" tab, click "Add…" and under "Package to
upgrade", select "OpenOffice.org 2.0" and click "OK". The
properties dialog will display the text "Replace OpenOffice.org 2.0".
11. Under the "Modifications" tab, add Check_OOE.mst and the other
transforms you downloaded earlier (if any), then click "OK". The
selected transforms will appear in the properties dialog.
12. The option "Uninstall this application when it falls out of the
scope of management" can be set under the "Deployment" tab. This
option will cause the application to be automatically uninstalled
if this group policy object is deleted or unlinked. Alternately,
the application can be uninstalled later by right-clicking on its
package name and selecting "All Tasks" -> "Remove…"
13. When all of the installation properties look correct, click "OK"
to accept the properties, then close the Group Policy Object Editor.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the new version of OpenOffice will be installed the next time
the computer is rebooted. The installation process will take several
minutes.

Installation Troubleshooting

There a several methods to obtain information about the installation
process:

1. Installation failure and success messages are logged in each
computer's Application Event Log.
2. Group Policy and software installation operations can also be
logged. For more information, see the manual section /Logging
Group Policy and/or Software Installation/.

Eliminare chiavi di registro da file .reg

Eliminazione di chiavi e valori del Registro di sistema
Per eliminare una chiave del Registro di sistema con un file reg,
inserire un trattino (-) davanti al PercorsoRegistrodisistema nel file
reg. Per eliminare ad esempio la sottochiave Test dalla seguente chiave
del Registro di sistema:
HKEY_LOCAL_MACHINE\Software
inserire un trattino davanti alla seguente chiave nel file reg:
HKEY_LOCAL_MACHINE\Software\Test
L'esempio riportato di seguito corrisponde a un file reg che consente di
eseguire questa operazione.
[-HKEY_LOCAL_MACHINE\Software\Test]
Per eliminare un valore del Registro di sistema con un file reg,
inserire un trattino (-) dopo il segno di uguale (=) che segue il
NomeElementoDati nel file reg. Per eliminare ad esempio la sottochiave
TestValue dalla seguente chiave:
HKEY_LOCAL_MACHINE\Software\Test
inserire un trattino dopo "TestValue"= nel file reg. L'esempio riportato
di seguito corrisponde a un file reg che consente di eseguire questa
operazione.
HKEY_LOCAL_MACHINE\Software\Test
"TestValue"=-
Per creare il file reg, utilizzare Regedit.exe per esportare la chiave
del Registro di sistema che si desidera eliminare, quindi utilizzare il
Blocco note per modificare il file reg e inserire il trattino.

Dovecot – problema – il client continua a scaricare vecchi messaggi

Allora, forse ho individuato il problema…

[maillog]
Mar 19 08:50:59 zion dovecot: pop3-login: Login: user=<xxx@xxx.com>…
Mar 19 08:50:59 zion dovecot: pop3(xxx@xxx.com): mbox sync: Expunged
message reappeared in mailbox
/var/spool/mail/vhosts/xxx/xxx (U ID 7953 < 7976, seq=1, idx_msgs=0)
Mar 19 08:51:11 zion dovecot: pop3(xxx@xxx.com): mbox sync: UID inserted
in the middle of mailbox /var/spool/mail/vhosts/xxx.com/xxx (7976 >
7953, seq=1, idx_msgs=8)
[/maillog]

*************************************
http://wiki.dovecot.org/MboxProblems

If you insert messages, or if you "undelete" messages (eg. replace mbox
from a backup), you may see errors in Dovecot's logs:

mbox sync: UID inserted in the middle of mailbox /home/tss/mail/inbox
(817 > 787, seq=18, idx_msgs=32)

***************************************

probabilmente è stato modificato qlcs sui file mbox del dovecot che ora
impazzisce.

Secondo me la soluzione migliore è:

Far scaricare le caselle di posta da tutti i pc in cui sn configurate;
Cancellare i file mbox del dovecot, riavviare dovecot

Ciaoooooo