[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Size accumulation in smtpserver?

On Tue, Feb 29, 2000 at 03:24:38PM +0000, Alexey Lobanov wrote:
> Hello.
> > For many years :-) I can see the following problem: when big message  
> > is addressed to several recipients (multiple RCPT TO), and MAIL FROM 
> > contains proper SIZE tag, then message size is being accumilated. 
> > I.e., 1.5M message with two RCPT TO: is not accepted if 2M limit 
> 2.99.52
>     /* SS->sizeoptsum += SS->sizeoptval; */
>         SS->sizeoptsum = SS->sizeoptval;
> BUT WHY !!!!!!!!!???????

	Somebody spoke me around from accumulating message size for
	all recipients and blocking when the total sum exceeds maxsize.

	Reading the code arount that one, I can see that proper fix was not
	to block the message with  sizeoptsum,  but only when the sizeoptval
	is over maxsize.  The  sizeoptsum is to be compared against system
	available space.  (Thinking that all final UNIX-like mailboxes are
	stored into same partition/volume as where POSTOFFICE is.)

	Hmm... No, not even that is good rule.

	Ok, adding   "PARAM  sum-sizeoption-value"   -- which presence will
	accumulate sizeoptsum so that comparing its sum against  availspace
	will block message reception if total amount exceeds the space
	available in POSTOFFICE spool area.

	That won't make sense, unless each recipient is stored locally
	separately (in classic UNIX mailbox sense), and the spool area
	for them is same device as where  POSTOFFICE  area is.

	The default for this PARAM will be OFF.

> Alexey

/Matti Aarnio	<mea@nic.funet.fi>