[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Oinkage in the 'post' command SSL handling...

From: Valdis . Kletnieks
Subject: Re: [Nmh-workers] Oinkage in the 'post' command SSL handling...
Date: Tue, 03 Jan 2012 15:57:55 -0500

On Tue, 03 Jan 2012 15:20:38 EST, Ken Hornstein said:

> Could you try out commit 096c67e (just pushed to master) and see if that
> solves your problem?  I was able to reproduce your problem here with a
> test file and this change made it work much better.

Sent out a mail with a 1.5M jpg attached, and tcpdump says:

15:42:18.898205 IP > Flags 
[FP.], seq 18290:18327, ack 1650786, win 840, options [nop,nop,TS val 
2295033105 ecr 13160930], length 37

So about 1.6M on the wire.

Testing with a copy of the original 800K 20-bytes-per-line data file:

15:48:59.835075 IP > Flags 
[FP.], seq 18290:18327, ack 373124, win 556, options [nop,nop,TS val 2295133338 
ecr 13561860], length 37

373K on the wire - must have gotten some compression along the way?  The full
800K made it through, complete with a still-valid PGP signature, so no data

Fix looks good, thanks.

Attachment: pgp5VKfX1bwGV.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]