Agrippa
asked on
Deferred: Broken Pipe - Internal or External problem?
Hi All,
Major problem. Several customers experience the same problem: Deferred: Broken Pipe error message when sending email to their own internal Exchange 2007 server. This error occurs when there is an attachment of 1MB or more. They all have Internet from the same ISP, cable (no ADSL). I have learned that this has something to do with an incorrect MTU size. Within all hardware of the company the size is 1500. There is a spamfilter between the outside world and the Exchange server. WITH this spamfilter this error occurs. WITHOUT this spamfilter no problem. The filter itself is not the problem, at 98% of all domain using this filter it works fine.
Here are the tracert's of a working and failing situation:
FAILING:
TracePath Output:
1: luna.subnetonline.net (85.17.185.51) 0.132ms pmtu 1500
1: gi7-0.r1.sbp.leaseweb.net (85.17.250.253) 20.783ms
2: 85.17.129.37 (85.17.129.37) 1.252ms
3: be11.crs.evo.leaseweb.net (85.17.100.225) 4.006ms
4: ziggo.nikhef.nl-ix.net (193.239.116.136) asymm 5 1.418ms
5: tb-rc0001-cr102-ae0-0.core .as9143.ne t (213.51.158.155) asymm 6 53.913ms
6: tb-rc0001-dr101-lo0-0.core .as9143.ne t (213.51.125.2) asymm 7 3.423ms pmtu 1456
7: 5ED39579.cm-7-4c.dynamic.z iggo.nl (94.211.149.121) 17.378ms
8: D57D3F0B.static.ziggozakel ijk.nl (213.125.63.11) 14.772ms
9: no reply
10: no reply
11: no reply
12: no reply
WORKING:
TracePath Output:
1: luna.subnetonline.net (85.17.185.51) 0.133ms pmtu 1456
1: gi7-0.r1.sbp.leaseweb.net (85.17.250.253) 0.901ms
2: 85.17.129.37 (85.17.129.37) 0.710ms
3: be11.crs.evo.leaseweb.net (85.17.100.225) 2.780ms
4: ziggo.nikhef.nl-ix.net (193.239.116.136) asymm 5 12.539ms
5: ht-rc0001-cr102-ae0-0.core .as9143.ne t (213.51.158.103) asymm 6 3.027ms
6: ht-rc0001-dr101-lo0-0.core .as9143.ne t (213.51.124.2) asymm 7 3.184ms
7: 541ECB0D.cm-5-7d.dynamic.z iggo.nl (84.30.203.13) 12.261ms
8: D57D11A3.static.ziggozakel ijk.nl (213.125.17.163) asymm 7 17.523ms
9: no reply
10: no reply
11: no reply
12: no reply
Fingers crossed :-)
Major problem. Several customers experience the same problem: Deferred: Broken Pipe error message when sending email to their own internal Exchange 2007 server. This error occurs when there is an attachment of 1MB or more. They all have Internet from the same ISP, cable (no ADSL). I have learned that this has something to do with an incorrect MTU size. Within all hardware of the company the size is 1500. There is a spamfilter between the outside world and the Exchange server. WITH this spamfilter this error occurs. WITHOUT this spamfilter no problem. The filter itself is not the problem, at 98% of all domain using this filter it works fine.
Here are the tracert's of a working and failing situation:
FAILING:
TracePath Output:
1: luna.subnetonline.net (85.17.185.51) 0.132ms pmtu 1500
1: gi7-0.r1.sbp.leaseweb.net (85.17.250.253) 20.783ms
2: 85.17.129.37 (85.17.129.37) 1.252ms
3: be11.crs.evo.leaseweb.net (85.17.100.225) 4.006ms
4: ziggo.nikhef.nl-ix.net (193.239.116.136) asymm 5 1.418ms
5: tb-rc0001-cr102-ae0-0.core
6: tb-rc0001-dr101-lo0-0.core
7: 5ED39579.cm-7-4c.dynamic.z
8: D57D3F0B.static.ziggozakel
9: no reply
10: no reply
11: no reply
12: no reply
WORKING:
TracePath Output:
1: luna.subnetonline.net (85.17.185.51) 0.133ms pmtu 1456
1: gi7-0.r1.sbp.leaseweb.net (85.17.250.253) 0.901ms
2: 85.17.129.37 (85.17.129.37) 0.710ms
3: be11.crs.evo.leaseweb.net (85.17.100.225) 2.780ms
4: ziggo.nikhef.nl-ix.net (193.239.116.136) asymm 5 12.539ms
5: ht-rc0001-cr102-ae0-0.core
6: ht-rc0001-dr101-lo0-0.core
7: 541ECB0D.cm-5-7d.dynamic.z
8: D57D11A3.static.ziggozakel
9: no reply
10: no reply
11: no reply
12: no reply
Fingers crossed :-)
ASKER
Hi JamesGolden,
there are no limitations on the spamfilter and I doubt it will be something simple, unfortunately. Also 98% of all domains in that spamfilter work fine, even with 15MB attachments.
there are no limitations on the spamfilter and I doubt it will be something simple, unfortunately. Also 98% of all domains in that spamfilter work fine, even with 15MB attachments.
Can you attach one of the full bounce messages that contain the broken pipe error? Obviously blot out any sensitive names or IP addresses first.
Also, if you intentionally send spam to a personal account (as you describe these users doing with attachments) and the spam filter blocks them, does it do so with a different error than "broken pipe", or is it the same?
Also, if you intentionally send spam to a personal account (as you describe these users doing with attachments) and the spam filter blocks them, does it do so with a different error than "broken pipe", or is it the same?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Own solution was the right one in this case
Check the settings on the spam filter for attachment limitations.