|
Do you have a virus scanner on that live
server? The COM object first writes the file and then renames it (from
what I remmeber) and, if a process is locking the file then that would be a
problem.
Regards,
Howie
----- Original Message -----
Sent: Monday, August 30, 2004 8:12
PM
Subject: Re: [iMS] Fwd: iMS com
object
We are now running 2.6.2 prerelease 7 of the POST server but
this has made no difference. We also deregistered the DLL for the COM object
and reregistered it, but the files are still being created with no .mbx
extension.
Ciao,
Michelle
At 09:42 AM 31/08/2004, you
wrote:
Hi Howie,
We have made
some progress. It appears that on the dev server the mail files have the
correct .mbx extension, but the ones being created on the production server
don't. If we manually add an mbx extension they appear to get sent
okay.
We are going to shift the POST server back to the prerelease of
2.6.2 to see if this fixes the problem.
Will keep you "POSTED"
;->>
Ciao,
Michelle Davis
Date: Tue, 31 Aug 2004 09:30:37
+1000
To: <[EMAIL PROTECTED]>
From: Michelle Davis
<[EMAIL PROTECTED]>
Subject: iMS com
object
Hi,
We are using the iMS com object in C# ASP.NET to
put mail into the post queue. This has been working beautifully on the
development server, the files go into the Out directory and are happily
processed by the POST server. However on the Production server, the files
go into the Out directory but they just sit there and are never processed.
The production POST server is working fine, we can see CFX_imsmail
happily inserting mail and the mail is processing and arriving at it's
destination fine.
We assume this is some sort of configuration
problem, but can't work out what ...
Any ideas or help would be
appreciated.
The production POST server is version 2.6.3 and the
COM object is v 1.1
The development POST server is 2.6.2 and the
COM object is v 1.1
We could step the production server back to
2.6.2 but we really only want to do this if there is a genuine
problem.
Ciao,
Michelle Davis
|
