Having a flag on the messageblks is great for joins (see previous post); but
if there is the possibility of multiple header blocks that may pose a
problem.

However -- you could set the value to "1" for 1 header block, "2" for
multiple header blocks (or qty, etc) -- and then if when you do the simple
join:

E.g.    select messages.*, messages.isheader, messageblks.messageblk as
headers from
messages,messageblks where
messages.message_idnr=messageblks.messageblks_idnr and
messageblks.isheader=1 order by <SORT KEY> 

If the 'isheader' flag returned 1, then *just for that row* the client
applications could do a second pass where they looked up all the header
fields.

/Mark

PS. Happy with bouncing messages with long headers though myself -- bound to
be spammers...



> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Stone
> Sent: Friday, 19 March 2004 7:53 a.m.
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] dbmail 2.0 rc4
> 
> For the uber-large headers problem, would you rather bounce 
> the message or add
> the is_header column to the messageblks table and allow for 
> multiple header
> blocks? Also, since we currently pass the header around as a 
> single char
> array, how would you propose to throttle the memory usage so 
> that someone
> cannot DoS the server with garbage jigabyte headers?
> 
> Aaron
> 
> 
> Ilja Booij <[EMAIL PROTECTED]> said:
> 
> > Hi,
> > 
> > I'd like to release rc4 tomorrow. Is anybody aware of any 
> showstoppers 
> > we have to fix before releasing rc4 other than the ones 
> I'll mention below?
> > 
> > * Headers > 512kB don't work. Messages get dropped.
> > 
> > * code indentation: run indent -i8 -kr (unless anybody 
> wants something 
> > completely different :) )
> > 
> > Ilja
> > 
> > 
> > _______________________________________________
> > Dbmail-dev mailing list
> > [email protected]
> > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> > 
> 
> 
> 
> -- 
> 
> 
> 
> _______________________________________________
> Dbmail-dev mailing list
> [email protected]
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> 

Reply via email to