message not delivered due to "broken pipe"

Michele

posted Dec 4 '07 at 8:37 pm

Apparently the issue isn't as solved as I hoped.

We got several more failures over the weekend. I was able to have one of the problem messages sent to my personal gmail account. The attachment was in pdf format, and was 293K. When I tried to forward that from gmail to the originally intended office address in Pegasus I could see the message hit the SMPT server on Mercury, but it never went to the core - or to intended mailbox.

I spoke to the ISP (who say it is not a problem on their end) and our consultant who suggested it might be a problem with timing out. The TCP/IP is set to 60 - should it be higher?

Also - I tried to update to v 4.01c. I did manage to get to 4.01b (which I needed before attempting to patch to c) but I can not get the 4.01c patch to apply. I exited Mercury. Copied the dll file into the Mercury directory - restarted...and still show v 4.01b as the current version. Any ideas on that?

thanks in advance

Michele

Apparently the issue isn't as solved as I hoped.&nbsp;We got several more failures over the weekend.&nbsp; I was able to have one of the problem messages sent to my personal gmail account.&nbsp; The attachment was in pdf format, and was 293K.&nbsp; When I tried to forward that from gmail to the originally intended office address in Pegasus&nbsp; I could see the message hit the SMPT server on Mercury, but it never went to the core - or to intended mailbox.&nbsp; &nbsp;I spoke to the ISP (who say it is not a problem on their end) and our consultant who suggested it might be a problem with timing out.&nbsp; The TCP/IP is set to 60 - should it be higher?&nbsp;Also - I tried to update to v 4.01c.&nbsp; I did manage to get to 4.01b (which I needed before attempting to patch to c) but I can not get the 4.01c patch to apply.&nbsp; I exited Mercury.&nbsp; Copied the dll file into the Mercury directory - restarted...and still show v 4.01b as the current version.&nbsp; Any ideas on that?&nbsp;thanks in advanceMichele&nbsp;

Michele

posted Nov 27 '07 at 7:20 pm

An individual was trying to send a message with a 12MB attachment. The messages was returned to the sender with this reason:

A message that you sent has not been delivered to all of its recipients
after more than 12 hours on the queue on smtp1.primushost.com.

The message identifier is:     1IwfgA-0006JH-IJ

The subject of the message is: Case Process

The date of the message is:    Mon, 26 Nov 2007 08:43:54 -0500

The following address(es) have not yet been delivered:

Laurie@XXXXXX.com

    Delay reason: Broken pipe:

    mail.XXXXXX.com [XXX.XXX.XX.X]

I have contacted our ISP (Primus) and they determined it was a limit set in our mail server (running Mercury/32 v 4.01a

Any idea where I can check size limits or how to fix a broken pipe?

&nbsp;An individual was trying to send a message with a 12MB attachment.&nbsp; The messages was returned to the sender with this reason: A message that you sent has not been delivered to all of its recipients after more than 12 hours on the queue on smtp1.primushost.com. &nbsp; The message identifier is:&nbsp;&nbsp;&nbsp;&nbsp; 1IwfgA-0006JH-IJ &nbsp; The subject of the message is: Case Process &nbsp; The date of the message is:&nbsp;&nbsp;&nbsp; Mon, 26 Nov 2007 08:43:54 -0500 The following address(es) have not yet been delivered: &nbsp; Laurie@XXXXXX.com &nbsp;&nbsp;&nbsp; Delay reason: Broken pipe: &nbsp;&nbsp;&nbsp; mail.XXXXXX.com [XXX.XXX.XX.X] &nbsp;I have contacted our ISP (Primus) and they determined it was a limit set in our mail server (running Mercury/32 v 4.01a&nbsp;Any idea where I can check size limits or how to fix a broken pipe?&nbsp;MR&nbsp;

Rolf Lindby

posted Nov 27 '07 at 11:03 pm

If you are receiving messages via the SMTP module there is a setting (Configuration/Mercury SMTP Server/General/ESMTP maximum size) to control this. The default value 0 means no limit.

"Broken pipe" seems to indicate some sort of networking problem, that could be anywhere in the Internet between the sender's server and your server.

If you are receiving mail via SMTP from the Internet you need to update your system to version 4.01c (or 4.52) instantly (really really important):
http://www.pmail.com/patches.htm

/Rolf

If you are receiving messages via the SMTP module there is a setting (Configuration/Mercury SMTP Server/General/ESMTP maximum size) to control this. The default value 0 means no limit. "Broken pipe" seems to indicate some sort of networking problem, that could be anywhere in the Internet between the sender's server and your server.If you are receiving mail via SMTP from the Internet you need to update your system to version 4.01c (or 4.52) instantly (really really important): http://www.pmail.com/patches.htm /Rolf&nbsp;

Michele

posted Nov 27 '07 at 11:27 pm

Yes, but the attachments were sent a few different times (on different days) and we've had no other problems receiving mail. Eventually we convinced the person to zip the files and we received them with no further problems.

I did find the ESMTP setting - it was already set to "0"

thanks for the help. I feel less alone now

&nbsp;Yes, but the attachments were sent a few different times (on different days) and we've had no other problems receiving mail.&nbsp; Eventually we convinced the person to zip the files and we received them with no further problems. &nbsp;I did find the ESMTP setting - it was already set to "0"&nbsp;&nbsp;thanks for the help.&nbsp; I feel less alone now &nbsp;MR&nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history