Mercury 4.01a SMTP Client (Relay Version) - TCP/IP error during processing. Error FF servicing queue job

[Gordon J. Marwood]

I am new to Mercury, but it's been working well on a Windows XP SP1 machine.
I would like to move this mail-server function to a different machine which
is running XP SP2. I installed Mercury on the XP2 machine and it seems to
work except the SMTP Client (Relay Version). Whenever there is something in
the queue to send, SMTP fails with "TCP/IP error during processing. Error
FF servicing queue job". So far as I can see, the Mercury set-up is the
same on both machines. They are both on the same LAN (just different ports
on the same cable DSL router) and I am using the same account at the same
ISP to try to send mail. The firewall settings are the same on both
machines, and I have also tried SMTP on the XP2 machine with the firewall
turned off, but this doesn't help.

The Mercury core module shows the outgoing mail (from Outlook Express) being
processed correctly. Strangely enough, although the XP2 Mercury will not
send mail originating from Outlook Express, it will send a message from its
own limited e-mail client.

I have also tried to send mail from the XP1 machine, but using the XP2
machine Mercury as the server. The same failure occurs. Outlook Express
works fine through Mercury when I use the XP1 machine as the Mercury server.

I have seen some references to this error from a Google search, but I have
found nothing useful (most of the problems seem to relate to dial-up
connections). I haven't found anything on this newsgroup.

Thank you
Gordon

[Jerry Park]

Post by Gordon J. Marwood
I am new to Mercury, but it's been working well on a Windows XP SP1 machine.
I would like to move this mail-server function to a different machine which
is running XP SP2. I installed Mercury on the XP2 machine and it seems to
work except the SMTP Client (Relay Version). Whenever there is something in
the queue to send, SMTP fails with "TCP/IP error during processing. Error
FF servicing queue job". So far as I can see, the Mercury set-up is the
same on both machines. They are both on the same LAN (just different ports
on the same cable DSL router) and I am using the same account at the same
ISP to try to send mail. The firewall settings are the same on both
machines, and I have also tried SMTP on the XP2 machine with the firewall
turned off, but this doesn't help.
The Mercury core module shows the outgoing mail (from Outlook Express) being
processed correctly. Strangely enough, although the XP2 Mercury will not
send mail originating from Outlook Express, it will send a message from its
own limited e-mail client.
I have also tried to send mail from the XP1 machine, but using the XP2
machine Mercury as the server. The same failure occurs. Outlook Express
works fine through Mercury when I use the XP1 machine as the Mercury server.
I have seen some references to this error from a Google search, but I have
found nothing useful (most of the problems seem to relate to dial-up
connections). I haven't found anything on this newsgroup.
Thank you
Gordon

I don't know about your problem directly, but on the system I am running
Mercury (XP sp2), I have to turn off the windows firewall. Setting the
ports to allow Mercury doesn't work.

[Gordon J. Marwood]

Thank you for the reply. At least you have confirmed for me that Mercury
will run on XP SP2. I am not using the Windows XP firewall, but I did try
turning off the firewall that I am using, and this didn't help. The XP SP1
machine, which is running Mercury successfully, also has the same firewall
and I don't have to turn it off for Mercury to work.

Thank you again.

Gordon

Post by Jerry Park

Post by Gordon J. Marwood
I am new to Mercury, but it's been working well on a Windows XP SP1 machine.
I would like to move this mail-server function to a different machine which
is running XP SP2. I installed Mercury on the XP2 machine and it seems to
work except the SMTP Client (Relay Version). Whenever there is something in
the queue to send, SMTP fails with "TCP/IP error during processing.

Error

Post by Jerry Park

Post by Gordon J. Marwood
FF servicing queue job". So far as I can see, the Mercury set-up is the
same on both machines. They are both on the same LAN (just different ports
on the same cable DSL router) and I am using the same account at the same
ISP to try to send mail. The firewall settings are the same on both
machines, and I have also tried SMTP on the XP2 machine with the firewall
turned off, but this doesn't help.
The Mercury core module shows the outgoing mail (from Outlook Express) being
processed correctly. Strangely enough, although the XP2 Mercury will not
send mail originating from Outlook Express, it will send a message from its
own limited e-mail client.
I have also tried to send mail from the XP1 machine, but using the XP2
machine Mercury as the server. The same failure occurs. Outlook Express
works fine through Mercury when I use the XP1 machine as the Mercury server.
I have seen some references to this error from a Google search, but I have
found nothing useful (most of the problems seem to relate to dial-up
connections). I haven't found anything on this newsgroup.
Thank you
Gordon

I don't know about your problem directly, but on the system I am running
Mercury (XP sp2), I have to turn off the windows firewall. Setting the
ports to allow Mercury doesn't work.

[Mike Preston]

Gordon,

On Thu, 28 Apr 2005 20:42:03 -0400, "Gordon J. Marwood"

Post by Gordon J. Marwood
Thank you for the reply. At least you have confirmed for me that Mercury
will run on XP SP2. I am not using the Windows XP firewall, but I did try
turning off the firewall that I am using, and this didn't help. The XP SP1
machine, which is running Mercury successfully, also has the same firewall
and I don't have to turn it off for Mercury to work.

It would be better for future conversations if you didn't top-post.

Post by Gordon J. Marwood

Post by Jerry Park

Post by Gordon J. Marwood
I am new to Mercury, but it's been working well on a Windows XP SP1

machine.

Post by Jerry Park

Post by Gordon J. Marwood
I would like to move this mail-server function to a different machine

which

Post by Jerry Park

Post by Gordon J. Marwood
is running XP SP2. I installed Mercury on the XP2 machine and it seems

to

Post by Jerry Park

Post by Gordon J. Marwood
work except the SMTP Client (Relay Version). Whenever there is something

in

Post by Jerry Park

Post by Gordon J. Marwood
the queue to send, SMTP fails with "TCP/IP error during processing.

Error

Post by Jerry Park

Post by Gordon J. Marwood
FF servicing queue job". So far as I can see, the Mercury set-up is the
same on both machines. They are both on the same LAN (just different

ports

Post by Jerry Park

Post by Gordon J. Marwood
on the same cable DSL router) and I am using the same account at the same
ISP to try to send mail. The firewall settings are the same on both
machines, and I have also tried SMTP on the XP2 machine with the firewall
turned off, but this doesn't help.
The Mercury core module shows the outgoing mail (from Outlook Express)

being

Post by Jerry Park

Post by Gordon J. Marwood
processed correctly. Strangely enough, although the XP2 Mercury will not
send mail originating from Outlook Express, it will send a message from

its

Post by Jerry Park

Post by Gordon J. Marwood
own limited e-mail client.
I have also tried to send mail from the XP1 machine, but using the XP2
machine Mercury as the server. The same failure occurs. Outlook Express
works fine through Mercury when I use the XP1 machine as the Mercury

server.

Post by Jerry Park

Post by Gordon J. Marwood
I have seen some references to this error from a Google search, but I

have

Post by Jerry Park

Post by Gordon J. Marwood
found nothing useful (most of the problems seem to relate to dial-up
connections). I haven't found anything on this newsgroup.
Thank you
Gordon

I don't know about your problem directly, but on the system I am running
Mercury (XP sp2), I have to turn off the windows firewall. Setting the
ports to allow Mercury doesn't work.

I have 4.01b on XP sp2, I have the windows firewall in operation and
my SMTP Client (relay version) works just fine.

Have you:

1) Enabled SMTP in the windows firewall?

2) Enabled the Mercury Core process in the windows firewall?

3) Port Forwarded SMTP (25 and, perhaps, 2525) to the machine you are
using as the server? That is, after you tested the machine that works
as a server, before you attempted to use the machine that doesn't work
as a server, did you modify the Port Forwarding, if any,
appropriately?

Have you checked HELP|ABOUT to confirm that the temporary files are
pointed to the proper place and that you have all rights necessary?

Maybe the fact that I'm running b rather than a makes the difference?

mike

[Gordon J. Marwood]

I just had an interesting result. I had been running Mercury with SMTP
"Session Logging" disabled. However, I enabled Session Logging to try to
see what was going on with the TCP/IP failures and SMTP then worked fine. I
have now sent three messages with logging enabled and each one was
successful. However, when I disable Session Logging again, I am back to the
failure situation. I wonder if there could be a timing issue of some sort?

Gordon

[tomk]

Post by Gordon J. Marwood
I just had an interesting result. I had been running Mercury with SMTP
"Session Logging" disabled. However, I enabled Session Logging to try to
see what was going on with the TCP/IP failures and SMTP then worked fine. I
have now sent three messages with logging enabled and each one was
successful. However, when I disable Session Logging again, I am back to the
failure situation. I wonder if there could be a timing issue of some sort?
Gordon

did you change the tcp/ip timeout? the help file suggests 600. i think
it defaults to something like 30.

[Gordon J. Marwood]

Post by tomk

Post by Gordon J. Marwood
I just had an interesting result. I had been running Mercury with SMTP
"Session Logging" disabled. However, I enabled Session Logging to try to
see what was going on with the TCP/IP failures and SMTP then worked fine. I
have now sent three messages with logging enabled and each one was
successful. However, when I disable Session Logging again, I am back to the
failure situation. I wonder if there could be a timing issue of some sort?
Gordon

did you change the tcp/ip timeout? the help file suggests 600. i think
it defaults to something like 30.

On my XP SP1 machine, the SMTP client works fine with a 30 sec TCP/IP
timeout. I tried changing the setting to 600 sec on the XP SP2 machine and
this didn't help.

With Session Logging ON, the XP SP2 machine is working fine. I have found
no problems with that configuration and have sent mail from both the server
machine and from another machine on my network, using the XP SP2 machine as
it's server. However, I find it strange why I have to use this setting to
get things to work.

I have applied the 4.01b patch and this makes no difference.

Thank you for the suggestion.

Gorrdon

[Mike Preston]

On Fri, 29 Apr 2005 16:36:13 -0400, "Gordon J. Marwood"

Post by Gordon J. Marwood
I just had an interesting result. I had been running Mercury with SMTP
"Session Logging" disabled. However, I enabled Session Logging to try to
see what was going on with the TCP/IP failures and SMTP then worked fine. I
have now sent three messages with logging enabled and each one was
successful. However, when I disable Session Logging again, I am back to the
failure situation. I wonder if there could be a timing issue of some sort?

I admit to having Session Logging enabled, as well. I wouldn't have
thought it relevant either.

Glad it is working!

mike

[Gordon J. Marwood]

Post by Mike Preston
On Fri, 29 Apr 2005 16:36:13 -0400, "Gordon J. Marwood"

Post by Gordon J. Marwood
I just had an interesting result. I had been running Mercury with SMTP
"Session Logging" disabled. However, I enabled Session Logging to try to
see what was going on with the TCP/IP failures and SMTP then worked fine.

I

Post by Mike Preston

Post by Gordon J. Marwood
have now sent three messages with logging enabled and each one was
successful. However, when I disable Session Logging again, I am back to the
failure situation. I wonder if there could be a timing issue of some sort?

I admit to having Session Logging enabled, as well. I wouldn't have
thought it relevant either.
Glad it is working!
mike

Thank you Mike. The machine with the problem is the faster of the two (AMD
XP3200 ... the other being an AMD XP2100), so maybe this is just enough to
cause some timing issues, though this rather surprises me. Anyway,
everything seems to be working OK with session logging on, so I should be
happy about that.

Gordon

[Mike Preston]

On Sat, 30 Apr 2005 10:14:15 -0400, "Gordon J. Marwood"

Post by Gordon J. Marwood

Post by Mike Preston
On Fri, 29 Apr 2005 16:36:13 -0400, "Gordon J. Marwood"

Post by Gordon J. Marwood
I just had an interesting result. I had been running Mercury with SMTP
"Session Logging" disabled. However, I enabled Session Logging to try to
see what was going on with the TCP/IP failures and SMTP then worked fine.

I

Post by Mike Preston

Post by Gordon J. Marwood
have now sent three messages with logging enabled and each one was
successful. However, when I disable Session Logging again, I am back to

the

Post by Mike Preston

Post by Gordon J. Marwood
failure situation. I wonder if there could be a timing issue of some

sort?

Post by Mike Preston
I admit to having Session Logging enabled, as well. I wouldn't have
thought it relevant either.
Glad it is working!
mike

Thank you Mike. The machine with the problem is the faster of the two (AMD
XP3200 ... the other being an AMD XP2100), so maybe this is just enough to
cause some timing issues, though this rather surprises me. Anyway,
everything seems to be working OK with session logging on, so I should be
happy about that.

Indeed. Remember to delete the logs every month or two.

mike

[Vimal]

Post by Mike Preston
On Sat, 30 Apr 2005 10:14:15 -0400, "Gordon J. Marwood"

Post by Gordon J. Marwood

Post by Mike Preston
On Fri, 29 Apr 2005 16:36:13 -0400, "Gordon J. Marwood"

Post by Gordon J. Marwood
I just had an interesting result. I had been running Mercury with SMTP
"Session Logging" disabled. However, I enabled Session Logging to try to
see what was going on with the TCP/IP failures and SMTP then worked fine.

I

Post by Mike Preston

Post by Gordon J. Marwood
have now sent three messages with logging enabled and each one was
successful. However, when I disable Session Logging again, I am back to

the

Post by Mike Preston

Post by Gordon J. Marwood
failure situation. I wonder if there could be a timing issue of some

sort?

Post by Mike Preston
I admit to having Session Logging enabled, as well. I wouldn't have
thought it relevant either.
Glad it is working!
mike

Thank you Mike. The machine with the problem is the faster of the two (AMD
XP3200 ... the other being an AMD XP2100), so maybe this is just enough to
cause some timing issues, though this rather surprises me. Anyway,
everything seems to be working OK with session logging on, so I should be
happy about that.

Indeed. Remember to delete the logs every month or two.
mike

I have the same problem with my Mercury Mail server. It does this every now
and then. Are you relaying your mail to a Symantec SMTP Gateway by any
chance? What I normally do is stop and start the Symantec SMTP service on
the machin I am forwading to and this usually fixes it.