Re: [Exim] hole in message_size_limit? (was: verify = heade…

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Ron
CC: exim-users
Subject: Re: [Exim] hole in message_size_limit? (was: verify = header_sender ...)
On Tue, 20 Jul 2004, Ron wrote:

> Is a client that sends EHLO misbehaved if it ignores an advertised
> SIZE in the response?


Not really. The RFC says:

5.3 Messages larger than the declared size.

Once a server has agreed (via the extended MAIL command) to accept a
message of a particular size, it should not return a 552 reply code
after the transfer phase of the DATA command, unless the actual size
of the message transferred is greater than the declared message size.
A server may also choose to accept a message which is somewhat larger
than the declared message size.

A client is permitted to declare a message to be smaller than its
actual size. However, in this case, a successful (250) reply code is
no assurance that the server will accept the message or has
sufficient resources to do so. The server may reject such a message
after its DATA transfer.

> What currently happens if you hit the (presumed) hard limit of what
> exim can accept as DATA?


It swallows the rest, and gives a 5xx response when it finally gets the
terminating dot.

--
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book:    http://www.uit.co.uk/exim-book