Re: sendmail Broken Pipe Error
On Sun, Mar 30, 2014 at 12:44 PM, Allan Jude wrote: > On 2014-03-30 15:31, Willy Offermans wrote: > > Hello Rick and FreeBSD friends, > > > > How can I save this setting in the rc.conf file to disable TSO at > startup? > > > > add -tso to the ifconfig line: > > ifconfig_bge0="inet netmask -tso" > -- > Allan Jude > > I'd recommend that people stop using the long obsolete netmask form of ifconfig, especially when making suggestions to others. CIDR notation is about two decades old now. ifconfig_bge0="inet -tso" -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: sendmail Broken Pipe Error
On 2014-03-30 15:31, Willy Offermans wrote: > Hello Rick and FreeBSD friends, > > On Fri, Mar 28, 2014 at 06:25:23PM -0400, Rick Macklem wrote: >> John-Mark Gurney wrote: >>> Willy Offermans wrote this message on Thu, Mar 27, 2014 at 15:46 >>> +0100: Hello John-Mark and FreeBSD friends, On Wed, Mar 26, 2014 at 04:04:27PM -0700, John-Mark Gurney wrote: > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 18:22 > +0100: >> Hello John-Mark and FreeBSD friends, >> >> On Wed, Mar 26, 2014 at 09:20:35AM -0700, John-Mark Gurney >> wrote: >>> Willy Offermans wrote this message on Wed, Mar 26, 2014 at >>> 12:17 +0100: On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > Willy Offermans wrote this message on Tue, Mar 25, 2014 > at 11:39 +0100: >> I'm not an expert in tcpdump. Can anyone make sense out >> of the messages? > > If you dumped the contents, using -s 0 -X, and look at > that last packet > you should see 0d 0a 2e 0d 0a at the end.. which is > CR/LF/./CR/LF.. If > you don't see that, then for some reason sendmail/FreeBSD > isn't telling > the server that it's done sending which would prevent the > receiving > side from ack'ing the email causing the timeout... I followed your suggestions. However I'm not able to distinguish the last packet. Is there a way to find this with help of the Flags? The following is the output of tcpdump -r /root/tmp/tcpdump -X | grep Flags 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags [S], seq 1001452351, win 65535, options [mss 1448,nop,wscale 6,sackOK,TS val 407239960 ecr 0], length 0 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags [S.], seq 1277075046, ack 1001452352, win 8192, options [mss 1452], length 0 >>> >>> It should look something like: >>> 09:18:34.723280 IP jmgmac.funkthat.com.64724 > >>> h2.funkthat.com.ssh: Flags [.], ack 177, win 33280, options >>> [nop,nop,TS val 1854905469 ecr 3482476972], length 0 >>> 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 >>> E..4..@.@... >>> 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc >>> ~H#..rC. >>> 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d >>> |...n..} >>> 0x0030: cf92 61ac >>>..a. >>> >>> Notice the hex output... I didn't see any of that in your >>> output... >>> The last packet I was talking about is the last one that had >>> length >>> 1448 that your server sent... >> >> I sent two e-mails consecutively: the first without an >> attachment, the >> second with attachment. I dumped tcp of the NIC for port smtp. >> I got the >> following: >> >> >> 12:20:55.988622 IP MyServer.com.37191 > Smarthost.com.smtp: >> Flags [P.], seq 18943:19104, ack 412, win 65535, length 161 >> 0x: 4500 00c9 eebd 4000 4006 c0a8 0004 >> E.@.@... >> 0x0010: d54b 3f0d 9147 0019 4ea0 36dd 15a7 38a0 >> .K?..G..N.6...8. >> 0x0020: 5018 4481 2020 2020 2020 2020 >> P...D... >> 0x0030: 2020 2020 2020 2020 2020 2020 2020 2020 >> >> 0x0040: 2020 2020 2020 2020 2020 2020 2020 205c >> ...\ >> 0x0050: 2f20 205c 205e 0d0a 2020 2020 2020 2020 >> /..\.^.. >> 0x0060: 2020 2020 2020 2020 2020 2020 2020 2020 >> >> 0x0070: 2020 2020 2020 2020 2020 2020 2020 2020 >> >> 0x0080: 2020 202e 5c2e 5f2f 5f29 0d0a 0d0a 2020 >> \._/_).. >> 0x0090: 2020 2020 2020 2020 2020 2020 2020 2020 >> >> 0x00a0: 2020 2020 2020 2020 2020 2020 2020 2020 >> >> 0x00b0: 2020 2020 2077 2e46 7265 6542 5344 >> .www.FreeBSD >> 0x00c0: 2e6f 7267 0d0a 2e0d 0a >> .org. >> >> As predicted by John-Mark, the first ended with "0d0a 2e0d 0a". >> However it >> was not the last packet with length 1448. I hope that this will >> not spoil >> the party. Is the Flag [P.] more indicative? It looks like to >> me, but I'm >> just learning. >> >> Anyway the second mail ended with: >> >> 12:22:17.960896 IP MyServer.com.37191 > Smarthost.com.smtp: >> Flags [.], seq 35127:36575, ack 638, win 65535, length 1448 >> 0x: 4500 05d0 fe9d 4000 4006 c0a8
Re: sendmail Broken Pipe Error
Hello Rick and FreeBSD friends, On Fri, Mar 28, 2014 at 06:25:23PM -0400, Rick Macklem wrote: > John-Mark Gurney wrote: > > Willy Offermans wrote this message on Thu, Mar 27, 2014 at 15:46 > > +0100: > > > Hello John-Mark and FreeBSD friends, > > > > > > On Wed, Mar 26, 2014 at 04:04:27PM -0700, John-Mark Gurney wrote: > > > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 18:22 > > > > +0100: > > > > > Hello John-Mark and FreeBSD friends, > > > > > > > > > > On Wed, Mar 26, 2014 at 09:20:35AM -0700, John-Mark Gurney > > > > > wrote: > > > > > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at > > > > > > 12:17 +0100: > > > > > > > On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney > > > > > > > wrote: > > > > > > > > Willy Offermans wrote this message on Tue, Mar 25, 2014 > > > > > > > > at 11:39 +0100: > > > > > > > > > I'm not an expert in tcpdump. Can anyone make sense out > > > > > > > > > of the messages? > > > > > > > > > > > > > > > > If you dumped the contents, using -s 0 -X, and look at > > > > > > > > that last packet > > > > > > > > you should see 0d 0a 2e 0d 0a at the end.. which is > > > > > > > > CR/LF/./CR/LF.. If > > > > > > > > you don't see that, then for some reason sendmail/FreeBSD > > > > > > > > isn't telling > > > > > > > > the server that it's done sending which would prevent the > > > > > > > > receiving > > > > > > > > side from ack'ing the email causing the timeout... > > > > > > > > > > > > > > I followed your suggestions. However I'm not able to > > > > > > > distinguish the last > > > > > > > packet. Is there a way to find this with help of the Flags? > > > > > > > The following > > > > > > > is the output of tcpdump -r /root/tmp/tcpdump -X | grep > > > > > > > Flags > > > > > > > > > > > > > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: > > > > > > > Flags [S], seq 1001452351, win 65535, options [mss > > > > > > > 1448,nop,wscale 6,sackOK,TS val 407239960 ecr 0], length 0 > > > > > > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: > > > > > > > Flags [S.], seq 1277075046, ack 1001452352, win 8192, > > > > > > > options [mss 1452], length 0 > > > > > > > > > > > > It should look something like: > > > > > > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > > > > > > > h2.funkthat.com.ssh: Flags [.], ack 177, win 33280, options > > > > > > [nop,nop,TS val 1854905469 ecr 3482476972], length 0 > > > > > > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 > > > > > > E..4..@.@... > > > > > > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc > > > > > > ~H#..rC. > > > > > > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d > > > > > > |...n..} > > > > > > 0x0030: cf92 61ac > > > > > >..a. > > > > > > > > > > > > Notice the hex output... I didn't see any of that in your > > > > > > output... > > > > > > The last packet I was talking about is the last one that had > > > > > > length > > > > > > 1448 that your server sent... > > > > > > > > > > I sent two e-mails consecutively: the first without an > > > > > attachment, the > > > > > second with attachment. I dumped tcp of the NIC for port smtp. > > > > > I got the > > > > > following: > > > > > > > > > > > > > > > 12:20:55.988622 IP MyServer.com.37191 > Smarthost.com.smtp: > > > > > Flags [P.], seq 18943:19104, ack 412, win 65535, length 161 > > > > > 0x: 4500 00c9 eebd 4000 4006 c0a8 0004 > > > > > E.@.@... > > > > > 0x0010: d54b 3f0d 9147 0019 4ea0 36dd 15a7 38a0 > > > > > .K?..G..N.6...8. > > > > > 0x0020: 5018 4481 2020 2020 2020 2020 > > > > > P...D... > > > > > 0x0030: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > > > 0x0040: 2020 2020 2020 2020 2020 2020 2020 205c > > > > > ...\ > > > > > 0x0050: 2f20 205c 205e 0d0a 2020 2020 2020 2020 > > > > > /..\.^.. > > > > > 0x0060: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > > > 0x0070: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > > > 0x0080: 2020 202e 5c2e 5f2f 5f29 0d0a 0d0a 2020 > > > > > \._/_).. > > > > > 0x0090: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > > > 0x00a0: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > > > 0x00b0: 2020 2020 2077 2e46 7265 6542 5344 > > > > > .www.FreeBSD > > > > > 0x00c0: 2e6f 7267 0d0a 2e0d 0a > > > > > .org. > > > > > > > > > > As predicted by John-Mark, the first ended with "0d0a 2e0d 0a". > > > > > However it > > > > > was not the last packet with length 1448. I hope that this will > > > > > not spoil > > >
Re: sendmail Broken Pipe Error
* Willy Offermans [2014-03-24 14:36]: > Dear FreeBSD friends, > > Lately I have setup a new FreeBSD server with 10.0-STABLE. Most of it went > smoothly. However I have an issue with sendmail. Some of the mails can be > sent out correctly, some of them stay in /var/spool/mqueue/. The provided > error messages are in the latter case: > > Mar 24 14:16:01 MyServer sm-mta[11725]: s2ODCWT4011717: SYSERR(root): timeout > writing message to MyProvider.com: Broken pipe Mar 24 14:16:01 MyServer > sm-mta[11725]: s2ODCWT4011717: to=, delay=00:03:29, > xdelay=00:03:26, mailer=relay, pri=1284849, relay=MyProvider.com > [XXX.XXX.XXX.XXX], dsn=4.0.0, stat=Deferred > > I'm using Version 8.14.7 All was fine when I was using Version 8.14.5. Could be a number of things -- maybe even TLS? I am currently on 8.14.8 which is the latest. I have a pretty complex setup including milters galore with zero problems. Have you considered updating to the latest release? That might help. You can also try sending an email via debug in sendmail to MyProvider.com and see if there is something going on or perhaps provide us with a few more details.. -- | _o_ |_)o_ _ _ |_|_|(_||_|_> | \|/_/_(_) - Lucius.Tel -- ++ What the hell is it good for? ++ ++ -- Robert Lloyd (engineer of the Advanced Computing Systems ++ ++ Division of IBM), to colleagues who insisted that the ++ ++ microprocessor was the wave of the future, c. 1968 ++ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: sendmail Broken Pipe Error
John-Mark Gurney wrote: > Willy Offermans wrote this message on Thu, Mar 27, 2014 at 15:46 > +0100: > > Hello John-Mark and FreeBSD friends, > > > > On Wed, Mar 26, 2014 at 04:04:27PM -0700, John-Mark Gurney wrote: > > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 18:22 > > > +0100: > > > > Hello John-Mark and FreeBSD friends, > > > > > > > > On Wed, Mar 26, 2014 at 09:20:35AM -0700, John-Mark Gurney > > > > wrote: > > > > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at > > > > > 12:17 +0100: > > > > > > On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney > > > > > > wrote: > > > > > > > Willy Offermans wrote this message on Tue, Mar 25, 2014 > > > > > > > at 11:39 +0100: > > > > > > > > I'm not an expert in tcpdump. Can anyone make sense out > > > > > > > > of the messages? > > > > > > > > > > > > > > If you dumped the contents, using -s 0 -X, and look at > > > > > > > that last packet > > > > > > > you should see 0d 0a 2e 0d 0a at the end.. which is > > > > > > > CR/LF/./CR/LF.. If > > > > > > > you don't see that, then for some reason sendmail/FreeBSD > > > > > > > isn't telling > > > > > > > the server that it's done sending which would prevent the > > > > > > > receiving > > > > > > > side from ack'ing the email causing the timeout... > > > > > > > > > > > > I followed your suggestions. However I'm not able to > > > > > > distinguish the last > > > > > > packet. Is there a way to find this with help of the Flags? > > > > > > The following > > > > > > is the output of tcpdump -r /root/tmp/tcpdump -X | grep > > > > > > Flags > > > > > > > > > > > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: > > > > > > Flags [S], seq 1001452351, win 65535, options [mss > > > > > > 1448,nop,wscale 6,sackOK,TS val 407239960 ecr 0], length 0 > > > > > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: > > > > > > Flags [S.], seq 1277075046, ack 1001452352, win 8192, > > > > > > options [mss 1452], length 0 > > > > > > > > > > It should look something like: > > > > > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > > > > > > h2.funkthat.com.ssh: Flags [.], ack 177, win 33280, options > > > > > [nop,nop,TS val 1854905469 ecr 3482476972], length 0 > > > > > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 > > > > > E..4..@.@... > > > > > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc > > > > > ~H#..rC. > > > > > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d > > > > > |...n..} > > > > > 0x0030: cf92 61ac > > > > >..a. > > > > > > > > > > Notice the hex output... I didn't see any of that in your > > > > > output... > > > > > The last packet I was talking about is the last one that had > > > > > length > > > > > 1448 that your server sent... > > > > > > > > I sent two e-mails consecutively: the first without an > > > > attachment, the > > > > second with attachment. I dumped tcp of the NIC for port smtp. > > > > I got the > > > > following: > > > > > > > > > > > > 12:20:55.988622 IP MyServer.com.37191 > Smarthost.com.smtp: > > > > Flags [P.], seq 18943:19104, ack 412, win 65535, length 161 > > > > 0x: 4500 00c9 eebd 4000 4006 c0a8 0004 > > > > E.@.@... > > > > 0x0010: d54b 3f0d 9147 0019 4ea0 36dd 15a7 38a0 > > > > .K?..G..N.6...8. > > > > 0x0020: 5018 4481 2020 2020 2020 2020 > > > > P...D... > > > > 0x0030: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x0040: 2020 2020 2020 2020 2020 2020 2020 205c > > > > ...\ > > > > 0x0050: 2f20 205c 205e 0d0a 2020 2020 2020 2020 > > > > /..\.^.. > > > > 0x0060: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x0070: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x0080: 2020 202e 5c2e 5f2f 5f29 0d0a 0d0a 2020 > > > > \._/_).. > > > > 0x0090: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x00a0: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x00b0: 2020 2020 2077 2e46 7265 6542 5344 > > > > .www.FreeBSD > > > > 0x00c0: 2e6f 7267 0d0a 2e0d 0a > > > > .org. > > > > > > > > As predicted by John-Mark, the first ended with "0d0a 2e0d 0a". > > > > However it > > > > was not the last packet with length 1448. I hope that this will > > > > not spoil > > > > the party. Is the Flag [P.] more indicative? It looks like to > > > > me, but I'm > > > > just learning. > > > > > > > > Anyway the second mail ended with: > > > > > > > > 12:22:17.960896 IP MyServer.com.37191 > Smarthost.com.smtp: > > > > Flags [.], seq 35127:36575, ack 638, win 65535, length 1448
Re: sendmail Broken Pipe Error
Hello John-Mark and FreeBSD friends, On Thu, Mar 27, 2014 at 08:27:01PM -0700, John-Mark Gurney wrote: > Willy Offermans wrote this message on Thu, Mar 27, 2014 at 15:46 +0100: > > Hello John-Mark and FreeBSD friends, > > > > On Wed, Mar 26, 2014 at 04:04:27PM -0700, John-Mark Gurney wrote: > > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 18:22 +0100: > > > > Hello John-Mark and FreeBSD friends, > > > > > > > > On Wed, Mar 26, 2014 at 09:20:35AM -0700, John-Mark Gurney wrote: > > > > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 12:17 > > > > > +0100: > > > > > > On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > > > > > > > Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 > > > > > > > +0100: > > > > > > > > I'm not an expert in tcpdump. Can anyone make sense out of the > > > > > > > > messages? > > > > > > > > > > > > > > If you dumped the contents, using -s 0 -X, and look at that last > > > > > > > packet > > > > > > > you should see 0d 0a 2e 0d 0a at the end.. which is > > > > > > > CR/LF/./CR/LF.. If > > > > > > > you don't see that, then for some reason sendmail/FreeBSD isn't > > > > > > > telling > > > > > > > the server that it's done sending which would prevent the > > > > > > > receiving > > > > > > > side from ack'ing the email causing the timeout... > > > > > > > > > > > > I followed your suggestions. However I'm not able to distinguish > > > > > > the last > > > > > > packet. Is there a way to find this with help of the Flags? The > > > > > > following > > > > > > is the output of tcpdump -r /root/tmp/tcpdump -X | grep Flags > > > > > > > > > > > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags > > > > > > [S], seq 1001452351, win 65535, options [mss 1448,nop,wscale > > > > > > 6,sackOK,TS val 407239960 ecr 0], length 0 > > > > > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags > > > > > > [S.], seq 1277075046, ack 1001452352, win 8192, options [mss 1452], > > > > > > length 0 > > > > > > > > > > It should look something like: > > > > > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > h2.funkthat.com.ssh: > > > > > Flags [.], ack 177, win 33280, options [nop,nop,TS val 1854905469 ecr > > > > > 3482476972], length 0 > > > > > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 > > > > > E..4..@.@... > > > > > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc > > > > > ~H#..rC. > > > > > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d > > > > > |...n..} > > > > > 0x0030: cf92 61ac..a. > > > > > > > > > > Notice the hex output... I didn't see any of that in your output... > > > > > The last packet I was talking about is the last one that had length > > > > > 1448 that your server sent... > > > > > > > > I sent two e-mails consecutively: the first without an attachment, the > > > > second with attachment. I dumped tcp of the NIC for port smtp. I got the > > > > following: > > > > > > > > > > > > 12:20:55.988622 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [P.], > > > > seq 18943:19104, ack 412, win 65535, length 161 > > > > 0x: 4500 00c9 eebd 4000 4006 c0a8 0004 > > > > E.@.@... > > > > 0x0010: d54b 3f0d 9147 0019 4ea0 36dd 15a7 38a0 > > > > .K?..G..N.6...8. > > > > 0x0020: 5018 4481 2020 2020 2020 2020 > > > > P...D... > > > > 0x0030: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x0040: 2020 2020 2020 2020 2020 2020 2020 205c > > > > ...\ > > > > 0x0050: 2f20 205c 205e 0d0a 2020 2020 2020 2020 > > > > /..\.^.. > > > > 0x0060: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x0070: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x0080: 2020 202e 5c2e 5f2f 5f29 0d0a 0d0a 2020 > > > > \._/_).. > > > > 0x0090: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x00a0: 2020 2020 2020 2020 2020 2020 2020 2020 > > > > > > > > 0x00b0: 2020 2020 2077 2e46 7265 6542 5344 > > > > .www.FreeBSD > > > > 0x00c0: 2e6f 7267 0d0a 2e0d 0a .org. > > > > > > > > As predicted by John-Mark, the first ended with "0d0a 2e0d 0a". However > > > > it > > > > was not the last packet with length 1448. I hope that this will not > > > > spoil > > > > the party. Is the Flag [P.] more indicative? It looks like to me, but > > > > I'm > > > > just learning. > > > > > > > > Anyway the second mail ended with: > > > > > > > > 12:22:17.960896 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [.], > > > > seq 35127:36575, ack 638, win 65535, length 1448 > > > > 0x: 4500 05d0 fe9d 4000 4006 c0a8 0004 > > > > E.@.@... > > > > > > > > > >
Re: sendmail Broken Pipe Error
Willy Offermans wrote this message on Thu, Mar 27, 2014 at 15:46 +0100: > Hello John-Mark and FreeBSD friends, > > On Wed, Mar 26, 2014 at 04:04:27PM -0700, John-Mark Gurney wrote: > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 18:22 +0100: > > > Hello John-Mark and FreeBSD friends, > > > > > > On Wed, Mar 26, 2014 at 09:20:35AM -0700, John-Mark Gurney wrote: > > > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 12:17 +0100: > > > > > On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > > > > > > Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 > > > > > > +0100: > > > > > > > I'm not an expert in tcpdump. Can anyone make sense out of the > > > > > > > messages? > > > > > > > > > > > > If you dumped the contents, using -s 0 -X, and look at that last > > > > > > packet > > > > > > you should see 0d 0a 2e 0d 0a at the end.. which is > > > > > > CR/LF/./CR/LF.. If > > > > > > you don't see that, then for some reason sendmail/FreeBSD isn't > > > > > > telling > > > > > > the server that it's done sending which would prevent the receiving > > > > > > side from ack'ing the email causing the timeout... > > > > > > > > > > I followed your suggestions. However I'm not able to distinguish the > > > > > last > > > > > packet. Is there a way to find this with help of the Flags? The > > > > > following > > > > > is the output of tcpdump -r /root/tmp/tcpdump -X | grep Flags > > > > > > > > > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags > > > > > [S], seq 1001452351, win 65535, options [mss 1448,nop,wscale > > > > > 6,sackOK,TS val 407239960 ecr 0], length 0 > > > > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags > > > > > [S.], seq 1277075046, ack 1001452352, win 8192, options [mss 1452], > > > > > length 0 > > > > > > > > It should look something like: > > > > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > h2.funkthat.com.ssh: > > > > Flags [.], ack 177, win 33280, options [nop,nop,TS val 1854905469 ecr > > > > 3482476972], length 0 > > > > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 > > > > E..4..@.@... > > > > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc > > > > ~H#..rC. > > > > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d > > > > |...n..} > > > > 0x0030: cf92 61ac..a. > > > > > > > > Notice the hex output... I didn't see any of that in your output... > > > > The last packet I was talking about is the last one that had length > > > > 1448 that your server sent... > > > > > > I sent two e-mails consecutively: the first without an attachment, the > > > second with attachment. I dumped tcp of the NIC for port smtp. I got the > > > following: > > > > > > > > > 12:20:55.988622 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [P.], > > > seq 18943:19104, ack 412, win 65535, length 161 > > > 0x: 4500 00c9 eebd 4000 4006 c0a8 0004 E.@.@... > > > 0x0010: d54b 3f0d 9147 0019 4ea0 36dd 15a7 38a0 .K?..G..N.6...8. > > > 0x0020: 5018 4481 2020 2020 2020 2020 P...D... > > > 0x0030: 2020 2020 2020 2020 2020 2020 2020 2020 > > > 0x0040: 2020 2020 2020 2020 2020 2020 2020 205c ...\ > > > 0x0050: 2f20 205c 205e 0d0a 2020 2020 2020 2020 /..\.^.. > > > 0x0060: 2020 2020 2020 2020 2020 2020 2020 2020 > > > 0x0070: 2020 2020 2020 2020 2020 2020 2020 2020 > > > 0x0080: 2020 202e 5c2e 5f2f 5f29 0d0a 0d0a 2020 \._/_).. > > > 0x0090: 2020 2020 2020 2020 2020 2020 2020 2020 > > > 0x00a0: 2020 2020 2020 2020 2020 2020 2020 2020 > > > 0x00b0: 2020 2020 2077 2e46 7265 6542 5344 .www.FreeBSD > > > 0x00c0: 2e6f 7267 0d0a 2e0d 0a .org. > > > > > > As predicted by John-Mark, the first ended with "0d0a 2e0d 0a". However it > > > was not the last packet with length 1448. I hope that this will not spoil > > > the party. Is the Flag [P.] more indicative? It looks like to me, but I'm > > > just learning. > > > > > > Anyway the second mail ended with: > > > > > > 12:22:17.960896 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [.], > > > seq 35127:36575, ack 638, win 65535, length 1448 > > > 0x: 4500 05d0 fe9d 4000 4006 c0a8 0004 E.@.@... > > > > > > > > > 0x0560: 5670 6876 4a67 5a5a 5a50 4b2f 4b78 3774 VphvJgZZZPK/Kx7t > > > 0x0570: 382f 4230 594f 6b78 3449 0d0a 4a76 6551 8/B0YOkx4I..JveQ > > > 0x0580: 2b6e 7765 5647 2f33 6e79 6231 6133 496f +nweVG/3nyb1a3Io > > > 0x0590: 5474 554f 4d61 4374 696b 714b 436b 4959 TtUOMaCtikqKCkIY > > > 0x05a0: 704a 7668 3055 416d 6c33 4754 4f4c 6455 pJvh0UAml3GTOLdU > > > 0x05b0: 774b 4145 7151 5741 78
Re: sendmail Broken Pipe Error
Hello John-Mark and FreeBSD friends, On Wed, Mar 26, 2014 at 04:04:27PM -0700, John-Mark Gurney wrote: > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 18:22 +0100: > > Hello John-Mark and FreeBSD friends, > > > > On Wed, Mar 26, 2014 at 09:20:35AM -0700, John-Mark Gurney wrote: > > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 12:17 +0100: > > > > On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > > > > > Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 > > > > > +0100: > > > > > > I'm not an expert in tcpdump. Can anyone make sense out of the > > > > > > messages? > > > > > > > > > > If you dumped the contents, using -s 0 -X, and look at that last > > > > > packet > > > > > you should see 0d 0a 2e 0d 0a at the end.. which is CR/LF/./CR/LF.. > > > > > If > > > > > you don't see that, then for some reason sendmail/FreeBSD isn't > > > > > telling > > > > > the server that it's done sending which would prevent the receiving > > > > > side from ack'ing the email causing the timeout... > > > > > > > > I followed your suggestions. However I'm not able to distinguish the > > > > last > > > > packet. Is there a way to find this with help of the Flags? The > > > > following > > > > is the output of tcpdump -r /root/tmp/tcpdump -X | grep Flags > > > > > > > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags [S], > > > > seq 1001452351, win 65535, options [mss 1448,nop,wscale 6,sackOK,TS val > > > > 407239960 ecr 0], length 0 > > > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags [S.], > > > > seq 1277075046, ack 1001452352, win 8192, options [mss 1452], length 0 > > > > > > It should look something like: > > > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > h2.funkthat.com.ssh: Flags > > > [.], ack 177, win 33280, options [nop,nop,TS val 1854905469 ecr > > > 3482476972], length 0 > > > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 E..4..@.@... > > > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc ~H#..rC. > > > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d |...n..} > > > 0x0030: cf92 61ac..a. > > > > > > Notice the hex output... I didn't see any of that in your output... > > > The last packet I was talking about is the last one that had length > > > 1448 that your server sent... > > > > I sent two e-mails consecutively: the first without an attachment, the > > second with attachment. I dumped tcp of the NIC for port smtp. I got the > > following: > > > > > > 12:20:55.988622 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [P.], seq > > 18943:19104, ack 412, win 65535, length 161 > > 0x: 4500 00c9 eebd 4000 4006 c0a8 0004 E.@.@... > > 0x0010: d54b 3f0d 9147 0019 4ea0 36dd 15a7 38a0 .K?..G..N.6...8. > > 0x0020: 5018 4481 2020 2020 2020 2020 P...D... > > 0x0030: 2020 2020 2020 2020 2020 2020 2020 2020 > > 0x0040: 2020 2020 2020 2020 2020 2020 2020 205c ...\ > > 0x0050: 2f20 205c 205e 0d0a 2020 2020 2020 2020 /..\.^.. > > 0x0060: 2020 2020 2020 2020 2020 2020 2020 2020 > > 0x0070: 2020 2020 2020 2020 2020 2020 2020 2020 > > 0x0080: 2020 202e 5c2e 5f2f 5f29 0d0a 0d0a 2020 \._/_).. > > 0x0090: 2020 2020 2020 2020 2020 2020 2020 2020 > > 0x00a0: 2020 2020 2020 2020 2020 2020 2020 2020 > > 0x00b0: 2020 2020 2077 2e46 7265 6542 5344 .www.FreeBSD > > 0x00c0: 2e6f 7267 0d0a 2e0d 0a .org. > > > > As predicted by John-Mark, the first ended with "0d0a 2e0d 0a". However it > > was not the last packet with length 1448. I hope that this will not spoil > > the party. Is the Flag [P.] more indicative? It looks like to me, but I'm > > just learning. > > > > Anyway the second mail ended with: > > > > 12:22:17.960896 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [.], seq > > 35127:36575, ack 638, win 65535, length 1448 > > 0x: 4500 05d0 fe9d 4000 4006 c0a8 0004 E.@.@... > > > > > > 0x0560: 5670 6876 4a67 5a5a 5a50 4b2f 4b78 3774 VphvJgZZZPK/Kx7t > > 0x0570: 382f 4230 594f 6b78 3449 0d0a 4a76 6551 8/B0YOkx4I..JveQ > > 0x0580: 2b6e 7765 5647 2f33 6e79 6231 6133 496f +nweVG/3nyb1a3Io > > 0x0590: 5474 554f 4d61 4374 696b 714b 436b 4959 TtUOMaCtikqKCkIY > > 0x05a0: 704a 7668 3055 416d 6c33 4754 4f4c 6455 pJvh0UAml3GTOLdU > > 0x05b0: 774b 4145 7151 5741 7841 4141 5a66 7647 wKAEqQWAxAAAZfvG > > 0x05c0: 706b 6c36 0d0a 7a4e 6234 745a 6633 5a6c pkl6..zNb4tZf3Zl > > > > Being packet with length 1448 and sent from my side. The code "0d0a 2e0d > > 0a" is missing. Immediately thereafter the following packets: > > We clearly haven
Re: sendmail Broken Pipe Error
Willy Offermans wrote this message on Wed, Mar 26, 2014 at 18:22 +0100: > Hello John-Mark and FreeBSD friends, > > On Wed, Mar 26, 2014 at 09:20:35AM -0700, John-Mark Gurney wrote: > > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 12:17 +0100: > > > On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > > > > Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 +0100: > > > > > I'm not an expert in tcpdump. Can anyone make sense out of the > > > > > messages? > > > > > > > > If you dumped the contents, using -s 0 -X, and look at that last packet > > > > you should see 0d 0a 2e 0d 0a at the end.. which is CR/LF/./CR/LF.. If > > > > you don't see that, then for some reason sendmail/FreeBSD isn't telling > > > > the server that it's done sending which would prevent the receiving > > > > side from ack'ing the email causing the timeout... > > > > > > I followed your suggestions. However I'm not able to distinguish the last > > > packet. Is there a way to find this with help of the Flags? The following > > > is the output of tcpdump -r /root/tmp/tcpdump -X | grep Flags > > > > > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags [S], > > > seq 1001452351, win 65535, options [mss 1448,nop,wscale 6,sackOK,TS val > > > 407239960 ecr 0], length 0 > > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags [S.], > > > seq 1277075046, ack 1001452352, win 8192, options [mss 1452], length 0 > > > > It should look something like: > > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > h2.funkthat.com.ssh: Flags > > [.], ack 177, win 33280, options [nop,nop,TS val 1854905469 ecr > > 3482476972], length 0 > > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 E..4..@.@... > > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc ~H#..rC. > > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d |...n..} > > 0x0030: cf92 61ac..a. > > > > Notice the hex output... I didn't see any of that in your output... > > The last packet I was talking about is the last one that had length > > 1448 that your server sent... > > I sent two e-mails consecutively: the first without an attachment, the > second with attachment. I dumped tcp of the NIC for port smtp. I got the > following: > > > 12:20:55.988622 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [P.], seq > 18943:19104, ack 412, win 65535, length 161 > 0x: 4500 00c9 eebd 4000 4006 c0a8 0004 E.@.@... > 0x0010: d54b 3f0d 9147 0019 4ea0 36dd 15a7 38a0 .K?..G..N.6...8. > 0x0020: 5018 4481 2020 2020 2020 2020 P...D... > 0x0030: 2020 2020 2020 2020 2020 2020 2020 2020 > 0x0040: 2020 2020 2020 2020 2020 2020 2020 205c ...\ > 0x0050: 2f20 205c 205e 0d0a 2020 2020 2020 2020 /..\.^.. > 0x0060: 2020 2020 2020 2020 2020 2020 2020 2020 > 0x0070: 2020 2020 2020 2020 2020 2020 2020 2020 > 0x0080: 2020 202e 5c2e 5f2f 5f29 0d0a 0d0a 2020 \._/_).. > 0x0090: 2020 2020 2020 2020 2020 2020 2020 2020 > 0x00a0: 2020 2020 2020 2020 2020 2020 2020 2020 > 0x00b0: 2020 2020 2077 2e46 7265 6542 5344 .www.FreeBSD > 0x00c0: 2e6f 7267 0d0a 2e0d 0a .org. > > As predicted by John-Mark, the first ended with "0d0a 2e0d 0a". However it > was not the last packet with length 1448. I hope that this will not spoil > the party. Is the Flag [P.] more indicative? It looks like to me, but I'm > just learning. > > Anyway the second mail ended with: > > 12:22:17.960896 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [.], seq > 35127:36575, ack 638, win 65535, length 1448 > 0x: 4500 05d0 fe9d 4000 4006 c0a8 0004 E.@.@... > > > 0x0560: 5670 6876 4a67 5a5a 5a50 4b2f 4b78 3774 VphvJgZZZPK/Kx7t > 0x0570: 382f 4230 594f 6b78 3449 0d0a 4a76 6551 8/B0YOkx4I..JveQ > 0x0580: 2b6e 7765 5647 2f33 6e79 6231 6133 496f +nweVG/3nyb1a3Io > 0x0590: 5474 554f 4d61 4374 696b 714b 436b 4959 TtUOMaCtikqKCkIY > 0x05a0: 704a 7668 3055 416d 6c33 4754 4f4c 6455 pJvh0UAml3GTOLdU > 0x05b0: 774b 4145 7151 5741 7841 4141 5a66 7647 wKAEqQWAxAAAZfvG > 0x05c0: 706b 6c36 0d0a 7a4e 6234 745a 6633 5a6c pkl6..zNb4tZf3Zl > > Being packet with length 1448 and sent from my side. The code "0d0a 2e0d > 0a" is missing. Immediately thereafter the following packets: We clearly haven't gotten the last mime-boundary, we are still in the base64 encoded data of the attachment... > 12:22:18.003557 IP Smarthost.com.smtp > MyServer.com.37191: Flags [.], ack > 36575, win 65160, length 0 > 0x: 4500 0028 11fb 4000 7a06 19d0 d54b 3f0d E..(..@.zK?. > 0x0010: c0a8 0004 0019 9147 15a7 3982 4ea0
Re: sendmail Broken Pipe Error
Hello John-Mark and FreeBSD friends, On Wed, Mar 26, 2014 at 09:20:35AM -0700, John-Mark Gurney wrote: > Willy Offermans wrote this message on Wed, Mar 26, 2014 at 12:17 +0100: > > On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > > > Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 +0100: > > > > I'm not an expert in tcpdump. Can anyone make sense out of the messages? > > > > > > If you dumped the contents, using -s 0 -X, and look at that last packet > > > you should see 0d 0a 2e 0d 0a at the end.. which is CR/LF/./CR/LF.. If > > > you don't see that, then for some reason sendmail/FreeBSD isn't telling > > > the server that it's done sending which would prevent the receiving > > > side from ack'ing the email causing the timeout... > > > > I followed your suggestions. However I'm not able to distinguish the last > > packet. Is there a way to find this with help of the Flags? The following > > is the output of tcpdump -r /root/tmp/tcpdump -X | grep Flags > > > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags [S], seq > > 1001452351, win 65535, options [mss 1448,nop,wscale 6,sackOK,TS val > > 407239960 ecr 0], length 0 > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags [S.], seq > > 1277075046, ack 1001452352, win 8192, options [mss 1452], length 0 > > It should look something like: > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > h2.funkthat.com.ssh: Flags > [.], ack 177, win 33280, options [nop,nop,TS val 1854905469 ecr 3482476972], > length 0 > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 E..4..@.@... > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc ~H#..rC. > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d |...n..} > 0x0030: cf92 61ac..a. > > Notice the hex output... I didn't see any of that in your output... > The last packet I was talking about is the last one that had length > 1448 that your server sent... > > -- > John-Mark GurneyVoice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" I sent two e-mails consecutively: the first without an attachment, the second with attachment. I dumped tcp of the NIC for port smtp. I got the following: 12:20:55.988622 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [P.], seq 18943:19104, ack 412, win 65535, length 161 0x: 4500 00c9 eebd 4000 4006 c0a8 0004 E.@.@... 0x0010: d54b 3f0d 9147 0019 4ea0 36dd 15a7 38a0 .K?..G..N.6...8. 0x0020: 5018 4481 2020 2020 2020 2020 P...D... 0x0030: 2020 2020 2020 2020 2020 2020 2020 2020 0x0040: 2020 2020 2020 2020 2020 2020 2020 205c ...\ 0x0050: 2f20 205c 205e 0d0a 2020 2020 2020 2020 /..\.^.. 0x0060: 2020 2020 2020 2020 2020 2020 2020 2020 0x0070: 2020 2020 2020 2020 2020 2020 2020 2020 0x0080: 2020 202e 5c2e 5f2f 5f29 0d0a 0d0a 2020 \._/_).. 0x0090: 2020 2020 2020 2020 2020 2020 2020 2020 0x00a0: 2020 2020 2020 2020 2020 2020 2020 2020 0x00b0: 2020 2020 2077 2e46 7265 6542 5344 .www.FreeBSD 0x00c0: 2e6f 7267 0d0a 2e0d 0a .org. As predicted by John-Mark, the first ended with "0d0a 2e0d 0a". However it was not the last packet with length 1448. I hope that this will not spoil the party. Is the Flag [P.] more indicative? It looks like to me, but I'm just learning. Anyway the second mail ended with: 12:22:17.960896 IP MyServer.com.37191 > Smarthost.com.smtp: Flags [.], seq 35127:36575, ack 638, win 65535, length 1448 0x: 4500 05d0 fe9d 4000 4006 c0a8 0004 E.@.@... 0x0560: 5670 6876 4a67 5a5a 5a50 4b2f 4b78 3774 VphvJgZZZPK/Kx7t 0x0570: 382f 4230 594f 6b78 3449 0d0a 4a76 6551 8/B0YOkx4I..JveQ 0x0580: 2b6e 7765 5647 2f33 6e79 6231 6133 496f +nweVG/3nyb1a3Io 0x0590: 5474 554f 4d61 4374 696b 714b 436b 4959 TtUOMaCtikqKCkIY 0x05a0: 704a 7668 3055 416d 6c33 4754 4f4c 6455 pJvh0UAml3GTOLdU 0x05b0: 774b 4145 7151 5741 7841 4141 5a66 7647 wKAEqQWAxAAAZfvG 0x05c0: 706b 6c36 0d0a 7a4e 6234 745a 6633 5a6c pkl6..zNb4tZf3Zl Being packet with length 1448 and sent from my side. The code "0d0a 2e0d 0a" is missing. Immediately thereafter the following packets: 12:22:18.003557 IP Smarthost.com.smtp > MyServer.com.37191: Flags [.], ack 36575, win 65160, length 0 0x: 4500 0028 11fb 4000 7a06 19d0 d54b 3f0d E..(..@.zK?. 0x0010: c0a8 0004 0019
Re: sendmail Broken Pipe Error
Gregory Shapiro wrote this message on Wed, Mar 26, 2014 at 09:23 -0700: > > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags [S], > > > seq 1001452351, win 65535, options [mss 1448,nop,wscale 6,sackOK,TS val > > > 407239960 ecr 0], length 0 > > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags [S.], > > > seq 1277075046, ack 1001452352, win 8192, options [mss 1452], length 0 > > > > It should look something like: > > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > h2.funkthat.com.ssh: Flags > > [.], ack 177, win 33280, options [nop,nop,TS val 1854905469 ecr > > 3482476972], length 0 > > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 E..4..@.@... > > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc ~H#..rC. > > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d |...n..} > > 0x0030: cf92 61ac..a. > > > > Notice the hex output... I didn't see any of that in your output... > > The last packet I was talking about is the last one that had length > > 1448 that your server sent... > > Willy mentioned that this only happened on mail with attachments. Could it > be an MTU issue? Specifically, see: > > http://www.sendmail.com/sm/open_source/tips/path_mtu/ I don't see how it could be... If it is litterally only mail with attachments and not large emails w/o attachments, then it's definately not that issue..He could just disable path_mtu on the server: sysctl net.inet.tcp.path_mtu_discovery=0 to test this, but I'd be surprised if it allows email through, since he's already getting 1448 byte packets through and acked before the hang up occurs... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: sendmail Broken Pipe Error
> > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags [S], seq > > 1001452351, win 65535, options [mss 1448,nop,wscale 6,sackOK,TS val > > 407239960 ecr 0], length 0 > > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags [S.], seq > > 1277075046, ack 1001452352, win 8192, options [mss 1452], length 0 > > It should look something like: > 09:18:34.723280 IP jmgmac.funkthat.com.64724 > h2.funkthat.com.ssh: Flags > [.], ack 177, win 33280, options [nop,nop,TS val 1854905469 ecr 3482476972], > length 0 > 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 E..4..@.@... > 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc ~H#..rC. > 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d |...n..} > 0x0030: cf92 61ac..a. > > Notice the hex output... I didn't see any of that in your output... > The last packet I was talking about is the last one that had length > 1448 that your server sent... Willy mentioned that this only happened on mail with attachments. Could it be an MTU issue? Specifically, see: http://www.sendmail.com/sm/open_source/tips/path_mtu/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: sendmail Broken Pipe Error
Willy Offermans wrote this message on Wed, Mar 26, 2014 at 12:17 +0100: > On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > > Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 +0100: > > > I'm not an expert in tcpdump. Can anyone make sense out of the messages? > > > > If you dumped the contents, using -s 0 -X, and look at that last packet > > you should see 0d 0a 2e 0d 0a at the end.. which is CR/LF/./CR/LF.. If > > you don't see that, then for some reason sendmail/FreeBSD isn't telling > > the server that it's done sending which would prevent the receiving > > side from ack'ing the email causing the timeout... > > I followed your suggestions. However I'm not able to distinguish the last > packet. Is there a way to find this with help of the Flags? The following > is the output of tcpdump -r /root/tmp/tcpdump -X | grep Flags > > 11:57:56.539788 IP MyServer.com.41115 > Smarthost.com.smtp: Flags [S], seq > 1001452351, win 65535, options [mss 1448,nop,wscale 6,sackOK,TS val 407239960 > ecr 0], length 0 > 11:57:56.555262 IP Smarthost.com.smtp > MyServer.com.41115: Flags [S.], seq > 1277075046, ack 1001452352, win 8192, options [mss 1452], length 0 It should look something like: 09:18:34.723280 IP jmgmac.funkthat.com.64724 > h2.funkthat.com.ssh: Flags [.], ack 177, win 33280, options [nop,nop,TS val 1854905469 ecr 3482476972], length 0 0x: 4510 0034 d7ac 4000 4006 e1af c0a8 0003 E..4..@.@... 0x0010: c0a8 0004 fcd4 0016 7e48 238e d872 43dc ~H#..rC. 0x0020: 8010 8200 7c08 0101 080a 6e8f 9c7d |...n..} 0x0030: cf92 61ac..a. Notice the hex output... I didn't see any of that in your output... The last packet I was talking about is the last one that had length 1448 that your server sent... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: sendmail Broken Pipe Error
Hello John-Mark Gurney, On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 +0100: > > I found the following command, that generates some more informative output, > > I hope. > > > > root@MyServer:/home/MyName # sendmail -q -v > > > > Running /var/spool/mqueue/s2ODs1hH016114 (sequence 1 of 2) > > ... Connecting to Smarhost.com via relay... > > 220 CPSMTPM-CMT109.MyProvider.com MyProvider.com Tue, 25 Mar 2014 10:45:21 > > +0100 > > >>> EHLO MyServer.MyDomain.com > > 250-CPSMTPM-CMT109.MyProvider.com Hello [77.170.60.162] > > 250-TURN > > 250-SIZE 15744000 > > 250-ETRN > > 250-PIPELINING > > 250-DSN > > 250-ENHANCEDSTATUSCODES > > 250-8bitmime > > 250-CHUNKING > > 250-VRFY > > 250 OK > > >>> MAIL From: SIZE=1254972 > > 250 2.1.0 MyName@MyRewrittenDomainNameSender OK > > >>> RCPT To: > > >>> DATA > > 250 2.1.5 MyFriend@MyFriendsDomainName > > 354 Start mail input; end with . > > timeout writing message to Smarhost.com: Broken pipe > > ... Deferred > > > > If I copy the *s2ODs1hH016114 files to MySecondServer and run > > sendmail -q -v once more, I got the following: > > > > Running /var/spool/mqueue/s2ODs1hH016114 (sequence 1 of 1) > > ... Connecting to Smarhost.com via relay... > > 220 CPSMTPM-cmt107.MyProvider.com MyProvider.com Tue, 25 Mar 2014 10:57:56 > > +0100 > > >>> EHLO MySecondServer.MyRewrittenDomainName > > 250-CPSMTPM-cmt107.MyProvider.com Hello [77.170.60.162] > > 250-TURN > > 250-SIZE 15744000 > > 250-ETRN > > 250-PIPELINING > > 250-DSN > > 250-ENHANCEDSTATUSCODES > > 250-8bitmime > > 250-CHUNKING > > 250-VRFY > > 250 OK > > >>> MAIL From: SIZE=1254972 > > 250 2.1.0 MyName@MyRewrittenDomainNameSender OK > > >>> RCPT To: > > >>> DATA > > 250 2.1.5 MyFriend@MyFriendsDomainName > > 354 Start mail input; end with . > > >>> . > > 250 2.6.0 <20140324135355.gc6...@vpn.mydomain.com> Queued mail for delivery > > ... Sent ( > > <20140324135355.gc6...@vpn.mydomain.com> > > Queued mail for delivery) > > Closing connection to Smarhost.com > > >>> QUIT > > 221 2.0.0 CPSMTPM-cmt107.MyProvider.com Service closing transmission > > channel > > > > The test shows me that the problem is not on the MyProvider side. > > > > The sendmail.cf files on the two server are identical, except the names of > > the > > servers and some comments. > > > > The sendmail versions are different and the FreeBSD versions are different: > > MyServer: > > Sendmail Version 8.14.7 > > FreeBSD 10.0-STABLE > > > > MySecondServer: > > Sendmail Version 8.14.5 > > FreeBSD 9.0-RELEASE-p4 > > > > It is also important to note that above can only be observed for some > > e-mails, not all. Thus some mails will be sent from MyServer, some are not! > > > > If I make a tcpdump during the connection between sendmail and smarthost > > concerning s2ODs1hH016114, I got the following: > > > > 11:24:23.301300 IP MyServer.MyDomain.com.49165 > DNSMyProvider.domain: > > 32794+ [1au] MX? Smarhost.com. (43) > > 11:24:23.320078 IP DNSMyProvider.domain > MyServer.MyDomain.com.49165: > > 32794 1/1/1 CNAME CNameMyProvider. (125) > > 11:24:23.321592 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [S], seq 2245424203, win 65535, options [mss 1448,nop,wscale > > 6,sackOK,TS val 318826742 ecr 0], length 0 > > 11:24:23.339171 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [S.], seq 2238169153, ack 2245424204, win 8192, options [mss 1452], > > length 0 > > 11:24:23.339221 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [.], ack 1, win 65535, length 0 > > 11:24:23.355143 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 1:84, ack 1, win 65160, length 83 > > 11:24:23.355254 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [P.], seq 1:24, ack 84, win 65535, length 23 > > 11:24:23.370795 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 84:276, ack 24, win 65137, length 192 > > 11:24:23.371025 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [P.], seq 24:76, ack 276, win 65535, length 52 > > 11:24:23.392751 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 276:326, ack 76, win 65085, length 50 > > 11:24:23.393010 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [P.], seq 76:119, ack 326, win 65535, length 43 > > 11:24:23.414297 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 326:364, ack 119, win 65042, length 38 > > 11:24:23.520345 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [.], ack 364, win 65535, length 0 > > 11:24:23.535218 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 364:410, ack 119, win 65042, length 46 > > 11:24:23.769098 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [.], seq 119:1567, ack 410, win 65535, length 1448 > > 11
Re: sendmail Broken Pipe Error
Hallo FreeBSD friends, On Tue, Mar 25, 2014 at 09:43:16AM -0700, John-Mark Gurney wrote: > Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 +0100: > > I found the following command, that generates some more informative output, > > I hope. > > > > root@MyServer:/home/MyName # sendmail -q -v > > > > Running /var/spool/mqueue/s2ODs1hH016114 (sequence 1 of 2) > > ... Connecting to Smarhost.com via relay... > > 220 CPSMTPM-CMT109.MyProvider.com MyProvider.com Tue, 25 Mar 2014 10:45:21 > > +0100 > > >>> EHLO MyServer.MyDomain.com > > 250-CPSMTPM-CMT109.MyProvider.com Hello [77.170.60.162] > > 250-TURN > > 250-SIZE 15744000 > > 250-ETRN > > 250-PIPELINING > > 250-DSN > > 250-ENHANCEDSTATUSCODES > > 250-8bitmime > > 250-CHUNKING > > 250-VRFY > > 250 OK > > >>> MAIL From: SIZE=1254972 > > 250 2.1.0 MyName@MyRewrittenDomainNameSender OK > > >>> RCPT To: > > >>> DATA > > 250 2.1.5 MyFriend@MyFriendsDomainName > > 354 Start mail input; end with . > > timeout writing message to Smarhost.com: Broken pipe > > ... Deferred > > > > If I copy the *s2ODs1hH016114 files to MySecondServer and run > > sendmail -q -v once more, I got the following: > > > > Running /var/spool/mqueue/s2ODs1hH016114 (sequence 1 of 1) > > ... Connecting to Smarhost.com via relay... > > 220 CPSMTPM-cmt107.MyProvider.com MyProvider.com Tue, 25 Mar 2014 10:57:56 > > +0100 > > >>> EHLO MySecondServer.MyRewrittenDomainName > > 250-CPSMTPM-cmt107.MyProvider.com Hello [77.170.60.162] > > 250-TURN > > 250-SIZE 15744000 > > 250-ETRN > > 250-PIPELINING > > 250-DSN > > 250-ENHANCEDSTATUSCODES > > 250-8bitmime > > 250-CHUNKING > > 250-VRFY > > 250 OK > > >>> MAIL From: SIZE=1254972 > > 250 2.1.0 MyName@MyRewrittenDomainNameSender OK > > >>> RCPT To: > > >>> DATA > > 250 2.1.5 MyFriend@MyFriendsDomainName > > 354 Start mail input; end with . > > >>> . > > 250 2.6.0 <20140324135355.gc6...@vpn.mydomain.com> Queued mail for delivery > > ... Sent ( > > <20140324135355.gc6...@vpn.mydomain.com> > > Queued mail for delivery) > > Closing connection to Smarhost.com > > >>> QUIT > > 221 2.0.0 CPSMTPM-cmt107.MyProvider.com Service closing transmission > > channel > > > > The test shows me that the problem is not on the MyProvider side. > > > > The sendmail.cf files on the two server are identical, except the names of > > the > > servers and some comments. > > > > The sendmail versions are different and the FreeBSD versions are different: > > MyServer: > > Sendmail Version 8.14.7 > > FreeBSD 10.0-STABLE > > > > MySecondServer: > > Sendmail Version 8.14.5 > > FreeBSD 9.0-RELEASE-p4 > > > > It is also important to note that above can only be observed for some > > e-mails, not all. Thus some mails will be sent from MyServer, some are not! > > > > If I make a tcpdump during the connection between sendmail and smarthost > > concerning s2ODs1hH016114, I got the following: > > > > 11:24:23.301300 IP MyServer.MyDomain.com.49165 > DNSMyProvider.domain: > > 32794+ [1au] MX? Smarhost.com. (43) > > 11:24:23.320078 IP DNSMyProvider.domain > MyServer.MyDomain.com.49165: > > 32794 1/1/1 CNAME CNameMyProvider. (125) > > 11:24:23.321592 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [S], seq 2245424203, win 65535, options [mss 1448,nop,wscale > > 6,sackOK,TS val 318826742 ecr 0], length 0 > > 11:24:23.339171 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [S.], seq 2238169153, ack 2245424204, win 8192, options [mss 1452], > > length 0 > > 11:24:23.339221 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [.], ack 1, win 65535, length 0 > > 11:24:23.355143 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 1:84, ack 1, win 65160, length 83 > > 11:24:23.355254 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [P.], seq 1:24, ack 84, win 65535, length 23 > > 11:24:23.370795 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 84:276, ack 24, win 65137, length 192 > > 11:24:23.371025 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [P.], seq 24:76, ack 276, win 65535, length 52 > > 11:24:23.392751 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 276:326, ack 76, win 65085, length 50 > > 11:24:23.393010 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [P.], seq 76:119, ack 326, win 65535, length 43 > > 11:24:23.414297 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 326:364, ack 119, win 65042, length 38 > > 11:24:23.520345 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [.], ack 364, win 65535, length 0 > > 11:24:23.535218 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > > Flags [P.], seq 364:410, ack 119, win 65042, length 46 > > 11:24:23.769098 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > > Flags [.], seq 119:1567, ack 410, win 65535, length 1448 > > 11:
Re: sendmail Broken Pipe Error
Willy Offermans wrote this message on Tue, Mar 25, 2014 at 11:39 +0100: > I found the following command, that generates some more informative output, > I hope. > > root@MyServer:/home/MyName # sendmail -q -v > > Running /var/spool/mqueue/s2ODs1hH016114 (sequence 1 of 2) > ... Connecting to Smarhost.com via relay... > 220 CPSMTPM-CMT109.MyProvider.com MyProvider.com Tue, 25 Mar 2014 10:45:21 > +0100 > >>> EHLO MyServer.MyDomain.com > 250-CPSMTPM-CMT109.MyProvider.com Hello [77.170.60.162] > 250-TURN > 250-SIZE 15744000 > 250-ETRN > 250-PIPELINING > 250-DSN > 250-ENHANCEDSTATUSCODES > 250-8bitmime > 250-CHUNKING > 250-VRFY > 250 OK > >>> MAIL From: SIZE=1254972 > 250 2.1.0 MyName@MyRewrittenDomainNameSender OK > >>> RCPT To: > >>> DATA > 250 2.1.5 MyFriend@MyFriendsDomainName > 354 Start mail input; end with . > timeout writing message to Smarhost.com: Broken pipe > ... Deferred > > If I copy the *s2ODs1hH016114 files to MySecondServer and run > sendmail -q -v once more, I got the following: > > Running /var/spool/mqueue/s2ODs1hH016114 (sequence 1 of 1) > ... Connecting to Smarhost.com via relay... > 220 CPSMTPM-cmt107.MyProvider.com MyProvider.com Tue, 25 Mar 2014 10:57:56 > +0100 > >>> EHLO MySecondServer.MyRewrittenDomainName > 250-CPSMTPM-cmt107.MyProvider.com Hello [77.170.60.162] > 250-TURN > 250-SIZE 15744000 > 250-ETRN > 250-PIPELINING > 250-DSN > 250-ENHANCEDSTATUSCODES > 250-8bitmime > 250-CHUNKING > 250-VRFY > 250 OK > >>> MAIL From: SIZE=1254972 > 250 2.1.0 MyName@MyRewrittenDomainNameSender OK > >>> RCPT To: > >>> DATA > 250 2.1.5 MyFriend@MyFriendsDomainName > 354 Start mail input; end with . > >>> . > 250 2.6.0 <20140324135355.gc6...@vpn.mydomain.com> Queued mail for delivery > ... Sent ( > <20140324135355.gc6...@vpn.mydomain.com> > Queued mail for delivery) > Closing connection to Smarhost.com > >>> QUIT > 221 2.0.0 CPSMTPM-cmt107.MyProvider.com Service closing transmission > channel > > The test shows me that the problem is not on the MyProvider side. > > The sendmail.cf files on the two server are identical, except the names of > the > servers and some comments. > > The sendmail versions are different and the FreeBSD versions are different: > MyServer: > Sendmail Version 8.14.7 > FreeBSD 10.0-STABLE > > MySecondServer: > Sendmail Version 8.14.5 > FreeBSD 9.0-RELEASE-p4 > > It is also important to note that above can only be observed for some > e-mails, not all. Thus some mails will be sent from MyServer, some are not! > > If I make a tcpdump during the connection between sendmail and smarthost > concerning s2ODs1hH016114, I got the following: > > 11:24:23.301300 IP MyServer.MyDomain.com.49165 > DNSMyProvider.domain: 32794+ > [1au] MX? Smarhost.com. (43) > 11:24:23.320078 IP DNSMyProvider.domain > MyServer.MyDomain.com.49165: 32794 > 1/1/1 CNAME CNameMyProvider. (125) > 11:24:23.321592 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > Flags [S], seq 2245424203, win 65535, options [mss 1448,nop,wscale > 6,sackOK,TS val 318826742 ecr 0], length 0 > 11:24:23.339171 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > Flags [S.], seq 2238169153, ack 2245424204, win 8192, options [mss 1452], > length 0 > 11:24:23.339221 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > Flags [.], ack 1, win 65535, length 0 > 11:24:23.355143 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > Flags [P.], seq 1:84, ack 1, win 65160, length 83 > 11:24:23.355254 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > Flags [P.], seq 1:24, ack 84, win 65535, length 23 > 11:24:23.370795 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > Flags [P.], seq 84:276, ack 24, win 65137, length 192 > 11:24:23.371025 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > Flags [P.], seq 24:76, ack 276, win 65535, length 52 > 11:24:23.392751 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > Flags [P.], seq 276:326, ack 76, win 65085, length 50 > 11:24:23.393010 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > Flags [P.], seq 76:119, ack 326, win 65535, length 43 > 11:24:23.414297 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > Flags [P.], seq 326:364, ack 119, win 65042, length 38 > 11:24:23.520345 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > Flags [.], ack 364, win 65535, length 0 > 11:24:23.535218 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > Flags [P.], seq 364:410, ack 119, win 65042, length 46 > 11:24:23.769098 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > Flags [.], seq 119:1567, ack 410, win 65535, length 1448 > 11:24:23.769108 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp: > Flags [.], seq 119:1567, ack 410, win 65535, length 1448 > 11:24:23.811918 IP ActualSmarthost.com.smtp > MyServer.MyDomain.com.51274: > Flags [.], ack 1567, win 65160, length 0 > 11:24:24.077092 IP MyServer.MyDomain.com.51274 > ActualSmarthost.com.smtp:
Re: sendmail Broken Pipe Error
Dear Claus and FreeBSD friends, On Mon, Mar 24, 2014 at 12:22:30PM -0700, Claus Assmann wrote: > On Mon, Mar 24, 2014, Willy Offermans wrote: > > > Mar 24 14:16:01 MyServer sm-mta[11725]: s2ODCWT4011717: SYSERR(root): > > timeout writing message to MyProvider.com: Broken pipe > > Mar 24 14:16:01 MyServer sm-mta[11725]: s2ODCWT4011717: > > to=, delay=00:03:29, xdelay=00:03:26, > > mailer=relay, pri=1284849, relay=MyProvider.com [XXX.XXX.XXX.XXX], > > dsn=4.0.0, stat=Deferred > > > Since there is a timeout error, I like to know what sendmail is writing to > > MyProvider.com > > The mail message (DATA) -- as the log entry states. > > > Is there a way to debug sendmail to disclose the message written to > > MyProvider.com and the response from MyProvider.com. I'm pretty sure that > > There's no response... > check out s2ODCWT4011717 in your mail queue. > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" This sounds very reasonable, but for your better understanding the following: My old FreeBSD server is still running as well. This server runs sendmail 8.14.5 and does not show these errors. So I'm puzzled what the problem might be. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: sendmail Broken Pipe Error
On Mon, Mar 24, 2014 at 02:36:34PM +0100, Willy Offermans wrote: > ... > Since there is a timeout error, I like to know what sendmail is writing to > MyProvider.com > > Is there a way to debug sendmail to disclose the message written to > MyProvider.com and the response from MyProvider.com. I'm pretty sure that > there lays the solution to my problem. > > Any help is highly appreciated. > ... When acting as an (E)SMTP client, sendmail queues outbound messages -- by default, in /var/spool/mqueue/ (ref. "QUEUE_DIR" in the configuration). When I look there, I see files with names like "df..." and "qf..." (where "..." represents a string of numeric & mixed-case alphabetic charcaters). These are in pairs: the "df*" files contain the data to be transmitted via (E)SMTP, while the "qf*" files contain meta-data about the message (including reasons the message didn't get sent yet). The Sendmail Installation and Operation Guide (a copy of which may be found in src/contrib/sendmail/doc/op/op.me) has considerable detail on these files -- search for "qf" (as a suggestion). Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpoWstL062GY.pgp Description: PGP signature
Re: sendmail Broken Pipe Error
Willy Offermans wrote this message on Mon, Mar 24, 2014 at 14:36 +0100: > Dear FreeBSD friends, > > Lately I have setup a new FreeBSD server with 10.0-STABLE. Most of it went > smoothly. However I have an issue with sendmail. Some of the mails can be > sent out correctly, some of them stay in /var/spool/mqueue/. The provided > error messages are in the latter case: > > Mar 24 14:16:01 MyServer sm-mta[11725]: s2ODCWT4011717: SYSERR(root): timeout > writing message to MyProvider.com: Broken pipe > Mar 24 14:16:01 MyServer sm-mta[11725]: s2ODCWT4011717: > to=, delay=00:03:29, xdelay=00:03:26, mailer=relay, > pri=1284849, relay=MyProvider.com [XXX.XXX.XXX.XXX], dsn=4.0.0, stat=Deferred > > I'm using Version 8.14.7 > All was fine when I was using Version 8.14.5. > > Since there is a timeout error, I like to know what sendmail is writing to > MyProvider.com > > Is there a way to debug sendmail to disclose the message written to > MyProvider.com and the response from MyProvider.com. I'm pretty sure that > there lays the solution to my problem. > > Any help is highly appreciated. You could use tcpflow to capture the flows for myprovider.com and look at them... Though you are seeing a timeout, so it sounds like myprovider.com isn't reading your message in a timely fasion.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: sendmail Broken Pipe Error
On Mon, Mar 24, 2014, Willy Offermans wrote: > Mar 24 14:16:01 MyServer sm-mta[11725]: s2ODCWT4011717: SYSERR(root): timeout > writing message to MyProvider.com: Broken pipe > Mar 24 14:16:01 MyServer sm-mta[11725]: s2ODCWT4011717: > to=, delay=00:03:29, xdelay=00:03:26, mailer=relay, > pri=1284849, relay=MyProvider.com [XXX.XXX.XXX.XXX], dsn=4.0.0, stat=Deferred > Since there is a timeout error, I like to know what sendmail is writing to > MyProvider.com The mail message (DATA) -- as the log entry states. > Is there a way to debug sendmail to disclose the message written to > MyProvider.com and the response from MyProvider.com. I'm pretty sure that There's no response... check out s2ODCWT4011717 in your mail queue. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
