Is the MTU-buffer-size mismatch in the SMTP client or the milter?
An upgrade to clamav-milter is being carried out tonight during scheduled
downtime so I will investigate at this time and post to the list
accordingly.
Dave Green
Wietse Venema:
Dave Green:
Can you do some tests with a recent version of Postfix's own stress
testing tool?
smtp-source -t bitbuc...@sigmasys.co.uk -l 5242880 -m 10 206.125.173.103
0m42.62s real0m0.02s user0m0.31s system
smtp-source -t bitbuc...@sigmasys.co.uk
On Mon, Mar 22, 2010 at 06:57:42AM -0400, Wietse Venema wrote:
Another possible test:
#ifconfig lo0 mtu 1500
That should decide any argument about write buffer sizes.
Has the OP considered turning off the clamav milter, and retesting?
--
Viktor.
P.S. Morgan Stanley is
Another possible test:
#ifconfig lo0 mtu 1500
That should decide any argument about write buffer sizes.
Was about to start with tcpdump, but changing the mtu resolves the issue
entirely, confirming your earlier thoughts. There is now no significant
delay for mail submitted with large
On Mon, Mar 22, 2010 at 07:05:32PM -0400, Wietse Venema wrote:
My sincerest of thanks for providing both a solution and information about
OpenBSD semantics of which I was not aware.
It's no different with Linux, Solaris, and so on.
The loopback MTU is usually large to improve
Dave Green:
Thanks kindly for your reply
There is no fundamental reason why pickup-cleanup is slower than
smtpd-cleanup (other than different receive_override_options
settings in master.cf).
However, it is possible that you're sending mail INTO Postfix at
a slower rate than
Dave Green:
Can you do some tests with a recent version of Postfix's own stress
testing tool?
smtp-source -t bitbuc...@sigmasys.co.uk -l 5242880 -m 10 206.125.173.103
0m42.62s real0m0.02s user0m0.31s system
smtp-source -t bitbuc...@sigmasys.co.uk -l 5242880 -m 10
