Failed Mail

[wfl]

For no reason I can see our V5 client has started giving the foillowing error when we try and send mail;

>>>>>

Failed to communicate with the SMTP server.

Possible Cause:
Network transmission problems.

Recommendation:
Retry

Resolution:
If retry fails, check your SMTP settings
or contact your ISP.


The error was:
58325<email address>Unable to write to mail socket (10: Broken pipe

Command: send Filename:

<<<<

The PC itself sends and receives mail fine.

Our SMTP is open but I have tried others and localhost without any luck.

I have tried deleting files and then stopping and starting everything.

It has the appearance of a stuck spooler.

[Mark]

We have 2 clients with the exact same problem - 1 on v5 and 1 on v6.

The v6 client's stopped for about a week and then rectified itself.

The v5 has been out for about a fortnight now.

Any ideas would be appreciated.

[wfl]

I've had it a couple of times but after deleting a few mails it corrected itself.

At the time I thought mabe it was some kind of spooler problem but that doesn't seem to be the case.

Anyhow I have just discovered a load of these errors in the web server error file.

This one corresponds to sending mail from our client PC;

Program = MailScri, Program version = 6 , HTTP Server = Apache/1.3.28 (Unix) , Return code = 999 , Date and Time = 12/08/2003 14:36:34, Internal Errors = Unable to write to the mail socket (10: Broken pipe)

And this one coresponds to the web server sending mail;

Program = ORDERSCR, Program version = 356 , HTTP Server = Apache/1.3.28 (Unix) , Return code = 999 , Date and Time = 12/08/2003 14:56:17, Internal Errors = Unable to write to the mail socket (10: Broken pipe)

The problem seems to be occuring on the webs server and the client send mail but I can't see why the client ever involves the web server in sending mail.

[cdicken]

but I can't see why the client ever involves the web server in sending mail.

When the Actinic desktop application sends an email, it connects to the Perl online, and sends the email via the Perl scripts - so the actual operation is actually pretty identical to when the Customer Receipt email is generated by the online Perl scripts.

Hope this helps you track down the problem.

[wfl]

Thanks Chris

The problem vanished this morning of it's own accord