To begin with, let me apologize for the length of this post, but I
want to include as much information as possible to help get this issue
fixed without allot of "back and forth" questions and answers.
We are using Pegasus Mail 4.41 on 4 workstations, each running win2k
with gigabit nic connections. Each workstation's mailbox is the
same: A shared folder called MAIL on our Linux (samba) server (F:
\MAIL). Each workstation's installation is on it's individual hard
drive. We've had it set up this way for nearly 10 years (obviously
not all with v4.41 though...) and It's worked great. My virus
protection is AVG 7.5 Internet Security.
Recently we began having an intermittent problem with forwarding or
replying. It only happens about 5-10% of the time and it can occur on
any machine.
Once we begin to send the reply or forwarded message, the display at
the bottom of the screen reads "Sending message: 0%". That's where
everything stops. It then locks up all network connections, not
allowing anyone to access the local network or the internet. It will
remain there until the offending machine is hard booted. While the pc
will continue to run non-network applications, it is unable to shut
down Pegasus; even with ctl-alt-del.
The outgoing file will then need to be deleted, since if we try and
send again once we've re-booted, it will all happen again.
I have been working around this by re-creating the message from
scratch and sending that version with no issues UNLESS I copy and
paste the text from the original offending message. If I do that, we
get the same problem. As this happens 2 or three times a day, I've
become ready to do what I need to do to fix it before I pull what's
left of my hair out!
My initial thought is to backup the trays, folders & user data to
retain all stored messages and configurations then uninstall all
workstation copies, delete the server folder and re-install from
scratch, then moving the backed up files back to their respective
directories. I'm not sure though which files to back up. I want to
get everything I need, but don't want to go to all the work, only to
inadvertently replace a corrupt file that's causing the fiasco to
begin with.
Any ideas on what's going on or suggestions on how to go about re-
installations? I would appreciate any input at all!
Thanks!
Paul
To begin with, let me apologize for the length of this post, but I
want to include as much information as possible to help get this issue
fixed without allot of "back and forth" questions and answers.
<P>We are using Pegasus Mail 4.41 on 4 workstations, each running win2k
with gigabit nic connections. &nbsp;Each workstation's mailbox is the
same: &nbsp;A shared folder called MAIL on our Linux (samba) server (F:
\MAIL). &nbsp;Each workstation's installation is on it's individual hard
drive. &nbsp;We've had it set up this way for nearly 10 years (obviously
not all with v4.41 though...) and It's worked great. &nbsp; My virus
protection is AVG &nbsp;7.5 Internet Security.
<P>Recently we began having an intermittent problem with forwarding or
replying. &nbsp;It only happens about 5-10% of the time and it can occur on
any machine.
<P>Once we begin to send the reply or forwarded message, the display at
the bottom of the screen reads "Sending message: &nbsp;0%". &nbsp;That's where
everything stops. &nbsp;It then locks up all network connections, not
allowing anyone to access the local network or the internet. &nbsp;It will
remain there until the offending machine is hard booted. &nbsp;While the pc
will continue to run non-network applications, it is unable to shut
down Pegasus; even with ctl-alt-del.
<P>The outgoing file will then need to be deleted, since if we try and
send again once we've re-booted, it will all happen again.
<P>I have been working around this by re-creating the message from
scratch and sending that version with no issues UNLESS I copy and
paste the text from the original offending message. &nbsp;If I do that, we
get the same problem. As this happens 2 or three times a day, I've
become ready to do what I need to do to fix it before I pull what's
left of my hair out!
<P>My initial thought is to backup the trays, folders &amp; user data to
retain all stored messages and configurations then uninstall all
workstation copies, delete the server folder and re-install from
scratch, then moving the backed up files back to their respective
directories. &nbsp;I'm not sure though which files to back up. &nbsp;I want to
get everything I need, but don't want to go to all the work, only to
inadvertently &nbsp;replace a corrupt file that's causing the fiasco to
begin with.
<P>Any ideas on what's going on or suggestions on how to go about re-
installations? &nbsp;I would appreciate any input at all!
<P>Thanks!
<P>Paul </P>