[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amavis-tech
Subject:    Re: new server/client protocol, draft 0.01
From:       Tapani Tarvainen <tt () it ! jyu ! fi>
Date:       2003-05-03 18:58:21
[Download RAW message or body]

On Fri, May 02, 2003 at 04:18:38PM +0300, Tapani Tarvainen wrote:

>    321 HEADER string\r\n

One problem here: how should continuation lines be handled?
Possibilities:

(1) Fold them into one line (e.g., just remove internal newlines).
There should be no useful information lost, and since this is just
info for amavisd it would not affect the original message anyway.
However, at least in theory it would be useful to know how header
lines were originally split (some virus might depend on that).

(2) Send continuation lines separately and let amavisd take care
of putting them back together. This would break the natural
mapping between milter callbacks and messages to the server,
and it would be somewhat messy to handle on the server side.

(3) Replace internal newlines with something else and let
amavisd convert them back. This should work and be easy to
handle but it's rather too ugly to my taste.

(4) Use a different terminator for HEADER (e.g., double it:
\r\n\r\n cannot occur within headers, or use a different
message number & keyword, or something). This should also work
but complicates message handling in server side - ugly.

(5) Use a different terminator scheme in general (for example
the suggested lenght-of-message first, or double \r\n\r\n for
all messages - although BODY still needs special treatment).

I don't really like any of those. :-(

Opinions, suggestions?

-- 
Tapani Tarvainen


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
AMaViS-tech mailing list
AMaViS-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-tech
[prev in list] [next in list] [prev in thread] [next in thread]