Re: [URGENT] What the heck? Message e112cbd810804e731e2e0d397787af62 seems to be gone!

Guru On Call- Justin Scott schrieb:

> Torsten,
> 
> Thank you for your response.
> 
> Please let me re-iterate that this neomail setup was moved from Cobalt Linux to
> RedHat Linux.
> 
> It was installed under Cobalt, and moved to RedHat.
> 
> The only thing that has changed is the physical residency of the files.

So the next question would be:

On the Cobalt box were "special" users like neomail setup ?
How about the suidperl thing ...

(These are more general questions, as i can't see the real reason
for the behaviour of neomail now :-/ )

> All files moved except the /var/spool/mail/* files.
> 
> Also, let me point out that: homedirfolders != homedirspool.
> 
> Users spools still reside in /var/spool/mail, as they did in Cobalt-land.
> 
> It is imperative that none of these users lose their folders (i.e.
> saved-messages, sent-mail, neomail-trash, INBOX).  These files all still exist,
> though they are not viewable even though the directory structures are the same
> (minus the fact that users home directories changed from cobalt kludginess of
> /home/sites/site4/users/username to simply /home/username) and the exact same
> file contents exist from Cobalt and RedHat due to the loveliness of tar. :)
> 
> The issue remains- When a user connects, it shows the contents of
> /var/spool/mail/username as I would expect.  When a user clicks on a message,
> the get the "What the heck?" error message.  A users folder names are indeed
> seen by the system, but when a folder is selected it shows up empty, including
> when a  user attempts to go BACK to INBOX.
> 
> If re-installing from scratch will eradicate this problem while still
> maintaining the users individual folder dirs and preferences stored within
> /home/neomail/users/username, then I am all up for it.  I was just hoping there
> would be a quick fix or someone would know what small thing would cause this
> error.

Hmm, you are right, there must be a difference between your Cobalt and
the
RedHat system, but i can't see it.
So possibly a reinstall is the fastest way to solve the problem, but not
the best way to find out what's going on. Depending of your need, how
fast you need to have a working neomail you have to decide yourself.

If you want "the way of knowing" (TM) you should add more debug lines
to neomail.pl to find i.e. out, what file (and additional informations)
neomail tries to read in the "second run on the INBOX" or the opening
of a folder.

Torsten


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/