IMHO you can re-install Xmail into a new dir. Copy & paste all fixed information : *.tab, domains, etc files except Spool/* and *.locks files Then new Xmail should start and become stable with no information in = spool. When this is ok; you could start and manually copy & paste the 'old' = spool message files into the new local/spool-folder.
I'm guessing that xmail is fumbling around in the index-ed spool = structure. Above scenario should solve this (I hope ;-) > -----Oorspronkelijk bericht----- > Van: S=F6nke Ruempler [mailto:[EMAIL PROTECTED]]=20 > Verzonden: woensdag 4 december 2002 13:07 > Aan: [EMAIL PROTECTED] > Onderwerp: [xmail] Re: wondering about smail server >=20 >=20 >=20 > > What version? >=20 > tested 1.11 and 1.10 - both the same. >=20 > > I'd suggest a temporarily RE-install in an other directory=20 > to manage =3D=20 > > your work flow > > And deal with spooled mails later (or by manually copying=20 > them into the =3D > > new > > 'local/spool' dir. >=20 > there are 2000 domains, so that is not easy. >=20 > > This is really something for Davide? >=20 > i think so, yes. >=20 > > Some might suggest that the spool-dir is messed-up during multiple=20 > > kill-all/reboot seq's? >=20 > maybe, but how to solve that problem? xmail worked 6 months=20 > without problems for us and now it's totally "fucked up" ;-( >=20 > - > To unsubscribe from this list: send the line "unsubscribe=20 > xmail" in the body of a message to [EMAIL PROTECTED]=20 > For general help: send the line "help" in the body of a=20 > message to [EMAIL PROTECTED] >=20 - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
